<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.security.ids.snort.devel">
    <title>gmane.comp.security.ids.snort.devel</title>
    <link>http://blog.gmane.org/gmane.comp.security.ids.snort.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5204"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5203"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5200"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5198"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5197"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5194"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5187"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5183"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5182"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5176"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5171"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5167"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5164"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5156"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5153"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5151"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5150"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5147"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5144"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5142"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5204">
    <title>Unified2 with EXTRA_DATA fields</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5204</link>
    <description>&lt;pre&gt;Hi,

I want to explain a problem that we have while adapting our Unified2 parser
to the new extra-data fields.

The problem is that when you want to parse the vents in real time you don't
have a way to know if the Event will have an ExtraData later in the file.

Example:

(Event)
  1663     sensor id: 0    event id: 31    event second: 1337848659
 event microsecond: 228367
  1664     sig id: 99999   gen id: 1   revision: 1  classification: 0
  1665     priority: 0 ip source: 188.40.16.205    ip destination:
192.168.2.183
  1666     src port: 80    dest port: 49892    protocol: 6 impact_flag: 0
 blocked: 0
  1667
  1668 Packet
  1669     sensor id: 0    event id: 31    event second: 1337848659
  1670     packet second: 1337848659   packet microsecond: 228367
  1671     linktype: 1 packet_length: 1506

...
...

1768 (ExtraDataHdr)
  1769     event type: 4   event length: 62
  1770
  1771 (ExtraData)
  1772     sensor id: 0    event id: 14    event second: 1337848659
  1773     type: 9 datatype: 1 bloblength: 3&lt;/pre&gt;</description>
    <dc:creator>Jaime Blasco</dc:creator>
    <dc:date>2012-05-24T11:14:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5203">
    <title>Bug in SSL preproc or doc update/clarification?</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5203</link>
    <description>&lt;pre&gt;I was trying to come up with sigs to hit on a C&amp;amp;C that uses malformed
SSLv3 client hello followed by server data that does not contain an
SSL fatal alert of some kind.  For the sake simplicity below is a rule
I would expect to match on the fatal alert from the server in response
to a malformed client hello. Based on documentation in the snort
manual it seems this rule should fire with default snort.conf but it
doesn't on 2.9.2.3. Removing both "trustservers, noinspect_encrypted"
from the ssl preproc allows this rule to fire. Bug? Expected Behavior?
User Error? pcap available upon request....

Regards,

Will

#Manual Entry
"Typically, SSL is used over port 443 as HTTPS. By enabling the SSLPP
to inspect port 443 and enabling the noinspect_encrypted option, only
the SSL handshake of each connection will be inspected. Once the
traffic is determined to be encrypted, no further inspection of the
data on the connection is made.

By default, SSLPP looks for a handshake followed by encrypted traffic
traveling to both&lt;/pre&gt;</description>
    <dc:creator>Will Metcalf</dc:creator>
    <dc:date>2012-05-23T17:26:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5200">
    <title>Snort 2.9.3 Beta Now Available</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5200</link>
    <description>&lt;pre&gt;Snort 2.9.3 Beta is now available on snort.org, at
http://www.snort.org/snort-downloads/ in the Latest Development
Release section.

2.9.0 RC &amp;amp; later packages are signed with a new PGP key
(that is signed with the previous key).

Snort 2.9.3 introduces the following new capabilities:

[*] New additions
  * Updates to flowbit rule option to allow for OR and AND
    of individual bits within a single rule, and allow flowbits
    to be used in multiple groups.  See README.flowbits and
    the Snort manual for details.

  * Dynamic output plugin architecture to provide an API that
    developers can write their own output mechanisms to log alert
    and packet data from Snort.  Some output plugins have been
    removed as a result of this to be maintained by their
    respective authors.

  * Update to dcerpc2 preprocessor for improved accuracy and
    handling of different OSs for SMB processing.  See README.dcerpc2
    and the Snort manual for details.

  * Updates to reputation preprocessor for handling of wh&lt;/pre&gt;</description>
    <dc:creator>Snort Releases</dc:creator>
    <dc:date>2012-05-18T13:55:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5198">
    <title>Perfmonitor Issue</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5198</link>
    <description>&lt;pre&gt;Hi all,

I have an issue using the perfmonitor preprocessor for snort inline  to
provide the "Max performance snort stats" with the following parameters:

 

  preprocessor perfmonitor: time 300 pktcnt 5000 events max console

 

