Extracting VerifyingKey from X.509 certificates

Open
#119 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cryptography, security

Research direction

Start by locating VerifyingKey and its existing key-parsing entry points. Review #113 for context, then determine how PEM and DER X.509 certificates should be handled. Done means VerifyingKey can extract a public key from both certificate formats, with coverage for each path.

Written by the indexing model from the issue text.

Description

feature help wanted

The public keys are not usually distributed as bare RFC5912 ASN.1 objects but rather as X.509 certificates.

Add support for parsing certificates (in PEM and DER format) to VerifyingKey.

see also: #113

Dominant language
Python
Stars
973
Forks
343
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tlsfuzzer/python-ecdsa

All issues in tlsfuzzer/python-ecdsa

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.