Opened 14 years ago

Last modified 12 years ago

#26293 assigned enhancement

Wireshark ChmodBPF

Reported by: hsivank@… Owned by: ghosthound
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: opendarwin.org@…, jasperfrumau@…, fyodor.vassiley@…, bmourelo@…, overhacked (Ross Williams), 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 (6)

Portfile-wireshark-devel.diff (1.1 KB) - added by hsivank@… 14 years ago.
Portfile-wireshark-devel-r2.diff (816 bytes) - added by hsivank@… 14 years ago.
Portfile-wireshark-devel-r3.diff (805 bytes) - added by hsivank@… 14 years ago.
Portfile-wireshark-devel-r4.diff (1.1 KB) - added by hsivank@… 14 years ago.
Portfile.withLaunchdChmodBPF.diff (1.4 KB) - added by ghosthound 13 years ago.
diff to wireshark Portfile to add a launchd-based Chmodbpf equivalent
org.macports.wireshark-chmodbpf.plist (600 bytes) - added by ghosthound 13 years ago.
launchd plist to do ChmodBPF equivalent at startup

Download all attachments as: .zip

Change History (23)

comment:1 Changed 14 years ago by jmroot (Joshua Root)

Cc: opendarwin.org@… added

comment:2 Changed 14 years ago by ghosthound

Owner: changed from macports-tickets@… to ricci@…
Status: newassigned

comment:3 Changed 14 years ago by hsivank@…

attached a patch to fix this issue.

Changed 14 years ago by hsivank@…

comment:4 Changed 14 years ago by hsivank@…

This new patch does not rely anymore on startup item script.

Changed 14 years ago by hsivank@…

comment:5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Your patch removes the epoch line; the epoch line can never be removed from a portfile.

Changed 14 years ago by hsivank@…

comment:6 in reply to:  5 ; Changed 14 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 14 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:8 Changed 14 years ago by jasperfrumau@…

Cc: jasperfrumau@… added

Cc Me!

comment:9 Changed 14 years ago by ghosthound

Has this startup item been tested w/ launchd - in particular does launchd not try to keep respawning it after the shell script runs?

Changed 14 years ago by hsivank@…

comment:10 Changed 14 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:11 Changed 14 years ago by fyodor.vassiley@…

Cc: fyodor.vassiley@… added

Cc Me!

comment:12 Changed 14 years ago by bmourelo@…

Cc: bmourelo@… added

Cc Me!

comment:13 Changed 14 years ago by overhacked (Ross Williams)

Cc: ross@… added

Cc Me!

comment:14 Changed 13 years ago by ghosthound

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 13 years ago by ghosthound

diff to wireshark Portfile to add a launchd-based Chmodbpf equivalent

Changed 13 years ago by ghosthound

launchd plist to do ChmodBPF equivalent at startup

comment:15 Changed 13 years 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?

comment:16 Changed 13 years ago by sam.kuper@…

Cc: sam.kuper@… added

Cc Me!

comment:17 Changed 12 years ago by jeff@…

Cc: jeff@… added

Cc Me!

Note: See TracTickets for help on using tickets.