Skip to content

Conversation

@sjaeckel
Copy link
Member

@sjaeckel sjaeckel commented Sep 8, 2025

Start implemeting X.509 APIs.

In #693 this was requested and I was already at it and now we have the first part: Parsing of an X.509 certificate and the cryptographic validation of such a certificate.

NB: This does not yet contain the logic that is required to determine whether a CA is eligible to sign a certificate etc.

Checklist

  • documentation is added or updated
  • tests are added or updated

@sjaeckel sjaeckel requested review from karel-m and levitte September 8, 2025 12:20
@sjaeckel sjaeckel marked this pull request as draft September 8, 2025 12:21
@sjaeckel sjaeckel force-pushed the x509_import branch 8 times, most recently from a342826 to d9b0684 Compare September 11, 2025 12:50
@sjaeckel sjaeckel force-pushed the some-improvements branch 2 times, most recently from 028775e to 6fe53a5 Compare September 12, 2025 16:50
Base automatically changed from some-improvements to develop September 15, 2025 13:35
@sjaeckel sjaeckel mentioned this pull request Oct 3, 2025
@sjaeckel sjaeckel changed the base branch from develop to new-rsa-api November 19, 2025 14:44
Signed-off-by: Steffen Jaeckel <[email protected]>
Signed-off-by: Steffen Jaeckel <[email protected]>
This includes the certificates included in the test suites of OpenSSL
and GnuTLS.

Signed-off-by: Steffen Jaeckel <[email protected]>
Signed-off-by: Steffen Jaeckel <[email protected]>
Run x509_verify for all certs.

Signed-off-by: Steffen Jaeckel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants