XML-Security / XML-Security/signxml
Support XAdES unsigned properties
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 154
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
What is the security model for unsigned properties? If it's reasonable, we might want to separately verify any countersigned properties and add them to XAdESVerifyResult with documentation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by examining the XAdES verification flow and defining the security model for unsigned and countersigned properties. Done means the behavior is specified, countersigned properties are separately verified if appropriate, XAdESVerifyResult exposes them, and the result is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100