Confirm the recipient has SSH keys on GitHub.
Visit github.com/their-username.keys in a browser. If you see one or more ssh-ed25519 or ssh-rsa lines, they can receive encrypted files this way.
GitHub publishes every user's SSH public keys at a predictable URL. AgePony can fetch them by username and encrypt to them, so you can send a developer an encrypted file knowing nothing but their handle.
Visit github.com/their-username.keys in a browser. If you see one or more ssh-ed25519 or ssh-rsa lines, they can receive encrypted files this way.
Start the Encrypt flow and choose the option to add a recipient by GitHub username.
Type the GitHub handle. AgePony fetches the published keys from GitHub and adds them as recipients. If the account has multiple keys, the file is encrypted so any of them can decrypt.
Select your file, choose armored or binary output, and tap Encrypt.
Send the encrypted file to the recipient. They decrypt it with the SSH private key matching any key on their GitHub profile.
AgePony encrypts so that any of their listed keys can decrypt. They only need the private key for one of them.
AgePony requests the public keys URL, which is already public. No GitHub login is involved.
Then this method will not work. Ask them for an SSH or age public key directly instead.
This guide covers GitHub's keys endpoint. For other hosts, obtain the SSH public key and follow the encrypt-to-SSH-key guide.
Free file encryption for iOS and Android. No accounts, no tracking, no servers.