[prev in list] [next in list] [prev in thread] [next in thread] 

List:       snort-users
Subject:    Re: [Snort-users] deciding between Snort2 and Snort3
From:       "Joel Esler \(jesler\) via Snort-users" <snort-users () lists ! snort ! org>
Date:       2020-02-04 18:30:15
Message-ID: 22C40B62-EC7D-4A5F-9C0C-240BD65389FF () cisco ! com
[Download RAW message or body]

Hello Paul,

I would start looking at Snort 3 if I were in your position.


-- 
Joel Esler
Manager, Communities Division
Cisco Talos Intelligence Group
http://www.talosintelligence.com

> On Feb 3, 2020, at 3:43 PM, Paul M via Snort-users <snort-users@lists.snort.org> wrote:
> 
> For a networking product integrating Snort app-id to be released in ~6
> months, is there some guidance on which version to use?  Snort 2 is
> presumably more stable, but it looks like Snort 3 has better
> performance and features and will be supported further into the
> future.  Is it advisable to use Snort 3 in its alpha stage for a
> finished product?  Is there any estimated release date?
> 
> Thanks.
> -Paul Mathison
> _______________________________________________
> Snort-users mailing list
> Snort-users@lists.snort.org
> Go to this URL to change user options or unsubscribe:
> https://lists.snort.org/mailman/listinfo/snort-users
> 
> 	To unsubscribe, send an email to:
> 	snort-users-leave@lists.snort.org
> 
> Please visit http://blog.snort.org to stay current on all the latest Snort news!
> 
> Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette

_______________________________________________
Snort-users mailing list
Snort-users@lists.snort.org
Go to this URL to change user options or unsubscribe:
https://lists.snort.org/mailman/listinfo/snort-users

	To unsubscribe, send an email to:
	snort-users-leave@lists.snort.org

Please visit http://blog.snort.org to stay current on all the latest Snort news!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette
[prev in list] [next in list] [prev in thread] [next in thread]