Password & Secret Generator
Generate cryptographically random passwords, RADIUS shared secrets and pre-shared keys using the browser CSPRNG, with entropy calculated honestly.
Result
About Password & Secret Generator
Random secrets should come from a cryptographic random source, not from a pattern a human invented. This uses the browser CSPRNG and reports the actual entropy, which is the only number that matters when comparing password policies.
Where generated secrets should live
A secret is only as good as its storage. Device shared secrets, API keys and service credentials belong in a password manager or a secrets store (Vault, AWS Secrets Manager, SOPS-encrypted files in Git), not in a configuration backup, a ticket or a spreadsheet. Rotate on staff departure and device replacement rather than on a calendar, and prefer one unique secret per device so a single compromise has a bounded blast radius.
Entropy, not complexity rules
Entropy is length × log2(alphabet size). A 24-character alphanumeric string carries around 143 bits - unbreakable by brute force. An 8-character password with an uppercase letter, a digit and a symbol carries about 52 bits, which falls to a modern GPU cluster in hours. Length beats character-class rules decisively, and the composition rules most policies mandate mainly produce predictable substitutions.
Common use cases
- Creating a RADIUS shared secret or a WireGuard pre-shared key.
- Generating service account credentials during a deployment.
- Producing a batch of unique secrets for multiple devices.
Edge cases and gotchas
- Anything generated here exists only in this tab - store it before navigating away.
- Do not reuse one secret across devices; a single compromise then exposes the estate.