Ticket #26293 (assigned enhancement)
Wireshark ChmodBPF
| Reported by: | hsivank@… | Owned by: | ricci@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | opendarwin.org@…, jasperfrumau@…, fyodor.vassiley@…, bmourelo@…, ross@…, sam.kuper@…, jeff@… | |
| Port: | wireshark wireshark-devel |
Description
Wireshark ports does not place ChmodBPF files, to allow users with read access to the BPF devices to capture packets.
Attachments
Change History
comment:2 Changed 3 years ago by ricci@…
- Owner changed from macports-tickets@… to ricci@…
- Status changed from new to assigned
comment:4 Changed 3 years ago by hsivank@…
This new patch does not rely anymore on startup item script.
comment:5 follow-up: ↓ 6 Changed 3 years ago by ryandesign@…
Your patch removes the epoch line; the epoch line can never be removed from a portfile.
comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 3 years ago by hsivank@…
Replying to ryandesign@…:
Your patch removes the epoch line; the epoch line can never be removed from a portfile.
Sorry :/
This patch Portfile-wireshark-devel-r2.diff should be ok
comment:7 in reply to: ↑ 6 Changed 3 years ago by hsivank@…
Replying to hsivank@…:
Replying to ryandesign@…:
Your patch removes the epoch line; the epoch line can never be removed from a portfile.
Sorry :/
This patch Portfile-wireshark-devel-r2.diff should be ok
i'm mean this one Portfile-wireshark-devel-r3.diff
comment:9 Changed 3 years ago by ricci@…
Has this startup item been tested w/ launchd - in particular does launchd not try to keep respawning it after the shell script runs?
comment:10 Changed 3 years ago by hsivank@…
Portfile-wireshark-devel-r3.diff doesn't seems to work ... drawback to startup script mode Portfile-wireshark-devel-r4.diff
i use "startupitem.pidfile none" option. launchd should not keep respawning. Am i wrong ?
comment:14 Changed 2 years ago by ricci@…
The attached diff and file (place in port dir wireshark/files/) should work as well - the only problem I've got right now with it is that it violates mtree by making the link in /Library/LaunchDaemons. I'm not (immediately) seeing how to make a custom launchd script without doing so, if anyone can comment/provide a fix that'd be great.
Changed 2 years ago by ricci@…
- Attachment Portfile.withLaunchdChmodBPF.diff added
diff to wireshark Portfile to add a launchd-based Chmodbpf equivalent
Changed 2 years ago by ricci@…
- Attachment org.macports.wireshark-chmodbpf.plist added
launchd plist to do ChmodBPF equivalent at startup
comment:15 Changed 22 months ago by sam.kuper@…
I just installed Wireshark using Macports and encountered the problem that clicking Capture > Interfaces... gives a popup with the error message, "There are no interfaces on which a capture can be done."
Judging by http://anonsvn.wireshark.org/viewvc/trunk/packaging/macosx/ChmodBPF/README.macosx?revision=29831&view=markup , it seems that this problem is due to the ChmodBPF folder not having been placed in /Library/StartupItems/ directory by the MacPorts installation routine for Wireshark.
Am I right in thinking that this bug report is designed to address this problem? If so, is it safe, in the meantime - i.e. until the patches have been applied to Macports and the bug marked "Resolved" - to obtain a copy of the ChmodBPF directory somewhere else and copy it to the /Library/StartupItems/ folder manually, or does this risk preventing Macports from being able to update Wireshark (including the ChmodBPF folder) safely in the future?