Any more invites? k e n c o o p at g m a i l . c o m Thanks!
Introducing the Keybase filesystem
111–120 of 501 posts
Re: Introducing the Keybase filesystem
#112Isn't it against HN guidelines to advertise a private beta?
Re: Introducing the Keybase filesystem
#113> Your app will encrypt just for you and then awake and rekey in the background when that Twitter user joins and announces a key. Isn't this the weak link in the chain? If you can convince the client that you're the person the data was encrypted for, it will re-encrypt it with a new key and send it to you, thus making the encryption useless. What's the protection against this, other than "don't worry, we won't introd…
Well I can audit the source code of my client and be assured that it will only rekey when it sees proof (posted via twitter) that the person the data was encrypted for has joined.
Keybase doesn't have my private key (only I do), so they can't re-encrypt the contents.
(sorry if I misunderstood your question)
Re: Introducing the Keybase filesystem
#114I also have invites if anyone needs them, reply or find my email in profile.
One more invite available for me? luislupe |at| gmail
Re: Introducing the Keybase filesystem
#115Looking for an invite. thanks!
Re: Introducing the Keybase filesystem
#116Earlier quoted context omitted.
"Centralised Crypto" in what sense? Unless I'm very much mistaken, your private key never leaves your control - signing/encryption is done client-side.
They are the trusted source for my public key.
The entire system is architected so that you don't need to trust them for anything, beyond the trust you generally need to have in open-source developers. What is a specific scenario that concerns you?
Re: Introducing the Keybase filesystem
#117I've been using this for a couple weeks. Along with Zcash, it is the most amazing crypto-engineering project I've seen in years. Imagine being able to share files on an ad hoc basis with anyone -- on any network. Share with someone based on Twitter, on Facebook, or email address. Even better, all with cryptographic proofs of identity, strong crypto at every level, and open source.
A bit offtopic, but what do you like about Zcash, and what's different from Bitcoin?
Re: Introducing the Keybase filesystem
#118>If that person hasn't installed Keybase yet, your human work is still done. They can join and access the data within seconds Good luck getting people to do that. Edit: I guess if the audience for this is technical people, then the kind of person who follows them is likely to be the kind that would download it, but that's a very small market. There's a far greater barrier to getting people to install software (with l…
It's also a little bit hard to "join and access your data in seconds" when signup is still essentially by invite only...
Re: Introducing the Keybase filesystem
#119Maybe it's because I am not a keybase user, but can somebody explain this product in human terms? I am not an idiot, and it does sound interesting, but the post is too long and I just want to know what makes it unique compared to dropbox, etc. in one sentence.
This is DropBox with secure digital signatures and end-to-end encryption integrated into it in a easily accessible way.
Re: Introducing the Keybase filesystem
#120I wonder if you can tail a file, to create an ad-hoc encrypted messaging channel like: Read your messages: tail -f /keybase/private/yourname/inbox.log Send a message to someone: echo 'Hi, friend!' >> /keybase/private/yourfriend/inbox.log And I wonder how it handles filename collisions? Guess I'm going to need to play with this a bit later. :)
It works flawlessly! Here's a helper function for chatting which includes your handle before each message (helps keep track of who's saying what):
KBUSER=`keybase status | grep Username | awk '{print $NF}'`;
function say() { echo "$KBUSER: $@" >> /keybase/private/shared,folder,between,multiple,users/chat.txt }