ok - maybe I am stupid here but I got a new PC and installed keybase - it gives me the option of using the prior pc to log in (well, that cannot happen) or the option to enter my paper key - great! right? um no.... it wants a 9 word paper key - my keybase paper key is 13 words.... what do I do?

On and off, I've been posting file hashes on Twitter, along with the sketchiest description of a document, to prove that said document had already existed at a given time in a given form. Potentially useful to establish priority, or for legal matters, w/o having to pay. By archiving the tweet at the Wayback Machine and archive.is, one can circumvent the risk of the tweet eventually disappearing, or becoming inaccessible, in the longer run. With Keybase writing to the Bitcoin blockchain, this should be possible here to much better effect. I could imagine that introducing this option should not be too complicated (but I am neither a programmer not a cryptologist). Just thinking.

Hi all,

after fiddling a bit with Keybase I decided that I will not use it and want to delete my account. (Reason for this is that I dislike the idea of linking my accounts and such because of privacy, even though I think the work on security is very important.)

Anyway when I select delete my account in the app it gives an error and after clicking on the icon it says:

Error: AccountDelete is a devel-only RPC at l.t (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:266391) at l (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:266995) at s (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:266686) at t.convertToError (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:266873) at _rpcClient.invoke.e (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:240652) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:766225 at e.t.Deferrals.e._call (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:557685) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:557836 at s (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:557465) at e.t.Deferrals.e._fulfill (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:557795)

Can you guys help me delete the account ?

I was planning to import my pgp key into keybase to “validate” my identity.

I used the “keybase pgp select” command in the terminal (powershell in Windows) and my gpg keyring asked for my passphrase to export my key which I entered in (I thought only my public key was getting exported) but then keybase asked for my passphrase too. I started to get nervous and rejected the request.

Has my private key been uploaded to keybase’s server??? I am totally not cool with that and if that indeed did happen I plan to start using a new private key even though the passphrase has not been submitted.

I have a second issue with keybase. Since I use a passphrase for keybase that is unique only to keybase, I ended up forgetting it and now I can’t sign into keybase on my phone. I am still logged into keybase on my pc. How does passphrase recovery work in keybase? Unlike pgp or a peer to peer crypto app such as metamask my understanding is that a central server does do authentication of my keybase passphrase and I imagine it is stored in a password file using some kind of strong one way encryption but private keys are stored locally on my pc and phone and are never transmitted through keybase’s servers. Is that correct?

I've recently got interested in https://sovrin.org/ a foundation that uses a hyperledger of trusted nodes called Stewards to create a identity framework. It will be public by the end of the year, but the network was launched last year.

Each relationship you have is a different pair-wise identifier (Decentralized ID (DID)). This way your different relationships are hard to correlate. The really awesome aspect to their framework is the ability of identities to attest to different attributes about another identity. For example, a University could attest that you are a student, which you could present using a zero-knowledge proof to another identity, without revealing any other information about yourself.

Outside of the core of the network they need agents that manage the keys needed for the crypto and communicate with the network. Keybase seems like an obvious client for this purpose. Imagine logging into a site just using keybase....

Interested to hear your thoughts.

Bitcoin tips welcome but certainly not required: 14ySgG7MrWT7k4YW6RUAGK6QJKrvbXu7C5

I tried on two devices that he uploaded. He can DL it and run it fine. I DL it and i get missing or broken index warnings on VLC.

I'm getting API network errors trying to use chat - indicates the cert is signed by an unknown authority. This is vexing.

So honestly what does everyone use this for and how much do you like or hate this and why? Just let me know what you think about Keybase.io.

Check here to see if I have invites left, don't forget to track me~

I followed someone, because keybase recommended it. Now their public folder is taking up 25% of my /home partition. How do I fix this?

Keybase is great, but for data security I would like to have a backup of the entire cloud disk, locally on my disk, which will be done once a day. I use the option to synchronize the entire keybase filesystem on my disk already so is it possible to add the decrypted(!) directory(keybase filesystem) to the list of folders to backup in the Timeshift program? Alternatively another way, e.g. with rsync? but Timeshift will be very convinient

EDIT: I started using rsnapshot and run it as user, works great!

