AES with variables

Overview & Cryptographic Context

In larger cryptographic test suites, hardcoding literal hex keys and test payloads inside individual nodes makes switching between environments or test vectors tedious and error-prone. NodeCrypto provides a Value Registry where named variables (such as $example.aes.key and $example.aes.plaintext) are stored separately from the workflow graph and resolved at execution time.

This workflow reproduces the canonical NIST FIPS 197 Appendix C.1 (AES-128) single-block test vector. Instead of storing literal byte strings in the two Static Value nodes, their valueBytes properties hold {"$var": "$example.aes.key"} and {"$var": "$example.aes.plaintext"} references.

Pipeline Architecture & Wiring Flow

1. Variable Resolution (Static Value × 2): Before executing the graph, the runtime looks up $example.aes.key (000102030405060708090a0b0c0d0e0f) and $example.aes.plaintext (00112233445566778899aabbccddeeff) in the Value Registry and emits their 16-byte values on the Value output ports.
2. Block Encryption (AES Encrypt): Runs AES-128 in ECB mode with padding = "None" to produce the 16-byte FIPS 197 ciphertext block on its ciphertext output port.

Nodes & Configuration

Node reference →

Variables, Outputs & Test Vector Verification

Verification Source: FIPS 197 Appendix C.1 (AES-128 example vector)

Value Registry Variables

Expected Outputs