AppArmor dbus rejects messages from tasks that have exited

Bug #865605 reported by John Johansen on 2011-10-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Some tasks fire off messages at the end of their life that don't need a reply, and some times the task exit before dbus handles the message. Resulting in apparmor not being able to get the security context for the message sender.

John Johansen (jjohansen) wrote :

To fix this we need to update how the kernel is doing labeling for unix domain sockets, and then we can use getpeersec, and the labeling can be pulled from the socket instead of the task.

Jamie Strandboge (jdstrand) wrote :

Is this bug still relevant with the new IPC mediation?

Changed in apparmor:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for AppArmor because there has been no activity for 60 days.]

Changed in apparmor:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers