bugtraq - Re: Sun M-class hardware denial of service

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]

Date: Sun, 28 Sep 2008 20:36:17 -0600
From: Theo de Raadt <deraadt@....openbsd.org>
To: Brett Lymn <blymn@...systems.com.au>
Cc: Florian Weimer <fw@...eb.enyo.de>,
	B 650 <dunc.on.usenet@...glemail.com>, bugtraq@...urityfocus.com
Subject: Re: Sun M-class hardware denial of service 

> On Sun, Sep 28, 2008 at 08:14:35PM -0600, Theo de Raadt wrote:
> > 
> > OpenBSD of course cannot run in a Solaris zone.
> > 
> 
> Right.  Glad that is clear.
> 
> > OpenBSD can run in a hardware zone, and when something it does (which
> > we don't know yet) locks up that hardware zone, the only way to get
> > the hardware zone back is to POWER THE MACHINE OFF.  That is a lack
> > of hardware zoning, or isolation.  That is not what people paid a lot
> > of money for.
> > 
> 
> Yes, we all agree that is bad but this is an OpenBSD specific problem
> and, whilst interesting, the reality is that there are no going to be
> many people that are lunatic enough to run an untrusted third party
> operating system on a machine of this class.

Oh I get it.  You can use a "trust relationship with your
administrators" to get around the fact that Sun sold a piece of
hardware which does not provide the isolation they promised in their
white papers and documentation.

I guess it is some modern creed.  Ask for little, and accept it when
you don't even get it.