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] Two rules detecting video streams

Subject: Re: [Snort-sigs] Two rules detecting video streams
Date: Mon, 14 Nov 2005 09:39:53 -0500
Chich,

Would you have any problem with these rules going into the Community ruleset? There was an agreement reached on Sept. 29th that all future rules posted to the Snort-Sigs list would be incorporated into the Community rules (see http://marc.theaimsgroup.com/?l=snort-sigs&m=112803802610884&w=2), but you've used "BLEEDING-EDGE" in your msg: fields, implying that you want your rules included there.

There's certainly no problem with putting the rules in either set; I just want to make sure that your wishes are respected. Please send an e-mail indicating your preference (with a cross-post to bleeding-sigs@bleedingsnort.com if you want to have the rules go there), and I will ensure that either a) a Community pack including these is released or b) the Bleedingsnort guys have been appropriately notified so that they can take these rules.

Thanks,
Alex Kirk
Community Rules Manager
Sourcefire, Inc.

Regards,

I have written these two rules in order to detect video streams.

It is possible to precise the destination ports (554 for the first one, .1755 for the second one). However, I let them undefined in order to see if some applications use these protocols on non standard ports.

alert tcp any any -> any any (msg: "BLEEDING-EDGE streaming RTSP (realpayer)"; content:"PLAY rtsp\://"; offset: 0; depth: 12; classtype: policy-violation; reference:url,www.rtsp.org; rev: 1;)

alert tcp any any -> any any (msg: "BLEEDING-EDGE streaming Windows Mediaplayer";content:"|01000000cefa0bb0|";offset: 0;depth: 8;
content:"MMS"; distance: 4; depth: 4;classtype: policy-violation; reference:url,www.microsoft.com;rev:1;)


Thierry CHICH


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Snort-sigs mailing list
Snort-sigs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-sigs





------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ 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>