Feature request: Add SM2 public key encryption/decryption support

[somes]

Hi wolfSSL team,

I would like to ask whether wolfSM could support SM2 public key encryption and decryption.

Currently, the wolfSM README describes SM2 support as:

• ECDH key agreement
• Signature scheme using the specified 256-bit elliptic curve

It would be very useful to have SM2 encryption/decryption support for use cases that require public-key encryption based on SM2.

It would also be helpful if the implementation supports the commonly used SM2 ciphertext formats, such as C1C3C2 and/or C1C2C3.

Could you please let me know whether SM2 encryption/decryption is planned, or whether you would consider adding it to wolfSM?

Thanks!

[kareem-wolfssl]

Hi @somes,

We don't currently have this on our roadmap, but I can certainly log a feature request for this.
Can you share some information about your project? Are you working on a commercial or personal project? Please also share where you are located.
If this information is sensitive feel free to email us at support@wolfssl.com.

[somes]

Hi @kareem-wolfssl,

Thanks for your reply.

This is currently a personal project for learning purposes. I am learning about microcontrollers and embedded development, and I have some hardware devices such as a YubiKey and a GM3000 token. I would like to experiment with building a similar USB security token using an RP2040.

The goal is to better understand how this kind of hardware works, including smart-card-like workflows, CCID/PIV-style communication, and Chinese cryptographic algorithms such as SM2, SM3, and SM4.

SM2 signature support is already useful, but SM2 public key encryption/decryption would make the project more complete and closer to the functionality of real hardware tokens that support both signing and encryption/decryption use cases. Support for common SM2 ciphertext formats such as C1C3C2 and/or C1C2C3 would also help with interoperability.

I am located in China.

Although this is not a commercial project, I would appreciate it if this could be logged as a feature request or considered for a future wolfSM release.

Thanks again!