AppArmor profile for sbin.dhclient3 should handle connman
Bug #333711 reported by
Mark Shuttleworth
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Connection Manager |
Fix Released
|
Medium
|
|||
| connman (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
| dhcp3 (Ubuntu) |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Bug Description
Connection manager ("connman") runs /sbin/dhclient using some specific actions and stores leases in different locations to NetworkManager. The new sbin.dhclient3 AppArmor profile prevents connman from acquiring an IP address and storing the lease, I include a patch to the profile which addresses that.
I'm not sure whether AppArmor configurations can extend one another. If so, it may be better to extend the dhclient profiles (/sbin/dhclient3, /sbin/dhclient-
Related branches
Revision history for this message
| Mark Shuttleworth (sabdfl) wrote | #1 |
| Changed in connman: | |
| status: | Unknown → Confirmed |
Revision history for this message
| Jamie Strandboge (jdstrand) wrote | #2 |
| Changed in dhcp3: | |
| assignee: | nobody → jdstrand |
| status: | New → In Progress |
Revision history for this message
| Jamie Strandboge (jdstrand) wrote | #3 |
| Changed in connman: | |
| status: | New → Won't Fix |
Revision history for this message
| Jamie Strandboge (jdstrand) wrote | #4 |
| Changed in dhcp3: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in dhcp3: | |
| status: | Fix Committed → Fix Released |
| Changed in connman: | |
| status: | Confirmed → Fix Released |
| Changed in connman: | |
| importance: | Unknown → Medium |
To post a comment you must log in.
At this time, there is not currently a way to extend a profile in this manner, as the calling program's (in this case /sbin/dhclient3) profile must know about the called program. Since the called program's (/usr/lib/
Thanks for the patch Mark. This should be uploaded shortly.