lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Nov 2009 10:38:27 -0800
From:	John Johansen <>
To:	Eric Paris <>
Subject: Re: [PATCH 02/12] AppArmor: basic auditing infrastructure.

Eric Paris wrote:
> On Tue, Nov 3, 2009 at 6:48 PM, John Johansen
> <> wrote:
>> Update kenel audit range comments to show AppArmor's registered range of
>> 1500-1599.  This range used to be reserved for LSPP but LSPP uses the
>> SELinux range and the range was given to AppArmor.
>> Patch is not in mainline -- pending AppArmor code submission to lkml
>> Add the core routine for AppArmor auditing.
>> Signed-off-by: John Johansen <>
> As the audit maintainer I NAK.  I NAK any patch that calls
> audit_log_format() with %s.  Use an audit_log_string() function unless
> you can prove to me it meets all of the audit string handling rules
> (and you know them).  That part isn't too hard to fix but....
> I'd like to register an objection to this patch as a whole.  I know
> it's a pain and its probably going to take a little reshaping of your
> userspace tools that ran against your out of tree patches, but we get
> a lot of work for free if you would make use of the lsm_audit.{c,h}
> file instead of redoing everything.  Extend it as you need to the same
> way that SMACK and SELinux did.  Personally I think it needs a generic
> lsm=%s (SMACK does it in smack_log_callback, SELinux doesn't do it but
> could/should)
> I don't think we want to use more AUDIT messages for the same thing
> even if someone in userspace said you could a long time ago.
> LSM unification and code sharing is a good thing, even if the LSMs
> can't agree on much else  :)
yes that will be a pain but if that is what is needed then we will have
to live with it.  However there is a caveat, that I need to look into yet,
all apparmor loggin will necessarily go through the audit subsystem.

We are planning our own dedicated netlink interface and dumping high volume
complain (learning) mode messages to it if an external application is
registered.  I pretty sure we can make it work but I just haven't looked
at it enough yet.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists