From: Pekka Enberg <penberg@cs.helsinki.fi>
To: John Johansen <john.johansen@canonical.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 07/12] AppArmor: userspace interfaces
Date: Tue, 10 Nov 2009 18:29:52 +0200 [thread overview]
Message-ID: <84144f020911100829k515c7f73w84df942162a49a30@mail.gmail.com> (raw)
In-Reply-To: <1257869585-7092-8-git-send-email-john.johansen@canonical.com>
Hi John,
On Tue, Nov 10, 2009 at 6:13 PM, John Johansen
<john.johansen@canonical.com> wrote:
> The current apparmorfs interface is compatible with previous versions
> of AppArmor. The plans are to deprecate it (hence the config option
> APPARMOR_COMPAT_24) and replace it with a more sysfs style single
> entry per file interface.
We don't usually merge compatibility code to handle ABIs that were
developed out-of-tree. Why should we treat AppArmor differently?
Pekka
next prev parent reply other threads:[~2009-11-10 16:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:12 [AppArmor #3 0/12] AppArmor security module John Johansen
2009-11-10 16:12 ` [PATCH 01/12] AppArmor: misc. base functions and defines John Johansen
2009-11-10 16:12 ` [PATCH 02/12] AppArmor: basic auditing infrastructure John Johansen
2009-11-10 16:12 ` [PATCH 03/12] AppArmor: contexts used in attaching policy to system objects John Johansen
2009-11-10 16:12 ` [PATCH 04/12] AppArmor: core policy routines John Johansen
2009-11-10 16:12 ` [PATCH 05/12] AppArmor: dfa match engine John Johansen
2009-11-10 16:12 ` [PATCH 06/12] AppArmor: policy routines for loading and unpacking policy John Johansen
2009-11-10 16:13 ` [PATCH 07/12] AppArmor: userspace interfaces John Johansen
2009-11-10 16:29 ` Pekka Enberg [this message]
2009-11-10 16:44 ` Andi Kleen
2009-11-10 18:21 ` Stephen Hemminger
2009-11-15 22:14 ` david
2009-11-15 22:13 ` david
2009-11-10 18:51 ` John Johansen
2009-11-10 16:13 ` [PATCH 08/12] AppArmor: file enforcement routines John Johansen
2009-11-10 16:13 ` [PATCH 09/12] AppArmor: mediation of non file objects John Johansen
2009-11-10 16:13 ` [PATCH 10/12] AppArmor: domain functions for domain transition John Johansen
2009-11-10 16:13 ` [PATCH 11/12] AppArmor: LSM interface, and security module initialization John Johansen
2009-11-10 16:13 ` [PATCH 12/12] AppArmor: Enable configuring and building of the AppArmor security module John Johansen
2009-11-13 17:44 ` [AppArmor #3 0/12] " Stephen Hemminger
2009-11-13 17:58 ` John Johansen
2009-11-20 17:39 ` Tetsuo Handa
2009-11-21 5:28 ` Tetsuo Handa
2009-11-22 11:49 ` Tetsuo Handa
2009-11-23 10:10 ` John Johansen
2009-11-23 10:11 ` John Johansen
2009-11-23 10:10 ` John Johansen
-- strict thread matches above, loose matches on Subject: below --
2009-11-03 23:48 [Patch " John Johansen
2009-11-03 23:48 ` [PATCH 07/12] AppArmor: userspace interfaces John Johansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84144f020911100829k515c7f73w84df942162a49a30@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®