WispPGP vs PassPony

WispPGP is a focused OpenPGP toolkit for iPhone. Encrypt, decrypt, sign, and verify text in seconds, or use the Share Extension to protect content from any app and send it as ASCII‑armored .asc. Manage multiple keys, set an active key, and keep your workflow fast and predictable. Built for iOS 17+, WispPGP keeps cryptography practical: generate key pairs, label keys clearly, and choose whether to share encrypted output as a file attachment or as plain text. The experience is intentionally clean so you can work quickly without losing control of important details. Powered by GoOpenPGP (MIT) for broad OpenPGP compatibility. Armored exports include clear headers: Version: WispPGP, Comment: https://micro.mjanssen.nl/wisppgp Highlights • Encrypt and decrypt messages with OpenPGP. • Sign and verify messages to confirm authenticity. • Generate and manage multiple key pairs with name, email, and comment. • Set an active key to speed up repeated actions. • Share encrypted output as ASCII‑armored text or .asc files. • Use the Share Extension to protect text from any app. Security & Privacy • Biometric access is required for private keys and stored passphrases. • Private keys are stored in iOS Keychain with device-only access. • No plaintext key files are written to disk. • Sensitive passphrases are cleared when the app goes to background. • Optional clipboard auto-clear after pasting. • The source code is open source, so anyone can review what happens with their private keys. Security Test Checklist • Key Manager access prompts Face ID; cancel keeps the screen locked. • Private key actions (Decrypt/Sign/Export) always prompt biometrics. • Lockout behavior: repeated failures show the biometry lock message. • No biometric enrolled: shows a clear not enrolled/not available message. • Passcode disabled: shows a clear passcode-required message. • App backgrounding locks Key Manager again on return. • Share Extension prompts biometrics for private-key operations.

PassPony is a password manager for people who want to own their passwords. Every entry is one encrypted file in a store you control, in the same format as the pass and passage command line tools. Your Mac, your server, and your phone can all work on the same store. WHY A FILE-BASED STORE One entry, one file: the password on the first line, anything else after it. Encrypted with your keys: age identities for passage stores, OpenPGP keys for pass stores. Synced with git: clone your existing store, publish a new one, and resolve conflicts per entry, never with a silent merge. Interoperable: commits match the pass CLI format, so the store stays fully usable from the desktop tools. EVERYDAY USE QuickType autofill: your passes appear above the keyboard when you sign in. Only entry names are indexed; nothing decrypts until you fill. Live one-time codes: entries with an otpauth line show a TOTP code with a countdown ring. Face ID or Touch ID unlock, with a five-minute grace window shared with autofill. Ephemeral clipboard: copies are local only and clear after 45 seconds. Field-level editing that preserves the exact bytes of lines it does not touch. PRIVATE BY ARCHITECTURE No account, no signup, no PassPony server. The only network connection is the git remote you configure. No analytics, no ads, no tracking. Open source, Apache-2.0. The full app and its Rust core are published in a public git repository for anyone to audit. FORMATS passage stores encrypt with modern age identities. pass stores encrypt with OpenPGP keys (Cv25519 and X25519/Ed25519 in software). RSA-keyed stores need a smartcard, which is not supported yet. Each format keeps its own store; switching never touches the other. Localized in English, Spanish, French, German, Simplified Chinese, Brazilian Portuguese, and Russian. If you already run pass or passage, PassPony is the missing phone half of your setup. If you have never used them, the first-run tour will have you adding your first pass in about a minute.