Here are the options used to launch snort :

 

        -A none \

        --dynamic-engine-lib "${SNORT_ENG}" 

        --dynamic-preprocessor-lib-dir "${SNORT_DYNPPDIR}"

        --dynamic-detection-lib-dir "${SNORT_DYNRULDIR}" 

        --daq-dir "${DAQ_DIR}" 

        -i "${INTERFACE}" 

        -c "${SNORT_CONF}" 

        --perfmon-file "${LOG_DIR}/snort.stats" 

        -l "${LOG_DIR}" 

        -Q

 

Since I'm using the "max " and  "console" parameters, my console should
display the results, based on the following code:

if(iFlags &amp;amp; MAX_PERF_STATS)

{

      .

      .

  LogMessage("uSeconds/Pkt\n");

  LogMessage("----------------\n");

  LogMessage("Snort:
%.3f\n",sfBaseStats-&amp;gt;usecs_per_packet.usertime);

  LogMessage("Sniffing:
%.3f\n",sfBaseStats-&amp;gt;usecs_per_packet.syst&lt;/pre&gt;</description>
    <dc:creator>Abdelmonaim Mokadem</dc:creator>
    <dc:date>2012-05-16T18:10:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5197">
    <title>Snort 2.9.2.3 Now Available</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5197</link>
    <description>&lt;pre&gt;Snort 2.9.2.3 is now available on snort.org, at
http://www.snort.org/snort-downloads/ in the Latest Release section.

2.9.0 RC &amp;amp; later packages are signed with a new PGP key
(that is signed with the previous key).

Snort 2.9.2.3 includes changes for the following:

  * Update to GTP preprocessor to better handle GTPv1 data.

  * Update to DNP3 preprocessor to add stricter checking on
    packets before processing by dnp3.  Improved checking
    on reassembly buffer

  * Update to PCRE rule option processing to prevent issues
    seen w/ libpcre-8.30 and certain rules.

  * Update to dcerpc2 to not abort reassembly if target-based
    protocol is undefined.

Please see the Release Notes and ChangeLog for more details.

Please submit bugs, questions, and feedback to bugs&amp;lt; at &amp;gt;snort.org.

Happy Snorting!
The Snort Release Team


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat land&lt;/pre&gt;</description>
    <dc:creator>Snort Releases</dc:creator>
    <dc:date>2012-05-15T19:56:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5194">
    <title>AF_PACKET zero copy mode</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5194</link>
    <description>&lt;pre&gt;Hi all,

Is it possible to know if the implementation of AF_PACKET capture mode with zero copy mode is currently under development in Snort ?

https://home.regit.org/2012/02/using-af_packet-zero-copy-mode-in-suricata/


Thanks for your answer,

Guillaume DALEUX
Junior Research Engineer
Ingénieur Junior en Recherchetel : 450.430.8166 ext. 2279 | guillaume.daleux&amp;lt; at &amp;gt;abovesecurity.com
sans frais / toll free : 1.866.430.8166 | fax: 450.430.1858
 Managed Security Services ? Information Risk Management
Surveillance ? Gestion des Risques Informationnels
203 - 1919 boul. Lionel-Bertrand ? Boisbriand ? QC ? Canada ? J7H 1N8
www.abovesecurity.com




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl0&lt;/pre&gt;</description>
    <dc:creator>Guillaume Daleux</dc:creator>
    <dc:date>2012-05-10T13:28:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5187">
    <title>Question regarding snort statistics</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5187</link>
    <description>&lt;pre&gt;Hi all,

My name is Efi and Im a PhD student. Im writing this email, since I  
want to find out how to monitor for each rule and for each input  
packet which of the rule's predicates were satisfied and which not for  
the specific packet that is currently being processed. For example,  
given the rule

alert tcp 1.1.1.1 any -&amp;gt; 2.2.2.2 80 (content:"BOB"; gid:1000001;  
sid:1; rev:1;),

i want for each packet statistics of the form:

Packet 1 satisfied Protocol=tcp and srcIp = 1.1.1.1
and did not satisfy destIp = 2.2.2.2 and destport = 80 and content = "BOB"

What are the modifications that need to be performed to the src to get  
this info? For example, which functions, data structures hold this  
info ...

Best Regards,
Efi



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security,&lt;/pre&gt;</description>
    <dc:creator>Efthymia Tsamoura</dc:creator>
    <dc:date>2012-05-04T10:45:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5183">
    <title>Active response on two interfaces</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5183</link>
    <description>&lt;pre&gt;I/we need to get snort to operate on two interfaces.  For simplicity, 
let's just say I want to have snort monitor traffic on eth0, but then 
send its resets out on eth1.  What's the configuration magic to allow this?

I've tried something like this in the snort.conf:
config response: device eth1 attempts 2

This, however, seems to get snort into this mode (when it detects some 
TCP connection it's configured to reset) where it "sniffs" back in the 
RST packet (on the other interface), then sends another RST packet.  
Kinda like "eating it's own tail".  The snort process consumes the CPU 
and floods the network in this mode.

Also is there documentation someone could point me to regarding 
configuring snort for multiple interfaces?

Any and all information would be greatly appreciated!
Jonny L.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how&lt;/pre&gt;</description>
    <dc:creator>Jon Larson</dc:creator>
    <dc:date>2012-05-01T23:46:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5182">
    <title>SPDY Awareness</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5182</link>
    <description>&lt;pre&gt;Have you guys looked into SPDY awareness within Snort?
http://en.wikipedia.org/wiki/SPDY

Brian Wilhide
brian.wilhide&amp;lt; at &amp;gt;gmail.com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Snort-devel mailing list
Snort-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-devel

Please visit http://blog.snort.org for the latest news about Snort!

&lt;/pre&gt;</description>
    <dc:creator>Brian Wilhide</dc:creator>
    <dc:date>2012-05-01T20:46:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5176">
    <title>wirshark diameter snort</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5176</link>
    <description>&lt;pre&gt;Can i use the wireshark parsing code for snort?(e.g 
packet_diameter.c)?...need to decode diameter protocol
Since both are written in C, and both are using libpcap...it should 
work, isnt it?

any idea guys?

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Snort-devel mailing list
Snort-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-devel

Please visit http://blog.snort.org for the latest news about Snort!

&lt;/pre&gt;</description>
    <dc:creator>asiaimbiss</dc:creator>
    <dc:date>2012-04-23T12:26:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5171">
    <title>Core dump with SID 17647?</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5171</link>
    <description>&lt;pre&gt;Hi everybody,

We have with the snort version 2920 some problems.
Sometimes following core dump occurs:

#0 rule17647eval (p=0xffe29b5c)
at web-client_cve-2007-0071-swf-definesceneandframelabeldata-rce.c:245
cursor_normal = 0x9aad86e &amp;lt;Address 0x9aad86e out of bounds&amp;gt;
end_of_payload = 0xe5c91638 &amp;lt;Address 0xe5c91638 out of bounds&amp;gt;
type_and_length = 975
tag_length = 601998450
001 0xf6da4844 in CheckRule (p=0xffe29b5c, r=0xf6c5ba60)
at sf_snort_detection_engine.c:189
No locals.
#2 0x080b7053 in DynamicCheck (option_data=0x23e1c472, p=0xffe29b5c)
at sp_dynamic.c:265
result = &amp;lt;optimized out&amp;gt;

I recognized that the flowbit of the rule 17647 has changed from 
http.swf to file.swf since 2904
and with this older version of snort we have never had this core dump 
before.

It may be that an error was made when the change happend?
If the problem is already known, can it be fixed by a simple version update?

Thanks in advance,
Lukas Matt

&lt;/pre&gt;</description>
    <dc:creator>Lukas Matt</dc:creator>
    <dc:date>2012-04-19T09:40:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5167">
    <title>(no subject)</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5167</link>
    <description>&lt;pre&gt;how to open log files of snort.......

 my log file position  is-  var/log/snort/ stored log files list
and log fire type is application/octet-stream
 i also used wireshark then it is showing - "The file
"/var/log/snort/snort.u2.1333102054" isn't a capture file in a format
Wireshark understands."

please help me............






Indrajeet Gupta

07735657121
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev_______________________________________________
Snort-devel mailing list
Snort-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-devel

Please visit http://blog.snort.org for the latest news about Snort!&lt;/pre&gt;</description>
    <dc:creator>Indrajeet Gupta</dc:creator>
    <dc:date>2012-04-11T07:18:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5164">
    <title>(no subject)</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5164</link>
    <description>&lt;pre&gt;hi everyone,
does anyone know how to parse diameter protocol traffic with snort?
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev_______________________________________________
Snort-devel mailing list
Snort-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-devel

Please visit http://blog.snort.org for the latest news about Snort!&lt;/pre&gt;</description>
    <dc:creator>karan singhania</dc:creator>
    <dc:date>2012-04-10T11:11:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5156">
    <title>Snort.org Blog: VRT Rule Update for 4/3/2012,Rule-Recategorization</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5156</link>
    <description>&lt;pre&gt;
http://blog.snort.org/2012/04/vrt-rule-update-for-432012-rule.html

VRT Rule Update for 4/3/2012, Rule-Recategorization

Join us as we welcome the introduction of the newest rule release for today from the VRT. In this release we introduced 30 new rules and made modifications to 169 additional rules.

The following changes made to the snort.conf in this release, these can be added to the bottom of the snort.conf where the rule declarations are made:

include $RULE_PATH/file-office.rules
include $RULE_PATH/file-other.rules
include $RULE_PATH/file-pdf.rules
include $RULE_PATH/indicator-compromise.rules
include $RULE_PATH/indicator-obfuscation.rules
include $RULE_PATH/policy-multimedia.rules
include $RULE_PATH/policy-other.rules
include $RULE_PATH/policy-social.rules
include $RULE_PATH/pua-p2p.rules
include $RULE_PATH/pua-toolbars.rules
include $RULE_PATH/server-mail.rules

 In VRT's rule release: 
Synopsis: This release introduces eleven new rule categories and contains new and modified rules in several categ&lt;/pre&gt;</description>
    <dc:creator>Joel Esler</dc:creator>
    <dc:date>2012-04-03T21:35:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5153">
    <title>[PATCH]: RFC3514 Support for simplifying the task ofdetecting Evil.</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5153</link>
    <description>&lt;pre&gt;
Hi snort-devel,

The attached patch introduces RFC3514 support (The Security Flag in the IPv4
Header) into Snort.  Also known as the "Evil Bit", support of this flag
greatly simplifies the the task of detecting network traffic with evil
intentions.  Entire rulesets can be replaced by one, single rule:

alert ip any any &amp;lt;&amp;gt; any any (msg:"Evil Network Traffic Detected!";
fragbits:E; sid:42003514; rev:1; gid:1; classtype:bad-unknown;)

More information on this oft-overlooked RFC can be found here:
http://www.ietf.org/rfc/rfc3514.txt


Cheers! :)

&lt;/pre&gt;</description>
    <dc:creator>Joshua Kinard</dc:creator>
    <dc:date>2012-04-01T09:17:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5151">
    <title>Packet Capturing</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5151</link>
    <description>&lt;pre&gt;Dear All,
Have a good day,
I have a question about how snort capture the packets using libpcap. From my understanding in libpcap there are two function for capturing packets, pcap_loop() and pcap_next_ex(). which one of them used by Snort and why?. and generally which one of there function is more preferable (faster) for high speed links ? . Sorry if my question is not reliable.  
by the way, I found these two function in the tutorials of WinPcap, but I think that both, libpcap and winpcap are compatible. 
Regards,
Mohammed Faiz Aboalmaaly
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure_______________________________________________
Snort-devel mailing list
Snort-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-devel

Please visit http://blog.snort.org for the latest news about Snort!&lt;/pre&gt;</description>
    <dc:creator>Mahammed Faiz Aboalmaali</dc:creator>
    <dc:date>2012-03-26T05:35:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5150">
    <title>Snort 2.9.2.2 Now Available</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5150</link>
    <description>&lt;pre&gt;Snort 2.9.2.2 is now available on snort.org, at
http://www.snort.org/snort-downloads/ in the Latest Release section.

2.9.0 RC &amp;amp; later packages are signed with a new PGP key
(that is signed with the previous key).

Snort 2.9.2.2 includes changes for the following:

  * Updates to HTTP Inspect to handle normalization with large
    number of directories, eliminate false positives when chunks
    span multiple packets, and remove the upper limit on the
    gzip memcap.

  * Update stream handling for TCP session cleanup with RSTs and
    other TCP state tracking.

  * Update for active responses to fragmented IPv6 traffic and to
    the react page configuration.

  * Updates to SIP preprocessor to limit false positives.

  * Update for correct logging in unified2 when interface is passive.

  * Add stats for SMTP preprocessor at termination.

  * State tracking improvements to SMB processing in the dcerpc2
    preprocessor when missing packets on a session.

Please see the Release Notes and ChangeLog for more &lt;/pre&gt;</description>
    <dc:creator>Snort Releases</dc:creator>
    <dc:date>2012-03-27T21:25:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5147">
    <title>support current pflog format (&gt;= OpenBSD 4.9)</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5147</link>
    <description>&lt;pre&gt;pflog format changed over a year ago, here is a patch against 2.9.2.1 to
support the expanded pflog header size.


--- decode.h.origFri Jan 13 07:11:40 2012
+++ decode.hSun Mar 25 14:22:47 2012
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -797,13 +797,14 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; typedef struct _SLLHdr {
 
 
 /*
- * Snort supports 3 versions of the OpenBSD pflog header:
+ * Snort supports 4 versions of the OpenBSD pflog header:
  *
  * Pflog1_Hdr:  CVS = 1.3,  DLT_OLD_PFLOG = 17,  Length = 28
  * Pflog2_Hdr:  CVS = 1.8,  DLT_PFLOG     = 117, Length = 48
  * Pflog3_Hdr:  CVS = 1.12, DLT_PFLOG     = 117, Length = 64
+ * Pflog4_Hdr:  CVS = 1.16, DLT_PFLOG     = 117, Length = 100
  *
- * Since they have the same DLT, Pflog{2,3}Hdr are distinguished
+ * Since they have the same DLT, Pflog{2,3,4}Hdr are distinguished
  * by their actual length.  The minimum required length excludes
  * padding.
  */
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -871,6 +872,33 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; typedef struct _Pflog3_hdr
 #define PFLOG3_HDRLEN (sizeof(struct _Pflog3_hdr))
 #define PFLOG3_HDRMIN (PFLOG3_HDRLEN - PFLOG_PADLEN)
 
+typedef struct _Pflog4&lt;/pre&gt;</description>
    <dc:creator>Ryan McBride</dc:creator>
    <dc:date>2012-03-25T06:17:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5144">
    <title>Falses on 2011032/ET SCAN HTTP POST invalid methodcase?</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5144</link>
    <description>&lt;pre&gt;I seem to be getting falses on this where the HTTP headers
are not present, but a non-all-upcase 'post' appears in the
body.

1) I would think that a 'post' not at the beginning of the of the packet
  wouldn't get flagged as an HTTP method

2) I'm doing load-balancing with the PF_RING DAQ and I
   was wondering if perhaps that would chop up the flows
   so different snort processes would get chunks from the
   same TCP stream, so the snort process that received this
   packet wouldn't know it wasn't the first packet in the stream.
   However, I'm also seeing this on a non-PF_RING-enabled
   host.

Snort info:

 - version 2.9.2.1

 - configure flags: CFLAGS="-O2 -I/opt/local/include"
   LDFLAGS="-L/opt/local/lib -Wl,-rpath=/opt/local/lib" ./configure
   --prefix=/opt/pf --enable-ipv6 --enable-zlib --enable-reload
   --enable-flexresp3  --with-libpfring-includes=/opt/local/include
   --with-libpfring-libraries=/opt/local/lib --enable-perfprofiling

 - 1 PFRING-enabled sensor:
    uname -a:
      Linux &amp;lt;server &lt;/pre&gt;</description>
    <dc:creator>Packet Hack</dc:creator>
    <dc:date>2012-03-22T13:32:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5142">
    <title>log_tcpdump does not log</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5142</link>
    <description>&lt;pre&gt;Hi,

I am trying to look if packetfence is generating a false positive or not
on certain packages and to get that I would like to capture the packets
that generated an alert with log_tcpdump into a file.

Snort starts fine with that line in the configuration but the file isn't
generated after alerts. Yes snort can write to the given directory.

Actually I have three machines running snort and it works on one and not
the other two.



hboetes&amp;lt; at &amp;gt;oink /etc/snort % snort --version
   ,,_     -*&amp;gt; Snort! &amp;lt;*-
  o"  )~   Version 2.9.1 IPv6 GRE (Build 71)
   ''''    By Martin Roesch &amp;amp; The Snort Team:
http://www.snort.org/snort/snort-team
           Copyright (C) 1998-2011 Sourcefire, Inc., et al.
           Using libpcap version 1.1.1
           Using PCRE version: 8.12 2011-01-15
           Using ZLIB version: 1.2.5

hboetes&amp;lt; at &amp;gt;oink /etc/snort % l /var/log/snort/tcpdump.log.133*
-rw------- 1 root root 8.0M Mar 19 12:47
/var/log/snort/tcpdump.log.1332123032
hboetes&amp;lt; at &amp;gt;oink /etc/snort % stripcom snort.conf|grep tcpdump
output&lt;/pre&gt;</description>
    <dc:creator>Han Boetes</dc:creator>
    <dc:date>2012-03-19T11:59:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5136">
    <title>Deprecated support prelude on snort 2.9.3</title>
    <link>http://comments.gmane.org/gmane.comp.security.ids.snort.devel/5136</link>
    <description>&lt;pre&gt;Hi,

I have seen in the snort manual 2.9.2 that prelude plugin has considered 
deprecated in the next version 2.9.3.

This seems indicate that support of prelude will be not avaible anymore? 
is it true? why?

Thanks
&lt;/pre&gt;</description>
    <dc:creator>Albert Monfà</dc:creator>
    <dc:date>2012-02-28T08:45:22</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.security.ids.snort.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.security.ids.snort.devel</link>
  </textinput>
</rdf:RDF>

