Jeff Morriss
changed
bug 9516
| What |
Removed |
Added |
| Status |
INCOMPLETE
|
RESOLVED
|
| CC |
|
[email protected]
|
| Resolution |
---
|
WORKSFORME
|
Comment # 15
on bug 9516
from Jeff Morriss
As mentioned on the wireshark-dev thread of the same subject:
https://www.wireshark.org/lists/wireshark-dev/201312/msg00043.html
The RPM configuration does NOT (in general) follow what ./configure says
although we've been moving in that direction (see, for example, r53607).
To answer some specific questions:
(In reply to comment #13)
> Earlier I was using wireshark version 1.8.6(when it was working with NFS)
> but now for the first time I am using wireshark version 1.10.3 and getting
> the error. Has any change been done in 1.10.3(not working with NFS)
> regarding this?
Yes, in Wireshark 1.8.x dumpcap was not installed with capabilities (IIRC it
was just installed without any special properties so that you had to be very
naughty and run Wireshark as root in order to capture traffic). In Wireshark
1.10.x dumpcap is, by default, installed with "capabilities" to allow you to
run it without being root (and even without dumpcap running as root).
There are configuration options in the top of
packaging/rpm/SPECs/wireshark.spec.in which control how dumpcap is installed;
options include setcap, setuid-root, or no special permission. (Another option
relevant to the first two of those is whether dumpcap is only executable by
members of the group 'wireshark'.)
> Also I tried using ./configure --enable-setuid-install
> --disable-setcap-install, but that too didn't help.
>
> Then I thought of disabling dumpcap(./configure --enable-dumpcap=no) and
> after make rpm-package it was not there in ~vishnu.bhatt/install/bin but
> after rpm -ivhf wireshark.rpm
> I got the same error and dumpcap was present in ~vishnu.bhatt/install/bin
As mentioned above, the RPM packaging does not follow the ./configure output;
the "correct" (as of today) way of making changes is to edit the
wireshark.spec.in file.
> How is dumpcap getting created after running rpm -ivhf wireshark.rpm?
I'm not sure what you mean by this: dumpcap is in the RPM file and is copied to
the location specified in the RPM file with the permissions specified in the
RPM file.
(In reply to comment #14)
> One more thing to add is after make rpm-package, with 1.10.3, this time a
> new file wireshark-gnome.rpm is also getting created beside wireshark.rpm.
> Maybe it has something to do with capability error.
No, it doesn't. It's there to separate out the GUI from the core. In
Wireshark 1.11.x there's a new (Qt-based) GUI in a new RPM
(wireshark-qt-*.rpm).
Anyway I think this issue is basically resolved: you can make dumpcap not
setcap by editing wireshark.spec.in--at least until the RPM follows
./configure's output more (and I don't think we need a bug to track that).
You are receiving this mail because:
- You are watching all bug changes.