{"push_id":2691060654,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"728ab2177ca0d3cca2d4bc9c659e23b96127f424","before":"a5568d11324df34dc644911b3af243bbc1f3e05e","commits":[{"sha":"728ab2177ca0d3cca2d4bc9c659e23b96127f424","author":{"name":"Tom Gundersen","email":"7c8224529a7c718e876cb2496c973509fde1e50e@jklm.no"},"message":"apparmor: add skeleton support\n\nThe patches necessary for AppArmor support are not upstream in the kernel,\nso we also do not implement AppArmor support upstream in dbus-broker.\n\nHowever, this makes us respect the configuration to the extent possible.\nAppArmor can be in one of three modes:\n  * disable: we do nothing.\n  * enabled: if the kernel has AppArmor support we warn about the discrepancy and continue,\n             otherwise this is the same as 'disabled'.\n  * required: refuse to start (or stop on reload). This means the broker should not be running\n              unless AppArmor is being enforced.\n\nThe broker gains a new boolean argumnet, which unconditionally enables or disables AppArmor\n(so any conditionals on the kernel state should be checked in the launcher). For now this\nargument must be 'false'.\n\nSigned-off-by: Tom Gundersen <teg@jklm.no>","distinct":true,"url":"https://api.github.com/repos/bus1/dbus-broker/commits/728ab2177ca0d3cca2d4bc9c659e23b96127f424"}]}
{"actor":{"display_login":"teg"}}