If you do not sign the message or file, the recipient will be able to decrypt it but they won’t necessarily know it came from you. So, when your message is decrypted by the recipient, they’ll know for certain that you encrypted it and it hasn’t been changed by anyone else. If you choose to sign an encrypted message or file, your private key will also be used. Rest assured that only your recipient will be able to read it. From there, you can put the encrypted file anywhere you like. The encrypted file is automatically saved alongside your original file in the Saltpack format. If they’re not on Keybase yet, they’ll need an account before they can decrypt it.Īn encrypted message can be copied and pasted or exported so you can easily store or share it anywhere. You can encrypt something for anyone using their Keybase, Twitter, Facebook, GitHub, Reddit, or Hacker News username. Keybase will use your recipient’s public key to encrypt the message or file so only they can decrypt and read it. Just copy and paste, type it right in, drag and drop, or find a file. EncryptingĮncrypt a message or file you want to share with someone specific. You can decrypt and verify messages and files from others. (Encrypted or signed text is also known as ciphertext.)Īmong other things, this allows you to encrypt or sign messages or files and then share or store them safely anywhere. Messages and files that have been encrypted or signed through Keybase are converted into a Keybase format called Saltpack (you’ll see Saltpack in the file names). All you see are messages and files that you can read or store, safely and securely, within Keybase.īut, you can also encrypt, decrypt, sign, and verify messages and files that need to exist outside of Keybase but remain safe and secure. Everywhere else in Keybase, encryption, decryption, signing, and verifying happen seamlessly.