Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #87837 > unrolled thread

Bug#872726: linux: apparmor doesn't use proper audit event ids (was: Re: reopening 872726, found 872726 in 6.12.30-1)

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#872726: linux: apparmor doesn't use proper audit event ids (was: Re: reopening 872726, found 872726 in 6.12.30-1) Salvatore Bonaccorso <carnil@debian.org> - 2025-06-03 23:10 +0200
    Processed: linux: apparmor doesn't use proper audit event ids  (was: Re: reopening 872726, found 872726 in 6.12.30-1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-03 23:10 +0200
    Bug#872726: linux: apparmor doesn't use proper audit event ids Salvatore Bonaccorso <carnil@debian.org> - 2025-06-14 21:50 +0200
    Bug#872726: linux: apparmor doesn't use proper audit event ids Ben Hutchings <ben@decadent.org.uk> - 2025-06-19 01:10 +0200
      Processed: Re: Bug#872726: linux: apparmor doesn't use proper  audit event ids "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-19 01:10 +0200

#87837 — Bug#872726: linux: apparmor doesn't use proper audit event ids (was: Re: reopening 872726, found 872726 in 6.12.30-1)

Control: tags -1 + moreinfo

Hi Laurent,

On Tue, Jun 03, 2025 at 05:14:12PM +0200, Laurent Bigonville wrote:
> reopen 872726 
> found 872726 6.12.30-1
> thanks

You reopened this very old issue. I see two aspects: We do not want to
have bugs opened forever if there is no chance of a respective
upstream change fixing the issue.

So with this in mind I think it would be great if you can try to
respin the convesation with upstream and see if there is movement on
this topic.

Otherwise, if there is no chance to implement this, we can mark it
wontfix (and so this time with an explanation ;-)) and then close and
archive it again.

In short: any chance you can try to reach out to upstream for a
current state on this topic and loop us back?

Regards,
Salvatore

[toc] | [next] | [standalone]

#87838 — Processed: linux: apparmor doesn't use proper audit event ids (was: Re: reopening 872726, found 872726 in 6.12.30-1)

Processing control commands:

> tags -1 + moreinfo
Bug #872726 [src:linux] linux: apparmor doesn't use proper audit event ids
Added tag(s) moreinfo.

-- 
872726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#87977 — Bug#872726: linux: apparmor doesn't use proper audit event ids

Hi John,

On Tue, Jun 03, 2025 at 02:36:49PM -0700, John Johansen wrote:
> On 6/3/25 14:03, Salvatore Bonaccorso wrote:
> > Control: tags -1 + moreinfo
> > 
> > Hi Laurent,
> > 
> > On Tue, Jun 03, 2025 at 05:14:12PM +0200, Laurent Bigonville wrote:
> > > reopen 872726
> > > found 872726 6.12.30-1
> > > thanks
> > 
> > You reopened this very old issue. I see two aspects: We do not want to
> > have bugs opened forever if there is no chance of a respective
> > upstream change fixing the issue.
> > 
> > So with this in mind I think it would be great if you can try to
> > respin the convesation with upstream and see if there is movement on
> > this topic.
> > 
> > Otherwise, if there is no chance to implement this, we can mark it
> > wontfix (and so this time with an explanation ;-)) and then close and
> > archive it again.
> > 
> > In short: any chance you can try to reach out to upstream for a
> > current state on this topic and loop us back?
> > 
> 
> Yes we can try, and honestly we need to try because this is going to
> become more problematic when we start stacking apparmor with selinux
> as more than just a demo.
> 
> We are about 20 patches away from the upstream kernel being able to
> do this. It will be a few weeks before we can even get to trying this
> but I will add it to the queue of tickets. Maybe I can even get some
> priority on it by tying it to our work to get apparmor available in
> fedora

Do you have a reference were we can point at this bug for following
the current status?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#88035 — Bug#872726: linux: apparmor doesn't use proper audit event ids

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 wontfix
Control: close -1

On Wed, 2025-06-18 at 18:12 +0200, Uwe Kleine-König wrote:
> Hello John,
> 
> On Tue, Jun 03, 2025 at 02:36:49PM -0700, John Johansen wrote:
[...]
> > We are about 20 patches away from the upstream kernel being able to
> > do this. It will be a few weeks before we can even get to trying this
> > but I will add it to the queue of tickets. Maybe I can even get some
> > priority on it by tying it to our work to get apparmor available in
> > fedora
> 
> I have the impression you work with upstream on that issue and while the
> bug report is correct there is no need for the Debian kernel team to get
> active, right? And the impact for Debian users is practically void until
> there is a kernel which allows to use apparmor and selinux together?
> 
> In that case I see little benefit to keep this bug open, given that the
> only action needed here is tracking when it's fixed upstream and add a
> bug closer to d/changelog then.
[...]

I agree this doesn't need to be kept open.

This change isn't going to happen in Debian unless and until it is
changed upstream.  And no-one on the Debian kernel team seems to be in a
position to help with the upstream change, unfortunately.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.

[toc] | [prev] | [next] | [standalone]

#88036 — Processed: Re: Bug#872726: linux: apparmor doesn't use proper audit event ids

Processing control commands:

> tag -1 wontfix
Bug #872726 [src:linux] linux: apparmor doesn't use proper audit event ids
Added tag(s) wontfix.
> close -1
Bug #872726 [src:linux] linux: apparmor doesn't use proper audit event ids
Marked Bug as done

-- 
872726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web