We’ve been having bi-weekly office hours discussions with the osquery team and the rest of the community. With the release of 10.13, Apple made it impossible to query the state of the screensaver lock timeout, by moving the storage of the setting into the user’s LocalItems keychain. Now the preference table is (hopefully) less confusing to use, returns accurate results and takes into account preferences that are managed by a profile and those set by a user.Įven with this changes, the preferences table remains somewhat difficult to use. Reading the values from a plist file has also been separated into an independent table. The preferences table recommends that the user specify a WHERE clause, indicating the user and domain of the value. macOS preferences not checking the by-host level(part 2)Ī few changes were made as a result of these bug reports.macOS preferences not checking the by-host level.darwin preferences table not reading values enforced by profiles.Users of the table weren’t getting reliable results from the table. Querying preference values correctly requires deeper insights into a somewhat confusing system API. Many osquery examples featured queries like SELECT * from preferences, but the macOS APIs do not support enumerating preferences. Osquery has had the preferences table for a while, but the table had a few bugs and wasn’t well understood by its users. Over the course of the year I also became an active member of the osquery community, helping answer questions on Slack, and doing my best to document relevant issues.Īn interesting issue I had to deal with here was the lack of accuracy of the macOS preferences table. But my new job didn’t end my involvement with the MacAdmin community, which I’m grateful to be an active member/participant in. Joining Kolide was the end of my official tenure as a MacAdmin, as my new role was SRE. In the second half of 2016 I joined Kolide, a new startup focused on building tools that leverage the power of osquery. I wanted to take the end of the year as an opportunity to quickly summarize and reflect on the work I’ve done in the past 12 months. But I’ve written articles for other platforms and made quite a bit of contributions in my Github timeline. 2017 is coming to an end and unfortunately this blog has not seen many updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |