index bf8c2bf9341f377ce9476dee78b1012cba7c46c4..95ae19b39dc61f71e56a3949370dd46872203334 100644 (file)
--- a/README
+++ b/README
(which is strongly suggested), you won't be able to use the binaries as a
normal user, because you won't have the permission to open raw sockets.
(which is strongly suggested), you won't be able to use the binaries as a
normal user, because you won't have the permission to open raw sockets.
+ The “install” target will automatically try fix this, if it is run with UID~0
+ (as user root). When on Linux, the capabilities described below will be
+ added. On other UNIXes the traditional Set-UID method (also described below)
+ is used instead. The build system will not abort if this fails, because there
+ are file systems which do not support either method. Also, the Debian
+ packaging system and possibly other scenarios only act as if they were
+ running as root.
+
Linux
━━━━━
On Linux, the preferred method is to assign the required “capability” to the
Linux
━━━━━
On Linux, the preferred method is to assign the required “capability” to the
traditional set-UID root solution. If your system supports “saved set-UIDs”
(basically all systems do), the applications will drop the privileges during
initialization and only regain them when actually opening the socket(s).
traditional set-UID root solution. If your system supports “saved set-UIDs”
(basically all systems do), the applications will drop the privileges during
initialization and only regain them when actually opening the socket(s).
-
+
To set the set-UID bit, run (as user root):
# chown root: /opt/oping/bin/{,n}oping
To set the set-UID bit, run (as user root):
# chown root: /opt/oping/bin/{,n}oping