Was pre-hashed input considered for ECDSA?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Was it ever considered to allow passing a pre-hashed digest to crypto.subtle.sign() instead of raw data? I went through the issues but I have not found anything related.
Contributor guide
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
Start by reviewing the Web Cryptography API's existing ECDSA signing behavior and the issue discussion. Determine whether pre-hashed input is in scope and what specification change would be required; the issue is done when the proposal has a documented resolution or an agreed implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100