I do not recall upgrading How can I tell the version that I am running?
thanks Harry Vanderzand Intown Internet 11 Belmont Ave. W. Kitchener, ON, N2M 1L2 519-741-1222 -----Original Message----- From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil Sent: Saturday, January 12, 2008 12:09 PM To: Message Sniffer Community Subject: [sniffer] Re: SNF V2-9b1.5 Released - Please Upgrade Hello David, When using snfupd with the new version you can skip the line that tells SNF to reload. REM %LicenseID%.exe reload Most likely the error you received is because there is no executable named for your license ID. This is ok with the new version. The snfupd.cmd script was originally written to work with version 2 which does require "branding" the SNF executable. The new version of SNF does not require branding. Also, the new version will very quickly recognize that there is a new rulebase file and will load it automatically so there is no reason (nor facility) to notify it about the update. Hope this helps, _M Saturday, January 12, 2008, 11:21:37 AM, you wrote: > Ok I have most off this working with Imail 8.22 > So far this is what I have done > Copied, unpacked RImailSnifferUpdateTools.zip, edited snfupd.cmd and setup > task schedule. > Which generates an from the snfupd.cmd C:\SNF>>snfupd.cmd > 'mylicencekeynotshownhere.exe' is not recognized as an internal or external > command, > operable program or batch file. > REM Load new rulebase file. > %LicenseID%.exe reload > So how do I get the SNFserver to update with the latest .snf file. > Regards David Moore > [EMAIL PROTECTED] > J.P. MCP, MCSE, MCSE + INTERNET, CNE. > www.adsldirect.com.au for ADSL and Internet www.romtech.com.au for PC sales > Office Phone: (+612) 9453 1990 > Fax Phone: (+612) 9453 1880 > Mobile Phone: +614 18 282 648 > Skype Phone: ADSLDIRECT > POSTAL ADDRESS: > PO BOX 190 > BELROSE NSW 2085 > AUSTRALIA. > --------------------------------------------------------------------- > This email message is only intended for the addressee(s) and contains > information that may be confidential, legally privileged and/or copyright. > If you are not the intended recipient please notify the sender by reply > email and immediately delete this email. Use, disclosure or reproduction of > this email, or taking any action in reliance on its contents by anyone other > than the intended recipient(s) is strictly prohibited. No representation is > made that this email or any attachments are free of viruses. Virus scanning > is recommended and is the responsibility of the recipient. > --------------------------------------------------------------------- > -----Original Message----- > From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On Behalf > Of Pete McNeil > Sent: Thursday, 18 October 2007 9:58 AM > To: Message Sniffer Community > Subject: [sniffer] SNF V2-9b1.5 Released - Please Upgrade > Hello Sniffer folks, > Please find the latest SNF V2-9 distribution files here: > http://kb.armresearch.com/index.php?title=Message_Sniffer.GettingStarted.Dis > tributions#NEW_SNF_V2-9_Wide_Beta > If you are running a previous version of SNF V2-9, please upgrade as > soon as possible. > The newest version includes some bug fixes. From the change log: > 20071017 - SNF2-9b1.5.exe > Added a missing #include directive to the networking.hpp file. The > missing #include was not a factor on Linux and Windows systems but > caused compiler errors on BSD systems. > Corrected a bug in the GBUdb White Range code where any message with a > white range source IP was being forced to the white result code. The > engine now (correctly) only forces the result and records the event when > a black pattern rule was matched and the White Range IP causes that > scan result to be overturned. If the scan result was not a black pattern > match then the original scan result is allowed to pass through. > Corrected a bug in the Header Analysis filter chain module that would > cause the first header in the message to be ignored in some cases. > Corrected an XML log format problem so that <s/> elements are correctly > open ended <s ....> or closed (empty) <s..../> according to whether they > have subordinate elements. > Adjusted the GBUdb header info format. The order of the Confidence > figure and Probabilty figure is now the same as in the XML log files > (C then P). The confidence and probability figures are now preceeded > with c= and p= respectively so that it's easy to tell which is which. > Thanks! > _M -- Pete McNeil Chief Scientist, Arm Research Labs, LLC. ############################################################# This message is sent to you because you are subscribed to the mailing list <sniffer@sortmonster.com>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]> ############################################################# This message is sent to you because you are subscribed to the mailing list <sniffer@sortmonster.com>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
