View Bazaar branches
Get this repository:
git clone https://git.launchpad.net/apparmor

See all merge proposals.

Import details

Import Status: Reviewed

This repository is an import of the Git repository at https://gitlab.com/apparmor/apparmor.git.

The next import is scheduled to run .

Last successful import was .

Import started on juju-98ee42-prod-launchpad-codeimport-14 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-14 and finished taking 6 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-20 and finished taking 2 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-20 and finished taking 3 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-7 and finished taking 45 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-9 and finished taking 2 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-9 and finished taking 1 minute — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-20 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-20 and finished taking 1 minute — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-20 and finished taking 50 seconds — see the log

Branches

Name Last Modified Last Commit
master 2026-07-20 19:38:13 UTC
Merge Fix includes for parser

Author: Christian Boltz
Author Date: 2026-07-20 19:38:13 UTC

Merge Fix includes for parser

... as reported by include-what-you-use

Additionally do some manual fixes, for example in parser_lex.l (which
include-what-you-use can't handle)

Things intentionally not done in this commit/MR:

- `#include "common_flags.h" // for parseopts`
  - not sure if this is the right file

- `#include "perms.h" // for ostream`
  - `using std::ostream;` is probably the reason why perms.h gets
    proposed, but perms.h probably isn't the best solution.
  - also ignore other ostream-related additions like `<iosfwd>` for now

- and some others that need a second look, ideally by someone who is
  familiar with the parser code

Also add a "make check-includes" target to run include-what-you-use.
So far this isn't part of "make check" and needs to be run manually.

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/2088
Approved-by: Ryan Lee <rlee287@yahoo.com>
Merged-by: Christian Boltz <apparmor@cboltz.de>

apparmor-4.1 2026-07-20 16:25:33 UTC
Merge unix-chkpwd AppArmor profile denies the nslcd socket, breaking all LDAP...

Author: Christian Boltz
Author Date: 2026-07-20 16:25:33 UTC

Merge unix-chkpwd AppArmor profile denies the nslcd socket, breaking all LDAP logins

## Summary

The `unix-chkpwd` profile grants no rule for the nslcd socket at all. `abstractions/nameservice` (which the profile includes) covers nscd's socket, but nslcd's lives in `abstractions/ldapclient`, which the profile does not include.

On top of that, the profile is attached with `flags=(attach_disconnected.path=/att/unix-chkpwd/)`, and `unix_chkpwd` reaches the socket as a disconnected path, so it is mediated as `/att/unix-chkpwd/run/nslcd/socket`.

`unix_chkpwd` can then no longer resolve any LDAP-backed user. `pam_unix`'s account phase fails and **every LDAP user is denied login**, immediately after their public key has already been accepted. Local users are unaffected, which makes the failure look like a per-user problem rather than a policy one.

## Steps to reproduce

1. Join the host to an LDAP/AD directory using libnss-ldapd / nslcd
   * `passwd: files ldap` in `/etc/nsswitch.conf`
2. Confirm the directory works: `getent passwd <ldap-user>` succeeds as root.
3. Log in over ssh as that LDAP user with a valid public key.

## Actual result

Authentication succeeds, then the session is dropped.

Client:

```
debug1: Server accepts key: /home/<user>/.ssh/id_ed25519 ED25519 SHA256:...
Connection closed by <host> port 22
```

/var/log/auth.log:

```
unix_chkpwd[70567]: could not obtain user info (<user>)
sshd-session[70565]: fatal: Access denied for user <user> by PAM account configuration [preauth]
```

dmesg:

```
audit: type=1400 audit(...): apparmor="DENIED" operation="connect" class="file" \
  profile="unix-chkpwd" name="/att/unix-chkpwd/run/nslcd/socket" pid=70567 \
  comm="unix_chkpwd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=112
```

(`ouid=112` is the `nslcd` user.)

## Expected result

The LDAP user logs in. `unix_chkpwd` should be able to reach the nslcd socket whether or not the path is disconnected, exactly as it can already reach `authd.sock` and the systemd userdb sockets.

## Workaround

/etc/apparmor.d/local/unix-chkpwd:

```
/att/unix-chkpwd/run/nslcd/socket rw,

```

## Environment

- Ubuntu 26.04 LTS (resolute), amd64
- sshd: OpenSSH_10.2p1 Ubuntu-2ubuntu3.4
- nslcd: 0.9.13
- nscd: running, `passwd: files ldap`
- Profile header: `abi <abi/5.0>`, profile initially from the apparmor.d project (Copyright 2019-2021 Mikhail Morfikov; adapted, Copyright Christian Boltz 2024-2026)

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/2170
Approved-by: Christian Boltz <apparmor@cboltz.de>
Merged-by: Christian Boltz <apparmor@cboltz.de>

(cherry picked from commit 1c7cee3e901a766bb727c95b057e500d46de2a6e)

2df456d8 unix-chkpwd: allow the disconnected nslcd socket
229dcc53 Merge branch apparmor:master into unix-chkpwd-nslcd-socket

Co-authored-by: Christian Boltz <apparmor@cboltz.de>

apparmor-5.0 2026-07-20 16:25:18 UTC
Merge unix-chkpwd AppArmor profile denies the nslcd socket, breaking all LDAP...

Author: Christian Boltz
Author Date: 2026-07-20 16:25:18 UTC

Merge unix-chkpwd AppArmor profile denies the nslcd socket, breaking all LDAP logins

## Summary

The `unix-chkpwd` profile grants no rule for the nslcd socket at all. `abstractions/nameservice` (which the profile includes) covers nscd's socket, but nslcd's lives in `abstractions/ldapclient`, which the profile does not include.

On top of that, the profile is attached with `flags=(attach_disconnected.path=/att/unix-chkpwd/)`, and `unix_chkpwd` reaches the socket as a disconnected path, so it is mediated as `/att/unix-chkpwd/run/nslcd/socket`.

`unix_chkpwd` can then no longer resolve any LDAP-backed user. `pam_unix`'s account phase fails and **every LDAP user is denied login**, immediately after their public key has already been accepted. Local users are unaffected, which makes the failure look like a per-user problem rather than a policy one.

## Steps to reproduce

1. Join the host to an LDAP/AD directory using libnss-ldapd / nslcd
   * `passwd: files ldap` in `/etc/nsswitch.conf`
2. Confirm the directory works: `getent passwd <ldap-user>` succeeds as root.
3. Log in over ssh as that LDAP user with a valid public key.

## Actual result

Authentication succeeds, then the session is dropped.

Client:

```
debug1: Server accepts key: /home/<user>/.ssh/id_ed25519 ED25519 SHA256:...
Connection closed by <host> port 22
```

/var/log/auth.log:

```
unix_chkpwd[70567]: could not obtain user info (<user>)
sshd-session[70565]: fatal: Access denied for user <user> by PAM account configuration [preauth]
```

dmesg:

```
audit: type=1400 audit(...): apparmor="DENIED" operation="connect" class="file" \
  profile="unix-chkpwd" name="/att/unix-chkpwd/run/nslcd/socket" pid=70567 \
  comm="unix_chkpwd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=112
```

(`ouid=112` is the `nslcd` user.)

## Expected result

The LDAP user logs in. `unix_chkpwd` should be able to reach the nslcd socket whether or not the path is disconnected, exactly as it can already reach `authd.sock` and the systemd userdb sockets.

## Workaround

/etc/apparmor.d/local/unix-chkpwd:

```
/att/unix-chkpwd/run/nslcd/socket rw,

```

## Environment

- Ubuntu 26.04 LTS (resolute), amd64
- sshd: OpenSSH_10.2p1 Ubuntu-2ubuntu3.4
- nslcd: 0.9.13
- nscd: running, `passwd: files ldap`
- Profile header: `abi <abi/5.0>`, profile initially from the apparmor.d project (Copyright 2019-2021 Mikhail Morfikov; adapted, Copyright Christian Boltz 2024-2026)

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/2170
Approved-by: Christian Boltz <apparmor@cboltz.de>
Merged-by: Christian Boltz <apparmor@cboltz.de>

(cherry picked from commit 1c7cee3e901a766bb727c95b057e500d46de2a6e)

2df456d8 unix-chkpwd: allow the disconnected nslcd socket
229dcc53 Merge branch apparmor:master into unix-chkpwd-nslcd-socket

Co-authored-by: Christian Boltz <apparmor@cboltz.de>

apparmor-4.0 2026-06-08 08:47:48 UTC
Merge [4.0] Backport CI-related fixes

Author: John Johansen
Author Date: 2026-06-08 08:47:48 UTC

Merge [4.0] Backport CI-related fixes

* Remove `global` declarations when variables are only read but don't get a new value assigned.

Found by pyflakes 3.3.2 / python 3.13.3

While on it, remove some obsolete, commented out debugging code.
This fixes pyflakes warnings found because of the update CI

(cherry picked from commit 2bfdcb780fc18e0a08aa88f48ba342232a1a764d,
aa.py change adjusted to 4.1 branch)
(cherry picked from commit ef3d48299f4422d79bfb8e85c2bbd07b87c223a0,
aa.py change adjusted to 4.0 branch)

* utils: adjusts aa-notify tests to handle Python 3.13+

Python 3.13 changes the formatting of long-short option pairs that use a
meta-variable. Up until 3.13 the meta-variable was repeated. Since
Python change [1] the meta-var is only printed once.

[1] https://github.com/python/cpython/pull/103372

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
(cherry picked from commit 6336465edfc9eac73f8d28f4b84561b10fcb78aa / https://gitlab.com/apparmor/apparmor/-/merge_requests/1495)

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/2139
Approved-by: John Johansen <john@jjmx.net>
Merged-by: John Johansen <john@jjmx.net>

fix-test-suite-timeout-on-riscv64 2026-04-21 08:13:24 UTC
Test suite: increase a couple timeouts to make the tests robust on riscv64

Author: intrigeri
Author Date: 2026-04-21 08:13:24 UTC

Test suite: increase a couple timeouts to make the tests robust on riscv64

Author: Aurelien Jarno <aurel32@debian.org>

Fixes https://bugs.debian.org/1134203

apparmor-3.1 2026-04-20 18:54:30 UTC
Revert "Merge unix-chkpwd: add disconnected /run/ paths"

Author: Georgia Garcia
Author Date: 2026-04-20 18:54:30 UTC

Revert "Merge unix-chkpwd: add disconnected /run/ paths"

This reverts commit ee8642723caa3864a5df9b8dcf9b5a9b0fbf4395

apparmor-3.0 2026-04-20 18:54:08 UTC
Revert "Merge unix-chkpwd: add disconnected /run/ paths"

Author: Georgia Garcia
Author Date: 2026-04-20 18:54:08 UTC

Revert "Merge unix-chkpwd: add disconnected /run/ paths"

This reverts commit 6518f006c98602b43001b122832a34dd2213ed52

apparmor-2.13 2026-04-11 00:58:27 UTC
Merge parser: fix writing dfa flags

Author: John Johansen
Author Date: 2026-04-11 00:58:27 UTC

Merge parser: fix writing dfa flags

Currently the parser is not correctly setting the dfa flag value
and it hasn't been caught because base policy uses a flag value
of 0.

Signed-off-by: John Johansen <john.johansen@canonical.com>
(cherry picked from commit 6062262ccdf78cecd097303d545e2ee734a93216)
Signed-off-by: Georgia Garcia <georgia.garcia@canonical.com>

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/2044
Approved-by: John Johansen <john@jjmx.net>
Merged-by: John Johansen <john@jjmx.net>

fix/perms-t-cmp 2026-03-06 23:02:59 UTC
parser: fix perms_t comparator ordering

Author: Zygmunt Krynicki
Author Date: 2026-03-06 15:44:49 UTC

parser: fix perms_t comparator ordering

perms_t::operator<() had a duplicated audit comparison and never compared quiet
explicitly. Fix it by comparing quiet as the final field and returning
false when all fields are equal.

The operator is used indirectly via deref_less_than_perms in PermMap, idxmap_t
and in the cache.

I'm not sure if this was sufficient to cause real problems.

Signed-off-by: Zygmunt Krynicki <me@zygoon.pl>

fix-priority2 2025-02-06 20:24:04 UTC
parser: change priority so that it accumulates based on permissions

Author: John Johansen
Author Date: 2024-12-24 09:27:10 UTC

parser: change priority so that it accumulates based on permissions

The current behavior of priority rules can be non-intuitive with
higher priority rules completely overriding lower priority rules even in
permissions not held in common. This behavior does have use cases but
its can be very confusing, and does not normal policy behavior

Eg.
  priority=0 allow r /**,
  priority=1 deny w /**,

will result in no allowed permissions even though the deny rule is
only removing the w permission, beause the higher priority rule
completely over ride lower priority permissions sets (including
none shared permissions).

Instead move to tracking the priority at a per permission level. This
allows the w permission to still override at priority 1, while the
read permission is allowed at priority 0.

The final constructed state will still drop priority for the final
permission set on the state.

Note: this patch updates the equality tests for the cases where
the complete override behavior was being tested for.

The complete override behavior will be reintroduced in a future
patch with a keyword extension, enabling that behavior to be used
for ordered blocks etc.

Signed-off-by: John Johansen <john.johansen@canonical.com>

apparmor-2.12 2022-12-16 20:05:01 UTC
Merge log parsing fixes

Author: Georgia Garcia
Author Date: 2022-12-16 19:41:41 UTC

Merge log parsing fixes

small fixes on log parsing

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/959
Approved-by: Jon Tourville <jon.tourville@canonical.com>
Approved-by: Christian Boltz <apparmor@cboltz.de>
Merged-by: Georgia Garcia <georgia.garcia@canonical.com>
(cherry picked from commit 4f2d2a8cab285a725bf72d0322ddf17df312abe4)
Signed-off-by: Georgia Garcia <georgia.garcia@canonical.com>

apparmor-2.11 2022-08-22 22:31:58 UTC
Merge [2.11..2.13] Add 'mctp' network domain keyword [only to utils]

Author: John Johansen
Author Date: 2022-08-22 21:44:14 UTC

Merge [2.11..2.13] Add 'mctp' network domain keyword [only to utils]

Reported as comment on https://build.opensuse.org/request/show/951354
(update to glibc 2.35)

This is a partial backport of
https://gitlab.com/apparmor/apparmor/-/merge_requests/832

I propose this patch for 2.11, 2.12 and 2.13.

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/911
Approved-by: John Johansen <john@jjmx.net>
Merged-by: John Johansen <john@jjmx.net>
(cherry picked from commit 157c8ee36a09330601ec7667e8ead6d58d2ef4c8)
Signed-off-by: John Johansen <john.johansen@canonical.com>

fix-dirtest 2022-07-25 10:14:31 UTC
dirtest.sh: don't rely on apparmor_parser -N's output sort order to be determ...

Author: intrigeri
Author Date: 2022-07-25 10:04:13 UTC

dirtest.sh: don't rely on apparmor_parser -N's output sort order to be deterministic

I've seen this test fail because "apparmor_parser -N" returned the expected
lines, but in a different order than what's expected (dirtest.out).

To fix this, sort both the expected and actual output.

check-if-systemd-detect-virt-is-present 2022-07-06 06:41:35 UTC
rc.apparmor.functions: only use systemd-detect-virt if it's present

Author: intrigeri
Author Date: 2022-07-06 06:41:35 UTC

rc.apparmor.functions: only use systemd-detect-virt if it's present

This is a follow-up on !812, which added a call to systemd-detect-virt.
Everywhere else we don't assume that program is present,
and first check if it's there before we run it.
Let's do the same here.

250-what-is-the-minimum-kernel-version-required-for-apparmor-3 2022-06-29 13:25:14 UTC
Merge zgrep: allow executing egrep and fgrep

Author: Christian Boltz
Author Date: 2022-06-29 13:25:14 UTC

Merge zgrep: allow executing egrep and fgrep

egrep and fgrep also need to execute grep and write to /dev/tty in the
helper child profile.

Fixes: https://progress.opensuse.org/issues/113108

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/892
Approved-by: Jon Tourville <jon.tourville@canonical.com>
Merged-by: Christian Boltz <apparmor@cboltz.de>

160-the-trash-abstraction 2021-04-14 21:23:35 UTC
Merge severity.py: bump test coverage to 100%

Author: John Johansen
Author Date: 2021-04-14 21:23:35 UTC

Merge severity.py: bump test coverage to 100%

... by adding some new tests, and by marking two lines as "pragma: no branch" because I didn't find a testcase that doesn't let them continue with the next line.

Finally, remove severity.py from the "not 100% covered" list in test/Makefile.

Also run severity tests with the official severity.db instead of the slightly outdated copy in test/.

MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/737
Acked-by: John Johansen <john.johansen@canonical.com>

apparmor-2.10 2020-12-07 12:39:38 UTC
Release: Bump revision for 2.10.6 release

Author: John Johansen
Author Date: 2020-12-07 12:39:38 UTC

Release: Bump revision for 2.10.6 release

Signed-off-by: John Johansen <john.johansen@canonical.com>

cherry-pick-d257afd3 2020-04-02 08:49:51 UTC
Add xdg-open (and friends) abstraction

Author: John Johansen
Author Date: 2020-02-03 21:32:21 UTC

Add xdg-open (and friends) abstraction

Implement set of abstractions to handle opening uris via xdg-open and similar helpers used on different desktop environments.

Abstractions are intended to be included into child profile, together with bundle abstractions such as ubuntu-browsers, ubuntu-email and others, for fine-grained control on what confined application can actually open via xdg-open and similar helpers.

PR: https://gitlab.com/apparmor/apparmor/-/merge_requests/404
Acked-by: John Johansen <john.johansen@canonical.com>

(cherry picked from commit d257afd3096b25f5d76e2575478c13d4f6930f9a)

622fc44b Add xdg-open (and friends) abstraction
af278ca6 exo-open: Fix denials on OpenSUSE
f07f0771 exo-open: Allow playing alert sounds
80514906 kde-open5: use dbus-network-manager-strict abstraction
ac08dc66 kde-open5: fix denies Ubuntu Eoan
501aada8 gio-open: fix denies Ubuntu Eoan
0a55babe exo-open: do not enable a11y by default
e77abfa5 exo-open: update comment about DBUS denial
d35faafd kde-open5: do not enable a11y by default
8b481d46 kde-open5: do not enable gstreamer support by default
162e5086 xdg-open: update usage example

cherry-pick-d4296d21 2020-03-31 21:02:18 UTC
Merge: abstractions/nameservice: allow accessing /run/systemd/userdb/

Author: John Johansen
Author Date: 2020-03-29 08:51:55 UTC

Merge: abstractions/nameservice: allow accessing /run/systemd/userdb/

On systems with systemd 245, `nss-systemd` additionally queries NSS records from `systemd-userdbd.service`. See https://systemd.io/USER_GROUP_API/ .

This does not bring full support for `systemd-homed`, but I don't use that service so I can't help with that.

Fixes: https://gitlab.com/apparmor/apparmor/-/issues/82
PR: https://gitlab.com/apparmor/apparmor/-/merge_requests/459
Acked-by: John Johansen <john.johansen@canonical.com>

(cherry picked from commit d4296d217c888e08e10bec300fe35351c2ef2f81)

16f9f688 abstractions/nameservice: allow accessing /run/systemd/userdb/

apparmor-2.9 2018-06-29 18:30:00 UTC
profiles: adjust abstractions/python for python 3.7

Author: Christian Boltz
Author Date: 2018-06-28 11:34:08 UTC

profiles: adjust abstractions/python for python 3.7

Python 3.7 was released yesterday - and to make the abstraction
future-proof, also cover 3.8 and 3.9 in advance ;-)

(cherry picked from commit 01f41fbff821be7264a4b0aac83ed04747395055)

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>
PR: https://gitlab.com/apparmor/apparmor/merge_requests/139

apparmor-2.8 2017-10-28 05:46:04 UTC
git conversion: move .bzrignore to .gitignore

Author: Steve Beattie
Author Date: 2017-10-28 05:46:04 UTC

git conversion: move .bzrignore to .gitignore

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

apparmor-2.7 2012-04-25 19:58:58 UTC
Merge from trunk rev 2037:

Author: Kees Cook
Author Date: 2012-04-25 19:58:58 UTC

Merge from trunk rev 2037:

The m4 shipped to handle Python was incorrectly clearing
$CPPFLAGS. Additionally, do not repeat compiler flags for automake
targets that already include them, and pass more flags to the Perl build.

Signed-off-by: Kees Cook <kees@ubuntu.com>
Acked-By: Steve Beattie <sbeattie@ubuntu.com>

apparmor-2.6 2011-08-26 23:03:03 UTC
Merge from trunk revision 1805:

Author: Steve Beattie
Author Date: 2011-08-26 23:03:03 UTC

Merge from trunk revision 1805:

  Attached is a patch to make the initscript not fail if /tmp is full
  by converting the comm(1) usage on temporary files to an embedded
  awk script. On both Ubuntu and OpenSUSE, a version of awk (mawk in
  Ubuntu, gawk in OpenSUSE) is either a direct or indirect dependency
  on the minimal or base package set, and the original reporter also
  mentioned that an awk-based solution would be palatable in a way
  that converting to bash, or using perl or python here would not be.

  In the embedded awk script, I've tried to avoid gawk or mawk
  specific behaviors or extensions; e.g. this is the reason for the
  call to sort on the output of the awk script, rather than using
  gawk's asort(). But please let me know if you see anything that
  shouldn't be portable across awk implementations.

  An additional issue that is fixed in both scripts is handling
  child profiles (e.g. hats) during reload. If child profiles are
  filtered out (via grep -v '//') of the list to consider, then
  on reloading a profile where a child profile has been removed or
  renamed, that child profile will continue to stick around. However,
  if the profile containing child profiles is removed entirely,
  if the initscript attempts to unload the child profiles after the
  parent is removed, this will fail because they were unloaded when
  the parent was unloaded. Thus I removed any filtering of child
  profiles out, but do a post-awk reverse sort which guarantees that
  any child profiles will be removed before their parent is. I also
  added the LC_COLLATE=C (based on the Ubuntu version) to the sort
  call to ensure a consistent sort order.

  To restate, the problem with the existing code is that it creates
  temporary files in $TMPDIR (by default /tmp) and if that partition
  is full, problems with the reload action ensue. Alternate solutions
  include switching the initscript to use bash and its <$() extension
  or setting TMPDIR to /dev/shm/. The former is unpalatable to some
  (particularly for an initscript), and for the latter, /dev/shm is
  only guaranteed to exist on GNU libc based systems (glibc apparently
  expects /dev/shm to exist for its POSIX shared memory implementation;
  see shm_overview(7)). So to me, awk (sans GNU extensions) looks
  to be the least bad option here.

Nominated-By: Steve Beattie <sbeattie@ubuntu.com>
Acked-By: John Johansen <john.johansen@canonical.com>

Bug: https://launchpad.net/bugs/775785

apparmor-2.5 2011-06-06 17:39:54 UTC
Rename tags to conform with git tag requirements

Author: John Johansen
Author Date: 2011-06-06 17:39:54 UTC

Rename tags to conform with git tag requirements

Rename tags
  apparmor_2.5.2~rc1 to apparmor_2.5.2-rc1
  apparmor_2.6.0~rc1 to apparmor_2.6.0-rc1

this is necessary for export to the git mirror

Signed-off-by: John Johansen <john.johansen@canonical.com>

apparmor-2.3 2008-05-27 12:04:33 UTC
remove for-mainline dir from kernel patches

Author: John Johansen
Author Date: 2008-05-27 12:04:33 UTC

remove for-mainline dir from kernel patches

apparmor-2.1 2008-03-28 07:19:57 UTC
merge -r 1158 - fix fatal errors so that they have an exit with an exit code

Author: John Johansen
Author Date: 2008-03-28 07:19:57 UTC

merge -r 1158 - fix fatal errors so that they have an exit with an exit code
of 127

126 of 26 results

Other repositories

Name Last Modified
lp:apparmor 4 hours ago
lp:~apparmor-dev/apparmor/+git/apparmor-trunk-daily-ppa 2019-02-19
lp:~sbeattie/apparmor/+git/apparmor 2017-10-28
lp:~jjohansen/apparmor 2016-05-10
lp:~tyhicks/apparmor 2016-03-14
15 of 5 results
You can't create new repositories for AppArmor.