bugtraq - Re: Sun single-CPU DOS

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060524174815.GA29370@dojo.mi.org>
Date: Wed, 24 May 2006 13:48:15 -0400
From: "Mike O'Connor" <mjo@...o.mi.org>
To: bugtraq@...urityfocus.com
Subject: Re: Sun single-CPU DOS

:Beyond netstat -k, you can probably use lockstat or other kernel
:profiling tools as I mentioned in my earlier post to give them a
:good idea of where the bug really is.  Interrupt issues aren't 
:always going to be cut and dried.  There could be some particular 
:flavor of IOS, network adapter, media type, CPU, OS, etc. that 
:is more prone or less prone to the problem.  

One other thought comes to mind is that it could be a particular tty
discipline or STREAMS issue at hand.  The -network- may not be as much
of a factor as "how does the particular traffic that ends up displayed
on the telnet client interplay with the OS".  I doubt that's the issue
in this particular case, but you never know.  I've seen a whole lot of
stranger things...

-- 
 Mail: mjo@...o.mi.org  WWW: http://dojo.mi.org/~mjo/  Phone: +1 650 933 9487
 =--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=
"I was being patient, but it took too long."       -Anya, the Vengeance Demon