TLS Session Fields
See original GitHub issueIs there already a consensus as to where to place session properties for TLS sessions? I found some reference to a tls
subtree in #64, but nothing in the schema itself.
Will there be some session.tls
group or the like with TLS session related fields, eg. protocol versions, ciphers, session identifier, and the like?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
What happens in a TLS handshake? | SSL ... - Cloudflare
In a TLS/SSL handshake, clients and servers exchange SSL certificates, cipher suite requirements, and randomly generated data for creating session keys.
Read more >Networking 101: Transport Layer Security (TLS)
TLS runs over a reliable transport (TCP), which means that we must first complete the TCP three-way handshake, which takes one full roundtrip....
Read more >Traffic analysis of a TLS session - Seb's IT blog
In this post I want to show what happens at the protocol level when we use SSL/TLS. It is important to note that...
Read more >TLS Session Tickets - IETF
Standards Track [Page 1] RFC 5077 Stateless TLS Session Resumption January 2008 ... The extension_data field of SessionTicket extension contains the ticket.
Read more >Transport Layer Security - Wikipedia
DescriptionEdit · The handshake begins when a client connects to a TLS-enabled server requesting a secure connection and the client presents a list...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the hint.
The field list in Packetbeat is fairly exhaustive. The only missing field for our use case is the verification result of the provided client certificate (which is really an application property and nothing available on network level), so for the sake of completeness something like:
And for the certificate attributes I specifically miss
(L)ocality
andStreet
, which can be ocasionally seen in the wild.Ok, fine for me.