Skip to content

Key Molting & hu- Identity ​

ShellGuard is strictly passwordless. There are no server-side user passwords, no email reset links, and no forgotten password forms.


πŸ—οΈ The ClawKey (hu-) ​

Your identity and vault encryption root are unified into a single 67-character cryptographic token known as the ClawKey (hu- + 64 base62 characters; historically aliased the Human Key).

text
hu-3b9f4e81c7a20d4e9b6anuBIPW3ahovCJQX4bipwDKRY5cjqxELSZ6dkryFMT07e
└── Prefix (3 chars)
    └─────────────────── 256-bit Random Base62 Entropy (64 chars) β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The Dual Role of the hu- Key: ​

  1. Authentication Identity (Server-Side):

    • When you log in, your browser computes SHA-256(hu- key) client-side.
    • Only the SHA-256 hash is transmitted to POST /api/auth/token.
    • The server stores the hash and verifies it using a constant-time comparison (crypto.timingSafeEqual).
    • The server NEVER receives or stores the raw hu- key.
  2. Zero-Knowledge Decryption (Client-Side):

    • In your browser, the raw hu- key is fed into HKDF-SHA-256 alongside your user UUID (the HKDF salt) to derive your session ShellCryption AES-GCM-256 key.
    • All secret decryption occurs in browser memory. When you close the tab or lock your session, the key is wiped from RAM.

πŸ“₯ The Vault Access File (shellguard_identity_<username>.json) ​

When you register a new lobster identity during Setup, ShellGuard prompts you to download your Vault Access File:

json
{
  "username": "lucas",
  "displayName": "Lucas",
  "uuid": "4ff11202-d872-4415-99db-1bbad96776d8",
  "token": "hu-3b9f4e81c7a20d4e9b6a...",
  "createdAt": "2026-08-28T20:00:00.000Z"
}

CAUTION

Store this file safely in offline storage or a hardware token. If you lose your hu- key, your vault is mathematically unrecoverable. Because of ShellGuard's zero-knowledge architecture, no administrator or operator can reset it for you.

Sovereign Zero-Knowledge Secrets Vault. Released under AGPL-3.0. β€’ Privacy Policy