suricata
Here are 104 public repositories matching this topic...
-
Updated
Oct 28, 2020 - Shell
-
Updated
Nov 30, 2020 - Python
-
Updated
Aug 18, 2020
-
Updated
Apr 15, 2020 - C
-
Updated
Oct 26, 2020 - Lua
-
Updated
Aug 3, 2020 - Python
-
Updated
Jun 30, 2018 - Python
-
Updated
Jul 25, 2020 - Shell
-
Updated
Jan 13, 2020 - Go
-
Updated
Sep 22, 2020 - Go
-
Updated
Dec 4, 2020 - Python
-
Updated
Mar 17, 2020 - Jupyter Notebook
-
Updated
Aug 7, 2020 - C
-
Updated
Sep 21, 2020
-
Updated
Jul 13, 2020 - Shell
-
Updated
Oct 21, 2020 - C
-
Updated
Dec 3, 2020 - C++
-
Updated
Aug 29, 2020
-
Updated
Jul 28, 2020 - C
It would be great to match against known bad TLS certificate fingerprints and/or serial numbers with a bloomfilter. I see to possibilities here:
- Include bad fingerprints/serial numbers in default bloomfilter and match against the belonging fields in tls eve output.
- Include bad fingerpints/serial numbers in a sort of blacklist and match against the fingerprint/serial number feld in tls eve
Improve this page
Add a description, image, and links to the suricata topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the suricata topic, visit your repo's landing page and select "manage topics."


At the moment, we have some first unit tests. This is fine to check correctness at a fine granularity.
It would be nice as well to have a test case running somewhere that tests a combination of inputs against an actual backend and checks whether queries are correct, both using the GraphQL frontend and backend-specific query methods.