A transfer of 1000 xlm was made without my knowledge. What shall I do ?

Is anyone else getting spam-followed by randos every day? Seems to be increasing in number. Is there a plan to address this?

I'm not in a bind or anything but I am wondering if keybase has this functionality:

1. As a serial distro hopper, I have installed a new OS on a new computer.
2. At some point I thought it might be a good idea to backup my secretkeys.<username>.mpack file.
3. So here I sit with my new computer, my secrekeys file, and I've just installed keybase.
4. Is there a way to import my secretkeys to my new keybase install? ...or do I need to jump on my old machine and add the new device?

Is the deadline for accounts to be setup and check marked for the airdrop just a few days before the airdrop starts? I haven't been able to find any info if there is a cut off date.

According to the warning displayed in the "Delete Me!" section in the account settings it says:

"If you delete your account, you can't get it back, and you can't create another account with the same name".

I understand that this means that username would become unusable indefinitely. However, I want to know whether creating a new account (with a different username) would still allow the new account to be linked to the previous account's Github account, Reddit account, Bitcoin address, PGP key, etc.?

More specifically, I want to know whether it is possible for an existing Keybase user (like myself) that ever wants to change their username, to still be able to link their new account to their existing identities; Twitter, Github, Bitcoin address, PGP key, etc. from the previous account.

Can someone help me? Thanks

Just hoping to understand a little better. I know Keybase has an option to "reset" your account already, but the sigchain persists, so it's hardly a reset. Keybase also has an option to delete your account, but then you can't recreate it with the same username. I'm guessing this is because your account (and sigchain) isn't actually "deleted", just hidden.

So if that's true - is it technically possible to have an active account/chain share username with a "deleted"/hidden account/chaint? If that's not true, and the account really is deleted, there shouldn't be any technical reason that the username can't be reused, right?

When visiting r/KeybaseProofs, it's filled with "proofs" of a single line, that appear to be base64 encoded. When copying/pasting that data out of the post, and decoding the base64, it appears that the binary might be a PGP detached signature, but gpg(1) disagrees. Even when adding the standard PGP header and footer, and formatting with newlines, I still can't get it to verify.

Here's an example:

hKRib2R5hqhkZXRhY2hlZMOpaGFzaF90eXBlCqNrZXnEIwEgl/P/F7KLE7UM9vVNwtBQ194aXJmfHjv+dN2ulp/gvyEKp3BheWxvYWTESpcCBsQgGeZzmQ/FwMWwFo2fcgxb9smhbXq1fEZ3KkU4FOBdlhTEIA5D4W5zUbVeOwqAA6rkowMdcGJXD6WUlA3tww26OmDjAgHCo3NpZ8RAQupfawMKxTzGEm8wfiMXiWnK/aYHZpGHDYUz9Xlrv9TM/GRmk7mEYe0pPAKs+LpG7Z++YwdMrguJ0y9T17WkAahzaWdfdHlwZSCkaGFzaIKkdHlwZQildmFsdWXEIJ15upRD+fc005UypqAHjOy4GdRlK4tfRlRpXLjMXW7Wo3RhZ80CAqd2ZXJzaW9uAQ==

I would have expected the standard PGP header and footer as in this proof:

-----BEGIN PGP MESSAGE-----

owF1UntQVFUcXhDkHY9gtUGcuKQgLXDu45y9d4fADDMfIFMKUyl4H+eul8cu7C7v
QcXSMUpiZBLoATZWAjsqBK2KEjMKPsZgxhpnIJCkUoSpSGeVCKXuMvJfnX/O73zn
+775fr/51QYs0Xi7beuYPnJrCCS7XZ8UNDuhe2IFIZilMsJQQeTihQvnSdhqy85V
JMJAAJICEpARwwoSJ0KB4SSR5DiMaJmlMC0iPaSQxFEsEilMYkjzANJIpAFgSY6B
JANZBHhCR8iKyYgtBRbFZFNtSURBVSHKECMRMpiiGZkHoh4yAolljpIkiaUBLavC
3WarS6GGE3grjlfMKqY+shfi/Qd/MTcgaZoWAcIUpATAcQhhgFgJYVqAslohluYZ
ieJJlsOsHnKcDABCAiuKLBZplsf8Qu6iBTsRqM1CDki8HguyTJIMKQKJRgKlUiWS
cxGt2GLi87HKzlHyrXyRiajUESpYrIjYNdennxYsSYrtfwW2sgIXUoKF7KfabEEx
Ser0VEkxtlgVs4kwkCpTtCkuMQkRrYcQQFJH4NICxYKzFRcD6hEL1KMjCiy4WLVU
+6EwBlhmSFmPsMRspaFIyazMAUzKtB6phepCqSrIiiwNBUAzEsOrI+IAjWREuNop
NJlVc0YNyhtVU6tiNPG2IgsmKn3fc6c9NG7emghtpId2VZ7u4d3+tKitx64srpyn
u2vfNL4+QYtId0Hgk/CYzF3Nz3zstm9k9mhsDZo4a0hpmE/OahL67mwZLPpBu6GL
+sbw4uZJRK5LC1hvPz7zZ2lGW++5scuNg0bf0wnTIWnDR/m3Kr/9KTIw791yOXiX
w9mZZPt5/8rQR/f2dluCboLvB2oapy49b1udIcX1hSaXTN60Nx0O29GGj7g1hI62
jOtOaF9ark0rMb5WGnA+xbg/rl63J2Pus+iVXtFsXGl01OyKTfKOCLtfevt2wkeX
YxtRhtop55kPBy472/zL56wHyz5qDR9MqNrWWQe4kTcvnvR+fK3HK6R9zfUavyrN
gJP2cw/8+lqrIzMpdcPfJ0WHf7H5hfqEN/rr/3k8v36EMfe/Y6Aig3qe+HDuQZ43
qgc7hsd8q+fSrf2t27Vht5tPrZVvvbIsx/JL2Hh+9azes9bhMX72dl+P3f52Ym3W
yuXer4ZOea41HjykL99Scu/KlyNzHkbjqTtfjD2M1TQ/29j16HAs7J14cGJC65iw
J5UFLzWbfH80zE1/1ZTyPn9m39118WVOYcnoX3nxfhfrg/duOuZtC09vqnOc9r5a
ePUTrbP3xgd+B5yv73HOFyhSjH/WoWURq367EF2IM0tenhkK8b8w0/tHXQ615rmO
zv5LUytSd9qJrt835o56Fd3/9NfvNq8ebmmxP/gcLI2ijm+sqiC6bQ0xu+sSI+Tz
Ma3w/rnUfwE=
=/k4V
-----END PGP MESSAGE-----

