Edit

Page

Page title:

Page body:

[1] [CITE@en[draft-balfanz-tls-obc-01 - TLS Origin-Bound Certificates]]
( ([TIME[2014-08-03 08:41:42 +09:00]] 版))
<http://tools.ietf.org/html/draft-balfanz-tls-obc-01>

[2] [CITE@en[draft-balfanz-tls-channelid-01 - Transport Layer Security (TLS) Channel IDs]]
([TIME[2015-01-18 14:22:24 +09:00]] 版)
<http://tools.ietf.org/html/draft-balfanz-tls-channelid-01>

[3] [CITE[Origin-Bound Certificates - BrowserAuth.net]]
([TIME[2015-04-10 16:11:39 +09:00]] 版)
<http://www.browserauth.net/origin-bound-certificates>

[4] [CITE@en[balfanz/tls-obc-spec]]
([TIME[2015-04-14 14:22:10 +09:00]] 版)
<https://github.com/balfanz/tls-obc-spec>

[5] ([TIME[2015-04-14 14:22:40 +09:00]] 版)
<https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final162.pdf>

[FIG(quote)[
[FIGCAPTION[
[6] [CITE['''['''TLS''']''' Update on Origin-Bound Certificates: Now called "Channel ID"]]
( ([TIME[2012-11-28 23:50:29 +09:00]]))
<https://www.ietf.org/mail-archive/web/tls/current/msg09042.html>
]FIGCAPTION]

> As you might have noticed, I have let the TLS-Origin-Bound Certificates (TLS-OBC: http://tools.ietf.org/id/draft-balfanz-tls-obc-01.txt) draft expire. The reason for this is that we (i.e., Google) had implemented TLS-OBC as described in the draft (in Chrome and server-side), and we weren't too happy with it. There were a few of problems:
>

]FIG]

[7] [CITE@en[draft-balfanz-tls-channelid-01 - Transport Layer Security (TLS) Channel IDs]]
( ([TIME[2016-06-06 00:35:16 +09:00]]))
<https://tools.ietf.org/html/draft-balfanz-tls-channelid-01>

[8] [CITE@en[Stub for w3c/webappsec-clear-site-data#2.]]
([[mikewest]]著, [TIME[2016-07-20 20:12:20 +09:00]])
<https://github.com/w3c/webappsec-clear-site-data/commit/5724b15c8a31fc89d73823e4981b4619afabc4cc>

Historical Legal Sensitive Parent: [Help / License]

Edit

Page

Errors

Page name(s)