SM2 Encrypt

Overview

Encrypts a message utilizing the SM2 standard. SM2 is a public-key cryptography standard used in China.

Status

Field Value
Implementation Partial
Parity Unknown
Availability Available
Input requirement Required
Features none
Side effects []
Deterministic true

Input

Declared input type: Bytes.

Output

Declared output type: String. Redirect stdout or use --output-file for exact binary bytes.

Arguments

# Argument Type Required Default Allowed Sensitive Description
1 Public Key X HexBytes no <empty> no Public key component X in hex format (32 bytes)
2 Public Key Y HexBytes no <empty> no Public key component Y in hex format (32 bytes)
3 Output Format String no C1C3C2 no The format of the output ciphertext (C1C3C2 or C1C2C3)
4 Curve String no sm2p256v1 no The elliptic curve to use (sm2p256v1)

Implementation

The implementation is in src/operations/sm2_encrypt.rs and declares Bytes input and String output. The operation module owns conversion and domain-error rules; registry resolution, argument validation, input-requirement enforcement, tracing, and output validation are performed by rxchef::execution.

Command-line use

This operation requires input. Supply literal UTF-8 with --input, exact bytes with --input-file, or pipe bytes on stdin.

rxchef run "SM2 Encrypt" --input-file input.bin --output-file output.bin

Arguments may be supplied positionally in the table order or by name with repeatable --arg NAME=VALUE. Omitted optional arguments use the documented defaults.

Pipeline use

Place the operation anywhere a Bytes value is valid. Its String result becomes the next step's input. Compact syntax uses the operation name followed by comma-separated arguments; JSON/YAML recipes use an op field and an args array.

Error conditions

Schema violations are rejected before the operation runs. Malformed input, unsupported parameter combinations, unavailable optional backends, and domain processing failures produce structured errors and a non-zero CLI status; partial output is never reported as success.

CyberChef compatibility

Parity status: Unknown. Unknown records an unassessed compatibility claim; it does not imply equality or incompatibility.

Security considerations

Declared side effects: []. Treat parser inputs as untrusted and apply execution limits to large data. Arguments marked sensitive in the schema are redacted from metadata-aware History displays.

Testing evidence

Correctness tests: - tests/tests/operations/sm2_encrypt.rs

Performance classification

Excluded from the committed representative benchmark set: No stable representative benchmark case is defined; operation remains Partial until performance evidence is reviewed.

References