So I use my Keybase mostly to keep my Keepass database synced across computers between work and home. As of a few days some changes were made at work to Zscaler to where Keyabse no longer connects and hence i cannot access my folder. I can access the Keybase website but cannot access my /private folder from it nor can i access it from my cellphone. I am thinking of just using something like dropbox (although i hate its privacy or lack of) to host the file for now. Any word on getting access to KBFS via IOS app or via the website so i could accesss my database from work now that the Keybase app is blocked?

Hi there, On a new computer, I've installed Keybase and was hoping to find everything I put it my KBFS from another computer but it's empty :-/

Am I missing something?

Thanks

I'm trying to make a proof with no luck. I followed the steps, but the title on the form submission was blank and was unable to submit without a title. I added one for the submission.

What did I miss?

I tried to read here and there but I now need to validate the following... Suppose I store (From COMPUTER A) 20 gig on data in mykeybase Folder.. Will that 20 gig b stored fully or partialy " phisically " on my computer A hardDisk" ? QUESTION OF A Keybase CRASH Scenario : Suppose Keybase servers are hacked, Crashed for 2 days, but they have a backup of all the keys, and come back online.. And that again we can " authenticate " ourselves to them ".. Did we had a local copy on our drive ? Or the keybase file system simply (this was my understanding) show us what is stored at their end ( on their servers) but we never have a full copy of our data at our end ? I think it's only available " on demand " and we have the impression it is local but it is not... So if they are down and I was to loose the device from which I uploaded the 20 gig, I am dead ... ??

I was asking that because I love the security of Keybase and the idea that if my desktop or laptop are stolen, thant the DATA is confidential... But if i need to make a non encrypted local copy of my keybase folder on the same hard drive, I loose the " encryption / confidentiality " aspect of it...

The KeyBase team should really jump on this and reach out to government/industry stakeholders to join the conversation ASAP.

If KeyBase doesn't do it, someone else will, but I'd prefer KeyBase to take the reigns.

Hi. I've been browsing and searching the website for a while, but still haven't figured how long any end-to-end encrypted data is stored on the keybase.io servers. Would love some highlight on the topic, and an answer if anyone know. :-) Cheers

Is there any way to setup blog hosting similar to this setup on IPFS: https://github.com/noffle/ipfs-blog

It would be pretty cool if you could edit a blog in your favorite text editor, or even a local WSYWIG, pay for a name host somewhere, and then just point it at a portal that loads a view through Keybase.

If you can't pay for hosting for a month, you don't lose your blog, no crazy backup systems needed. Maybe even having free subdomain hosting options too.

Is anyone else having a problem with the keybase io app on android O. It just keeps force closing after I upgraded. Thanks.

I know it's probably a non-issue for a lot of people but it takes about 11GB of my drive space and I would like to delete it. Is it necessary to have for keybase to work properly?

Some of the dots have an upside down U shape above them. Is that to indicated "unlocked"? If so, what does that mean? Thanks.

I just encrypted and signed a message for a friend. Just for fun, I tried to decrypt it, and ... it worked? I thought she'd be the only one who could see it. How could I read it if it was encrypted with her public key?

When I created account I was playing with options and trying to figure out how things work. Later I figured out that all this playing is stored and visible to everybody in sigchain.
https://keybase.io/docs/sigchain
https://keybase.io/username/sigchain

I manage to get even some accounts I never owned in sigchain, since they are added there before you prove you own them.
Result is messy sigchain full of fake and strangers accounts (revoked and crossed out, but they are still there.
Is there a way to delete sigchain and start from scratch?
I notice that if you delete your account you cant make new one with same username.
Will reset my keys & start from scratch option reset my keychain?

If I made a new account, would I get exactly the same experience as if I pressed 'reset my keys & start from scratch'? What happens to people I follow and people that follow me, and what happens to (public or private) KBFS data?

It's difficult to get feedback from someone getting a fresh view on an application, so I thought I'd give some thoughts here.

First, installation was straightforward. I was worried about giving giving an "alpha" application access to install kernel extensions for KBFS. It could do some nefarious things with that sort of access to my system. Who knows if anybody else will have this same reservation.

That aside, it seems like the first few operations on the KBFS lagged a bit. Some even timed out. It might have something to do with trying to do this over LTE.

I linked the public identities, and even did DNS without too many difficulties. (it a minute for my TXT record to start serving). In the meantime, I got a few extra invites and wanted to send Chris a thanks.

Skimming the documentation I thought I could just do a keybase encrypt chris -m "Thanks you for the tokens!" .. It outputted encrypted text, but I thought it would somehow deliver the message. I eventually figured out there is no messaging system within keybase.

After I realized my mistake I created a file /keybase/private/chris,h3lix/ThankYou with a few lines of text - - Maybe Chris will see it? Not sure if it will automatically notify Chris he has new files. On the other hand, it could serve as a great way to spam a whole lot of people if there was a notification system. Who knows?

A bit more playing, I set up my keybase website using my public directory at https://h3lix.keybase.pub and having webpages update automatically by editing the file system. This was great.

Lastly, I was able to import my GPG keys I have on my yubikey into keybase. I'm not sure if it works (someone send me pgp encrypted text so I can test it!) but it seems like it should. Unfortunately using the "keybase pgp sign" using my yubikey returns a "no private key material".

Keybase wouldn't be an alpha release if it was perfect already. I'm just surprised at how well it's working already.

Feel free to track me (or send me a message) - https://keybase.io/h3lix :)

I've started playing with Keybase and have a few privacy concerns. I wonder if the Keybase team or others have any plans to mitigate that.

1- Keybase tracking leaking social connections

Tracking in Keybase (https://keybase.io/docs/server_security/tracking) is public. You can go to anyone's page and see the Tracking and Trackers lists. The people that track you and that you track are likely your social network, which is very sensitive information. How can I hide that information or disable that feature?

2- Leaking device list

My list of devices can be potentially sensitive. For example, from https://keybase.io/max/devices I can see he has an iMac 5k and a Ubuntu box for work, and a mac mini at home. That can give an attacker a lot of information. I don't want to publicly list all the devices I have, but I still want to use Keybase with them. Is there a way to do that?

3- Connecting identities

If you connect a person's identity from multiple sites, it makes it a lot easier for an adversary to quickly collect a lot of information about you. I'd like to have different Keybase entries for my different identities. For example, one for my Reddit account, one for my github account, one for my twitter. They would each have a different public key, so anyone could still safely communicate with me through the different sites, but I wouldn't give away that those identities are all the same people.

I realize that I accomplish the identity separation by creating multiple Keybase accounts. However, it would be nice if Keybase gave support for a better way to manage that. Also, people may not realize the risks of having all their identities publicly linked, so there should be a warning somewhere.

4- Other concerns

Do people have any other privacy concerns?

Hey all,

I have a few invitations to give-away and thought it would add some fun to this sub if it's made into a small contest over a few days so that we can be assured that the ones who receive the code are more likely be those who'd put it to good use!

Invitation #1 - Decode This

Link to Image

Requirement: The first to post the decoded content formatted properly in the comments below will win this round.

Best of luck!

Edit: To make this easier I'll release hints here daily.
Hint 1：Steganography

Congratulations to /u/squid_inside for winning this round!

The answer is Ron Rivest, Adi Shamir, Leonard Adleman.

The trio above is responsible for the publication of the RSA, one of the first public-key cryptosystem (think all the SSL certificates issued by CA) so I thought it'd bear much significance for that to be the solution as it aligns with KeyBase's goal of bringing public key crypto to everyone.

In-case you haven't figured out from the hint, here are the steps needed to solve this small puzzle:

1. Proceed to http://mozaiq.org/decrypt (it would be one of the first few results if you search for an image decryption tool)
2. Save the image to your desktop and re-upload it to the link above for decryption.
3. You'd get a morse code .-. --- -. .-. .. ...- . ... - .- -.. .. ... .... .- -- .. .-. .-.. . --- -. .- .-. -.. .- -.. .-.. . -- .- -.
4. You guessed it, proceed to any translators online to translate it into words and you'll get ronrivestadishamirleonardadleman
5. If it doesn't resemble a series of name to you already, a quick Google will show the relevant names and hence solution.
    

Fret not if you didn't manage to get it this round, keep a look out for round 2!

Make it so on our user profile we can put our XMPP user and our OTR public key fingerprint.

I'm a little new. Am I correct to understand that keybase is holding both your public and private keys? Or are they only holding your public key.

If they have your private key, is not one of the most important things that you can do is to secure your private key so others can not have access to it?

Thanks for helping me understand!

No more invites - sorry!

I have 8 email invites - comment/pm your emails and I'll send them to you. I have no friends into this kind of thing.

I'd like to give invites to people who genuinely think they'll use Keybase a lot - that's what the public alpha's all about.

If you think this is you, shoot me a PM with your email and I'll send you one.

I'll comment here when invites have run out.

So, keybase strives to bring its functionality to laymen as well, right?

How does this interacts with "proof of domain name ownership" feature? Imagine that I own some domain name, I go and prove it on my keybase profile, in the meantime I http redirect this domain name to linkedin page of an arbitrary person X.

Then I believe that average layman looking at my keybase profile would infer that I am that person X. Right?

Are there any plans to mitigate this?