Synchronous, "pure" signature verification should be possible

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cryptography, security

Research direction

Start by reviewing the proposed SignatureVerifier responsibilities and the distinction between local verification and network retrieval. Resolve how certificate-chain validity checks should be performed and whether results can be cached. Done means the design clearly separates synchronous pure verification from network-connected retrieval and specifies the chain-validation policy.

Written by the indexing model from the issue text.

Description

The hypothetical/proposed SignatureVerifier class does more than just verifying signatures, but also retrieves X509 chains from URLs. It would be nice to have two classes, one which does the verification itself and another which is network-connected.

What do we do with the certificate chain validity checks? (Stuff like -- verifying that it chains up to the root hash, verifying that dates are correct, verifying that the cert chains correctly.) Do we do them on every signature check? Do we cache results?

Dominant language
Python
Stars
5
Forks
4
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 mozilla-services/python-autograph-utils

All issues in mozilla-services/python-autograph-utils

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.