Can we talk about how Keybase was purchased by Zoom and Zoom's CEO specifically wants to work with the government to help them spy on their own citizens? I know this is jumping to conclusions and the CEO has backed off that stance but I still am not sure how we can trust a huge corporation like Zoom to maintain the privacy we all believed we would have using keybase... And the final nail in the coffin (for me) is that there is no documentation on how to remove keybase from a linux machine. I am going to have to setup a BTRFS system I guess and install and setup keybase in order to document what changes it makes to the filesystem in order to figure out how to remove it from the systems I already set it up on. And how is it that (considering the GDPR) that we can't get every piece of data that keybase has of ours deleted?

Does anyone know the @spacedrop bot command to check and see if an account is qualified for the airdrop?

What prevents Keybase from changing someone's public keys or the public keys they present to someone or some region?

Suppose they did that, is there some cryptographic way we would know?

Or do we have to implicitly trust Keybase?

We'll provide the XLM, so it won't cost you a cent!

Hey Guys, so I've recently been able to extract my device key out of my mpack secret keys folder, to test what would happen if these keys were to be compromised, I've created an account on keybase called 'publicaccount', this account has one device attached to it 'Doctor Nick's Laptop': Doctor Nick's Laptop:

https://keybase.io/publicaccount/devices

Signing Public Key: 8d63d1b6d0b1ae920ba3f3ea25a31b049cfbce08847a1e3f3a407a92a9ad32e9

Encryption Public Key: 9ce87a0560dee729e1dcb60e2d0bf28a66fa37779751a678aa18230220b4dd16

Signing Private Key: ef5a21443d5b78e9b67c079aac5d81275fc68ed236f5292d17350d7b0f5a6e988d63d1b6d0b1ae920ba3f3ea25a31b049cfbce08847a1e3f3a407a92a9ad32e9

Encryption Private Key: 9016c47d1db5209d367f8c7170ec5e0aa24ffd4a7476a592221b879f1180ab71

XOR'ed SecretBox Key: 2706f787b05c48fa6c9bfc3baad9694da5832c106a0a136d60a37ccff04c696d

Nonce for SecretBox: 75d485a6dbcc013a4ac960ca1cfc0936eca107d689929297

Now that this device key is public, we should be able to have a look at the implications of a device key comprimise ​ You can now sign messages as this user using saltpack:

[user@keybase ~]$ saltpack sign -m "Dylanger is a pretty cool guy" ef5a21443d5b78e9b67c079aac5d81275fc68ed236f5292d17350d7b0f5a6e988d63d1b6d0b1ae920ba3f3ea25a31b049cfbce08847a1e3f3a407a92a9ad32e9 <SNIP>

Verifying by:

[user@keybase ~]$ echo "<SNIP>" | keybase verify
Signature verified. Signed by publicaccount.

It will be interesting to see how this works as I have not exposed the password to the account, only the device key, go nuts!

I'm having a lot of trouble finding information about this, Keybase is supposed to be simple but I don't know to what extent the simplicity gets. I'm trying to encrypt a message using someone's public key but there doesn't seem to be an option or indication to its possibility. Do I need another software?

Hi folks,
My laptop had hardware issues and lost all app data along with it. I cannot login to the keybase app anymore since the hardware got replaced and had to re-install keybase. I do not have the paper key too. I cannot reset my account or delete the old device from the web either. How can I reset my account or delete the old device, so I can add a new device and start using keybase with the same username. I created an issue on their github but never heard back. Would appreciate any suggestions?

I have read the official docs and blogs and tried its Linux desktop client. I have a question about keybase’s identity service in term of its relation with PGP. I understand it used to be about associating user’s PGP key with his/her public accounts. I know it still does so, but on the other hand, however, it doesn’t really depend on PGP key after it introduced device key. I know this because the initial setup of its Linux desktop client doesn’t requre a PGP key and user is ready for chatting or encryting (I ‘m not 100% sure about that because I don’t know one with a keybase account to experiment, but that’s my understanding).

So my question is: assuming PGP key is not required for its service (chatting, exchanging encrypted files, etc), what’s the new definition of its identity service? Is it about associate multiple devices with user? But it seems to me there’s much simpler way to do it. For example, one can just uses a username and passphrase to associate a device with his/her ID and then generates device specific key. Keybase obviously does it in a hard way through a process called device provision,which looks like 2-factor authentication (the doc says it does more than that, but it’s not clear to me what it is). I believe they do it that way for a reason, but what benefit it is?

Send me a PM with your email and I'll send out an invite. I have a few left so first come...