Wireshark-users: Re: [Wireshark-users] Problem with permissions in ChmodBPF
From: kevin creason <ckevinj@xxxxxxxxx>
Date: Wed, 26 May 2010 13:53:34 -0500
Hi Robert-
First run these commands in a terminal to see what the permissions are currently.
Here are my results:
command to execute: ls -la /Library/StartupItems/
drwxr-xr-x 8 root wheel 272 Feb 3 10:56 .
drwxrwxr-t+ 63 root admin 2142 May 21 17:03 ..
drwxr-xr-x@ 5 root wheel 170 Dec 16 09:27 ChmodBPF
drwxr-xr-x 5 root wheel 170 Feb 3 11:11 NortonMissedTasks
drwxr-xr-x 8 root wheel 272 Feb 3 11:11 SymAutoProtect
dr-xr-xr-x 5 root wheel 170 Feb 3 11:11 SymProtector
drwxr-xr-x 5 root wheel 170 May 24 09:08 VirtualBox
drwxr-xr-x 4 root wheel 136 Jul 11 2008 globalSAN
second command: ls -l /Library/StartupItems/ChmodBPF/
-rwxr-xr-x 1 root wheel 954 Nov 24 2009 ChmodBPF
-rw-r--r--@ 1 root wheel 2551 Nov 24 2009 README.macosx
-rw-r--r--@ 1 root wheel 84 Nov 24 2009 StartupParameters.plist
As you can see everything in the StartupItems directory needs to be owned by root and group wheel.
To fix it I recommend becoming root and using the command line but you have to be careful and do it exactly as shown. Apparently somehow the directory for the other StartupItems were changed, common when not careful with typing or copy/paste.
To fix it--
become root in your terminal session. This is dangerous, be very careful and then exit out as soon as you are done.
command to become root: sudo su -
Once you are root change the working directory
command: cd /Library/StartupItems
Now the first question is does the permissions on your StartupItems directory match mine above? (This is the . permissions in my first example output).
If not, fix this one with command: chmod 755 .
And fix ownership with command: chown root:wheel .
Then proceed to do the same with each directory and file, replacing the "." in my examples with the file or directory listed until everything is rwxr-xr-x and owned by root:wheel
There are shortcuts to blast the permissions down the directory tree but that way lies danger for the Unix inexperienced.
don't forget to exit out of your root session, hit Ctl and 'd' key or type exit.
HTH
-Kevin
/*“ I am looking for a lot of men who have an infinite capacity to not know what can't be done. ” -- Henry Ford */
First run these commands in a terminal to see what the permissions are currently.
Here are my results:
command to execute: ls -la /Library/StartupItems/
drwxr-xr-x 8 root wheel 272 Feb 3 10:56 .
drwxrwxr-t+ 63 root admin 2142 May 21 17:03 ..
drwxr-xr-x@ 5 root wheel 170 Dec 16 09:27 ChmodBPF
drwxr-xr-x 5 root wheel 170 Feb 3 11:11 NortonMissedTasks
drwxr-xr-x 8 root wheel 272 Feb 3 11:11 SymAutoProtect
dr-xr-xr-x 5 root wheel 170 Feb 3 11:11 SymProtector
drwxr-xr-x 5 root wheel 170 May 24 09:08 VirtualBox
drwxr-xr-x 4 root wheel 136 Jul 11 2008 globalSAN
second command: ls -l /Library/StartupItems/ChmodBPF/
-rwxr-xr-x 1 root wheel 954 Nov 24 2009 ChmodBPF
-rw-r--r--@ 1 root wheel 2551 Nov 24 2009 README.macosx
-rw-r--r--@ 1 root wheel 84 Nov 24 2009 StartupParameters.plist
As you can see everything in the StartupItems directory needs to be owned by root and group wheel.
To fix it I recommend becoming root and using the command line but you have to be careful and do it exactly as shown. Apparently somehow the directory for the other StartupItems were changed, common when not careful with typing or copy/paste.
To fix it--
become root in your terminal session. This is dangerous, be very careful and then exit out as soon as you are done.
command to become root: sudo su -
Once you are root change the working directory
command: cd /Library/StartupItems
Now the first question is does the permissions on your StartupItems directory match mine above? (This is the . permissions in my first example output).
If not, fix this one with command: chmod 755 .
And fix ownership with command: chown root:wheel .
Then proceed to do the same with each directory and file, replacing the "." in my examples with the file or directory listed until everything is rwxr-xr-x and owned by root:wheel
There are shortcuts to blast the permissions down the directory tree but that way lies danger for the Unix inexperienced.
don't forget to exit out of your root session, hit Ctl and 'd' key or type exit.
HTH
-Kevin
/*“ I am looking for a lot of men who have an infinite capacity to not know what can't be done. ” -- Henry Ford */
On Wed, May 26, 2010 at 1:00 PM, Robert D. <210525p42015@xxxxxxxxxxxxxx> wrote:
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon, 24 May 2010 11:17:03 -0700
> They need to be owned by root, as do the containing directories.
> Make sure that /Library/StartupItems is owned by root:wheel,
I logged in as Root and just re-installed Wireshark
That did not help
So I changed permissions via 'Get Info' so that Wheel had R/W
things are actually a bit worse at atartup in either my account(ADmin)
or Root
"Items in the Startup Items folder (“/Library/StartupItems/”) have not
been started because the folder does not have the proper security settings.
“/Library/StartupItems/ChmodBPF” has not been started because it does
not have the proper security settings.
ChmodBPF shows _unknown R/w; staff R
I didn't touch this folder:
“/Library/StartupItems/ParallelsDesktopTransporter” has not been started
because it does not have the proper security settings.
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
- References:
- Re: [Wireshark-users] Problem with permissions in ChmodBPF
- From: Robert D.
- Re: [Wireshark-users] Problem with permissions in ChmodBPF
- Prev by Date: [Wireshark-users] yahoo messenger error capture
- Next by Date: Re: [Wireshark-users] Problem with permissions in ChmodBPF
- Previous by thread: Re: [Wireshark-users] Problem with permissions in ChmodBPF
- Next by thread: Re: [Wireshark-users] Problem with permissions in ChmodBPF
- Index(es):