w3ctag client-certificates issues

w3ctag / client-certificates

TAG spec review on keygen and use of client certificates in the web platform.

https://w3ctag.github.io/client-certificates

15 stars 12 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Please update the document in light of Web Authentication

#19 travisleithead opened 8 years ago
0
extend document to client certificate usage and user control

#18 bblfish opened 8 years ago
0
Privacy of the private key

#17 ekr opened 8 years ago
0
Update README.md

#16 adrianhopebailie opened 8 years ago
0
should the TAG call on implementations to improve client security UI?

#15 dbaron opened 8 years ago
0
should delegation to secure hardware really be recommended?

#14 dbaron opened 8 years ago
0
"Requirements and Recommendations" assumes that a private key is to be installed

#13 dbaron opened 8 years ago
0
Celebrate the decentralised and federated nature

#12 dirkx opened 8 years ago
1
Few small clarification; refining of a usecase.

#11 dirkx opened 8 years ago
0
PINs and secure hardware

#10 dirkx opened 8 years ago
0
Disclosure of certificate possession

#9 dirkx opened 8 years ago
0
"Pure" authentication v.s. redirected/derivative

#8 dirkx opened 8 years ago
0
tracking work in other standardisation forums regarding client certificates

#7 bblfish opened 8 years ago
2
visibility of authentication credentials used

#6 bblfish opened 8 years ago
0
bullet on using a private key is unclear

#5 dbaron opened 8 years ago
3
spelling fixes

#4 dbaron closed 8 years ago
1
describe a principle about tracking / supercookies

#3 dbaron opened 8 years ago
3
The document needs to clarify what it means to operate in the client's interest

#2 minfrin opened 8 years ago
1
Missing discussion about correlation, claims and cross-origin information

#1 hillbrad opened 8 years ago
7