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]

Message-ID: <20080909220901.GU16071@bofh.cns.ualberta.ca>
Date: Tue, 9 Sep 2008 16:09:01 -0600
From: Bob Beck <beck@...berta.ca>
To: B 650 <dunc.on.usenet@...glemail.com>
Cc: Theo de Raadt <deraadt@....openbsd.org>,
	bugtraq@...urityfocus.com
Subject: Re: Sun M-class hardware denial of service

> 
> Yet you don't know what it is that causes the issue?  What's Sun's
> support arrangement for OpenBSD on SPARC?  If it is reproduced in
> Solaris, then I'm sure Sun would address it, but where is the benefit
> for them to do so at present?

	It's not about OpenBSD on sparc - the OpenBSD people don't
really care - the fact that it's possible at all means anyone with
clue and a less than black hat can go take an OpenBSD kernel, figure
out what it's doing there, and likely make a solaris kernel module
to do the same thing - then they have a nice little tool. This indicates
that something is broken, and can likely be taken advantage of.

   	Frankly, the OpenBSD people aren't going to bother doing it.
They're only interested in making OpenBSD go. I can think of several
people I've met in bars on the other hand who might be interested
in having a domain-instabrick module for solaris.

	-Bob