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: <200709302205.58017.ak@suse.de>
Date:	Sun, 30 Sep 2007 22:05:57 +0200
From:	Andi Kleen <ak@...e.de>
To:	Theodore Tso <tytso@....edu>
Cc:	Joshua Brindle <method@...icmethod.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	casey@...aufler-ca.com, torvalds@...ux-foundation.org,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, James Morris <jmorris@...ei.org>,
	Paul Moore <paul.moore@...com>
Subject: Re: [PATCH] Version 3 (2.6.23-rc8) Smack: Simplified Mandatory Access Control Kernel


> Yes, normally the network is outside the Trusted Computing Base (TCB),

Normally as in the 99.99999% case.

> but a cluster of Linux machines in a rack is roughly the same size of
> a huge Unix server tens year ago --- and it's not like Ethernet is any
> more secure than the PCI bus.  

PCI busses normally don't have routers to networks outside the box connected
to them. 

> So don't be so quick to dismiss something like 
> CIPSO out of hand, just because it doesn't use IPSEC.

With your argumentation we could also just disable all security
in these situations (as in null LSM to save some overhead); after all these 
systems are protected by armed guards.  If someone gets past the guards
they could connect their laptop to the network and fake all the "secured"
packets. If you assume that won't happen why do you need computer security at all?

Anyways; if someone wants to cripple their security for some
performance this way they can surely do this; but i don't think we should 
offer it as a default configuration option (just as we don't have a 
CONFIG_NULL_LSM even though there are undoubtedly systems that don't
care about permission checking[1]) 

-Andi

[1] I bet I gave the linux-tiny crowd an idea now ;-)

-
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