** Also affects: apparmor
Importance: Undecided
Status: New
** 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.
https://bugs.launchpad.net/b
> comm="apparmor_signal" requested_mask="receive" denied_mask="receive"
signal=kill peer="/home/ubuntu/apparmor_signal_test_wrap.sh"
So you get a denial for receiving a signal from
peer="/home/ubuntu/apparmor_signal_test_wrap.sh" - which is not
surprising because that peer has a profile:
> "/home
For reference: This was fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/1218 in April.
Until fixed Ubuntu packages are available, you can manually apply the
(simple) patch from that merge request.
--
You received this bug notification because you are a member of Ubuntu
T
> # new python script to create vim profiles with
>
> python create-apparmor.vim.py
For the records: create-apparmor.vim.py exists since years, and ...
> # generates a new file called apparmor.vim.in
... it uses apparmor.vim.in as _input_ and generates the apparmor.vim
file (syntax highlighting
Slightly related:
> /usr/sbin/runc flags=(unconfined) {
Shouldn't that nowadays be(come)
profile runc /usr/sbin/runc flags=(unconfined) {
Ideally please fix this now, so that the upstream docker profile can use
peer=runc
--
You received this bug notification because you are a member of Ubuntu
> with the new apparmor Candidate: 4.0.0~alpha2-0ubuntu7
> DistroRelease: Ubuntu 24.04
This bug smells like a userns issue - programs using userns (often used
for sandboxing) now _must have_ an AppArmor profile.
Can you please save the following as /etc/apparmor.d/surfshark? (Adjust
the path to
This was already fixed upstream, see
https://gitlab.com/apparmor/apparmor/-/merge_requests/664
--
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/1934005
Title:
abstractions/
> apparmor_parser -R /etc/apparmor.d
-R means to unload profiles, in this case all profiles in
/etc/apparmor.d/. That's probably a bit ;-) too much...
I'd guess you want to unload only the tcpdump profile, which would be done with
apparmor_parser -R /etc/apparmor.d/usr.bin.tcpdump
An alternative
Looks like the profile for cups-browsed has a syntax error. (Did you
change something in the profile, or is it the original profile as
shipped in the package?)
Also, AFAIK this profile is shipped with the cups package, therefore I'm
adding that package.
** Also affects: cups (Ubuntu)
Importanc
This was already fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/848 (with a
slightly different patch that works for all python versions).
AppArmor >= 3.0.5 will include the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
The /usr/bin/redshift profile needs some additional dbus rules.
** Also affects: redshift
Importance: Undecided
Status: New
--
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.
A few comments and explanations:
> As part of that it locks down /dev to read-only:
> /dev/ r,
>
> However that also means /dev/pts is read-only, hence the error above denies
> write access.
The rule for /dev/ only allows reading the directory listing of /dev/.
It doesn't say or allow anything
Based on your DENIED message, I wonder if read (= directory listing)
permissions are really needed, or if
/var/cache/samba/printing/ w, # without r
would be enough. Can you please test and report back?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
aa-disable calls apparmor_parser, so this is most likely a problem
between apparmor_parser and the kernel. I've updated the summary
accordingly.
** Summary changed:
- "aa-disable" fails on autopkgtest.u.c (armhf)
+ parser fails to unload profile via "aa-disable" on autopkgtest.u.c (armhf) -
"Per
Typo? I'd expect 'Just "w" is enough' ;-)
--
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/1993572
Title:
samba profile: missing rule for mkdir /var/cache/samba/printing
S
Submitted as https://gitlab.com/apparmor/apparmor/-/merge_requests/937
--
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/1993572
Title:
samba profile: missing rule for mkdir
This is already fixed upstream (in AppArmor 2.12.2 and 2.13.2),
especially commit f997977e6.
However, the Ubuntu package doesn't have that fix yet, therefore I add
"apparmor (Ubuntu)" to the "affects" list.
Backporting the mentioned commit probably isn't too easy (it's quite big
and IIRC has depe
The ssl_certs and ssl_keys abstractions just got the paths for letsencrypt
added:
https://gitlab.com/apparmor/apparmor/merge_requests/283
(also backported to the 2.10..2.13 branches)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Also affects: apparmor
Importance: Undecided
Status: New
--
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/1784499
Title:
AppArmor treats regular NFS file acces
** Changed in: apparmor
Status: Fix Committed => 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/1785391
Title:
aa-genprof fails in an lxd instance
St
> unix (connect, send, receive) peer = (addr = "@
2F746D702F65736574732E736F636B00 *")
Did you really use exactly this line (with "@_space_2F...B00_space_*")?
If so, please try again without the spaces.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
** Changed in: apparmor
Status: Fix Committed => 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/1668892
Title:
CVE-2017-6507: apparmor service restart
** Changed in: apparmor
Status: Fix Committed => 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/1590561
Title:
webbrowser-app crashes on startup on fr
Fixed in AppArmor 2.12
** Changed in: apparmor
Status: Fix Committed => 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/1730536
Title:
"Unable to open
** Changed in: apparmor
Status: Fix Committed => 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/1717714
Title:
@{pid} variable broken on systems with
Just as a quick info - to get things working with non-default home
directory locations, edit /etc/apparmor.d/tunables/home (or add a file
to /etc/apparmor.d/tunables/home.d/) and add your custom path
("/data/home/") to the @{HOMEDIRS} variable.
I'm not sure why read access to /data/ was requested
Just wondering - if this bug survived so long without being noticed,
isn't it a sign that in most cases scrubbing doesn't hurt or is even a
good idea?
Should we introduce Ix to officially have a way to inherit with
scrubbing?
--
You received this bug notification because you are a member of Ubun
Looks like you have a syntax error in /etc/apparmor.d/tunables/multiarch
around line 13. Can you please attach this file? Also, did you modify it
manually?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
ht
For the records - I'm just working on a different implementation of
"(V)iew Changes", which will also replace the workaround with a real fix
:-) This will probably be in AppArmor 3.0, and will appear as merge
request on gitlab this weekend.
--
You received this bug notification because you are a
> There is also a python parser (in aa.py) which only seems to understand the
> 'include '
> syntax and it is this which throws errors when running the utility commands.
Exactly, that's the cause of this bug. I'll change the title to make it
obvious.
Interestingly, it has been this way for year
> c0n7r4 (c0n7r4) wrote:
> apparmor="AUDIT"
AUDIT events happen if your profile has a rule like
audit /tmp/tempfile/ r,
and the program is then really doing something that needs this rule (like
getting a directory listing for /tmp/tempfile/).
"audit" means that the action is allowed (but get
> Not quite sure now if apparmor upstream is found in launchpad[1] or
gitlab[2].
The code moved from bzr to gitlab recently. Bug tracking and
translations are still handled on launchpad.
> I would go with that versionning approach instead:
>
> apparmor | 2.11.0-2ubuntu17.1 | artful
> apparmor |
Reopening for upstream AppArmor - unfortunately nobody worked on this
yet :-(
** Changed in: apparmor
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launch
For the records: this is already fixed upstream (checked in master and
the latest 2.11 branch), so Ubuntu "just" needs to pick up the fix.
commit e2039f021e42793e07c1838499eae9c22e1ea8f2
Author: Christian Boltz
Date: Mon Aug 15 22:02:55 2016 +0200
See https://bugs.launchpad.net/app
Done - https://gitlab.com/apparmor/apparmor/merge_requests/131 will be
part of AppArmor 3.0
--
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/1528139
Title:
serialize_profil
> ./abstractions/lightdm: /bin/ rmix,
rmix permissions for a directory? That looks wrong to me, r permissions
should be enough.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bug
https://gitlab.com/apparmor/apparmor/merge_requests/157
For aa-logprof - a) what exactly is the problem and b) please answer in
a separate bugreport ;-)
** Changed in: apparmor
Status: New => Triaged
** Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
-
Fix commited to 2.10 branch..master
For the aa-logprof issue you mentioned, please answer my question in a
new bugreport ;-)
--
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/
** Changed in: apparmor
Status: Triaged => 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/1785391
Title:
aa-genprof fails in an lxd instance
Status
Also backported to the 2.12 and 2.13 branch, will be in 2.12.2 and
2.13.2.
--
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/1528139
Title:
serialize_profile_from_old_profil
> ... apparmor="DENIED" operation="create" ... family="unix"
sock_type="stream"
With the pinned-down feature set, you probably "lost" support for unix
rules.
In theory, apparmor_parser will downgrade those rules to "network unix,"
- but in practise a bug in apparmor_parser prevented it.This bug w
** Also affects: apparmor/2.11
Importance: Undecided
Status: New
** Changed in: apparmor/2.11
Status: New => Fix Committed
** Changed in: apparmor/2.11
Milestone: None => 2.11.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
/run/user/1000/wayland-0 doesn't sound like an Evince-specific thing.
Would it make sense to add it to the X abstraction instead? (restricting
it to "owner" probably makes sense)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is fixed in the (already released) AppArmor 2.10, but I'm unable to
set the target milestone to 2.10.
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to a
*** This bug is a duplicate of bug 1489196 ***
https://bugs.launchpad.net/bugs/1489196
** This bug has been marked a duplicate of bug 1489196
aa-genprof should display a clear error message instead of a stack trace if
it doesn't have write permissions to the profile directory
--
You rece
For the records:I accidently used --fixes lp:1466812 (= this bug) when
commiting bzr trunk r3266 and 2.9 branch r2961. Those commits actually
fixed bug 1509030, which is the file_inherit "twin" of this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
While I understand the reason to have a wayland abstraction (yes,
wayland != X), this probably also means we'll need to change all
profiles that include abstractions/X to also include the wayland
abstraction. That's also the reason why I proposed (ab)using
abstractions/X - that would mean we don't
The log message says family="inet6" so you'll need "network inet6
stream," (inet != inet6 ;-)
"stream" is an optional restriction - I'd recommend to add it (also to
the existing "network inet," rule, assuming that only "stream" is
needed) to avoid superfluous permissions.
--
You received this bu
Which apparmor version do you use?
I can't reproduce the problem using the latest version from the 2.9
branch and bzr trunk. (I tested with abstractions/base instead of
abstractions/lxc/start-container in the profile, but that shouldn't
matter.)
--
You received this bug notification because you
AppArmor 2.7 is _very_ old - especially given the fact that the tools
were rewritten in python for 2.9.
I just checked the perl code (which was used in 2.8.x and older) - it
_sets_ the flags (instead of adding or removing them), so it's not
surprising that attach_disconnected gets lost. (This is o
*** This bug is a duplicate of bug 1390223 ***
https://bugs.launchpad.net/bugs/1390223
nearly correct - the rule needs to be
/public/showq r,
(note the leading "/")
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lx
The fix *) for this is in upstream AppArmor 2.10 and will also be in
2.9.3.
*) fix means ignoring those log entries to avoid the crash. Ideally aa-
logprof should propose adding the attach_disconnected flag. See also
https://bugzilla.opensuse.org/show_bug.cgi?id=918787
Note: You'll need to add
This report is about AppArmor 2.9.2
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-tools
--
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
Just for the records - this is a duplicate of bug 1378095
--
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/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
St
Just to make sure this doesn't get lost/overlooked:
> # Oddly, comm="kill" is in both denials, despite the denials being for
send and receive masks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://b
I can reproduce the crash with both bzr trunk and the 2.9 branch using
the attached KernLog.txt
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-tools
** Changed in: apparmor
Importance: Undecided => High
--
You received this bug notification because y
Actually, I get a slightly different crash:
File "/home/cb/apparmor/HEAD-clean/utils/apparmor/logparser.py", line 258, in
add_event_to_tree
rmask = rmask.replace('c', 'a')
AttributeError: 'NoneType' object has no attribute 'replace'
('NoneType' instead of 'set')
--
You received this bug
This log line is enough to reproduce the crash:
Jun 19 12:00:55 piorun kernel: [4475115.459952] audit: type=1400
audit(1434708055.676:19629): apparmor="ALLOWED" operation="file_perm"
profile="/usr/sbin/apache2" pid=3512 comm="apache2"
laddr=:::193.0.236.159 lport=80 faddr=:::192.168.103.80
Patch to avoid the crash (by ignoring file_perm events without request_mask):
https://lists.ubuntu.com/archives/apparmor/2015-June/008250.html
I'm also adding the aa-kernel tag because the logging seems to be broken
somehow.
** Tags added: aa-kernel
--
You received this bug notification because
Silly question - did you set the x file permissions (chmod +x) for the
script? Otherwise...
# ./README
bash: ./README: Permission denied
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
http
Maybe the code in the Ubuntu package needs another patch that is in
upstream bzr, but not in the package. (Strictly speaking, that's not my
problem - I only do the openSUSE packaging :-P)
Can you please test with a bzr checkout of the latest upstream code from
lp:apparmor (trunk) and/or lp:apparmo
Public bug reported:
aa-logprof crashes on profiles that contain an #include _if_
there are events for this profile.
2.9 crash:
# aa-logprof -f /tmp/syslog
Lese Logeinträge von /tmp/syslog.
Aktualisiere AppArmor-Profile in /etc/apparmor.d.
Traceback (most recent call last):
File "aa-logprof",
Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
** Changed in: apparmor
Status: New => In Progress
** Changed in: apparmor
Milestone: None => 2.9.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
patches for trunk sent to ML.
** Changed in: apparmor
Status: New => In Progress
** Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Patch for 2.9 also sent to ML.
Note that the trunk patch actually honors the content of the include
directory, while the 2.9 patch "just" avoids the crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
h
Re comment #13:
Good to know, so my patch actually helps. Now Ubuntu "just" needs to release an
updated package ;-)
Re comment #14:
aa-logprof (to be exact: logparser.py) assumes "connect" events are always
network events, but some discussion on #apparmor (and of course your log entry)
brought
Fix for the utils commited to bzr (both trunk and 2.9).
For the kernel side that produces the broken log message, I just opened
bug 1472776.
** Changed in: apparmor
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Patches commited to trunk and 2.9.
** Changed in: apparmor
Status: In Progress => Fix Committed
** Changed in: apparmor
Milestone: None => 2.9.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Tags added: aa-tools
--
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/1489196
Title:
aa-genprof should display a clear error message instead of a stack
trace if it doe
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-policy
--
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/1717714
Title:
@{pid} varia
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-feature
--
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/1719935
Title:
It would be
You'll need to allow
/etc/gss/mech.d/ r,
and after that, I wouldn't be surprised if you get denials for files
inside this directory ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.laun
** Tags added: aa-tools
--
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/1669254
Title:
16.04 apparmor, aa-logprof and log files
Status in AppArmor:
New
Status in apparm
I added dbus support to aa-logprof in AppArmor 2.11, and I'd guess *)
16.04 has an older version.
*) I use openSUSE ;-)
--
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/17002
This was fixed in upstream bzr r3490 (2016-07-20), but only in trunk.
Looks like nobody backported it to the 2.10 branch or the Ubuntu
packages.
See also bug 1584069 (which is referred in the r3490 commit message) -
interestingly, there's a comment saying "This bug was fixed in Ubuntu
16.04 with a
** Tags added: aa-tools
--
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/1679856
Title:
ldd should be replaced in the utilities
Status in AppArmor:
New
Status in apparmo
Thanks for the report!
I commited the updated profile to bzr trunk r3651, 2.10 branch r3391 and
2.9 branch r3056.
If you want to update your profile locally, the needed changes are:
-/usr/lib/dovecot/dovecot-lda {
+/usr/lib/dovecot/dovecot-lda flags=(attach_disconnected) {
+ /run/dovecot/auth-
I don't care too much about dh_apparmor (EWRONGDISTRO ;-) - but still:
Are you sure that unloading profiles when uninstalling a package is a
good idea? The binary installed by this package could still be running,
and unloading the profile (= unconfining the binary) might be a security
risk. (I ass
I'd even recommend to restrict it a bit more:
owner /tmp/antispam-mail*/ rw,
owner /tmp/antispam-mail*/* rwkl,
sendmail might be a candidate for a child profile. Such a (maybe too
generous) profile already exists in the dovecot-lda profile, so cleaning
it up and removing permissions that are
** Also affects: apparmor/2.10
Importance: Undecided
Status: New
--
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/1507469
Title:
Evince's Apparmour profile preven
** Changed in: apparmor/2.10
Milestone: None => 2.10.2
** Changed in: apparmor/2.10
Status: New => Fix Committed
** Changed in: apparmor
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Changed in: apparmor
Status: Fix Committed => 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/1528139
Title:
serialize_profile_from_old_profile() cr
Fixed in AppArmor 2.11.
** Changed in: apparmor
Status: Fix Committed => 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/1584069
Title:
change_profile
** Changed in: apparmor
Status: Fix Committed => 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/1480492
Title:
aa-status in apparmor-2.10 depends on p
Fixed in AppArmor 2.11
** Changed in: apparmor
Status: Fix Committed => 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/1588069
Title:
parser doesn't
** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.10
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.9
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: apparmor
Status: Fix Committed => 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/1634199
Title:
In 16.10, LXD won't work with enforced
Fixed in AppArmor 2.11
** Changed in: apparmor
Status: Fix Committed => 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/1604872
Title:
Apps can't conn
** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.10
Status: Fix Committed => 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.l
** Changed in: apparmor
Status: Fix Committed => 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/1569316
Title:
Log flooded with run/dbus/system_bus_so
Fixed in AppArmor 2.11, 2.10.2 and 2.9.4
** Changed in: apparmor
Status: Fix Committed => 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/1546455
Title:
** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.10
Status: Fix Committed => 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.l
** Changed in: apparmor
Status: Fix Committed => 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/1566944
Title:
dnsmasq profile prevents LXD container
** Changed in: apparmor
Status: Fix Committed => 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/1540562
Title:
aa-genprof crashes in logparser NoneTyp
** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: apparmor/2.10
Status: Fix Committed => 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.l
** Changed in: apparmor
Status: Fix Committed => 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/1628745
Title:
Change in kernel exec transition behavi
** Changed in: apparmor
Status: Fix Committed => 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/1525119
Title:
Cannot permit some operations for sssd
** Changed in: apparmor/master
Status: Fix Committed => 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/1534405
Title:
Regression in parser compiling/l
** Changed in: apparmor
Status: Fix Committed => 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/1528230
Title:
[ADT test failure] linux: ubuntu_qrt_ap
This was already fixed in AppArmor 2.10.1
** Changed in: apparmor
Status: Fix Committed => 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/1484178
Title
1 - 100 of 258 matches
Mail list logo
