somethingnew
✨ https://twitter.com/itspeterc
[ my public key: https://keybase.io/petercollins; my proof: https://keybase.io/petercollins/sigs/yeZIba2qpUOE6XzgjubdowDhvETHlA7rcczXFu-u9c8 ]
📅 Joined in 2012
🔼 633 Karma
✍️ 111 posts
🌀
15 latest posts
Load more
👤somethingnew🕑1y🔼2🗨️0
👤somethingnew🕑3y🔼1🗨️0
👤somethingnew🕑9y🔼2🗨️0
👤somethingnew🕑9y🔼4🗨️0
(Replying to PARENT post)
👤somethingnew🕑10y🔼0🗨️0
Show HN:
👤somethingnew🕑10y🔼2🗨️1
👤somethingnew🕑10y🔼3🗨️0
(Replying to PARENT post)
Besides Session IDs and Session Tickets[1] which already exist in the TLS protocol. He could be referring to the Token Binding Protocol Draft[2] which, quoting from it's summary, "allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections".
[1] https://en.wikipedia.org/wiki/Transport_Layer_Security#Resum...
[2] https://tools.ietf.org/html/draft-ietf-tokbind-protocol-01
👤somethingnew🕑10y🔼0🗨️0
👤somethingnew🕑10y🔼8🗨️1
👤somethingnew🕑10y🔼3🗨️0
(Replying to PARENT post)
Not having to worry about calculating the length of the message before transferring it?
👤somethingnew🕑10y🔼0🗨️0
(Replying to PARENT post)