You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
are there any plans to support the ShangMi suite of algorithms, ciphers, curves etc. in dotnet?
there's an oss implementation https://github.com/GmSSL, which apparently supports C, Java, Python, Go and JS, just wondering, if there's a plan for dotnet to support those as well.
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
olaf-lange
changed the title
Question: ShangMi(SM2,SM3 & SM4, ...) crypto support in dotnet
Question: ShangMi(SM2, SM3, SM4, ...) crypto support in dotnet
Jan 21, 2025
By policy, .NET don't provide cryptographic algorithm itself and always depend on underlying OS to provide the implementations.
To get exported by .NET BCL, it requires somehow of popularity. Some algorithms implemented by OpenSSL but lacks in Windows are still not included. For example, Ed25519(#63174) has been requested for a long time, but still pending for more platforms to supported.
Specific to SM suites, the answer should be "very unlikely": it's only included in openssl, which isn't used on Windows. You can create a third-party implementation of the algorithm, but .NET won't provide a first-party one.
You linked to SM4-in-TLS. .NET doesn't have an implementation of TLS, we depend on the underlying platforms. So, if macOS adds SM4 to their TLS stack we'll use it on macOS; etc.
But there are no plans at this time to add those algorithms into .NET itself
Hi,
are there any plans to support the ShangMi suite of algorithms, ciphers, curves etc. in dotnet?
there's an oss implementation https://github.com/GmSSL, which apparently supports C, Java, Python, Go and JS, just wondering, if there's a plan for dotnet to support those as well.
for reference:
https://datatracker.ietf.org/doc/html/rfc8998
The text was updated successfully, but these errors were encountered: