This bug was fixed in the package apparmor - 2.8.0-0ubuntu28
---------------
apparmor (2.8.0-0ubuntu28) saucy; urgency=low
[ Tyler Hicks ]
* Move the aa-exec man page out of apparmor-utils into apparmor, since
aa-exec is now in apparmor
- debian/control: adjust Breaks/Replaces to use apparmor-utils
(<< 2.8.0-0ubuntu28)
- debian/apparmor.manpages: install the aa-exec man page
- debian/apparmor-utils.manpages: don't install the aa-exec man page
* debian/patches/0065-lp1220861.patch: Always NUL-terminate confinement
context strings returned from libapparmor (LP: #1220861)
* debian/patches/0066-lp1196880.patch: Don't assign mode pointer in
aa_getprocattr() if caller passed in NULL (LP: #1196880)
* debian/patches/0067-libapparmor-mode-strings-are-not-to-be-freed.patch:
Update man page and code comments to make it clear that freeing the *con
string returned from libapparmor's getcon functions also frees the *mode
string
* debian/patches/0068-libapparmor-mention-dbus-method-in-getcon-man.patch:
Document the D-Bus method, in the aa_getcon man page, that returns the
AppArmor task confinement string of a D-Bus connection
[ Jamie Strandboge ]
* debian/patches/0069-p11kit-abstraction.patch: p11-kit needs access to
/usr/share/p11-kit/modules
-- Jamie Strandboge <[email protected]> Tue, 10 Sep 2013 12:06:06 -0500
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220861
Title:
[REGRESSION] Task based libapparmor getcon functions don't always NUL-
terminate con strings properly
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1220861/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
