![]() | This article has multiple issues. Please help
improve it or discuss these issues on the
talk page. (
Learn how and when to remove these template messages)
|
Transport Layer Security Channel ID (TLS Channel ID, previously known as Transport Layer Security – Origin Bound Certificates TLS-OBC) [1] is a draft RFC proposal [2] [3] Transport Layer Security (TLS) extension that aims to increase TLS security by using certificates on both ends of the TLS connection. Notably, the client is permitted to dynamically create a local, self-signed certificate that provides additional security.
It can also protect users from the related domain cookie attack. [4][ unreliable source?] [5][ unreliable source?]
Token Binding is an evolution of the TLS Channel ID feature, [6] and the IETF draft has Microsoft and Google as authors. [7]
{{
cite web}}
: |author=
has generic name (
help)CS1 maint: multiple names: authors list (
link)
![]() | This article has multiple issues. Please help
improve it or discuss these issues on the
talk page. (
Learn how and when to remove these template messages)
|
Transport Layer Security Channel ID (TLS Channel ID, previously known as Transport Layer Security – Origin Bound Certificates TLS-OBC) [1] is a draft RFC proposal [2] [3] Transport Layer Security (TLS) extension that aims to increase TLS security by using certificates on both ends of the TLS connection. Notably, the client is permitted to dynamically create a local, self-signed certificate that provides additional security.
It can also protect users from the related domain cookie attack. [4][ unreliable source?] [5][ unreliable source?]
Token Binding is an evolution of the TLS Channel ID feature, [6] and the IETF draft has Microsoft and Google as authors. [7]
{{
cite web}}
: |author=
has generic name (
help)CS1 maint: multiple names: authors list (
link)