issues
search
davidben
/
merkle-tree-certs
Other
9
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Clarify that unparsable signing inputs are still misissuance
#47
bwesterb
closed
1 year ago
0
Add storage window
#46
bwesterb
opened
1 year ago
1
Is it worthwhile to reduce reliance on collision resistance from our hash?
#45
bwesterb
opened
1 year ago
2
Rename window to validity window
#44
bwesterb
closed
1 year ago
0
Miscellaneous
#43
bwesterb
closed
1 year ago
0
IANA considerations
#42
bwesterb
opened
1 year ago
0
Revocation
#41
bwesterb
opened
1 year ago
8
[duplicate] Client certificates
#40
bwesterb
closed
1 year ago
1
Include new post-quantum TLS signature schemes
#39
bwesterb
opened
1 year ago
0
Should TLSSubjectInfo have an extension list?
#38
bwesterb
opened
1 year ago
3
Downtime lenience
#37
bwesterb
opened
1 year ago
1
Multiple signing keys?
#36
bwesterb
opened
1 year ago
0
Should claims include ports?
#35
bwesterb
opened
1 year ago
0
Only include hash of subject_info in Assertion
#34
bwesterb
closed
1 year ago
1
Properly separate hashes in Merkle tree
#33
bwesterb
closed
1 year ago
0
Feedback on hash construction
#32
davidben
closed
1 year ago
0
Canonicalize claim structures further and think about multiplicity
#31
davidben
opened
1 year ago
1
Should the signing payload include 64 spaces in front?
#30
davidben
opened
1 year ago
1
Shorten some length prefixes
#29
davidben
closed
1 year ago
2
Shorten some length prefixes
#28
davidben
closed
1 year ago
1
Elaborate on CA public key
#27
bwesterb
closed
1 month ago
3
Bitflips
#26
bwesterb
opened
1 year ago
1
Subscriber-level delegation
#25
davidben
opened
1 year ago
1
TA negotiation useful for draft-kampanakis-tls-scas / draft-jackson-tls-cert-abridge
#24
bwesterb
opened
1 year ago
1
Evidence
#23
bwesterb
opened
1 year ago
0
Talk about RP <-> TS communication under Privacy Considerations
#22
davidben
opened
1 year ago
1
Rename window to validity window?
#21
davidben
closed
1 year ago
0
Clarify that we use just a single CertificateEntry
#20
davidben
closed
1 year ago
0
Mention canonical STHs in acknowledgements or so
#19
davidben
opened
1 year ago
3
Resolve client certificate type negotiation issues
#18
davidben
opened
1 year ago
6
Discuss clock skews
#17
davidben
opened
1 year ago
4
Editorial: Perhaps define certificate format earlier?
#16
davidben
opened
1 year ago
1
BikeshedCertificate is a placeholder name
#15
davidben
opened
1 year ago
1
Reword the introduction slightly
#14
davidben
closed
1 year ago
0
Flesh out ACME interface
#13
davidben
opened
1 year ago
1
Flesh out HTTP interface
#12
davidben
opened
1 year ago
1
Clarify you send only one CertificateEntry in TLS
#11
davidben
closed
1 year ago
0
Question: SubjectType, Intermediate CAs, and cross-signing
#10
bemasc
opened
1 year ago
1
Feature Request: Support for IP ranges
#9
bemasc
opened
1 year ago
0
Should the RP advertise TrustAnchor exclusions on top of TrustAnchor sets?
#8
davidben
opened
1 year ago
3
Should TLS CertificateType incorporate SubjectType?
#7
davidben
opened
1 year ago
3
Should we include or only bind public keys in assertions
#6
bwesterb
closed
1 year ago
5
Clarify that unparsable signing inputs are still misissuance
#5
davidben
closed
1 year ago
3
Clarify time computations are done in POSIX time
#4
davidben
closed
1 year ago
1
merkle_tree_sha256 TrustAnchors mean different things in different contexts
#3
davidben
opened
1 year ago
4
How long must long-expired batches be served
#2
davidben
opened
1 year ago
2
Time math is ambiguously-specified
#1
davidben
closed
1 year ago
1
Previous