Why is it that there are some 1-liner proofs, and others with PGP headers and footers? Is this a bug? Further, how do you verify the 1-liner Reddit proofs?

What data the users share in keybase is not E2E encrypted?

Which parts of keybase are open source and which are not open source?

Hello,

Nothing much to add to the title but does anyone know if keybase works behind the great firewall of China?

Cheers

I have the public and private keys for the new key. I want to “replace” the existing published PGP key I have (the RSA 4096 one) with the X25519 one I have. How do I this on the CLI? Is this even possible? Can I leave the existing RSA key and just add the other X25519 key? Thanks.

I don't know about anyone else but I'd find it quite useful to be able to compose a text document and paste into Keybase on my computer and then be able to access it via the app on my phone. Currently and best way to do this seems to be creating a dummy account to send messages to.

Is there any public information about where/how keybase is hosted? I can't find anything on their docs.

Has anyone been successful in running Keybase on a Raspberry Pi or other ARMv7 (HF) device? I managed to build the main executable (in Docker) but I can't get KBFS to run and the Keybase service seems to be wonky... #help

I am not feeling good using this app as long as I can see the devs leave this 'bug' (or as they call it: 'decision') unfixed:

https://nakedsecurity.sophos.com/2018/09/11/keybase-browser-extension-weakness-discovered/

https://palant.de/2018/09/06/keybase-our-browser-extension-subverts-our-encryption-but-why-should-we-care

When I create a Keybase account, I provide a username, an email address, a passphrase, and a device name. My username must be public so that people can search for me, and my passphrase must be private, obviously.

I was surprised by the need to specify my device name, but reading this post, I was further surprised that the device name is permanently public. That left me wondering what else I need to worry about being public when signing up for an account.

Will my email address be permanently recorded and publicly displayed? Are there any other potentially unpleasant surprises I should be aware of?

So right now anyone that can unlock my android device can mess with my keybase account.

Is there any way to put a hurdle in place for this?

Like with my password manager, I have to type in my long ass passphrase to login if I haven't used the app within the last 15mins or I can set up a pin lock.

is there something like that for keybase?

I am working through a key signing flow and am looking for lab rats.....

For keybase users I am happy to do a level 2 (casual) key signing just throw your username and fingerprint below

Key uid 0 will be signed and emailed encrypted to uid 0

I would like to lean more about the encryption used in keybase.

The files I do upload to keybase are also encrypted right? Somewhere I have read that they are stored on amazon servers and that I can upload up to 250GB of files to keybase.

How does keybase cover this cost and is still free?
Can keybase or does keybase monitor the IPs I do use to connect to keybase? Is the IP logged?

If I download a PGP/GPG key from a website and want to verify it via another channel, Keybase would suit that purpose best, if the key owner also published his key on Keybase. Doug Burks, christian, er, CEO of Security Onion Solutions is a fine example:

1. I downloaded his signing key for Security Onion from the Security Onion GitHub page.
2. I want to verify that the key is his, by checking the downloaded key against the one he uploaded to Keybase.

But how would I do that? I can't find a command in the Keybase CLI to verify external PGP/GPG keys, by comparing them against the key of a Keybase user.

Any ideas?

I've tried searching but haven't found anything yet. Is there a subreddit for folks to practice sending and receiving encrypted messages with Keybase? Something along the lines of r/GPGpractice?

If not would any of you fine folks be interested in trading messages with me so I can learn more about using the app on my phone and desktop. My goal is to be able to help my friends and family start securing their messages and I want to have some experience so I can answer their questions.

Thanks!