-
Notifications
You must be signed in to change notification settings - Fork 35
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
X509 folder move, table improvement, update for v1.4.0 #104
base: main
Are you sure you want to change the base?
Conversation
…e for consistency with other logs.
dst_endpoint is no longer required in v1.4 and this is now viable Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
Signed-off-by: JW-Corelight <[email protected]>
How did you figure out the TLS extensions to map to? |
I think you're talking about the I gave them the exact name of the field they're coming from, assuming that's how they work. If I'm misuderstanding this, i'm happy to realign. |
My understanding was that the TLS extension names comes from the RFC: https://datatracker.ietf.org/doc/html/rfc8446#page-35. At least that's where the schema links. |
After reviewing this again, I think I'm seeing what you're saying here @mavam The TLS Extensions are used by the TLS protocol while the connection is set up, while the 'other' Zeek fields I'm attempting to fit into there are really just details about the cert itself. They seem to belong in the |
…t after consideration Signed-off-by: JW-Corelight <[email protected]>
Move x509 folder under version folder and reorg README table structure for consistency with other logs.