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. |

| Subject: | Re: [Snort-sigs] Proposal for addition of author to standard rule listings |
|---|---|
| Date: | Wed, 3 Nov 2004 13:03:32 -0600 |
On 0, Frank Knobbe <frank@knobbe.us> allegedly wrote:
Greetings, I would like to propose the addition of an author reference to the rules. This is not to gloat about rules (although it might entice people to submit rules as their name in the rule shows their active community participation). But the main idea is to put some accountability on the submitter in hopes to raise the quality of community submitted rules. Since there is no "author:" tag in Snort, or a comment field, my thought was to use the "reference:" field for that purpose. So I would like to propose the addition of "author" as a reference type. That way rules can be referenced to their submitter (and subsequent people that modify, tweak and improve the rule). I envision something like "reference:author,bmc@snort.org;". Again, the main goals are to a) improve active participation (much like with the documentation efforts), and b) to cause people to create better quality rules before their name gets attached to it.
The documentation usually lays out the Contributors section in the following way... Rule Author(s) Documentation Author(s) Perhaps this isn't clear enough and some changes need to be made. Let me know what you think. While I'm on the topic of documentation, please remember that for *any* rule to be included in the official set, a document must be provided along with the rule. Just an FYI there :).
What is the thought of the community of this idea? Regards, Frank
+-----------------------------------------------------------------+
Nigel Houghton Research Engineer Sourcefire Inc.
Vulnerability Research Team
Cat: "Forget red - let's go all the way up to brown alert!"
Kryten: "There's no such thing as a brown alert sir."
Cat: "You won't be saying that in a minute!"
pgpa2B8IevGGb.pgp
Description: PGP signature
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Snort-sigs] Bleedingsnort.com Daily Update, Brian |
|---|---|
| Next by Date: | Re: [Snort-sigs] Proposal for addition of author to standard rule listings, Frank Knobbe |
| Previous by Thread: | Re: [Snort-sigs] Proposal for addition of author to standard rule listings, Matt Jonkman |
| Next by Thread: | Re: [Snort-sigs] Proposal for addition of author to standard rule listings, Jason |
| Indexes: | [Date] [Thread] [Top] [All Lists] |