Before update:
ch...@lucid-test:~$ sudo aa-status
[sudo] password for chuck:
apparmor module is loaded.
5 profiles are loaded.
5 profiles are in enforce mode.
/sbin/dhclient3
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/mysqld
Before update:
ch...@lucid-test:~$ sudo aa-status
[sudo] password for chuck:
apparmor module is loaded.
5 profiles are loaded.
5 profiles are in enforce mode.
/sbin/dhclient3
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/mysqld
Gah...yes this fixes the problem.
chuck
--
[SRU] upstart script does not load AppArmor profile
https://bugs.launchpad.net/bugs/573206
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs
This bug was fixed in the package mysql-dfsg-5.1 - 5.1.41-3ubuntu12.1
---
mysql-dfsg-5.1 (5.1.41-3ubuntu12.1) lucid-proposed; urgency=low
* debian/mysql-server-5.1.mysql.upstart: load AppArmor profile since
mysql can start before AppArmor now (LP: #573206).
-- Kees Cook
Copied to maverick.
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Status: Confirmed = Fix Released
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
[SRU] upstart script does not load AppArmor profile
https://bugs.launchpad.net/bugs/573206
You
This bug was fixed in the package mysql-dfsg-5.1 - 5.1.41-3ubuntu12.1
---
mysql-dfsg-5.1 (5.1.41-3ubuntu12.1) lucid-proposed; urgency=low
* debian/mysql-server-5.1.mysql.upstart: load AppArmor profile since
mysql can start before AppArmor now (LP: #573206).
-- Kees Cook
Accepted mysql-dfsg-5.1 into lucid-proposed, the package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: mysql-dfsg-5.1
Two questions:
* Did we ship the same AppArmor rules in Karmic, or were they
changed/tightened during lucid? In the latter case, this would be quite
an extensive change, since Lucid hasn't been tested with AppArmor
protection for MySQL.
* Does the command actually enable AA protection for
Yes we did have AppArmor rules in karmic, and I aware of one change
during lucid to the apparmor rules. For the second question, I am not
sure.
chuck
--
[SRU] upstart script does not load AppArmor profile
https://bugs.launchpad.net/bugs/573206
You received this bug notification because you are
** Summary changed:
- upstart script does not load AppArmor profile
+ [SRU] upstart script does not load AppArmor profile
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Assignee: (unassigned) = Chuck Short (zulcss)
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Assignee: (unassigned) =
Statement of Impact:
Mysql that was shipped with lucid is currently running unconfined. This
is due apparmor has not been converted to upstart yet, however mysql
has.
How this bug has been addressed:
apparmor has been enabled in the init script. There should be no
regressions with this change.
11 matches
Mail list logo
