Snort mailing list archives
Determining compile-time options after-the-fact
From: Mike Pilkington <MPilkington () lgc com>
Date: Thu, 29 Oct 2009 10:08:21 -0500
Is there a way to determine what compile-time options were invoked for a particular snort binary? I.e., say you have a pre-compiled snort binary from a package and want to know how it was compiled. Thanks, Mike ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
Current thread:
- X-Forwarded-For Carlos André (Oct 29)
- Determining compile-time options after-the-fact Mike Pilkington (Oct 29)
- Re: Determining compile-time options after-the-fact Russ Combs (Oct 29)
- Re: X-Forwarded-For San Mallissery (Nov 06)
- Determining compile-time options after-the-fact Mike Pilkington (Oct 29)