Pull request #3384: doc : Update user manual and dev_notes for default binder

Merge in SNORT/snort3 from ~VHORBAN/snort3:doc_update_default_binder_info to master

Squashed commit of the following:

commit 19a85009ceda81bf170a6b7728089f9f4f274f25
Author: Volodymyr Horban <vhorban@cisco.com>
Date:   Tue Apr 19 18:07:03 2022 +0300

    doc: add clarification on default bindings in developer notes and user notes

diff --git a/doc/user/binder.txt b/doc/user/binder.txt
index 4c5d686facb122ce97ef91a402eb6af2d83443bd..0ee4b6566247a3f5a3e2b9c542773a699535f897 100644 (file)
--- a/doc/user/binder.txt
+++ b/doc/user/binder.txt
@@ -48,3 +48,7 @@ configurations are applied.  binder.when can contain any combination of
 criteria and binder.use can specify an action, config file, or inspector
 configuration.
 
+If binder is not explicitly configured (via file *.lua or option --lua),
+a default binder will be instantiated in which bindings will be created for all
+service inspectors configured. Some bindings may require a configured wizard to
+detect the service type.
\ No newline at end of file

diff --git a/src/network_inspectors/binder/dev_notes.txt b/src/network_inspectors/binder/dev_notes.txt
index 9898312fdcc0f445341c8e6ad1d2724aabd3c634..763236d8ec706ae312a9516814366ea3666e42b9 100644 (file)
--- a/src/network_inspectors/binder/dev_notes.txt
+++ b/src/network_inspectors/binder/dev_notes.txt
@@ -5,7 +5,7 @@ bound to the flow.
 
 If the binder is not explicitly configured but the wizard is configured,
 then the inspector manager will create a default binder with bindings for
-each configured service inspector.
+each configured service inspector (excluding wizard itself).
 
 BinderModule creates a vector of Bindings from the Lua binder table which
 is moved to the Binder upon its construction.  Upon start of flow, the