Control: tag -1 upstream
intrigeri wrote (16 Jun 2013 13:26:27 GMT) :
The action that should be taken now belongs upstream.
Flagging as such: IMO it is not Debian's responsibility to fix the
situation. AppArmor userspace has been depending on out-of-tree kernel
patches since at least Linux
Package: apparmor
Version: 2.7.103-4
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
reload apparmor rule.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Control: severity -1 wishlist
Control: retitle -1 Please support AppArmor network rules
Hi,
johnw wrote (16 Jun 2013 07:53:11 GMT) :
* What was the outcome of this action?
it show the waring message: network rules not enforced
* What outcome did you expect instead?
enforced
On 2013年06月16日 星期日 04:30 下午, intrigeri wrote:
You may want to nag AppArmor upstream so that they have the network
mediation code merged into mainline Linux :) Cheers,
Ok, I am not complain, but did you talk to debian kernel team/developer
this issue?
again, I am not complain, I just want know,
Hi,
johnw wrote (16 Jun 2013 12:31:29 GMT) :
On 2013年06月16日 星期日 04:30 下午, intrigeri wrote:
You may want to nag AppArmor upstream so that they have the network
mediation code merged into mainline Linux :) Cheers,
Ok, I am not complain, but did you talk to debian kernel team/developer
this
5 matches
Mail list logo
