Attachment #127875
Add tests for activation when message send/receive is denied patch 2016-11-09 19:41:46 UTC 11.79 KB no flags Details
Attachment #127876
Do not auto-activate services if we could not send a message patch 2016-11-09 19:43:31 UTC 15.44 KB no flags Details
Attachment #127877
Mediate auto-activation attempts through AppArmor patch 2016-11-09 19:45:04 UTC 10.35 KB no flags Details
Attachment #127878
Spec: document what auto-starting is, and recommend it patch 2016-11-09 19:45:23 UTC 3.31 KB no flags Details
Attachment #127879
Spec: document systemd activation patch 2016-11-09 19:45:38 UTC 2.32 KB no flags Details
Attachment #127880
Spec: document AppArmor mediation of auto-starting patch 2016-11-09 19:45:54 UTC 3.93 KB no flags Details
Attachment #127881
Add an integration test for AppArmor mediating activation patch 2016-11-09 19:46:48 UTC 20.52 KB no flags Details
Attachment #128111
Do not auto-activate services if we could not send a message patch 2016-11-21 21:21:00 UTC 15.51 KB no flags Details
Attachment #128112
Mediate auto-activation attempts through AppArmor patch 2016-11-21 21:21:49 UTC 9.95 KB no flags Details
Attachment #128113
Spec: document AppArmor mediation of auto-starting patch 2016-11-21 21:24:11 UTC 4.59 KB no flags Details
Attachment #128114
Add an integration test for AppArmor mediating activation patch 2016-11-21 21:25:43 UTC 21.12 KB no flags Details
Attachment #128115
Activation test: exercise what happens with nonexistent AppArmor labels patch 2016-11-21 21:27:31 UTC 5.37 KB no flags Details
Attachment #128142
Spec: document AppArmor mediation of auto-starting patch 2016-11-22 11:42:50 UTC 4.61 KB no flags Details
Attachment #128243
Don't test AppArmor mediation of activation if libapparmor < 2.10 patch 2016-11-28 15:50:59 UTC 3.29 KB no flags Details
Attachment #128259
activation test: don't crash if AppArmor is built but unavailable patch 2016-11-29 01:01:06 UTC 988 bytes no flags Details

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.