munkiadmin
munkiadmin copied to clipboard
Perms on imported pkgs 600
Makes it hard to actually deliver files when they're imported as 600... I don't think there's a pref to change that behavior, is there?
MunkiAdmin is not setting any permissions, it's just copying. Clearly a bug since I've heard this multiple times now.
Is your repo local (where in file system?) or on a network share? Are both the pkginfo and the installer item having this or just the installer? Any ACL's set on parent paths, or umask?
local(default /Users/Shared/repo), just pkg, no ACLs, tried root and subfolders, all dirs are 755. Any other way I can assist?
Thanks. I'll do some digging on this tomorrow. It's definitely possible to have a preference option to force specific permissions after copying.
I can't replicate this no matter how hard I try. What are the original file permissions on the package before you import?
I will add the permission change option and let you know when there's something to test.
Not sure if this is the exact same bug, but I get this is the munki repo is mounted over smb: https://dl.dropboxusercontent.com/u/21533299/Vids/munkiperms.mov Over AFP all is fine
Edit: scratch that, it's not specific to munkiadmin, it appears to be an smb umask thing. Happens in all other apps, too.
Old issue, but as it's still open...
Running into the same thing on SFTP. Issue is described here: https://superuser.com/a/1076092
My desired solution would be a preference setting for default permissions of files + directories, where we could set 644/755, 664/775, or whatever else we need in our environment, and then MunkiAdmin would explicitly set those permissions on any files or directories it's saving/creating.
You can set a custom permissions for the imported file by running defaults write com.hjuutilainen.MunkiAdmin installerItemFilePermissions "0644". This is a preference key that is not set at all by default so that MunkiAdmin will skip any permission change. When that preference key is set, MunkiAdmin will try to modify the permissions of the imported installer item.
Good to know! I should have clarified our issue is with all files, not just imported installers… also manifests, catalogs, pkginfo files, etc.