Use cgroups / apparmor profile to authorize application connections to MIR
Bug #1327216 reported by
Benjamin Zeller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qtmir (Ubuntu) |
Triaged
|
Medium
|
Gerry Boland | ||
Bug Description
Currently only the primary PID is allowed to create a MIR connection, however
in the SDK launcher we have to start the application inside a gdbserver instance, which
will break the authorization and the application can not connect.
Related branches
| Changed in unity-mir: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Gerry Boland (gerboland) |
| Changed in qtmir: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Gerry Boland (gerboland) |
| no longer affects: | unity-mir |
| affects: | qtmir → qtmir (Ubuntu) |
To post a comment you must log in.
