Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | config: follow-up (#2268) | Ivan Nardi | 2024-01-20 |
| | | | | | | Some changes in the parameters names. Add a fuzzer to fuzz the configuration file format. Add the infrastructure to configuratin callbacks. Add an helper to map LRU cache indexes to names. | ||
* | config: allow configuration of guessing algorithms | Nardi Ivan | 2024-01-18 |
| | |||
* | config: move debug/log configuration to the new API | Nardi Ivan | 2024-01-18 |
| | |||
* | config: DNS: add two configuration options | Nardi Ivan | 2024-01-18 |
| | | | | | * Enable/disable sub-classification of DNS flows * Enable/disable processing of DNS responses | ||
* | config: HTTP: enable/disable processing of HTTP responses | Nardi Ivan | 2024-01-18 |
| | |||
* | config: configure TLS certificate expiration with the new API | Nardi Ivan | 2024-01-18 |
| | |||
* | config: remove `enum ndpi_prefs` | Nardi Ivan | 2024-01-18 |
| | |||
* | config: remove `ndpi_set_detection_preferences()` | Nardi Ivan | 2024-01-18 |
| | |||
* | config: move cfg of aggressiviness and opportunistic TLS to the new API | Nardi Ivan | 2024-01-18 |
| | |||
* | config: move IP lists configurations to the new API | Nardi Ivan | 2024-01-18 |
| | |||
* | config: move LRU cache configurations to the new API | Nardi Ivan | 2024-01-18 |
| | |||
* | New API for library configuration | Nardi Ivan | 2024-01-18 |
This is the first step into providing (more) configuration options in nDPI. The idea is to have a simple way to configure (most of) nDPI: only one function (`ndpi_set_config()`) to set any configuration parameters (in the present or on in the future) and we try to keep this function prototype as agnostic as possible. You can configure the library: * via API, using `ndpi_set_config()` * via a configuration file, in a text format This way, anytime we need to add a new configuration parameter: * we don't need to add two public functions (a getter and a setter) * we don't break API/ABI compatibility of the library; even changing the parameter type (from integer to a list of integer, for example) doesn't break the compatibility. The complete list of configuration options is provided in `doc/configuration_parameters.md`. As a first example, two configuration knobs are provided: * the ability to enable/disable the extraction of the sha1 fingerprint of the TLS certificates. * the upper limit on the number of packets per flow that will be subject to inspection |