Bug#712050: linux: Apparmor not working with kernels after wheezy

2014-01-02 Thread intrigeri
Control: fixed -1 2.8.0-1 Hi, intrigeri wrote (15 Jun 2013 11:10:11 GMT) : > falconbird, please do consider using a *working* email address in > here. Otherwise, you're adding unnecessary noise to everyone > involved's mailbox. Thanks in advance :) Six months later, no info came in. I still cann

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-15 Thread intrigeri
intrigeri wrote (15 Jun 2013 11:02:26 GMT) : > (Hopefully the reporter's email does not bounce this time.) It still does: : host mx.lavabit.com[72.249.41.52] said: 550 This account has been locked as a result of inactivity. (in reply to RCPT TO command) falconbird, please do consid

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-15 Thread intrigeri
Control: retitle -1 aa-status does not show loaded profiles Control: severity -1 normal Control: tag -1 - moreinfo Control: block -1 by 712370 Hi, (Hopefully the reporter's email does not bounce this time.) > I will try to answer your questions. First, rules are working and AppArmor is > blocki

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-14 Thread falconbird
Package: apparmor Version: 2.7.103-4 Followup-For: Bug #712050 Dear Maintainer, I will try to answer your questions. First, rules are working and AppArmor is blocking access to files. But when I try to run aa-status, I got this root@debian-box:~# aa-status AppArmor available in kernel. AppArm

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-13 Thread Ben Hutchings
On Thu, Jun 13, 2013 at 12:29:26PM +0200, intrigeri wrote: > Hi Ben, > > First, thanks for reassigning. > > Ben Hutchings wrote (12 Jun 2013 17:42:19 GMT) : > > The 'wheezy' kernel has some backward compatibility code to support > > old AppArmor userland. This code will never be part of the upst

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-13 Thread intrigeri
Hi Ben, First, thanks for reassigning. Ben Hutchings wrote (12 Jun 2013 17:42:19 GMT) : > The 'wheezy' kernel has some backward compatibility code to support > old AppArmor userland. This code will never be part of the upstream > kernel and we don't want to keep supporting it. I'm surprised to

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-13 Thread intrigeri
Hi, falconbird wrote (12 Jun 2013 15:04:00 GMT) : > In Linux versions after stable wheezy, AppArmor is not working, as > it should be Thank you for reporting this issue to Debian. AppArmor has been continuously working fine for me on sid since Wheezy was released, so I am surprised. On boot, my

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-12 Thread Ben Hutchings
Control: reassign -1 apparmor Control: tag -1 jessie sid On Wed, Jun 12, 2013 at 10:04:00PM +0700, falconbird wrote: > Package: linux > Severity: important > > Dear maintainer, > > In Linux versions after stable wheezy, AppArmor is not working, as it should > be - rules are ok, > but it's impos

Bug#712050: linux: Apparmor not working with kernels after wheezy

2013-06-12 Thread falconbird
Package: linux Severity: important Dear maintainer, In Linux versions after stable wheezy, AppArmor is not working, as it should be - rules are ok, but it's impossible to control it - it complains that no compitablity patch is in kernel, or it not have enough rules. It's ok in Ubuntu, but the v