![]() where is the encryption here?! Whatever you put inside your privateįolder can only be read by you and only you. Files are streamed on demand, so you won't be able to access these files without a working Internet connection. Synced between your devices and Keybase servers. Note: please keep in mind that Keybase doesn't work like Dropbox or similar. Haven't been changed by anyone else in the middle. the other users will access these files with the assurance they ![]() You can put whatever you want in these folders: your public PGP key, your official avatar, This is a public folder example of one of the Keybase developers: Share a file with them (or send a message, as we will see later) but you don't follow each other Note: This is very useful if you only know a person on Twitter (or GitHub etc.) and you want to keybase/public/ /hello.txt or /keybase/public/ /hello.txt ![]() Like for example /keybase/public/andreagrandi/hello.txt but you can also use any other identity like Every user public folder/file can be accessed using their Keybase username, Public foldersĪnything you place inside the /public folder can be accessed by any Keybase user and it'sĪutomatically signed. Where you will find at least three other folders: public, private, team. There is a virtual folder located at /keybase (on OSX/Linux or k:\keybase on Windows) One of the first features launched by Keybase was their encrypted filesystem. Very useful in some situations, we will see it later. Without having to know your email address or Keybase username. Once you are on Keybase, other users can look for you even using your GitHub or Twitter username Unless an attacker controls all your social accounts, they cannot impersonate and verify ![]() In Keybase youĬan link your existing online accounts to your Keybase account and show additional You don't just say "I'm Andrea Grandi, this is my PGP key.". Many of us have a personal blog, a Twitter or Facebook accounts, a GitHub account etc.Īll these accounts combined together make our online identity.Įvery Keybase account can be verified by other online identities. In Keybase it's possible to either generate a new PGP key or import an existing oneīut the most important thing is being able to verify our own identity using multiple proofs. To encrypt and decrypt a message for a certain user, but it also introduced a very nice When Keybase was launched it was mainly a wrapper for PGP commands Keybase really makes encryption easy to use. push-secret Push an encrypted copy of the secret key to the server.Using PGP can be quite hard, even if you have a lot of experience with computers.īy the way encryption is what gives us privacy and permits us to safely transmit informationĪnd for this reason it should be easy to use, for everyone. i, -infile Specify an infile (stdin by default). To also automatically push/sync your secret to keybase (so you can then use it on other linked devices) you can use -push-secret: ⇒ keybase pgp import -help ![]() So to export your secret keys, and import them into your local keybase keyring: gpg -armor -export-secret-keys MYSECRETKEYID | keybase pgp import` This is normally not very useful and is a security risk since private keys are left unprotected. This is the same as the command export, but private keys are exported instead of public keys. Just came across this issue myself, and found that the correct args to use aren't shown in the standard gpg -help text: ⇒ gpg -help | grep exportīut you can see the (very limited) help text for it here:Įxport-secret-keys - export secret keys export-secret-keys name. I can speculate to the answers myself, but since it's important stuff I'd rather ask, to be sure. Any other specific risks or things I should be aware of? I want to make very sure my PGP private key remains my own.Does option 2 mean you need to have your private key in a file at your current location? Is the file typically protected with your passphrase?.Does either option 1 or 2 give permanent access for the Keybase app to my PGP private key? Or is it just one time to sign a proof that the public key is mine?.#import from stdin and send the public half to KeybaseĪt first, I thought that they were 3 instructions to be followed in order, but then I realized they were 3 different main things you could do.Ĭan someone explain in basic terms (I know the basics of PGP and public/private key pairs) what the first two options entail behind the scenes? Instead, what I find is this: # import a key from gpg's key chain I had expected instructions to PGP-sign a specific text from the Keybase (Windows) app and re-upload that signed data (base64 or some such). I've created a Keybase account and imported the "easy" identities (e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |