Contents
Is Keybase really safe?
Keybase uses 256-bit encryption. This means someone would have to try more than 115 quattuorvigintillion possible keys to hack your private key. Not even a hundred thousand computers could try all those keys in trillions of years. This makes it safe for your public key to be public, as it is on Keybase.
What’s the point of Keybase?
Keybase allows users to prove a link between certain online identities (such as a Twitter or Reddit account) and their encryption keys. Instead of using a system such as OAuth, identities are proven by posting a signed statement as the account a user wishes to prove ownership of.
How is data encrypted on the client side?
Data that you encrypt on the client side arrives at Cloud Storage in an encrypted state, and Cloud Storage has no knowledge of the keys you used to encrypt the data. When Cloud Storage receives your data, it is encrypted a second time. This second encryption is called server-side encryption, which Cloud Storage manages.
Do you need a key to sign a message on Keybase?
After entering your information, it will ask if you want to push a copy of the encrypted secret key to the keybase.io servers. This part is optional, but if you want to sign your message (proving that the message is from you) or decrypt them directly from the web application, you’ll have to add it.
What can I do with my public key on Keybase?
Keybase also maps your identify to your public key: you can link your other social accounts such as Reddit, GitHub, Twitter to your Keybase profile. Keybase offers encryption via a web-based client, but also offers local, command-line clients for all major operating systems.
Do you need a PGP key to use Keybase?
The key part of Keybase is encryption. You can encrypt your message through the Keybase web platform: If it’s your first time encrypting information, and you don’t have PGP key, Keybase can generate keys for you. Click on add a PGP key.