Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

crypto needed for QUIC #51

Open
armanbilge opened this issue Jan 3, 2022 · 1 comment
Open

crypto needed for QUIC #51

armanbilge opened this issue Jan 3, 2022 · 1 comment

Comments

@armanbilge
Copy link
Member

H/t @ChristopherDavenport in Discord

Cypher Suites
TLS_AES_128_GCM_SHA256 - Mandatory
AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256

Digital Signatures
rsa_pkcs1_sha256 (for certificates)
rsa_pss_rsae_sha256 (for CertificateVerify and certificates)
ecdsa_secp256r1_sha256

key exchange
secp256r1 (NIST P-256) MUST
X25519
@bblfish
Copy link

bblfish commented Jan 4, 2022 •
edited
Loading

That would be something to be added to the branch on which PR #48 is.

The first thing that would be needed are test cases: Documents that show valid signatures for a given text with a given public and private key, ideally official documents. Perhaps @ChristopherDavenport has some pointers, as he was interested in those signature types? The existing signing algorithms all have their tests taken from the Signing Http Messages spec

@bblfish bblfish mentioned this issue Jan 4, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bblfish @armanbilge