Recommending GCM for interoperability
Open
Nobody has claimed this yet.
needs implementor interest
proposal
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Sec. 18.5.2: the algorithm list includes AES-CBC but not AES-GCM. We think it is time to make the switch, or at least to add GCM as mandatory to implement. Given the audience of this API, the advantage of GCM is that it can be used securely by mere mortals who do not understand the subtleties of integrity protection.
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 reading Sec. 18.5.2 of the Web Cryptography API specification and its current algorithm list. Determine whether the requested outcome is switching from AES-CBC or adding AES-GCM as mandatory to implement; done requires a resolved standards decision and corresponding specification update.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100