path: root/INSTALL
diff options
authorGerald Combs <gerald@wireshark.org>2008-03-24 16:22:30 +0000
committerGerald Combs <gerald@wireshark.org>2008-03-24 16:22:30 +0000
commitec74de59578ab264ac59051448e8ad1001743c94 (patch)
tree2d988f190e9952759013b044a8cfabd277503fb9 /INSTALL
parent0a34df9b85813d28633e28a884c6539fa751eb76 (diff)
dumpcap.c: Fix a typo.
INSTALL: Add entries for libcap. svn path=/trunk/; revision=24722
Diffstat (limited to 'INSTALL')
1 files changed, 15 insertions, 1 deletions
diff --git a/INSTALL b/INSTALL
index 91771c6885..673ccdc43e 100644
@@ -142,10 +142,24 @@ README.win32 for those instructions.
flag installs dumpcap with setuid root permissions, which lets any user
on the system capture live traffic. If this is not desired, you can
restrict dumpcap's permissions so that only a single user or group can
- run it.
+ run it. This can be used in conjunction with --with-libcap described
+ below.
Running Wireshark or TShark as root is not recommended.
+ --without-libcap
+ By default, if 'configure' finds libcap (the POSIX capabilities
+ library) dumpcap will be built so that if it is installed setuid
+ root, it will attempt to retain CAP_NET_RAW and CAP_NET_ADMIN
+ before dropping root privileges. Use this option to disable this
+ behavior.
+ --with-libcap=DIR
+ Use this option to tell 'configure' where libcap is installed,
+ if it is installed in a non-standard location. Note that libcap
+ (the POSIX capabilities library, sans "p") and libpcap (the
+ packet capture library, avec "p") are two very different things.
If you choose to build a packet analyzer that can analyze
capture files but cannot capture packets on its own, but you