[87551] in North American Network Operators' Group
Re: Destructive botnet originating from Japan
daemon@ATHENA.MIT.EDU (Hannigan, Martin)
Sun Dec 25 15:04:22 2005
Date: Sun, 25 Dec 2005 15:03:18 -0500
From: "Hannigan, Martin" <hannigan@verisign.com>
To: "Richard A Steenbergen" <ras@e-gerbil.net>
Cc: "NANOG" <nanog@merit.edu>
Errors-To: owner-nanog@merit.edu
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6098E.3FAD2A49
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
What's nsp-sec?
-----Original Message-----
From: Richard A Steenbergen [mailto:ras@e-gerbil.net]
Sent: Sun Dec 25 04:25:15 2005
To: Gadi Evron
Cc: Rob Thomas; NANOG
Subject: Re: Destructive botnet originating from Japan
On Sun, Dec 25, 2005 at 02:06:38AM -0600, Gadi Evron wrote:
>=20
> It is difficult to hear something important that one invested much in =
is
> doing harm, but that is the only conclusion I and others can come up =
with
> after years of study, and NSP-SEC, as amazing as it has been, has been =
of
> a negative impact other than to cause a community to form and act
> together. Which is amazing by itself and which is why I believe it
> can do so much more.. even if it is relatively young it has proven
> itself time and time again... I am straying from the subject here.
Could have told you that a long time ago. NSP-SEC became useless the day =
it became so bogged down in its own self-aggrandizing paranoia that no =
one=20
could possibly be bothered to actually tell anyone outside of the secret =
handshake club about security issues they've spotted.
On the other hand, if you ARE going to sit around pissing and moaning=20
about botnets you are too "sekure" to tell anyone else about, thus=20
assuring they never get fixed, at least it's nice to do it in one secret =
place so I don't have to hear it. :)
--=20
Richard A Steenbergen <ras@e-gerbil.net> =
http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 =
2CBC)
------_=_NextPart_001_01C6098E.3FAD2A49
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: Destructive botnet originating from Japan</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>What's nsp-sec?<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Richard A Steenbergen [<A =
HREF=3D"mailto:ras@e-gerbil.net">mailto:ras@e-gerbil.net</A>]<BR>
Sent: Sun Dec 25 04:25:15 2005<BR>
To: Gadi Evron<BR>
Cc: Rob Thomas; NANOG<BR>
Subject: Re: Destructive =
botnet originating from Japan<BR>
<BR>
<BR>
On Sun, Dec 25, 2005 at 02:06:38AM -0600, Gadi Evron wrote:<BR>
><BR>
> It is difficult to hear something important that one invested much =
in is<BR>
> doing harm, but that is the only conclusion I and others can come =
up with<BR>
> after years of study, and NSP-SEC, as amazing as it has been, has =
been of<BR>
> a negative impact other than to cause a community to form and =
act<BR>
> together. Which is amazing by itself and which is why I believe =
it<BR>
> can do so much more.. even if it is relatively young it has =
proven<BR>
> itself time and time again... I am straying from the subject =
here.<BR>
<BR>
Could have told you that a long time ago. NSP-SEC became useless the =
day<BR>
it became so bogged down in its own self-aggrandizing paranoia that no =
one<BR>
could possibly be bothered to actually tell anyone outside of the =
secret<BR>
handshake club about security issues they've spotted.<BR>
<BR>
On the other hand, if you ARE going to sit around pissing and =
moaning<BR>
about botnets you are too "sekure" to tell anyone else about, =
thus<BR>
assuring they never get fixed, at least it's nice to do it in one =
secret<BR>
place so I don't have to hear it. :)<BR>
<BR>
--<BR>
Richard A Steenbergen =
<ras@e-gerbil.net> <A =
HREF=3D"http://www.e-gerbil.net/ras">http://www.e-gerbil.net/ras</A><BR>
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 =
2CBC)<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6098E.3FAD2A49--
