您最多选择25个主题 主题必须以字母或数字开头,可以包含连字符 (-),并且长度不得超过35个字符

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368
  1. SNF Command Line & SNFMulti Engine / Client Change Log
  2. ------------------------------------------------------------------------------
  3. 20080626 - Version 3.0, It's official.
  4. Changed build information.
  5. 20080524 - Version V2-9rc2.25.7
  6. Optimized networking library for additional speed & stability by moving
  7. receive buffer allocation from heap to stack (automatic).
  8. Optimized timing parameters in SNFClient for improved speed. Polling dealys
  9. are now reduced to 10ms from 30ms.
  10. Removed speed-bug in SNFClient, 100ms guard time between retries was always
  11. executed after an attempt (even a successful attempt). The guard time is now
  12. condition and only fires on unsuccessful attempts.
  13. Updated XCI server logic to ensure non-blocking sockets for clients in all
  14. socket implementations.
  15. 20080424 - Version V2-9rc2.24.6
  16. Refactored snfScanData.clear() to reduce heap work and fragments.
  17. Added mutex to scanMessageFile() entry point just in case some app attempts to
  18. put multiple threads through a single engine handler. scanMessage() is already
  19. protected and fully wraped by the new scanMessageFile() mutex.
  20. Added non-specific runtime exception handling to XHDR injection code.
  21. Added 2 retries w/ 300ms delay to remove original message in XHDR inject code.
  22. If remove fails after 3 attempts the injector throws.
  23. Added 2 retries w/ 300ms delay to rename temp file to msg in XHDR inject code.
  24. If rename fails after 3 attempts the injector throws.
  25. 20080416 - Version V2-9rc2.23.6
  26. Fixed bug where SNCY open() would fail on some Win* platforms with
  27. WSAEINVAL instead of the standard EINPROGRESS or EALREADY which were expected.
  28. Also added WSAEWOULDBLOCK to cover other "ambiguities" in windows sockets
  29. implementations. InProgress() on Win* now test for any of:
  30. WSAEINPROGRESS, WSAEALREADY, WSAEWOULDBLOCK, WSAEINVAL
  31. 20080413 - Version V2-9rc2.22.6
  32. Fixed bug in TCPHost.open() where EALREADY was not counted as a version of
  33. EINPROGRESS. This would cause open() to throw an unnecessary exception when
  34. an open() required extra time.
  35. 20080413 - Version V2-9rc2.21.6
  36. Extended timeout for SYNC session open() to the full session length. This way
  37. if a session takes a long time to open it still has a shot at success.
  38. 20080411 - Version V2-9rc2.20.6
  39. Adjusted snfNETmgr to use non-blocking open in SYNC sessions. Open timeout
  40. is 1/3 of the session timeout. Session timeout is 2 * Session pacing. Open
  41. polling uses golden spiral delay from 10ms to 340ms.
  42. 20080410 - Version V2-9rc2.19.6
  43. Adjusted XCI manager to use new snfCFGPacket paradigm in checkCFG().
  44. Adjusted snf_RulebaseHandler::addRulePanic() to use MyMutex and eliminated
  45. the AutoPanicMutex and waiting scheme.
  46. Refactored scanMessage() to use a ScopeMutex() rather than lock()/unlock().
  47. Refactored scanMessage() to use MyCFGPacket.isRulePanic() test.
  48. Redesigned snfCFGPacket handling to automate grab() / drop() functions.
  49. Fixed lock-up bug: Redesigned AutoPanic posting and checking mechanisms to
  50. eliminate potential dead-lock condition. Under some conditions a precisely
  51. timed auto-panic posting could cause the RulebaseHandler mutex and the
  52. AutoPanicMutex to become intertwined leading to a cascading deadlock. When
  53. this occurred all XCI processing threads and eventually the XCI listener
  54. thread would become blocked waiting to get the current configuration.
  55. 20080409 - Version V2-9rc2.18.6
  56. Enhanced XCI exception handling and logging to provide additional detail.
  57. Added code to explicitely check for zero length files in scanMessagFile().
  58. Previously a zero length file would cause the CBFR module of the filter
  59. chain to throw an invalid buffer exception. Now if the message file is empty
  60. scanMessageFile() will throw a FileError stating FileEmpty!.
  61. 20080407 - Version V2-9rc2.17.6
  62. Enhanced exception reporting in snfXCImrg
  63. 20080405 - SNFServer V2-9rc2.16.6
  64. Reduced safetly limits on status reports to 100K for status reports and 100K
  65. for samples. Previous values were 10M. Most full sessions from the busiest
  66. systems are < 50K total.
  67. Recoded sendDataTimeout() to break uploads into 512 byte chunks and insert
  68. delays only when a chunk is fragmented. This methodology improves reliability
  69. on Win* systems without any significant penalty on systems that don't need
  70. socket sends() to be in smaller chunks.
  71. Fixed TCPClient::transmit() and TCPHost::transmit() bug where returned byte
  72. count might be -1. Now returned byte counts can only be 0 or more.
  73. 20080403 - SNFServer V2-9rc2.15.5
  74. Minor modifications to networking module to better support non-blocking open()
  75. Updated SNFClient with new timing and non-blocking open(). Worst case return
  76. time from SNFClient estimated at 200 seconds (theoretically impossible). No-
  77. connection return time from SNFClient estimated at 20 seconds.
  78. 20080326 - SNFServer V2-9rc2.15.4
  79. Refactored snfNETmgr::sync() to consolidate non-blocking io routines.
  80. Added detailed thread status data to XCI listener thread.
  81. Fixed minor bug in main (not changing revision), Debug flag for internal use
  82. was left on in the last build cycle. It is commented out now.
  83. 20080325 - SNFServer V2-9rc2.14.4
  84. Updated snfNETmgr with comprehensive thread status data.
  85. Refactored snfNETmgr::sync() to check a Timeout, removed TCPWatchdog.
  86. 20080325 - SNFServer V2-9rc2.13.4
  87. Upgraded TCPWatcher code to use new threading features (type, status).
  88. 20080324 - SNFServer v2-9rc2.12.4
  89. Added a "Rulebase Getter" feature as part of the snf_Reloader. When enabled
  90. the Rulebase Getter will launch a user defineable system() call whenever a
  91. new rulebase file is available. The call will be repeated until the condition
  92. is cleared by a successful update of the rulebase file. The Rulebase Getter
  93. will wait a configurable "guard time" between attempts. The default system()
  94. call is "getRulebase" with a guard time of 3 minutes. In most cases this will
  95. launch the provided getRulebase script which should be present in the start
  96. location of SNFServer on most systems. Best practice is to configure the full
  97. path to the update script. The system() call is made in a separate thread so
  98. that if the system() call hangs for some reason only the Rulebase Getter is
  99. stuck.
  100. Built thread monitoring function for SNFServer.exe (Full status report / sec).
  101. The thread monitoring report is turned on when the program is renamed to
  102. SNFDebugServer.exe or if "debug" appears in the file path to the program.
  103. Refactored XCI channels to leverage new thread monitoring.
  104. Refactored Threading to eliminate inline code.
  105. Improved exception handling/reporting in scanMessageFile().
  106. Updated scanMessagFile() header injection code to accommodate messages with
  107. no body. Previous version would throw an exception when it could not find an
  108. injection point. The new version makes the injection point byte 0 and puts
  109. the injected headers at the top of the message using it's best guess about the
  110. type of line endings (CRLF or LF) to use.
  111. Updated Threading library to include high level thread state tracking and
  112. naming. Also creates a global Threads object that can produce a real-time
  113. status report on all threads.
  114. Updated Networking library to use SO_REUSEADDR by default on listeners.
  115. 20080318 - SNF2-9rc1.11.exe Consolidated several mods/fixes
  116. Corrected scan error logging bug. Was posting <s/> now posts <e/>.
  117. Updated scan error logging to be more uniform with non-scan errors.
  118. Developed various script prototypes for postfix integration & automated
  119. updates on win* systems using the new UpdateReady.txt file mechanism.
  120. Fixed a bug in scanMessageFile() where an \n\n style insertion point
  121. would never be detected.
  122. Modified scanMessageFile() header injection to strip <CR> from line ends
  123. when the message file provided does not use them. The line-end style of
  124. the message file is detected while locating the insertion point. If the
  125. insertion point (first blank line) does not use <CR><LF> then the SNF
  126. generated X-Headers are stripped of <CR> in a tight loop before injection.
  127. Enhanced error and exception reporting in SNFMulti.cpp scanMessageFile().
  128. Enhanced exception handling in networking module. All exceptions now
  129. throw descriptive runtime_error exceptions.
  130. 20080306 - SNF2-9rc1.8.exe (FIRST RELEASE CANDIDATE for VERSION 3!)
  131. Added Drilldown Header Directive Functions - When the candidate source IP
  132. comes from a header matching a drilldown directive the IP is marked "Ignore"
  133. in GBUdb and the candidate is no longer eligible to be the source for that
  134. message. This allows SNF to follow the trusted chain of devices (by IP) down
  135. to the actual source of the message. It is handy for ignoring net blocks
  136. because it can match partial IPs but it is designed to allow SNF to learn
  137. it's way through the servers at large ISPs so that the original source for
  138. each message can be evaluated directly.
  139. Added Source Header Directive Functions - This feature allows SNF to acquire
  140. the source IP for a message from a specific header rather than searching
  141. through the Received headers in the message. This is useful when the original
  142. source for a message is not represented in Received headers. For example:
  143. Hotmail places the originating source IP in a special header and does not
  144. provide a Received header for that IP. This feature is protected from abuse
  145. by a "Context" feature which only activates the source header directive when
  146. specific content is found in a specific received header. Using the above
  147. example, this feature can be configured so that a Hotmail source header would
  148. only be read if the top Recieved header contained "hotmail.com [" indicating
  149. that the ptr lookup for the header matched the hotmail domain. Note: When a
  150. source is pulled from a header directive that source is put into a synthetic
  151. Received header and injected into the scanning stream (not the message) as
  152. the first Received header.
  153. Added forced source IP to XCI - It is now possible to "inject" or "force"
  154. the source IP for any message by providing that IP in the XCI request or
  155. directly in a scan...() function call. This allows the calling application
  156. to provide the source IP for a message ahead of any Received headers that
  157. might be in the message. This is useful when the calling application knows
  158. the original source IP for the message but that IP is not represented in
  159. the Received headers and it is not desireable to use the Source Header
  160. Directive mechanism.
  161. Added forced source IP mode to SNFClient - It is now possible to call the
  162. SNFClient utility with an IP4Address using the syntax:
  163. SNFClient -source=12.34.56.78
  164. The -source mode of SNFClient exercises the forced source IP feature in
  165. the XCI (see above)
  166. Added Status Report features to SNFClient and XCI - It is now possible to
  167. request the latest status.second, status.minute, or status.hour data via
  168. the XCI and SNFClient. The syntax for requesting a status report using the
  169. SNFClient is:
  170. SNFClient -status.second
  171. SNFClient -status.minute
  172. SNFClient -status.hour
  173. In addition to providing status reports the SNFClient in this mode will
  174. return a nonzero value (usually 99) if it is unable to get a status report
  175. from SNFServer. This feature can be used to verify that SNFServer is up
  176. and responding. If SNFServer is OK then the result code returned is 0.
  177. Added result codes to SNFClient -test and XCI IP test functions - The XCI
  178. engine has been upgraded to provide the range value for the IP under test
  179. as well as the symbolic result code associated with that range. This allows
  180. the -test function to provide results that are consistent with the GBUdb
  181. configuration without additional processing: For example, if the IP falls
  182. in the Caution range then the Caution result code will be returned just
  183. as if a message had been scanned with the same IP and no pattern match
  184. occurred. The same is true for Truncate and Black range hits.
  185. Added Timestamp and Command Line Parameter data to SNFClient.exe.err - When
  186. an error occurs with SNFClient that may not appear in the SNFServer logs an
  187. entry is appended to the SNFClient.exe.err file. That in itself is not new.
  188. The new feature is that the entries added to the SNFClient.exe.err file now
  189. include timestamp and command line data to aid in debugging.
  190. Added BIG-ENDIAN Conversion - When the SNFServer program is compiled on a
  191. system that uses a BIG-ENDIAN processor (such as a power-mac) the rulebase
  192. load process now includes a routine to convert the token matrix from it's
  193. native LITTLE-ENDIAN format to a BIG-ENDIAN format. This solves a bug where
  194. Power-Mac (and presumably other BIG-ENDIAN systems) could compile and run
  195. the SNF* software but were unable to capture spam because the token matrix
  196. in the rulebase file was misinterpreted.
  197. Note: The BIG-ENDIAN Conversion feature is still considered experimental
  198. because it has not yet been thoroughly tested.
  199. Updated the Configuration Log to include all of the current configuration
  200. features and to improve it's readability.
  201. 20080207 - SNF2-9b1.7.exe
  202. SYNC Timeout now 2x SYNC Schedule
  203. SNFServer now produces an UpdateReady.txt file when the UTC timestamp on
  204. the SYNC server is newer than the UTC timestamp of the active rulebase. It
  205. is presumed that a suitable update script or program will run periodically
  206. and download a fresh rulebase file if the UpdateReady.txt file is present.
  207. The update script should remove the UpdateReady.txt file when it completes
  208. a successful download of the new rulebase file.
  209. Added available rulebase UTC in status reports <udate utc.../>
  210. Added Automatic path fixup for ending / or \
  211. Added option to use local time in log rotation <rotation localtime='no'/>
  212. The default is still utc.
  213. 20071102 - SNF2-9b1.6.exe
  214. Increased MAX_EVALS from 1024 to 2048.
  215. Adjusted defult range envelopes in snf_engine.xml to be more conservative.
  216. 20071017 - SNF2-9b1.5.exe
  217. Added a missing #include directive to the networking.hpp file. The
  218. missing #include was not a factor on Linux and Windows systems but
  219. caused compiler errors on BSD systems.
  220. Corrected a bug in the GBUdb White Range code where any message with a
  221. white range source IP was being forced to the white result code. The
  222. engine now (correctly) only forces the result and records the event when
  223. a black pattern rule was matched and the White Range IP causes that
  224. scan result to be overturned. If the scan result was not a black pattern
  225. match then the original scan result is allowed to pass through.
  226. Corrected a bug in the Header Analysis filter chain module that would
  227. cause the first header in the message to be ignored in some cases.
  228. Corrected an XML log format problem so that <s/> elements are correctly
  229. open ended <s ....> or closed (empty) <s..../> according to whether they
  230. have subordinate elements.
  231. Adjusted the GBUdb header info format. The order of the Confidence
  232. figure and Probabilty figure is now the same as in the XML log files
  233. (C then P). The confidence and probability figures are now preceeded
  234. with c= and p= respectively so that it's easy to tell which is which.
  235. 20071009 - SNF2-9b1.4.exe
  236. Tightened up the XCI handler code and removed the watchdog. The watchdog
  237. would restart the listener if there were no connections in 5 minutes. It
  238. was originally added to provide additional stability, however in practice
  239. there have been no "stalled listeners". Also, a stalled listener would
  240. likely be a sign of a different problem that the watchdog would tend to
  241. hide.
  242. Modified and refactored the XCI configuration management code. All XCI config
  243. changes and up-down operations are now handled in a single function except
  244. upon exit from the main XCI thread where XCI_shutdown() is always called.
  245. Added some more detailed exception handling code to the XCI component so that
  246. more data will be logged in the event of an error.
  247. 20071008 - SNF2-9b1.2.exe
  248. Added support for passing Communigate Message Files directly. Communigate adds
  249. data to the top of the message file. That data stops at the first blank line and
  250. the rfc822 message begins. The SNFServer engine can now be told to ignore this
  251. extra data using the following option:
  252. <msg-file type='cgp'/> <!-- type='cgp' for communigate message files -->
  253. If the msg-file type is anything other than 'cgp' then it will treat the message
  254. file as a standard rfc822 message in the usual way. The default setting is
  255. <msg-file type='rfc822'/>