UberCA demonstrates how a Personal Network Hardware Security Module (pNHSM) can act as a Certificate Authority (CA) using OpenSSL and a TLS-SE Secure Element.
The CA and user private keys are generated and stored inside the Secure Element. They are never exported. OpenSSL prepares the X.509 certificates and certificate signing requests (CSRs), while the cryptographic signatures are performed inside the Secure Element through a secure TLS 1.3 PSK-ECDHE connection.
Live Demonstration
The demonstration consists of three steps:
- Create the Certificate Authority: Generate an ECDSA P-256 key pair at index 10 and create a self-signed CA certificate.
- Create the User CSR: Generate another ECDSA P-256 key pair at index 11 and create a signed certificate request for a user.
- Issue the User Certificate: Sign the user certificate using the CA private key at index 10 and verify the resulting certificate chain with OpenSSL.
The demo displays the public keys, certificates and execution steps. Certificates can be inspected and downloaded.
This demonstration illustrates how certificate issuance can be performed without exposing private keys outside the Secure Element. The generated certificates are intended for testing and are not publicly trusted.
Technical details and source code: UberCA — GitHub README
EtherTrust UberCA Demo
Generate a CA certificate (Secure Element key index 10) and a user certificate (key index 11) using TLS 1.3 PSK-ECDHE and OpenSSL. The private keys never leave the Secure Element.
P-256 · ECDSA/SHA-256 · TLS_AES_128_CCM_SHA256 · Maximum reservation 1 min
No Secure Element reserved.
1. Create Certificate Authority — Index 10
c10 → g10 → p10 → makek → OpenSSL → extract → s10 → sig2 → verify
CA public key and certificate
CA public key (uncompressed P-256)
Not generated.
CA certificate (PEM)
Not generated.
2. Create User CSR — Index 11
c11 → g11 → p11 → makek → OpenSSL CSR → extract → s11 → sig2
User public key and CSR
User public key (uncompressed P-256)
Not generated.
Signed CSR (PEM)
Not generated.
3. Issue and Verify User Certificate
OpenSSL constructs a draft certificate; extract hashes the TBS certificate, s10 signs it with the CA key, and sig2 inserts the signature. OpenSSL verifies the result.
Signed user certificate
Not generated.
Ready.
Execution log
Reserve a Secure Element to start.
Source: purien/uberca. Certificates are issued only for demonstration and are not publicly trusted.
