██ ██ ███████ ██ ██ ██████ ██ ██ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
█████ █████ ████ ██████ ██ ██ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ███████ ██ ██ ██████ ██████
$
ssh keypub.sh about
- Verified registry linking SSH public keys to email addresses
- No installation or configuration needed - works with your existing SSH setup
- Privacy-focused: you control what information is public or private
- Simple email verification process
- Free public service
$
ssh keypub.sh register alice@example.com
[info] Verification email sent to alice@example.com
[info] Please check your inbox and run: ssh keypub.sh confirm VERIFICATION-CODE
$
ssh keypub.sh confirm 346758
[success] Key registered successfully
[info] Fingerprint: SHA256:llcK7K7Zc6JGHMnrekqr2X/lVkJEoaam4S5eeCPOg0w
[info] Email: alice@example.com verified
$
ssh keypub.sh help
KeyPub.sh uses your SSH public key as your identity. Access the service via SSH commands. Reference other users by email or key fingerprint. For json output append `--json` or `-j`
| Command |
Description |
| register <email> |
Register your SSH key with an email address |
| confirm <code> |
Verify email with code from confirmation mail |
| whoami |
Show your registration details |
| allow <email> |
Grant email visibility to another user |
| deny <email> |
Revoke email visibility from user |
| get email <fingerprint> |
Get email for key (if authorized) |
| unregister |
Remove your key from registry |
| help |
Show this help message |
$
alias kp='ssh keypub.sh'
$
kp why
- Single verified identity for all SSH-based applications - register once, use everywhere
- Perfect for SSH application developers - no need to build and maintain user verification systems
- Users control their privacy - they decide which applications can access their email
- Lightweight alternative to OAuth for CLI applications - just use SSH keys that users already have
- Central identity system that respects privacy and puts users in control