{"push_id":1722655042,"size":1,"distinct_size":1,"ref":"refs/heads/new_strict_mode","head":"635e6fbb2b40173ffdd0f73431192ba104a888b9","before":"202569081cc8e9c841d61c62d08af98a3dd0302c","commits":[{"sha":"635e6fbb2b40173ffdd0f73431192ba104a888b9","author":{"name":"Mitchell Grenier","email":"4fed19bd00b95db4df9134da1597f1eec2d5c53b@fb.com"},"message":"This is what osquery distributed signing could look like\n\nAdding the ability to sign queries only for particular hosts\n\nMitigating Query Reply Attacks\n\nAdded a new table to get information about strict mode.\nAdded a counter that is incremented everytime a successful query runs, this counter survives a restart.\nModified the test_http_server to be abled to create signatures dynamically given a public key and host UUID\n\nHelper Script + Counter Flag\n\nI added a script to make generation of protected_table_sig much easier, no more faffing about on the command line. I also included some test keys. I also added the ability to turn off counter mode if you so choose. This should always be on because it will only apply to ad-hoc queries, scheduled queries (when I get around to adding signing there) will not check counters.\n\nIn previous versions, osquery would warn you if it wasn't starting in strict mode, this has been changed in favour of a table that you can query against to know if it's enabled on a host.","distinct":true,"url":"https://api.github.com/repos/jedi22/osquery/commits/635e6fbb2b40173ffdd0f73431192ba104a888b9"}]}
{"actor":{"display_login":"jedi22"}}