Keybase pgp decrypt11/19/2023 If you do choose to store your private key on the server, you take the chance of keybase being hacked. Unless someone hacks your twitter/github etc. If you don't store your private key on the server, yes. You get to verify a users identity, so you know that the person claiming to be me on twitter is actually me (as with github etc).Encryption is easy, as keybase provides the verified public key for you.ĭo you think that using such thing will be secure You can handle the decryption yourself or let keybase store your private key.Ĭould you please describes to me the security benefits of encrypting and decrypting messages using Keybase.io. If you don't want to store your private key on keybase, you don't have to. So, keybase never sees your encrypted message. Some people have strong feelings about this, for good reason ![]() On the website, all crypto is performed in JavaScript, in your browser. Keybase.io is also a Keybase client, however certain crypto actions (signing and decrypting) are limited to users who store client-encrypted copies of their private keys on the server, an optional feature we didn't mention above. The encrypted message can then be sent however you want. ![]() ![]() Encryption can happen via the command line, or the website. Keybase will provide the public key, which can be used to encrypt a message. Keybase just provides a means of getting a public key for a known username on x platform (for example, I have my twitter name and my github verified on keybase, people can use keybase to verify that my twitter is actually mine). The encrypted messages doesn't have to go through their servers.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |