Feature request: Add Argon2id support
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
- Active
- Tech stack
- c
- Domain
- cryptography, security
Research direction
The issue names no files, tests, or entry points, and asks whether the SymCrypt team would consider Argon2id support. Start by reviewing SymCrypt's existing algorithm APIs and contribution guidance, then clarify the supported platforms, API shape, test requirements, and acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Description
Argon2id is currently recommended by OWASP for password hashing and standardized in RFC 9106.
It would be useful to have an official Argon2id implementation in SymCrypt, especially since .NET currently has no built-in Argon2 support and generally relies on platform cryptographic implementations rather than implementing cryptographic primitives itself.
In dotnet/runtime discussion #117822, the .NET team explained that currently only OpenSSL provides Argon2, while Windows CNG and Apple CryptoKit/CommonCrypto do not. They also noted that support on at least two platforms is generally expected before adding such an algorithm to System.Security.Cryptography.
There is also a long-standing request for Argon2 support in dotnet/runtime#19933.
Adding Argon2id to SymCrypt could therefore help enable first-party support in the Windows cryptography stack and eventually System.Security.Cryptography / ASP.NET Core Identity, while avoiding reliance on third-party cryptographic implementations.
Would Argon2id support be something the SymCrypt team would consider?
- Dominant language
- C
- Stars
- 890
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/SymCrypt
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
bug compiler-support
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/SymCrypt
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
libc
Difficulty 2/5 1-2 days Newbie friendliness 76/100
llvm/llvm-project#225506 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
bug
Difficulty 2/5 Half a day Newbie friendliness 82/100