LiveMFA

ETHERTRUST · ONLINE SECURE ELEMENT

TLS 1.3 PSK-ECDHE · USB MFA Console

Connect the USB TLS-IM and verify your four-digit PIN before starting the TLS-SE session. Binder and Derive are performed by the USB token; KMS commands run over TLS 1.3 PSK-ECDHE.

1 · USB MFA Token

Not connected

2 · PIN Code

Timeout for PIN, Binder and Derive: 10 seconds by default (3–30 seconds). Does not change the firmware ACK window.

PIN not verified · TLS-SE connection disabled

USB: 19200 baud, 8N1, CRLF. The PSK remains inside the token. After disconnecting, the PIN must be verified again.

Target TLS-SE

Allowed TCP ports / ranges: 443-444, 888, 7000-8000, 8888. Only publicly routable IPv4 endpoints can be contacted.

KMS commands

One command per line. Lines beginning with # are comments. Click a suggested command below to insert it.

Binary KMS mode (automatic): for s, h, H, a, A, E, D, e, d, when the key index has bit 7 set (80–FF), enter the payload as hexadecimal pairs, e.g. s80001122FF. The three-character header stays ASCII; the payload is sent as raw bytes and the binary reply is shown as HEX. CRLF is automatic. Other commands remain text.

Ready · one TLS-SE session per run.

Secure Element Records · Z / I

Write a record using text on screen or Read from File (bytes preserved). Record indices 0–3 hold at most 1,280 bytes each. Z00–Z03 write the content followed by an additional CRLF; I00–I03 return the content followed by an additional CRLF. Internal CRLF and non-ASCII bytes are supported. Each operation uses the TLS connection settings above.

This setting affects the readable preview and text typed on screen. In French mode, accented letters such as é, è, ê, à, ç, ù, ô are decoded and encoded in one byte. Unrecognized bytes display as \xHH. Files and downloads remain byte-exact.

No file or record loaded.

Display only: literal sequences are interpreted in the preview, not in the record. The original bytes and downloaded files are unchanged. HEX lines are limited to 128 characters (64 bytes).

Experimental prototype: HTTPS required. Neither the PIN nor the PSK is sent to WordPress. Temporary Binder and Derive outputs pass through PHP; no permanent storage is intended. Do not use production secrets before a security review and tests on real hardware.