Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Signatures
[Top] [All Lists]

Re: [Snort-sigs] Community Rule Update

Subject: Re: [Snort-sigs] Community Rule Update
Date: Mon, 04 Apr 2005 11:08:12 -0400
Andreas,

Glad to know such a flag exists -- it definitely shows foresight on your part. That said, I think you've made my point for me when you say "I'm not sure anyone is actually using it" -- it sounds like a lot of people's installations would break if we introduced a new variable with little to no warning. Besides, as great as Oinkmaster is, there are plenty of people who use other rule updaters that may not have such an intelligent feature. :-)

I think this is where the OSSRC may come in handy (once it's up and operational, anyway) -- if there seems to be a need for new variables, particularly across a large number of rules, we could all agree on what those variables should be, give the community ample warning about their introduction, and then be around to help the people who will invariably pop up and say "Hey, you broke my Snort!" when the variable is actually introduced.

For now, though, I think it makes sense to err on the side of not breaking a large number of installations, especially if the note about using a variable is included in the documentation for anyone who wants to tweak the rule.

Alex Kirk
Research Analyst/
Community Rules Maintainer
Sourcefire, Inc.

On Monday 04 April 2005 15:11, Alex Kirk wrote:


As to the idea of a VALID_PROXY_SERVERS variable, it makes sense -- *if*
you've gone through as an admin and defined that variable. The problem
is, for people who are just letting Oinkmaster grab new rules without
touching their conf, this rule would break Snort, since they wouldn't
have that variable defined. That said, though, it's a good way to cut
down false positives if you take the time to define the variable, so
I'll add your suggestion to the doc.

Alex Kirk
Research Analyst/
Community Rules Maintainer
Sourcefire, Inc.



That's exactly what the -U flag in Oinkmaster is there for, i.e. merge new variables into your local snort.conf so Snort doesn't break when there are new variables introduced in the downloaded rules.
I'm not sure anyone is actually using it, but it's there :)


/Andreas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Snort-sigs mailing list
Snort-sigs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-sigs





------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Snort-sigs mailing list Snort-sigs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/snort-sigs

<Prev in Thread] Current Thread [Next in Thread>