Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.

4 лет назад
4 лет назад
4 лет назад
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. SNFServer is a basic Message Sniffer "service" that provides scanning via the XCI protocol.
  2. The most common way to use it is with SNFClient, but you can also build your own software to
  3. call the XCI endpoint directly. Generally, the client makes a tcp connection, tells SNFServer
  4. where the message file is, and gets back a scan result... all in simple XML.
  5. # Changelog / Journal
  6. ## 20200623_M [Server 3.2.2, Engine 3.2.2]
  7. - Removed saccades algorithm to provide more comprehensive scanning. This will allow SNF to
  8. operate as a feature extractor for machine learning algorithms by matching "above-band" rules
  9. that do not compete with normal "in-band" rules.
  10. The growing use of above-band rule groups like "Experimental Bulk/Noisy" and additional groups
  11. for machine learning feature extraction has changed the paradigm for heuristic competition in
  12. the SNF world. Where previously it was important to optimize scanning performance for low-powered
  13. hardware and heuristic competition could add pressure to select for more efficient rules; the
  14. new paradigm requires that any available patterns will match (at least once) and hardware
  15. constraints are no longer a serious concernt. For example, SNF is easily able to operate at
  16. scanning rates that are 3 orders of magnitude higher than most deployments require on modern
  17. equipment.
  18. This isn't to say that heuristic efficiency optimization will be going away -- but rather that
  19. the mechanisms for optimizing that efficiecncy can be moved more toward the back-end so that
  20. the front-end scanners can concentrate on making all available matches available for analysis
  21. and even more sophisticated learning algorithms.
  22. Saccades was fun, and effective, but it's time has passed.
  23. ## 20200622_M
  24. - encapsulated all codedweller in namespace codedweller
  25. - removed all using namespace std
  26. - got a clean build (saccades still commented out, but not cleanly removed)
  27. ## 20200618_M
  28. - Cleaned up all warnings in the build with the latest g++
  29. - Added SOP for installing the latest g++ in ubuntu
  30. - Added SOP for upgrading libstdc++6 on target ubuntus
  31. Additional note: Using RESTsnf as a test jig measured throughput at 8064/minute.
  32. However, this was only a single data point so only gives us a ballpark, and
  33. most systems operate at least 2 orders of magnitude below this message rate.
  34. Using the same test jig measured 7960/minute throughput with saccades off.
  35. Allowed the torture test to run so newer data would be in play and after 5 minutes
  36. measured 7806/minute. Here are a few more numbers:
  37. 2113 7279.7
  38. 2114 6084.89
  39. Conclusion is that performance penalty for disabling saccades is not significant.
  40. ## 20200617_M
  41. - Set up the readme.md file
  42. - Set up basic build structures for "the new way" of making all things SNF.