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: <200809290153.m8T1rBO4021575@cvs.openbsd.org>
Date: Sun, 28 Sep 2008 19:53:11 -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:16AM -0600, Theo de Raadt wrote:
> > 
> > the only workaround is to buy a seperate machine for the other uses.
> > 
> 
> No.
> 
> > So you buy a machine that can be split up into different machines, and
> > guess what, you still have to buy extra ones because it doesn't
> > work.
> > 
> 
> Unless you misstated the exploit vector in your original message then
> locking untrusted people into a zone will work.  I can't help it if
> you don't understand the implications of doing this.

Apparently you just plain can't understand simple english.

If you put someone running OpenBSD into a zone, and that zone locks up
completely and cannot be reset because of a flaw Sun has now admitted,
then if you NEED that zone back, you have to power the machine down.

If you don't understand that, you must be really really stupid.

Trust?

You want to talk about trust?  The entire idea is that you could
TRUST the zones to do their job.
 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