| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Remove JA3C output from ndpiReader (#2667) | Ivan Nardi | 2025-01-12 |
| | | | | | | | | | | | | | | Removing JA3C is an big task. Let's start with a simple change having an huge impact on unit tests: remove printing of JA3C information from ndpiReader. This way, when we will delete the actual code, the unit tests diffs should be a lot simpler to look at. Note that the information if the client/server cipher is weak or obsolete is still available via flow risk See: #2551 | ||
| * | ndpiReader: update JA statistics (#2646) | Ivan Nardi | 2025-01-06 |
| | | | | | Show JA4C and JA3S information (instead of JA3C and JA3S) See #2551 for context | ||
| * | STUN/RTP: improve metadata extraction (#2641) | Ivan Nardi | 2024-12-11 |
| | | |||
| * | ndpiReader: add some statistics about monitoring (#2602) | Ivan Nardi | 2024-10-19 |
| | | |||
| * | STUN: fix monitoring of Whatsapp and Zoom flows (#2590) | Ivan Nardi | 2024-10-15 |
| | | |||
| * | Add monitoring capability (#2588) | Ivan Nardi | 2024-10-14 |
| Allow nDPI to process the entire flows and not only the first N packets. Usefull when the application is interested in some metadata spanning the entire life of the session. As initial step, only STUN flows can be put in monitoring. See `doc/monitoring.md` for further details. This feature is disabled by default. Close #2583 | |||