Version to 2.4.0, minor doc tweaks. References to threat-exchanges repo.

Author: cybermaggedon

configure.ac

@@ -2,7 +2,7 @@
 # Process this file with autoconf to produce a configure script.
 
 AC_PREREQ([2.68])
-AC_INIT([cyberprobe], [2.3.14], [cyberprobe-discussion@googlegroups.com])
+AC_INIT([cyberprobe], [2.4.0], [cyberprobe-discussion@googlegroups.com])
 AM_INIT_AUTOMAKE([-Wall -Werror subdir-objects foreign])
 AC_CONFIG_SRCDIR([src/cyberprobe.C])
 AC_CONFIG_HEADERS([config.h])

docs/history.texi

@@ -6,6 +6,10 @@ Cyberprobe release highlights:
 
 @table @code
 
+@item 2.4
+@command{cybermon-detector} refactored to use FSM-based evaluation of
+boolean expressions.
+
 @item 2.3
 @command{cyberprobe-cli} and control API reworked, protobuf and gRPC support.
 Amazon Linux support.

docs/qs-threat-indicators.texi

@@ -20,12 +20,6 @@ The installation bundle includes a a file containing some
 sample indicators, search for @file{indicators.json}, which may be installed
 at @file{@value{PREFIX}/share/doc/cyberprobe}.
 
-
-
-
-
-
-
 @heading Deploying theat information to @command{cybermon}
 
 To run using your existing processing pipeline, stop any running
@@ -101,6 +95,9 @@ For more information on indicators, see
 @ref{@command{cybermon-detector} invocation} and
 @ref{Cyberprobe indicator format}.
 
+See @url{https://github.com/cybermaggedon/threat-exchanges} for code which
+creates indicator sets from threat exchanges.
+
 @heading Conclusion
 
 All done, I hope you enjoyed the tutorial! Any comments on the software, or

docs/ref-indicators.texi

@@ -212,3 +212,7 @@ The @samp{not} construct is true if its child is false.
 @}
 @end example
 
+@heading Threat exchanges
+
+See @url{https://github.com/cybermaggedon/threat-exchanges} for code which
+creates indicator sets from threat exchanges.