Full Disclosure mailing list archives

SNOSOFT


From: Day Jay <d4yj4y () yahoo com>
Date: Tue, 28 Jan 2003 14:03:48 -0800 (PST)

Looks like I "spammed snosoft" 
<simon () snosoft com>:
Connected to 66.51.71.212 but sender was rejected.
Remote host said: 550 5.7.1 Mail from 216.136.174.181
rejected, Reason:  you spammed!!
http://www.snosoft.com

FIRST OF ALL:

In my humble opinion: SNOSOFT hasn't offered anything
useful in terms of full disclosure. Where are the
advisories? Hmmm, writing exploits based on known
exploits that have already been written is quite
revolutionary!

They are out to seek publicity for their untalented
company. They are giving up in their failed quest to
write exploits because they simply can't do it
anymore. They are going to stop writing exploits
because, they CAN'T write them anymore. All available
skill has been used up. They forgot how to disassemble
and reverse engineer software to find exploitable
bugs. Don't give up, there's hope...

Hmmmm, is it me, or isn't Snosoft like a total
packetstorm wannabe providing sooo much warez to those
who need to pop root from local accounts on unix
machines? They don't believe in full-disclosure
anymore but they leave exploit code on their site-hmmm
hypocritical? YES. VERY.

Not to mention the fact that Snosoft hasn't written
any decent advisory ever. So they aren't providing any
more exploits? Boohoo! None of exploits released by
snosoft could be made into anything useful anyway.
This is yet another self-promotion of a company that
lacks skill and know-how.

I know alot of people are going to love the fact that
Snosoft stopped trying to release exploits, but I know
some script kids that are going to be devastated about
this.

But at least, Snosoft can now call themselves
Blackhats. Wohoo, another blackhat added to the list.
PHC up, hoes down.

day to the motherfucking jay

====
ATD <simon () snosoft com> said:
=========
I have been following the subject of full disclosure
for a while, and as most of you know, have dealt with
some of the issues that full disclosure can cause
(HP/Secure Network Operations/DMCA).  While the idea
of full disclosure is a good idea, and while we
support it, we feel that the exploit source code
should not be released to everyone.

===
With that said, Secure Network Operations, Inc. will
no longer be releasing functional proof of concept
code. We may release sufficiently detailed advisories.




__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html


Current thread: