linux-kernel - Re: [AppArmor #5 0/13] AppArmor security module

lists.openwall.net		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 linux-cve-announce 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]

Message-Id: <E1OZO8Z-0004a5-6S@pomaz-ex.szeredi.hu>
Date:	Thu, 15 Jul 2010 15:06:03 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	John Johansen <john.johansen@...onical.com>
CC:	linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [AppArmor #5 0/13] AppArmor security module

On Wed, 14 Jul 2010, John Johansen wrote:
> This is the fifth general posting of the newest version of the
> AppArmor security module it has been rewritten to use the security_path
> hooks instead of the previous vfs approach.  The current implementation
> is aimed at being as semantically close to previous versions of AppArmor
> as possible while using the existing LSM infrastructure.
> 
> Development is on going and
> improvements to file, capability, network, resource usage and ipc mediation
> are planned.
> 
> With this submission we believe AppArmor is ready for inclusion into
> the kernel.
> 
> _Issues NOT specifically addressed_
> * The d_namespace_path function still manually strips the " (deleted)"
>   string that __d_path appends.  A fix to __d_path is being pursued
>   independently of the AppArmor submission.

Latest posting on that front:

  http://lkml.org/lkml/2010/7/6/186

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/