Support verification of multiple signatures

Open
#59 6 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
security

Research direction

Start by locating the signature-verification entry point and current interface. Trace how signatures are discovered and filtered by the expected certificate, then determine how multiple matches should be reported or iterated. Done means breadth-first discovery, silent filtering, an error through the existing interface for multiple results, and an iterator for callers expecting multiple signatures.

Written by the indexing model from the issue text.

Description

  • Use breadth-first traversal when looking for signatures
  • Silently discard signatures that don't use the expected certificate
  • If multiple signatures remain and current interface is used, raise an error
  • Introduce iterator interface for situations where multiple signatures are expected
Dominant language
Python
Stars
154
Forks
113
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 XML-Security/signxml

All issues in XML-Security/signxml

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.