[apparmor] aa-logprof doesn't check if user is root

Hi, aa-logprof doesn't check if user is root Can someone add the verification please? just like aa-status and others Thanks! -- Best Regards, Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/ Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33 -- AppArmor mailing list

Re: [apparmor] Updating the Pidgin profile

Hi, thanks a lot, Seth and Simon, for the feedback. I realize I should have at least decrufted the profile a bit before sending it... sorry. I've taken all of your remarks into account, and removed a bunch of other lines that are better done via existing abstractions. I'm going to test the

[apparmor] Fwd: Bug#735470: Could be implemented centrally with a dpkg trigger instead of requiring every package shipping an apparmor file to use dh_apparmor

Hi, Didier Raboud suggested to use dpkg triggers for what dh_apparmor does, and is happy to give a hand. See the attached message. Thank you, Didier! What do the original dh_apparmor authors / Ubuntu folks think? Any reason Didier missed, that explains why this might not be that good an idea?

Re: [apparmor] Fwd: Bug#735470: Could be implemented centrally with a dpkg trigger instead of requiring every package shipping an apparmor file to use dh_apparmor

On 01/15/2014 01:14 PM, Seth Arnold wrote: On Wed, Jan 15, 2014 at 07:30:52PM +0100, intrigeri wrote: ... While updating src:cups to solve #735313, I went and took a look at dh-apparmor and I gained the convictions that this would be better implemented as part of a centralized dpkg-trigger

Re: [apparmor] aa-logprof doesn't check if user is root

Hello, Am Mittwoch, 15. Januar 2014 schrieb Aaron Lewis: aa-logprof doesn't check if user is root Can someone add the verification please? just like aa-status and others Well, not always ;-) aa-logprof doesn't always need root permissions (well, except for reloading the profiles). You can