This looks like one of your profiles doesn't have
include
which causes the "Found reference to variable etc_ro, but >" messages.
Unfortunately the systemctl output is cut off so I can't see which
profile it is. Can you please post the output of
systemctl status apparmor.service | cat
Thanks for the report and the patch!
I submitted the fix upstream at
https://gitlab.com/apparmor/apparmor/-/merge_requests/1484 - using a
slightly different patch (since there's already a sed call we can
extend). I also added a similar fix to aa-remove-unknown.
** Also affects: apparmor
Import
Switching back to "new" since the fix still needs to be added to the
Ubuntu package.
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This was fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/1240
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083612
Title:
aa-remove-unknown: I/O error for unconfined profi
Fix submitted for AppArmor upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/1333
Until the fix arrives in Ubuntu, you can add the additional lines to
your /etc/apparmor.d/abstractions/mesa or (better) create a file
/etc/apparmor.d/abstractions/mesa.d/lp2081692 with the added lines.
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
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062138
Title:
test-lo
In John's profile, I'd recommend to replace
include if exists
with
include if exists
;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051574
Title:
gnome-shell-portal-helper cras
If it's related to AppArmor, you should see some messages
(apparmor="ALLOWED" or apparmor="DENIED") about it in
/var/log/audit/audit.log, syslog or dmesg. Can you please check and
attach this log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Thanks!
https://gitlab.com/apparmor/apparmor/-/merge_requests/1268 increases the
timeout to 0.4 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062138
Title:
test-logprof.py from test_utils
There are several places in test-logprof.py with a 0.3s timeout. Can you
please show the detailed error message to make it clear where we need a
longer timeout?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I'm afraid apparmor_parser is not fully aware of this restriction.
# cat foo
/usr/bin/foo {
# mount options=(rw, runbindable) / -> /bar, # causes error
mount options=(rw, runbindable) -> /bar, # accepted as valid (as
expected)
mount options=(rw, runbindable) /, # acce
> 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
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
Bugs, which is sub
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948752
Title:
ap
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934005
Title:
abstractions/X: Possible regression of X s
> The second rule allows firefox to load and run code from that location.
> But doesn't allow firefox to write to it. So if there is malware [...]
That's correct for the added rule, but the profile also has
owner @{HOME}/.{firefox,mozilla}/** rw,
which means firefox _can_ write to that locat
The error is:
Traceback (most recent call last):
File "/usr/bin/aa-notify", line 39, in
import psutil
ModuleNotFoundError: No module named 'psutil'
Looks like a missing dependency on python3-psutil (or whatever the
package is named) in the package that contains aa-notify.
--
You received
Wild _guess_/hint that could explain the behaviour you see: Do you have
(snap?) profiles that have rules with "peer=libvirtd", and fail if
libvirtd is running unconfined (which would need "peer=unconfined" in
the other profile)?
--
You received this bug notification because you are a member of Ub
This bug is finally fixed with
https://gitlab.com/apparmor/apparmor/-/merge_requests/544
AppArmor 3.0 will include the fixed tools.
** Changed in: apparmor
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Indeed, that's not really helpful :-(
Another idea - does
apparmor_parser -r /etc/apparmor.d/
print any output? (If yes, please paste or attach it.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
In the meantime (actually nearly a year ago), log parsing was rewritten
and now does de-duplication instantly. This should reduce memory usage a
lot - my experience is that especially large lots have lots of
duplication included.
I also removed some intermediate steps in the chain from logfile to
For the records: Upstream commit
a57f01d86bdb01647966f3eeff7a1cc3fc6abd76 (from 2019-02-10) added rules
to allow this (with an additional type=stream restriction, which matches
the log mentioned in this bugreport), and was also backported to the
maintenance branches.
Therefore I'll mark the AppAr
I'm afraid the logs you attached don't include anything about the reason
why you get this failure. Can you please attach the output of
systemctl status -n200 apparmor.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
> id appears to be the only one to pick different letters.
For the records: changing the hotkeys is allowed, but you have to make
sure that you don't cause hotkey conflicts. To be sure, run the updated
translation through the AppArmor utils tests - or ask me to run these
tests ;-)
> and if it's c
KernLog.txt contains several ALLOWED lines for chromium, and also DENIED
lines for firefox (unrelated to this bugreport, but nevertheless we
should probably check them.
You mentioned that you got some EPERM in strace - can you please tell us
which files were affeted?
Wild guess: maybe those files
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
> 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
Bugs, which is subsc
** Changed in: apparmor
Status: Fix Committed => 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/1785391
Title:
aa-genprof fails in an lxd instance
To manage notifications about t
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784499
Title:
AppArmor treats regular NFS file access as network op
To manage no
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528139
Title:
serialize_profile_from_old_profile() crash if file contains mu
The net_admin denial is probably caused by a bug in systemd, see
https://bugzilla.opensuse.org/show_bug.cgi?id=991901 and
https://github.com/systemd/systemd/pull/10085
I'd recommend not to allow that capability in the nmbd profile, and instead
apply the patch to systemd.
Write permissions to /r
** Changed in: apparmor
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
aa-genprof fails in an lxd instance
To manage notifications about this b
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
aa-genprof
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)
-
> ./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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784023
Title:
Update p
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528139
Title:
serialize_profile_from_old_profile() crash if
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
> sudo mv /etc/apparmor.d/usr.sbin.smbd
/etc/apparmor.d/usr.sbin.smbd_OLD
Please move that *_OLD file outside of /etc/apparmor.d/ - otherwise it
will still be loaded on a "last one wins" base. Obviously you'll need to
reload the profiles once more afterwards to ensure the "right" profile
is loaded
** Changed in: apparmor
Status: Fix Committed => 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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
T
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730536
Title:
"Unable to open external link" in Evince whe
** Changed in: apparmor
Status: Fix Committed => 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/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
** Changed in: apparmor
Status: Fix Committed => 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/1668892
Title:
CVE-2017-6507: apparmor service restarts and package upgrades unload
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
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658943
Title:
It looks like the "xlsm" extension is not included in the profile
(checked with upstream LibreOffice 6.0.1.1). [Unless someone fixes this
quickly and says so, this is probably worth a separate bugreport.]
To find out if the encrypted partition is a problem, try to open a file
with a more common ex
> 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 |
> 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
> 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
The milestone is not 100% correct - the fix is included in 2.11.95 aka
2.12 beta1.
** Changed in: apparmor
Status: Fix Committed => 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/16
** 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
Bugs, which is subscrib
> ... 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
** Tags added: aa-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669254
Title:
16.04 apparmor, aa-logprof and log files
To manage notifications about this bug go to:
https://bugs.launchpad.ne
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719579
Title
aa-notify doesn't have an option to silence specific events - hey, it's
job is to annoy^Wnotify you, so what do you expect? ;-)
To silence the notifications, you'll have to update the profile.
The easiest solution is probably to download the latest smbd profile from
http://bazaar.launchpad.net/~a
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-feature
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719935
Title:
It would be great to get a stacktrace on
This is fixed in AppArmor bzr since
revno: 3437.1.4
timestamp: Wed 2016-04-13 09:24:46 -0400
usr.sbin.smbd: new lock dir used by recent versions (4.3.8)
so you'll "just" need to backport the smbd profile to 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-policy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pi
AFAIK this is fixed in the upstream debian/control (at least on github,
didn't check the release tarball), so syncing with that might be a
better option.
If you think the upstream debian/control needs changes, please send a
pull request on github.
--
You received this bug notification because yo
I'm afraid the given information isn't enough to reproduce and debug
this problem :-(
If you hit this again, please reopen and provide some more details.
** Changed in: apparmor
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
--
You received this bu
Just a quick update about the situation on openSUSE - in the meantime,
we got rid of the initscript and switched to a small wrapper script -
see apparmor.systemd and apparmor.service on
https://build.opensuse.org/package/show/security:apparmor/apparmor
That's obviously not the final solution, but
For the records:
revno: 3437
fixes bug: https://launchpad.net/bugs/1569316
committer: Tyler Hicks
branch nick: apparmor
timestamp: Tue 2016-04-12 16:36:43 -0500
message:
profiles: Add attach_disconnected flag to dnsmasq profile
https://launchpad.net/bugs/1569316
When Ubuntu made the j
no worries, I changed it back ;-)
** Changed in: apparmor/master
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658239
Title:
base abstraction missing g
Merged into AppArmor bzr.
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Fix Committed
** Changed in: apparmor
Milestone: None => 2.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700232
Title:
aa-logprof ignor
> Sorry, I meant it's the service's job to properly/forcefully stop a
> daemon. I agree that killing processes in postrm is dangerous.
I agree that kill -9 isn't the way to go (it was meant as a rhetoric question),
but there are still valid reasons why a daemon doesn't get stopped in postrm:
- th
You are technically correct that the still-loaded profile doesn't match
a clean uninstall. However, I have a different opinion on this and thing
keeping the profile loaded is the better choice.
Unloading a profile means removing the confinement from running
processes. So if a process is still runn
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
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
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-
** Tags added: aa-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679856
Title:
ldd should be replaced in the utilities
To manage notifications about this bug go to:
https://bugs.launchpad.net
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
** Also affects: apparmor/2.10
Importance: Undecided
Status: New
** Also affects: apparmor/2.11
Importance: Undecided
Status: New
** Changed in: apparmor/2.10
Milestone: None => 2.11.1
** Changed in: apparmor/2.10
Status: New => Fix Committed
** Changed in: apparm
** Changed in: apparmor/2.10
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658239
Title:
base abstraction missing glibc /proc/$pid/ things
To manage no
openSUSE still has /var/log/messages - at least if you install one of
the "normal" syslog deamons (syslogd, syslog-ng or rsyslog) instead of
relying on journald ;-)
OTOH, openSUSE never had /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Feel free to send out what you have now (with a "just FYI, WIP" note) -
maybe I can help in some details.
For "my" invalid rule: Well, I managed to pick an example that is "more
invalid" than yours ;-)
What I wanted to know is - if there's another parameter between two bus=...
parameters, will y
> It is too bad that all of the
> profiles have to be fully parsed just to use basic utilities that don't
> necessarily care about the rules inside of a profile.
The main problem is that we allow "random" filenames for the profiles,
so we need to check all files for the to-be-changed profile - but
Commited to AppArmor bzr - trunk r3627, 2.10 branch r3383 and 2.9 branch
r3048.
Fixing the Ubuntu packages is not my job ;-)
** Also affects: apparmor/2.9
Importance: Undecided
Status: New
** Also affects: apparmor/2.10
Importance: Undecided
Status: New
** Changed in: apparm
Well, up to 2.10 dbus rule handling in the tools was simply matching for
"dbus.*," and writing the line back to the profile without any changes.
I'm not sure if I'd call full support for dbus rules (including handling
of log events) a regression ;-) but I understand that it's annoying.
Writing a "
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658943
Title:
aa-notify blocks desktop with garbage noti
Agreed, aa-notify needs some love. Nevertheless, please open separate
bugreports for firefox and chromium to get their profiles fixed ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658943
Title:
** Changed in: apparmor/master
Milestone: None => 2.11.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658239
Title:
base abstraction missing glibc /proc/$pid/ things
To manage notifications a
** Changed in: apparmor/master
Milestone: None => 2.11.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658238
Title:
apache2 abstraction incomplete
To manage notifications about this bug go to
Note that upstream AppArmor renamed abstractions/php5 to
abstractions/php and added some more paths so that it also works with
PHP 7 on openSUSE. abstractions/php5 is still provided as compability
wrapper.
It would probably make sense to take the upstream files instead of your
patch.
--
You rece
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484178
Title:
Policy cache file mtimes
** Changed in: apparmor
Status: Fix Committed => 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/1525119
Title:
Cannot permit some operations for sssd
To manage notifications abou
** Changed in: apparmor
Status: Fix Committed => 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/1528230
Title:
[ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
** Changed in: apparmor
Status: Fix Committed => 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/1522938
Title:
unix rules not written to profile
To manage notifications about thi
** Changed in: apparmor/master
Status: Fix Committed => 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/1534405
Title:
Regression in parser compiling/loading a directory
To manage
** Changed in: apparmor
Status: Fix Committed => 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/1628745
Title:
Change in kernel exec transition behavior causes regression tests to
** 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
Bugs,
** Changed in: apparmor
Status: Fix Committed => 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/1540562
Title:
aa-genprof crashes in logparser NoneType has no "replace"
To manage
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507469
Ti
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546455
Title:
Many instances of 'apparmo
1 - 100 of 305 matches
Mail list logo
