Issue #22830 has been updated by Gary Larizza.

So it sounds like we need to update the provider to interact with the Sqlite db 
in 10.9 - is that a plan, Clay?  I don't have 10.9 on anything yet, but I'll 
pull it down when I get a no-travel week and see if I can't play around with 
it.  Thanks for reporting!

----------------------------------------
Bug #22830: macauthorization provider is broken on 10.9 (mavericks)
https://projects.puppetlabs.com/issues/22830#change-98966

* Author: Clay Caviness
* Status: Unreviewed
* Priority: Normal
* Assignee: 
* Category: OSX
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
In OS X 10.9, `/etc/authorization` has been "deprecated"; as of the GM, the 
update will move `/etc/authorization` to `/etc/authorization.deprecated`.

There is now `/System/Library/Security/authorization.plist` but it seems to 
just be the defaults; changing a right with the `security authorizationdb` 
command doesn't change that file, but instead updates a sqlite db at 
`/var/db/auth.db`.

I did some quick testing, and just changing `AuthDB` in 
`puppet/provider/macauthorization/macauthorization.rb` isn't enough because the 
provider reads the plist to determine current state, but in the 10.9 world the 
current state is reflected in the `auth.db` file (or the output of `security 
authorizationdb` commands) so even when a right change is applied, puppet 
doesn't know.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to