bugtraq - Re: Solaris telnet vulnberability

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: Wed, 14 Feb 2007 18:50:59 -0600 (CST)
From: Gadi Evron <ge@...uxbox.org>
To: Damien Miller <djm@...drot.org>
Cc: Casper.Dik@....COM, Michal Zalewski <lcamtuf@...ne.ids.pl>,
	Oliver Friedrichs <oliver_friedrichs@...antec.com>,
	bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: Solaris telnet vulnberability - how many on your network? 

On Thu, 15 Feb 2007, Damien Miller wrote:
> On Tue, 13 Feb 2007, Gadi Evron wrote:
> 
> > We all agree it is not a very likely possibility, but I wouldn't rule it
> > out completely just yet until more information from Sun becomes
> > available.
> 
> What more information do you need? You have an advisory, access to the
> source code, access to the change that resolved the problem and 
> patient conversations with a very patient Casper Dik.
> 
> The onus is on you to demonstrate how this could be a backdoor.
> Otherwise you are asking Sun to prove a negative.
> 
> IMO fixing security bugs at short notice is painful enough without
> people like yourself and Steve Gibson casting assertions of malice.

I think you are a few days lagged. This was on-going and no real
"accusations" were made. Questions were asked. Information was made
available.

I'd like to re-iterate the following point, as just like you said, it has
staggering impact on how other vendors handle vulnerabilities.

Quoting -

Opinion:

Whatever my thoughts are on how silly, sad or funny this vulnerability is
(quaint really), how they use telnet (?!) and how Sun should be smacked on
the back of the head for it, I have to honestly admit Sun.s response and
the level they were open to the community and industry on this without too
many PR/legal blocks getting in their way are very encouraging, releasing
information on the vulnerability, how it happened and why, a quick beta
patch and even discussing openly on mailing lists.
I am in awe. Now it is time for others to follow their example.

This one, despite its simplicity and age, is going to be with us for a
while.

	Gadi.

> 
> -d
>