Bad (700) permissions after install
Bad (700) permissions after install
- Subject: Bad (700) permissions after install
- From: Russ <email@hidden>
- Date: Wed, 19 Nov 2008 16:42:44 -0800 (PST)
After installation, some users are incorrectly winding up with 700 permissions on some installed files, and they don't own them, and so aren't able to access their newly-installed files (these are some support files, docs and scripts, not the app itself). I'm not sure what these people are doing, but IT staffs and larger organizations seem more likely to have this problem.
I'm using PackageMaker 3.0.1 (172) This is a pretty simple packagemaking setup, I think --- pretty much defaults for everything. Easy Install Only, to System Volume.
When I build the folder that will be packaged, my setup script sets all the files and folders to be owned by root with group admin. It sets all the folders to permissions 775 and all files to 664. Dylibs to 775. I've checked that it is working OK.
The problem area is with files installed out into /Library/Application Support/blahblahblah
I think they are showing up in mode 700 owned by the installing staffer, locking everyone else out. I have to tell people to go reset the permissions on the offending files, which is a challenge for some people, then all is well. It's a support headache and general waste of time all around.
I thought the whole point of this is that after installing, the modes and ownership would reproduce what they were originally set to, which is why we are told to set them up carefully to start.
I used to use an earlier packagemaker and this didn't happen, it started either with the newer packagemaker or with Leopard, not sure which.
Thanks
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden