You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ChangeLog.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,34 @@
1
+
# wolfSentry Release 0.4.0 (May 27, 2022)
2
+
3
+
Preview Release 0.4.0 of the wolfSentry embedded firewall/IDPS has bug fixes and new features including:
4
+
5
+
## New Features
6
+
7
+
* User-defined key-value pairs in JSON configuration: allows user plugins to access custom config parameters in the wolfSentry config using the new wolfsentry_user_value_*() family of API functions. Binary configuration data can be supplied in the configuration using base64 encoding, and are decoded at parse time and directly available to user plugins in the original raw binary form. The key-value facility also supports a custom validator callback to enforce constraints on user-defined config params in the JSON.
8
+
9
+
* User-defined address families: allows user plugins for custom address families and formats, using new wolfsentry_addr_family_*() API routines. This allows idiomatic formats for non-Internet addresses in the JSON config, useful for various buses and device namespaces.
10
+
11
+
* Formalization of the concepts of default events and fallthrough rules in the route tables.
12
+
13
+
* A new subevent action list facility to support logging and notifications around the final decisions of the rule engine, alongside the existing subevents for rule insertions, matches, and deletions.
14
+
15
+
* The main plugin interface (wolfsentry_action_callback_t) now passes two separate routes, a "trigger_route" with full attributes of the instant traffic, and a "rule_route" that matches that traffic. In dynamic rule scenarios, plugins can manipulate the passed rule_route and set the WOLFSENTRY_ACTION_RES_INSERT bit in the to define a new rule that will match the traffic thereafter. All actions in the chain retain readonly access to the unmodified trigger route for informational purposes.
16
+
17
+
* The JSON DOM facility from CentiJSON is now included in the library by default (disabled by make NO_JSON_DOM=1), layered on the SAX facility used directly by the wolfSentry core to process the JSON config package. The DOM facility can be used as a helper in user plugins and applications, for convenient JSON parsing, random access, and production.
18
+
19
+
20
+
## Noteworthy Changes
21
+
22
+
* In the JSON config, non-event-specific members of top level node "config-update" node have been moved to the new top level node "default-policies", which must appear after "event-insert". "default-policies" members are "default-policy-static", "default-policy-dynamic", "default-event-static", and "default-event-dynamic".
23
+
24
+
25
+
## Bug Fixes
26
+
27
+
* In wolfsentry_config_json_init(), properly copy the load_flags from the caller into the _json_process_state.
28
+
29
+
* The JSON SAX API routines (wolfsentry/centijson_sax.h) are now properly exported.
30
+
31
+
1
32
# wolfSentry Release 0.3.0 (Dec 30, 2021)
2
33
3
34
Preview Release 0.3.0 of the wolfSentry embedded firewall/IDPS has bug fixes and new features including:
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,7 @@
2
2
3
3
## Description
4
4
5
-
wolfSentry is the wolfSSL IDPS (Intrusion Detection and Prevention System). It
6
-
is mainly used as a library, but can also be used as part of a kernel module.
5
+
wolfSentry is the wolfSSL IDPS (Intrusion Detection and Prevention System). It is mainly used as a library, but can also be used as part of a kernel module.
7
6
8
7
At a high level, wolfSentry is a dynamically configurable logic hub, arbitrarily associating user-defined events with user-defined actions, contextualized by connection attributes, tracking the evolution of the client-server relationship. At a low level, wolfSentry is an embedded firewall engine (both static and fully dynamic), with O(log n) lookup of known hosts/netblocks.
9
8
@@ -57,8 +56,9 @@ Build and test libwolfsentry.a without support for multithreading:
57
56
58
57
`make -j SINGLETHREADED=1 test`
59
58
60
-
Other available make flags are `STATIC=1` and `STRIPPED=1`, and the defaults values
61
-
for `DEBUG`, `OPTIM`, and `C_WARNFLAGS` can also be usefully overridden.
59
+
Other available make flags are `STATIC=1`, `STRIPPED=1`, `NO_JSON=1`, and
60
+
`NO_JSON_DOM=1`, and the defaults values for `DEBUG`, `OPTIM`, and `C_WARNFLAGS`
61
+
can also be usefully overridden.
62
62
63
63
Build with a user-supplied makefile preamble to override defaults:
0 commit comments