Snort mailing list archives
Re: Sourcefire VRT Certified Snort Rules Update2010-03-17
From: Alex Kirk <akirk () sourcefire com>
Date: Wed, 24 Mar 2010 10:08:30 -0400
Finally, Matt's list was ordered 1, B, 3. :)
That's just the way he operates. Take that however you like it. ;-) On Wed, Mar 24, 2010 at 9:56 AM, evilghost () packetmail net < evilghost () packetmail net> wrote:
I did want to clarify publicly that I have no issues (except one or two guys) with any of the SF people and will absolutely not attack someone personally. In my eyes Sourcefire (the company) is different from Sourcefire (the employees). I like Sourcefire (the employees, minus one or two guys). I'm not such a fan of Sourcefire (the company).
OK, I think I speak for the entire list here when I say: who are these employees you don't like, and why is it that they specifically bother you? If we don't know who they are or what they're doing, we can't go beat them into submission (assuming such a beating is appropriate).
Not really worth much value but I did want to throw that out there. I'm sure there's a gaggle of SF guys that may hate me and what I say (especially in the manner it's delivered). It's not personal. We know it's not personal, and we're a very difficult bunch to offend (the
only offense I can recall us ever having taken was to the lovely and extremely hard-working Ms. Hong being dubbed "Shlong", which was quickly discovered to be a typo and unintentional). Sticks and stones may break our bones, but feedback helps our products. If you decide on your own to tone down the level of your commentary, I'm sure no one would complain - but frankly, if you ever stop reporting bugs and pressing us for features for any reason even remotely related to "feelings", I'll sick Nigel and his Learning Stick of Justice (TM) on you. We need to hear from anyone and everyone who has a problem with the way we do things, because if we don't, it will be that much harder to improve our work going forward.
-evilghost Matt Olney wrote:Well, this has been an entertaining read. I was teaching yesterday or I would have chimed in earlier. Some points: 1) There isn't any snake-oil here. This isn't functionality we have had in the past, but we've also been honest about not having it. The addition was in response to customer requests, so there were certainly people who knew this feature wasn't there. If you want to be angry that we didn't have this, that's fine. But if you want to be correct, don't accuse us of deception over it. That isn't accurate. B) Will, Ghost, I (personally) don't give a flying crap whether you post pro- or anti- Sourcefire stuff here, as long as you are correct about what you say. I watch this list every day and add bugs as I see things that need to be fixed. As long as you aren't directly attacking somebody or outright lying, I got the Nomex underwear I need to handle it. Marketing might disagree, but they can get their own list. We're going to be wrong about things, as long as you let us know, we'll try and make it right. 3) On that, Ghost, if you have issues with the VRT subscription, you can email me directly, the VRT (research () sourcefire com <mailto:research () sourcefire com>) as a whole or you can post here. I think it is fair to say that, more than any other vendor you are going to find, Sourcefire thrives on feedback. If you have something to say, then say it. I can't promise it will be fixed, now or ever, but I'll promise you that it will be seen by the developers (who watch this and the snort-dev list) and if I don't see a bug go in for something that needs it, I'll put it in myself. That doesn't mean it will be fixed soon or ever, but someone will have to justify not addressing it. So, flame on, I got my Nomex undies on and a bugzilla window open. Matt------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Snort-sigs mailing list Snort-sigs () lists sourceforge net https://lists.sourceforge.net/lists/listinfo/snort-sigs
-- Alex Kirk AEGIS Program Lead Sourcefire Vulnerability Research Team +1-410-423-1937 alex.kirk () sourcefire com
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Snort-sigs mailing list Snort-sigs () lists sourceforge net https://lists.sourceforge.net/lists/listinfo/snort-sigs
Current thread:
- Re: Sourcefire VRT Certified Snort RulesUpdate2010-03-17, (continued)
- Re: Sourcefire VRT Certified Snort RulesUpdate2010-03-17 evilghost () packetmail net (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Mike Cox (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Joel Esler (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Seth Art (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Will Metcalf (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Seth Art (Mar 23)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Will Metcalf (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update2010-03-17 evilghost () packetmail net (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update2010-03-17 Matt Olney (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update2010-03-17 evilghost () packetmail net (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update2010-03-17 Alex Kirk (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update2010-03-17 Joel Esler (Mar 24)
- Re: Sourcefire VRT Certified Snort Rules Update 2010-03-17 Frank Knobbe (Mar 24)
