{"id":302,"date":"2026-11-17T15:23:14","date_gmt":"2026-11-17T15:23:14","guid":{"rendered":"https:\/\/ethertrust.com\/?page_id=302"},"modified":"2026-11-17T15:39:50","modified_gmt":"2026-11-17T15:39:50","slug":"console","status":"publish","type":"page","link":"https:\/\/ethertrust.com\/index.php\/console\/","title":{"rendered":"Console"},"content":{"rendered":"\n<div class=\"etsc-landing\" id=\"ethertrust-tls-console-page\">\n  <section class=\"etsc-explain\">\n    <h3>Two authentication modes<\/h3>\n    <p><strong>Direct PSK.<\/strong> 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 <code>TLS_AES_128_CCM_SHA256<\/code> cipher suite.<\/p>\n    <p><strong>Remote TLS-IM.<\/strong> A first TLS 1.3 PSK connection securely accesses a remote TLS-SE that acts as a TLS Identity Module. The TLS-IM computes <code>?D0<\/code> (Binder) and <code>?D1<\/code> (Derive), or <code>?D2<\/code> (Derive with hardware acknowledgment). This authorizes a second TLS connection to the target pNHSM without requiring its PSK3 to be entered in the browser.<\/p>\n    <p>The TLS-IM access PSK is different from the target TLS-SE&rsquo;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.<\/p>\n  <\/section>\n<\/div>\n\n\n    <section class=\"etsc-console\" data-etsc-root=\"1\">\n      <div class=\"etsc-console-head\"><span class=\"etsc-kicker\">ETHERTRUST \u00b7 ONLINE SECURE ELEMENT<\/span><h2>TLS 1.3 PSK Command Console<\/h2>\n        <p>Enter your Secure Element connection parameters and run KMS commands. <strong>CRLF (\\r\\n)<\/strong> is appended automatically. No PSK is stored in the page or WordPress database.<\/p>\n      <\/div>\n            <div class=\"etsc-layout\">\n      <div class=\"etsc-section\">\n        <label class=\"etsc-label\" for=\"etsc-mode\">Connection mode<\/label>\n        <select id=\"etsc-mode\" data-etsc-field=\"mode\"><option value=\"direct\">Direct TLS 1.3 PSK<\/option><option value=\"im\">Remote TLS-IM (recursive authentication)<\/option><\/select>\n        <h3>Target TLS-SE<\/h3>\n        <div class=\"etsc-fields\">\n          <label>Server (DNS or IPv4)<input data-etsc-field=\"target_host\" type=\"text\" placeholder=\"your-pnhsm.example\" autocomplete=\"off\" maxlength=\"253\" required><\/label>\n          <label>TCP port<input data-etsc-field=\"target_port\" type=\"number\" min=\"1\" max=\"65535\" value=\"888\" required><\/label>\n          <label>Server Name (SNI)<input data-etsc-field=\"target_sni\" type=\"text\" placeholder=\"key1.com\" maxlength=\"253\" required><\/label>\n          <label>PSK identity<input data-etsc-field=\"target_identity\" type=\"text\" value=\"Client_identity\" maxlength=\"128\" required><\/label>\n        <\/div>\n        <div data-etsc-direct><label class=\"etsc-label\">TLS-SE PSK (hexadecimal)<input data-etsc-field=\"target_psk\" type=\"password\" spellcheck=\"false\" autocomplete=\"new-password\" placeholder=\"32\u2013256 hexadecimal characters\" maxlength=\"256\"><\/label><\/div>\n        <div data-etsc-im hidden>\n          <h3>Remote TLS Identity Module<\/h3>\n          <p class=\"etsc-hint\">The TLS-SE target PSK3 stays in the remote TLS-IM. Only the separate access PSK is entered below.<\/p>\n          <div class=\"etsc-fields\">\n            <label>TLS-IM server<input data-etsc-field=\"im_host\" type=\"text\" placeholder=\"your-tls-im.example\" maxlength=\"253\"><\/label>\n            <label>TLS-IM TCP port<input data-etsc-field=\"im_port\" type=\"number\" min=\"1\" max=\"65535\" value=\"888\"><\/label>\n            <label>TLS-IM SNI<input data-etsc-field=\"im_sni\" type=\"text\" placeholder=\"im1.example\" maxlength=\"253\"><\/label>\n            <label>TLS-IM access identity<input data-etsc-field=\"im_identity\" type=\"text\" value=\"Client_identity\" maxlength=\"128\"><\/label>\n          <\/div>\n          <label class=\"etsc-label\">TLS-IM access PSK (hexadecimal)<input data-etsc-field=\"im_psk\" type=\"password\" autocomplete=\"new-password\" spellcheck=\"false\" maxlength=\"256\" placeholder=\"32\u2013256 hexadecimal characters\"><\/label>\n          <div class=\"etsc-fields\">\n            <label>TLS-IM cipher suite<select data-etsc-field=\"im_suite\"><option value=\"TLS_AES_128_CCM_SHA256\">TLS_AES_128_CCM_SHA256<\/option><option value=\"TLS_AES_128_GCM_SHA256\">TLS_AES_128_GCM_SHA256<\/option><\/select><\/label>\n            <label>Remote Derive<select data-etsc-field=\"derive_op\"><option value=\"?D1\">?D1 \u00b7 Standard Derive<\/option><option value=\"?D2\">?D2 \u00b7 Derive with hardware ACK<\/option><\/select><\/label>\n          <\/div>\n          <p class=\"etsc-hint\" data-etsc-d2-note hidden>When ?D2 is selected, a person must confirm on the TLS-IM hardware. Allow enough time for acknowledgment.<\/p>\n        <\/div>\n        <label class=\"etsc-label\">Per-operation timeout (seconds)<input data-etsc-field=\"timeout\" type=\"number\" min=\"5\" max=\"45\" value=\"15\"><\/label>\n        <p class=\"etsc-hint\">Allowed TCP ports: 443,444,888,8888. Only publicly routable IPv4 endpoints can be contacted.<\/p>\n      <\/div>\n      <div class=\"etsc-section etsc-terminal\">\n        <h3>KMS commands<\/h3><p class=\"etsc-hint\">One command per line. Lines beginning with <code>#<\/code> are comments. Click a suggested command in the section below to insert it.<\/p>\n        <textarea data-etsc-commands rows=\"8\" spellcheck=\"false\" autocomplete=\"off\">?00<\/textarea>\n        <div class=\"etsc-actions\"><button type=\"button\" data-etsc-run class=\"etsc-button\" >Connect &amp; run commands<\/button><button type=\"button\" data-etsc-clear class=\"etsc-secondary\">Clear<\/button><\/div>\n        <p class=\"etsc-status\" data-etsc-status aria-live=\"polite\">Ready \u00b7 one TLS-SE session per run.<\/p>\n        <div class=\"etsc-results\" data-etsc-results hidden><\/div>\n      <\/div><\/div>\n      <p class=\"etsc-footnote\">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.<\/p>\n    <\/section>\n\n\n\n<div class=\"etsc-landing\">\n<section class=\"etsc-suggestions\">\n  <h3>Suggested TLS-SE Commands<\/h3>\n  <p>Click any command to add it to the console. <strong>You can edit, remove or add buttons here directly in the WordPress Custom HTML block.<\/strong> Modify the <code>data-etsc-suggest<\/code> attribute and the visible label together. These are examples, not a server-side command whitelist.<\/p>\n  <p><strong>Identification and read-only commands<\/strong><\/p>\n  <div class=\"etsc-command-grid\">\n    <button type=\"button\" data-etsc-suggest=\"?00\">?00 \u00b7 Version<\/button>\n    <button type=\"button\" data-etsc-suggest=\"?01Hello TLS-SE\">?01Hello TLS-SE \u00b7 Echo<\/button>\n    <button type=\"button\" data-etsc-suggest=\"?0A\">?0A \u00b7 Application public key<\/button>\n    <button type=\"button\" data-etsc-suggest=\"?0B\">?0B \u00b7 Application certificate<\/button>\n    <button type=\"button\" data-etsc-suggest=\"p10\">p10 \u00b7 ECC secp256r1 public key<\/button>\n    <button type=\"button\" data-etsc-suggest=\"p00\">p00 \u00b7 ECC secp256k1 public key<\/button>\n    <button type=\"button\" data-etsc-suggest=\"p2100\">p2100 \u00b7 RSA-2048 modulus (slot 1)<\/button>\n    <button type=\"button\" data-etsc-suggest=\"p2101\">p2101 \u00b7 RSA-2048 exponent (slot 1)<\/button>\n  <\/div>\n  <p><strong>Key generation and signing<\/strong> \u2014 these commands affect the selected Secure Element and require suitable privileges.<\/p>\n  <div class=\"etsc-command-grid\">\n    <button type=\"button\" data-etsc-suggest=\"c10\">c10 \u00b7 Clear ECC r1 slot 0<\/button>\n    <button type=\"button\" data-etsc-suggest=\"g10\">g10 \u00b7 Generate ECC r1 slot 0<\/button>\n    <button type=\"button\" data-etsc-suggest=\"c00\">c00 \u00b7 Clear ECC k1 slot 0<\/button>\n    <button type=\"button\" data-etsc-suggest=\"g00\">g00 \u00b7 Generate ECC k1 slot 0<\/button>\n    <button type=\"button\" data-etsc-suggest=\"c21\">c21 \u00b7 Clear RSA slot 1<\/button>\n    <button type=\"button\" data-etsc-suggest=\"g21\">g21 \u00b7 Generate RSA slot 1<\/button>\n    <button type=\"button\" data-etsc-suggest=\"s1000112233445566778899AABBCCDDEEFF00112233445566778899AABBCCDDEEFF\">s10 \u00b7 ECDSA signature of 32-byte sample<\/button>\n  <\/div>\n  <p><strong>AES-128 and HMAC-SHA-256<\/strong><\/p>\n  <div class=\"etsc-command-grid\">\n    <button type=\"button\" data-etsc-suggest=\"t3000112233445566778899AABBCCDDEEFF\">t30 \u00b7 Set 16-byte test secret<\/button>\n    <button type=\"button\" data-etsc-suggest=\"A0000112233445566778899AABBCCDDEEFF\">A00 \u00b7 Encrypt one AES block<\/button>\n    <button type=\"button\" data-etsc-suggest=\"h0048656C6C6F\">h00 \u00b7 HMAC-SHA256 (Hello)<\/button>\n    <button type=\"button\" data-etsc-suggest=\"m00Hello\">m00 \u00b7 HMAC-SHA256 (ASCII Hello)<\/button>\n  <\/div>\n  <p>Examples use the TLS-SE 3.05 shell syntax. ECC curve-to-slot mappings depend on the firmware configuration. Commands may return <code>ERROR<\/code> if the slot is empty or its access policy forbids the operation.<\/p>\n  <p style=\"font-size:.85rem\">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.<\/p>\n<\/section>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-302","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/pages\/302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/comments?post=302"}],"version-history":[{"count":2,"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/pages\/302\/revisions"}],"predecessor-version":[{"id":305,"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/pages\/302\/revisions\/305"}],"wp:attachment":[{"href":"https:\/\/ethertrust.com\/index.php\/wp-json\/wp\/v2\/media?parent=302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}