issues
search
EntrustCorporation
/
draft-ounsworth-composite-sigs
DEPRECATED REPO - moved to https://github.com/lamps-wg/draft-composite-sigs
Other
5
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Sort references into Normative and Informative
#97
ounsworth
closed
1 year ago
0
Look over / clean up the ASN.1 modules to reflect content changes
#96
ounsworth
closed
1 year ago
0
Composite-OR signatures MUST put a null in place of omitted signatures
#95
ounsworth
closed
3 years ago
2
Only sigs
#94
ounsworth
closed
3 years ago
1
Change "signature verification algorithm" to "signature verification process" to line up with FIPS 186-4
#93
ounsworth
closed
3 years ago
0
Do we need an Composite Algorithm OID for keys and a composite OID for Signatures?
#92
jogray72
closed
3 years ago
6
Add to Security Considerations: Component keys of a composite signature should never be used in isolation (ie RSA-only sister certs need unique keys)
#91
ounsworth
closed
1 year ago
1
Mike/ednote cleanup
#90
ounsworth
closed
4 years ago
0
EDNOTE 13: Comparison with draft-truskovksy
#89
ounsworth
closed
4 years ago
1
EDNOTE 12: CableLab's IRP statement
#88
ounsworth
closed
4 years ago
1
EDNOTE 11: redundant mention of PEM encoding rules
#87
ounsworth
closed
4 years ago
1
EDNOTE 10: list of potential topics for the "In Practice" section
#86
ounsworth
closed
1 year ago
1
EDNOTE 9: combining sigs and KEMs
#85
ounsworth
closed
4 years ago
1
EDNOTE 8: subset signatures
#84
ounsworth
closed
4 years ago
2
EDNOTE 6: alternatives for alg params
#83
ounsworth
closed
4 years ago
1
EDNOTE 5:
#82
ounsworth
closed
4 years ago
1
EDNOTE 4: unsure whether the params should be absent
#81
ounsworth
closed
1 year ago
1
EDNOTE 3: temporary OpenCA OID
#80
ounsworth
closed
2 years ago
1
EDNOTE 2: why we need to define a generic composite structure
#79
ounsworth
closed
2 years ago
1
EDNOTE 1: scope restricted to signatures
#78
ounsworth
closed
4 years ago
3
Added sections on explicit composite algorithms
#77
ounsworth
closed
3 years ago
2
Should OID in 2.1 be the same as in the 5. ?
#76
kriskwiatkowski
closed
4 years ago
4
fix: small merge issue
#75
kriskwiatkowski
closed
4 years ago
0
Editorial fixes
#74
kriskwiatkowski
closed
4 years ago
0
remove information about private key from public key
#73
kriskwiatkowski
closed
4 years ago
1
pk-Composite PUBLIC-KEY includes private key
#72
kriskwiatkowski
closed
4 years ago
4
Add Bibtex reference
#71
ounsworth
closed
5 years ago
2
Propose LAMPS re-charter text
#70
ounsworth
closed
5 years ago
1
Come up with a concrete use-case
#69
ounsworth
closed
1 year ago
1
Weakening of strong unforgeability
#68
ounsworth
closed
1 year ago
1
Address Jim Shaad's feedback on the LAMPS mailing list
#67
ounsworth
closed
5 years ago
0
Minor Nits based on open tickets, 23.06.2019
#66
ounsworth
closed
5 years ago
0
Clean up compile warnings
#65
ounsworth
closed
5 years ago
1
Merge sections "In Practice" and "Implications for Existing Standards"
#64
ounsworth
closed
5 years ago
0
Strengthen security properties of composite signature primitive
#63
sergemister
closed
7 months ago
12
Implementation thoughts
#62
danvangeest
closed
1 year ago
3
Add line indicating key usage bits apply to all keys.
#61
danvangeest
closed
5 years ago
0
Should we submit a talk to the ETSI Quantum-Safe Workshop in Nov?
#60
ounsworth
closed
5 years ago
2
Restructure and simplify the Public Key ASN.1
#59
ounsworth
closed
5 years ago
14
Banning recursive composite types
#58
ounsworth
closed
5 years ago
0
Adjusted Max's wording around pem storage of private keys
#57
ounsworth
closed
5 years ago
1
BER vs DER cleanup
#56
ounsworth
closed
5 years ago
1
Mention potential implementation gotchas for unknown component algorithm types
#55
danvangeest
closed
1 year ago
2
IETF question: only signature algorithms or KEMs (and others?) as well?
#54
danvangeest
closed
4 years ago
2
IETF question: how much CMS detail do we want?
#53
danvangeest
closed
1 year ago
1
Resolve DER and BER encoding text
#52
danvangeest
closed
5 years ago
1
Only define a single OID for composite objects
#51
danvangeest
closed
5 years ago
3
Only define a single OID for composite algorithms
#50
danvangeest
closed
5 years ago
2
"-----BEGIN COMPOSITE PRIVATE KEY-----" do we need the equiv PUBLIC KEY?
#49
ounsworth
closed
5 years ago
5
Should we have initial values for the OIDS?
#48
sfluhrer
closed
5 years ago
5
Previous
Next