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: <20071129220842.GZ8181@ftp.linux.org.uk>
Date:	Thu, 29 Nov 2007 22:08:42 +0000
From:	Al Viro <viro@....linux.org.uk>
To:	Valdis.Kletnieks@...edu
Cc:	Jon Masters <jonathan@...masters.org>,
	Ray Lee <ray-lk@...rabbit.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, tvrtko.ursulin@...hos.com,
	Casey Schaufler <casey@...aufler-ca.com>,
	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Out of tree module using LSM

On Thu, Nov 29, 2007 at 03:56:28PM -0500, Valdis.Kletnieks@...edu wrote:
> Yes, most of these schemes *can* be bypassed because some malicious code does a
> mmap() or similar trick. But what is being overlooked here is that in most
> cases, what is *desired* is a way to filter things being handled by *non*
> malicious code.  Yeah, sure, a shar archive can contain a binary that does evil
> things - but if we stop /bin/cp from copying the file that has the evil in it,
> it's a non-issue.

Then all you need is scan-on-commit with commit-on-close.  Which requires
no changes of anything that would run in kernel mode and no bothering with
LSM whatsoever.

Incidentally, I would really love to see the threat profile we are talking
about.  I have some impressions in that area, but I would rather keep them
to myself for now - I really want to see the answers.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