[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <200309211556.h8LFuS5m076005@mailserver1.hushmail.com>
Date: Sun, 21 Sep 2003 08:56:28 -0700
From: <joeypork@...hmail.com>
To: bmc@...rt.org
Cc: snort-users@...ts.sourceforge.net, snort-devel@...ts.sourceforge.net,
full-disclosure@...ts.netsys.com, bugtraq@...urityfocus.com,
incidents@...urityfocus.com
Subject: Re: Snort and SourceFire "Backdoored"
Well, there was nothing on snort.org up about this incident. There is
nothing in the mailing list archive about this incident. Where is public
warning? I dont see any! Show me where, Mr. Caswell....
More importantly, which functions were "trojaned" and changed? Why don't
we all get to see what you have changed to the Snort source? What are
you hiding?
Also, why are you getting all defensive and telling me to "grow up"?
Im merely putting forth some constructive criticizism, I happen to run
Snort and I am concerned.
On Sun, 21 Sep 2003 08:24:54 -0700 Brian <bmc@...rt.org> wrote:
>On Sun, Sep 21, 2003 at 08:22:03AM -0700, joeypork@...hmail.com wrote:
>> I guess now that we have this incident validated as positively
>true from
>> the main Snort/SourceFire IT person, it lends a lot of credibility
>to
>> the Snort/SourceFire "backdoor" rumor.
>
>No, it does not. Did you read my email?
>
>I said this was OLD news. A LONG time ago. We published our findings
>on
>snort.org a LONG time ago. Your assumptions are all wrong.
>
>Grow up already.
>
>-brian
>
>
Concerned about your privacy? Follow this link to get
FREE encrypted email: https://www.hushmail.com/?l=2
Free, ultra-private instant messaging with Hush Messenger
https://www.hushmail.com/services.php?subloc=messenger&l=434
Promote security and make money with the Hushmail Affiliate Program:
https://www.hushmail.com/about.php?subloc=affiliate&l=427
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
Powered by blists - more mailing lists