Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Something looks to be missing a dependency on python-configparser, based
on the failed import in the DpkgTerminalLog.txt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1764848, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1764848, so it is being marked as such. Please look
This is likely a duplicate of bug 1764848. Do you have python-ubuntu-
sso-client installed? Purging that package should hopefully let you work
around this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1764848, so it is being marked as such. Please look
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1732120
Title:
i can't login correctly..
Status in xorg package in
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
** Description changed:
To mitigate Spectre Variant 2, gcc needs to have retpoline support
(-mindirect-branch and -mfunction-return arguments on amd64 and i386).
Packages with this will go into the proposed pockets but need to be
published in the -security pockets for their respective r
** Summary changed:
- Add amd64/i386 support
+ Add amd64/i386 retpoline support
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1749261
Title:
Add amd64/i386 retpoline sup
Hi Raúl,
Sorry your profile slipped through the cracks. I'm going to open this
against the apparmor-profiles project, as that's likely a better
location for it.
Thanks!
** Also affects: apparmor-profiles
Importance: Undecided
Status: New
--
You received this bug notification because
Not sure whether the issue is a poor interaction with sd-pam and the
kernel or strictly a kernel issue.
Kernel timeout backtrace:
Sep 21 03:00:33 mainframe01 kernel: [292411.276266] Not tainted
4.15.0-1021-aws #21-Ubuntu
Sep 21 03:00:33 mainframe01 kernel: [292411.277931] "echo 0 >
/proc/
Looking at the dmesg log, it seems that the ubuntu image or device
you're installing from is corrupt:
[ 7412.559612] SQUASHFS error: zlib decompression failed, data probably
corrupt
[ 7412.559621] SQUASHFS error: squashfs_read_data failed to read block
0x3b6a61
** Information type changed
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Hi,
Thanks for preparing the debiff. However, this issue was addressed in
the interim in USN 3706-1 http://www.ubuntu.com/usn/usn-3706-1 (libjpeg-
turbo 1.3.0-0ubuntu2.1) for trusty.
Thanks again.
** Changed in: libjpeg-turbo (Ubuntu Trusty)
Status: Confirmed => Fix Released
** Changed i
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Public bug reported:
To mitigate Spectre Variant 2, gcc needs to have retpoline support
(-mindirect-branch and -mfunction-return arguments on amd64 and i386).
Packages with this will go into the proposed pockets but need to be
published in the -security pockets for their respective releases.
**
** Changed in: gcc-4.8 (Ubuntu)
Assignee: (unassigned) => Steve Beattie (sbeattie)
** Also affects: gcc-4.8 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: gcc-4.8 (Ubuntu Trusty)
Assignee: (unassigned) => Steve Beattie (sbeattie)
--
You received th
Fix committed upstream in http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3722.
Thanks!
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: apparmor
Status: New
Here's what I see on wily when making the following change:
--- /usr/bin/ubuntu-support-status 2015-10-08 22:07:36.0 -0700
+++ ./ubuntu-support-status 2015-10-23 14:49:44.092719697 -0700
@@ -48,7 +48,7 @@
# check the release date and show support information
# based on t
Note that on a trusty host I have where ubuntu-support-status doesn't
throw a traceback, the following files exist:
-rw-r--r-- 1 root root 64441 Oct 22 23:53
/var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_trusty-security_InRelease
-rw-r--r-- 1 root root 63459 Oct 1 23:28
/var/lib/apt/
Julian, sorry, but python-apt in get_release_filename_for_pkg()
hardcodes the string '_Release' to the path returned by the function
regardless of whether apt has downloaded a _Release or _InRelease file.
Here's a prototype patch I worked up to address that:
diff -Nru python-apt-1.0.1build1/apt/ut
Here it is in patch form. Note that it doesn't entirely address the
issue as passing the _InRelease file to python-apt's
get_release_date_from_release_file(path) function ends up handing the
file to pkg_apt.TagFile() which doesn't recognize the inline gpg signed
file as a RFC 2822 tag formatted fi
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1415515
Title:
ifup crashed with SIGSEGV in main()
Status in ifupdown p
** Also affects: libpng (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: libpng (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: libpng (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because
Packages to address the issue in lxc are currently building in the
ubuntu-security-proposed ppa: https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/ ; please test these when they complete to
verify that there aren't any additional regressions that have cropped up
in this update. T
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Public bug reported:
apport in Ubuntu 15.04 and 15.10 includes in bug reports a file
JournalErrors.txt that is the recorded output of the command 'journalctl
-b --priority warning'. Apport also makes a best effort attempt to
filter out information that bug reporters would like to keep private,
lik
Brian, I've subscribed you to LP: #1505626 which has an example of this.
Perhaps it affects vivid only?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1505852
Title:
apport
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Brian, I've also subscribed you to LP: #1504864, in which the
JournalErrors.txt contains some unfiltered zeitgeist entries as well as
an email address.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://
I've reproduced the issue with gcc-4.8 4.8.2-19ubuntu1 in trusty, and
verified that gcc-4.8 4.8.4-2ubuntu1~14.04 from trusty-proposed fixes
the issue. I've also run the test-gcc-security.py script from lp:qa-
regression-testing (which also has a test for this issue) and the
version in trusty-propos
This bug is a duplicate of bug 1317305, which has already been verified
successfully. Marking this bug as verified as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This was fixed in utopic in apparmor 2.8.98-0ubuntu2.
** Changed in: apparmor (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs
Here's a patch to fix this for trusty.
** Patch added: "php5-Zend_semaphore-lp1401084.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1401084/+attachment/4399530/+files/php5-Zend_semaphore-lp1401084.patch
** Description changed:
+ [impact]
+
+ This bug prevents the proper fun
This will be addressed in wily by apparmor 2.9.2-0ubuntu1. Attached is a
patch for trusty.
** Patch added: "dnsmasq-lxc_networking-lp1403468.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1403468/+attachment/4399532/+files/dnsmasq-lxc_networking-lp1403468.patch
** Description
This will be fixed in wily with apparmor 2.9.2-0ubuntu1. Attached is a
patch for this issue as part of a trusty SRU.
** Patch added: "profiles-texlive_font_generation-lp1010909.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1010909/+attachment/4399534/+files/profiles-texlive_fo
Attached is the changes as part of an SRU for trusty.
** Patch added: "apparmor_apport-lp1304447.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304447/+attachment/4399536/+files/apparmor_apport-lp1304447.patch
** Description changed:
+ [impact]
+
+ This bug prevents apport
This will be fixed in wily with apparmor 2.9.2-0ubuntu1. Attached is
patch to update the dovecot profiles for a trusty SRU.
** Patch added: "profiles-dovecot-updates-lp1296667.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1296667/+attachment/4399538/+files/profiles-dovecot-upd
Attached is a patch as a part of a trusty SRU.
** Patch added: "libapparmor-fix_memory_leaks-lp1340927.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1340927/+attachment/4399540/+files/libapparmor-fix_memory_leaks-lp1340927.patch
--
You received this bug notification because
Here is the patch to address the apparmor userspace component of this
bug as part of a trusty SRU. It's already been addressed in utopic and
later.
** Patch added: "tests-workaround_for_unix_socket_change-lp1425398.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+attachm
Attached is a patch for the debian/control changes to address this issue
as part of a trusty SRU. It should be fixed in wily in apparmor
2.9.2-0ubuntu1.
** Patch added: "apparmor_fix_python3_overwrite.patch"
https://bugs.launchpad.net/ubuntu/trusty/+source/apparmor/+bug/1373259/+attachment/439
Attached is a patch for trusty to address this issue as part of an SRU.
** Patch added: "profiles-adjust_X_for_lightdm-lp1339727.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1339727/+attachment/4399558/+files/profiles-adjust_X_for_lightdm-lp1339727.patch
** Description chang
This will have been addressed in wily in apparmor 2.9.2-0ubuntu1.
Attached is the (large) patch to update the python utils in trusty to
the 2.9.2 version as part of an SRU.
** Patch added: "utils-update_to_2.9.2.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1449769/+attachment
Here is the full debdiff for the trusty SRU, incorporating this fix and
several others.
** Patch added: "apparmor_2.8.95~2430-0ubuntu5.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1449769/+attachment/4399564/+files/apparmor_2.8.95%7E2430-0ubuntu5.2.debdiff
--
You receiv
** Description changed:
+ [impact]
+
+ This bug makes it difficult for trusty users to use the apparmor policy
+ utilities.
+
+ [steps to reproduce]
+
+ See below
+
+ [regression potential]
+
+ This issue is being addressed by updating the python utilities to the
+ version in apparmor 2.9.2 a
** Description changed:
- $ aa-logprof -f aadenylog
+ [impact]
+
+ This bug makes it difficult for trusty users to use the apparmor policy
+ utilities.
+
+ [steps to reproduce]
+
+ See below
+
+ [regression potential]
+
+ This issue is being addressed by updating the python utilities to the
** Description changed:
+ [impact]
+
+ This bug makes it difficult for trusty users to use the apparmor policy
+ utilities.
+
+ [steps to reproduce]
+
+ See below
+
+ [regression potential]
+
+ This issue is being addressed by updating the python utilities to the
+ version in apparmor 2.9.2 a
** Description changed:
+ [impact]
+
+ This bug makes it difficult for trusty users to use the apparmor policy
+ utilities.
+
+ [steps to reproduce]
+
+ See below
+
+ [regression potential]
+
+ This issue is being addressed by updating the python utilities to the
+ version in apparmor 2.9.2 a
** Description changed:
+ [impact]
+
+ This bug prevents users with mount points that contain non-ascii UTF_8
characters in their names from easily seeing the status of their apparmor
policy.
+
+ [steps to reproduce]
+
+ 1) create mount point with non-ascii characters in it
+ 2) run aa-statu
** Description changed:
[impact]
Leading up to the release of 14.04, we decided to pull in a pre-release
version of the python utils, because we did not want to continue
supporting the out of date perl tools for the 5 years of the 14.04
release support lifetime. There were a number of
Seyong Kim, the plan is to address this in trusty via the SRU for the
apparmor utilities (and other things) described in bug 1449769.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.n
For the apparmor trusty SRU, I reproduced the failure with the source
for apparmor 2.8.95~2430-0ubuntu5.1 from trusty-updates with a hardware
enablement kernel and confirmed that apparmor 2.8.95~2430-0ubuntu5.2
addresses the issue. I also verified that the rest of the apparmor
regression tests pass
** Changed in: apparmor (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1378095
Title:
aa-complain traceback when
My apologies, I neglected to include this bug report in the changelog
for my apparmor trusty SRU. It has ben accepted into trusty-proposed and
is available at
https://launchpad.net/ubuntu/+source/apparmor/2.8.95~2430-0ubuntu5.2 as
well as from the trusty-proposed repository. See
https://wiki.ubunt
agent 8131, apparmor 2.9.2-0ubuntu1 just landed in wily and contains a
fix for this that attempts to only apply the transformation for file
based events, specifically in http://bazaar.launchpad.net/~apparmor-
dev/apparmor/2.9/revision/2905 , so you should no longer see this in
wily.
Also, this ver
Thanks, Brad. Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1304447
Title:
apport-bug crashing on server ins
I have reproduced this issue with apparmor 2.8.95~2430-0ubuntu5.1 from
trusty-updates, and have verified that apparmor 2.8.95~2430-0ubuntu5.2
fixes the issue. Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touc
I have reproduced the traceback with apparmor 2.8.95~2430-0ubuntu5.1
from trusty-updates, and can confirm that apparmor
2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem. Marking
verification-done.
** Tags added: aa-tools verification-done
--
You received this bug notification becaus
I have reproduced the traceback when profiling empathy with apparmor
2.8.95~2430-0ubuntu5.1 from trusty-updates, and can confirm that
apparmor 2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem.
Marking verification-done.
--
You received this bug notification because you are a member o
I have reproduced the traceback when profiling empathy with apparmor
2.8.95~2430-0ubuntu5.1 from trusty-updates, and can confirm that
apparmor 2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem.
Marking verification-done.
** Tags added: verification-done
--
You received this bug notif
Bah, my apologies, posted to the wrong bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1319829
Title:
aa-genprof will crash when select scan on Ubuntu 14.04 se
I have reproduced the failures on generating fonts with evince on a dvi
file and apparmor 2.8.95~2430-0ubuntu5.1 and can confirm that apparmor
2.8.95~2430-0ubuntu5.2 addresses the issue. Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you
I reproduced the memory leaks with libapparmor from apparmor
2.8.95~2430-0ubuntu5.1 from trusty-updates, and verified that
libapparmor from apparmor 2.8.95~2430-0ubuntu5.2 in trusty-proposed
fixes the issue. I did this by running valgrind on aa-notify against
each version of the library after havin
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1458148
Title:
package python-apt 0.9.3.11 failed to install/
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Bah, sorry about that. Thanks for taking the time to report this bug and
helping to make Ubuntu better. We appreciate the difficulties you are
facing, but this appears to be a "regular" (non-security) bug. I have
unmarked it as a security issue since this bug does not show evidence of
allowing att
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
I have reproduced the traceback with aa-status from apparmor
2.8.95~2430-0ubuntu5.1 in trusty-updates, and have verified that the
version in of apparmor in trusty-proposed, 2.8.95~2430-0ubuntu5.2, fixes
the issue.
** Tags added: verification-done
--
You received this bug notification because you
I was able to reproduce the issue with the version of apparmor-utils and
python-apparmor from trusty-updates, 2.8.95~2430-0ubuntu5.1, and can
confirm that the version of each in trusty-proposed,
2.8.95~2430-0ubuntu5.2, fixes the issue. Marking verification-done.
** Tags added: verification-done
-
I was able to reproduce the issue with the version of apparmor-utils and
python3-apparmor from trusty-updates, 2.8.95~2430-0ubuntu5.1, and can
confirm that the version of each in trusty-proposed,
2.8.95~2430-0ubuntu5.2, fixes the issue. Marking verification-done.
** Tags added: verification-done
I managed to reproduce this rejection after setting user-authority-in-
system-dir=true in lightdm.conf with apparmor 2.8.95~2430-0ubuntu5.1
from trusty-updates. I verified that with apparmor
2.8.95~2430-0ubuntu5.2 in trusty-proposed, the rejection on the
Xauthority file no longer appears. Marking v
I have reproduced the issue with apparmor 2.8.95~2430-0ubuntu5.1 from
trusty-updates, and can confirm that the version of apparmor in trusty-
proposed, 2.8.95~2430-0ubuntu5.2, fixes the issue with the Zend
semaphore file accesses for php scripts. Marking verification-done.
** Tags added: verificat
I was able to reproduce this by installing apparmor and appamror-utils
from https://launchpad.net/ubuntu/+source/apparmor/2.8.0-0ubuntu11 and
then upgrading to the version in trusty-updates, 2.8.95~2430-0ubuntu5.1.
I then verified that upgrading to 2.8.95~2430-0ubuntu5.2 in trusty-
proposed succeed
** Changed in: apparmor
Milestone: None => 2.10
** Changed in: apparmor
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/14134
I've reproduced the issue with the dnsmasq profile from apparmor-
profiles 2.8.95~2430-0ubuntu5.1 in trusty-updates, and can confirm that
the version of the dnsmasq profile in apparmor-profiles
2.8.95~2430-0ubuntu5.2 in trusty-proposed fixes the issue. Marking
verification-done.
** Tags added: ver
I have gone through and verified each of the individual linked bug
reports are fixed in the version of apparmor-utils/python3-apparmor in
trusty-proposed. I've also gone through and ran the lp:qa-regression-
testing test-apparmor.py script against the version in trusty-proposed
on both i386 and amd
Unfortunately, while preparing the fix for this, I did not take into
account that the debian/apparmor-profiles.install file needed to be
updated to take the additional missing profiles into account. Marking
verification-failed.
However, failing to install the additional dovecot profiles does not
c
** Changed in: apparmor (Ubuntu Trusty)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bu
** Also affects: apparmor/2.9
Importance: Undecided
Status: New
** Changed in: apparmor/2.9
Status: New => Fix Committed
** Changed in: apparmor/2.9
Importance: Undecided => Low
** Changed in: apparmor/2.9
Milestone: None => 2.9.3
** Changed in: apparmor
Milestone: N
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
The dovecot profiles were addressed in apparmor 2.9.2 or earlier,
closing that portion of this bug.
** Changed in: apparmor
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu
*** This bug is a duplicate of bug 1466768 ***
https://bugs.launchpad.net/bugs/1466768
The traceback from this is:
Traceback (most recent call last):
File "/usr/sbin/aa-status", line 194, in
commands[cmd]()
File "/usr/sbin/aa-status", line 17, in cmd_enabled
if get_profiles() ==
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Public bug reported:
libapparmor is missing the following manpages from upstream:
aa_query_label.2
aa_features.3
aa_kernel_interface.3
aa_policy_cache.3
aa_splitcon.3
** Affects: apparmor (Ubuntu)
Importance: Medium
Assignee: Steve Beattie (sbeattie)
Status: In
A man page for aa_query_label(3) was included in the AppArmor 2.10
release.
** Changed in: apparmor
Status: Triaged => Fix Released
** Changed in: apparmor
Milestone: 2.9.3 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
101 - 200 of 496 matches
Mail list logo
