hippotat-setup-permissions(8)
π hippotat-setup-permissions π
okay bestie, welcome to hippotat-setup-permissions(8) β the little helper script that sorts out permissions so you don't have to run hippotat as root. it lives in section 8 of the manual, which is where all the sysadmin-y baddies hang out. π
β¨ NAME β¨
hippotat-setup-permissions β set up permissions for (non-root) use of hippotat π«Ά
β¨ SYNOPSYS β¨
(yes it's spelled that way in the original, we don't make the rules π )
hippotat-setup-permissions client
hippotat-setup-permissions server
hippotat-setup-permissions revoke
β¨ DESCRIPTION β¨
this script sets up β or revokes β the permissions that let hippotat and/or hippotatd actually run. it's giving gatekeeper energy. πͺβ¨
with server, the permissions the server needs get granted to the _hippotat user β or whatever other user you set with USER in /etc/default/hippotat.
with client, the permissions the client needs get granted to the _hippotat group β or whatever other group you set with GROUP in /etc/default/hippotat.
which permissions are actually required? that gets figured out from the hippotat config in /etc/hippotat. π§ (the hippotat or hippotatd program is run in a special mode just to go query that config. sneaky but iconic.)
and here's the part that's lowkey important: every single run revokes the permissions that previous invocations of this script granted to the configured user and/or group, if those permissions aren't needed anymore according to the config and the command line. so:
revokerevokes all the permissions πͺοΈclientandservereach revoke the other π
heads up bestie: only the permissions granted in the specific files that this script uses will be amended or revoked. it stays in its own lane, fr fr.
β¨ FILES β¨
/etc/userv/ipif-access/hippotatgives the right user or group the ability to make the virtual network interfaces, and to route traffic to them. created on both clients and servers. π¦/etc/authbind/byuid/uid gives the server the ability to bind to the configured ports and addresses. the uid is the one for the_hippotatuser, orUSER. created on servers. π₯/etc/userv/services.d/ipifenables theipifuserv service, which is itself controlled by/etc/userv/ipif-access/etc.
it will be made a symlink to /etc/userv/services-available/ipif. created on both clients and servers. it does not get removed during revocation, because other programs on the system might still need it. π
makes the symlink in .
(this is not undone by revoke, since that might disturb other services which are relying on it. so, yeah, it stays. periodt.)
/etc/default/hippotata shell script fragment sourced by the init script, byhippotat-setup-permissions, and by thehippotatdinit script. it can setUSERandGROUP(plus other variables that control the init script). π
π SEE ALSO π
(okay there's no SEE ALSO section in this one, but if you're here you're probably deep in the hippotat lore already, iykyk π)
π and that's the whole page! π thanks for reading, bestie, you ate. β¨
this cutie was brought to you by perl v5.40.1 and Hippotat β go off, hippotat-setup-permissions(8). ππΈ
π¦ where this page comes from
- debian trixie: hippotat-common 1.2.2
- ubuntu questing: hippotat-common 1.2.2
- ubuntu resolute: hippotat-common 1.2.3
- ubuntu stonking: hippotat-common 1.3.3build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms