Two authentication modes
Direct PSK. The PSK entered below authenticates the TLS 1.3 connection between the WordPress server and your TLS-SE. The handshake uses PSK-DHE on P-256 and the TLS_AES_128_CCM_SHA256 cipher suite.
Remote TLS-IM. A first TLS 1.3 PSK connection securely accesses a remote TLS-SE that acts as a TLS Identity Module. The TLS-IM computes ?D0 (Binder) and ?D1 (Derive), or ?D2 (Derive with hardware acknowledgment). This authorizes a second TLS connection to the target pNHSM without requiring its PSK3 to be entered in the browser.
The TLS-IM access PSK is different from the target TLS-SE’s PSK3. The former is entered in this console; PSK3 remains in the remote Secure Element. The handshake and traffic secrets are handled by the experimental PHP TLS client.
TLS 1.3 PSK Command Console
Enter your Secure Element connection parameters and run KMS commands. CRLF (\r\n) is appended automatically. No PSK is stored in the page or WordPress database.
Target TLS-SE
Remote TLS Identity Module
The TLS-SE target PSK3 stays in the remote TLS-IM. Only the separate access PSK is entered below.
When ?D2 is selected, a person must confirm on the TLS-IM hardware. Allow enough time for acknowledgment.
Allowed TCP ports: 443,444,888,8888. Only publicly routable IPv4 endpoints can be contacted.
KMS commands
One command per line. Lines beginning with # are comments. Click a suggested command in the section below to insert it.
Ready · one TLS-SE session per run.
Experimental TLS implementation for development Secure Elements. No browser-side PSK persistence. HTTPS is required. Avoid production keys; the WordPress server processes the PSK during each request, and TLS-IM access credentials are briefly passed to an OpenSSL process.
Suggested TLS-SE Commands
Click any command to add it to the console. You can edit, remove or add buttons here directly in the WordPress Custom HTML block. Modify the data-etsc-suggest attribute and the visible label together. These are examples, not a server-side command whitelist.
Identification and read-only commands
Key generation and signing — these commands affect the selected Secure Element and require suitable privileges.
AES-128 and HMAC-SHA-256
Examples use the TLS-SE 3.05 shell syntax. ECC curve-to-slot mappings depend on the firmware configuration. Commands may return ERROR if the slot is empty or its access policy forbids the operation.
Each test is executed on the WordPress server over HTTPS. PSKs are provided anew for each test and are not saved in this page. Use test keys and devices. Connection attempts are limited to publicly routable IPv4 addresses and TCP ports permitted by the site administrator.