-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alpn log/v3 #11204
Alpn log/v3 #11204
Conversation
For later logging and detection.
Part of the extended logging. Logs `client_alpns` and `server_alpns` arrays in the tls object. Ticket: OISF#7055.
Needs review, esp of log format. Also needs docs still. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11204 +/- ##
==========================================
- Coverage 82.98% 82.95% -0.03%
==========================================
Files 942 943 +1
Lines 250838 250641 -197
==========================================
- Hits 208147 207927 -220
- Misses 42691 42714 +23
Flags with carried forward coverage won't be shown. Click here to find out more. |
Information: QA ran without warnings. Pipeline 20894 |
The format looks good to me. What would be the alternative ?
|
I think this looks OK: "client_alpns": [
"h2",
"http/1.1"
],
"server_alpns": [
"http/1.1"
] I didn't find any prior art, but:
|
Replaced by #11325 |
SV_BRANCH=OISF/suricata-verify#1873
https://redmine.openinfosecfoundation.org/issues/7055
Looking for feedback on the logging format. From the test:
Replaces #11198, adding
tls.alpn
keyword.Example alert for rule
gives