![]() Until then, you can use something called as “paper keys”. The mobile apps are still in development. So if any user has their device compromised, it will let you know. In case any of your devices is compromised, remove it from your account. Each device comes with an encryption key. You can add devices to your keybase account. It might be safe but your private key is meant for your eyes only - better to keep it that way. $ keybase pgp select # if you already have keysīe cautious about adding your private key to the Keybase server. If you prefer to use the CLI: $ keybase login This is will open a GUI where you can login. After joining, install the keybase app for your desktop. Note: The following is primarily meant for Linux. Everything in your public folder is signed by you and private folders are end-to-end encrypted which means even Keybase can’t see them! There are two types of folders - public and private. In simple terms, it’s a secure way of file sharing. The awesome file system: Keybase also has a file system of its own called KBFS. ![]() So people now know that one of your devices was hacked and they won’t send messages to that device anymore. If one of your devices get hacked, you can remove that device from your Keybase identity. Protection against hacks: Keybase associates each device you own with an encryption key. This is quite handy if you want to send/recieve encrypted messages - it eliminates the need to share the key with the person separately. Storehouse of public keys: Keybase can be considered as a storehouse with easily searchable public keys. You will have to post something on twitter, github gists, etc to tell everyone that you control these accounts. Once you do this, people can feel comfortable sending you messages even if they haven’t met you IRL. Essentially, you are claiming your accounts and hence your identity. This reinforces my conviction in your public key and makes me feel comfortable in sending you the message.Įstablishes identity: Keybase solves the problem of fake accounts by making you ‘prove’ your online identity - twitter, github, etc. So now I get to verify your identity and know that the person claiming to be you on twitter is actually you (as with github, etc). It will require you to post on each of your accounts - claiming them and linking back to your keybase account. Keybase establishes trust by connecting to your social accounts. However, I want to be sure that it is indeed you to whom I am sending the message - this is where the trust factor creeps in. ![]() If I want to send you an encrypted message, I can easily find your public key. Keybase is a trusted storehouse of public keys. Hope this post clears all the fuzzy theories you have about Keybase. It took me some googling to figure out what it really was. The concept of Keybase seems to be easy to understand…once you have understood it! When I first heard of it, I was confused. (At the time of writing this, Keybase does not require an invite even though the landing page of the website says otherwise. Unfortunately, when I first set my sight on it, it required an invitation to sign up. Ever since I heard of Keybase, I wanted to join it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |