Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing the Keybase filesystem

keybase.io

Post reply on HN
Print view View original

141–150 of 501 posts

Re: Introducing the Keybase filesystem

#141

Post by cbhl »

jrockway wrote: post #92

> 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…

I think the bigger problem with this is the Skype message deliverability problem. Everyone uses battery-powered devices (laptops and cell phones) now, so it's possible that days or weeks could go by before the app could wake up and rekey the data.

Re: Introducing the Keybase filesystem

#144

Post by greglindahl »

toomuchtodo wrote: post #68
kevincox wrote: post #53

Earlier quoted context omitted.

You don't have to, but unless someone decides to "pin" it it might just disappear at any time. So you better pin it yourself or find someone reliable to pin it for you.

> or find someone reliable to pin it for you. The Internet Archive will eventually be the "pin" of last resort.

And/or someone will make a business out of pinning files.

For public files, I hope that there will be several organizations organizing multiple long-term pins of files.

Re: Introducing the Keybase filesystem

#146

Post by vmp »

I hate begging but I've been in the keybase queue for at least a year and would like to finally see what it's all about. I'd appreciate it a ton if someone could shoot me an invite: [removed] Thank you very much ashishchaudhary! :)

Re: Introducing the Keybase filesystem

#147

Post by zobzu »

Unfortunately you just need to hack keybase and serve malicious code. It doesnt matter if its signed if my malicious code tells you the signature verification succeeded.

Client side needs versioned code to make this harder. Including signed, versioned javascript code, automagically.

This will also make alterations of web sites code a lot easier to detect.

Re: Introducing the Keybase filesystem

#148

Post by ryan-c »

stoye wrote: post #129
ryan-c wrote: post #80

Random unrelated keybase question: I generated new subkeys with GPG recently - how do I update my keybase account? The master key has not changed.

I think you're looking for: keybase pgp update

That does not work - I have to log in with the command line client, which fails because I it doesn't have GPG sign with the correct key. Edit: Managed to get it to work by restoring a backed up keyring from before I updated my keys.

Re: Introducing the Keybase filesystem

#150

Post by toomuchtodo »

greglindahl wrote: post #144
toomuchtodo wrote: post #68

Earlier quoted context omitted.

> or find someone reliable to pin it for you. The Internet Archive will eventually be the "pin" of last resort.

And/or someone will make a business out of pinning files. For public files, I hope that there will be several organizations organizing multiple long-term pins of files.

That's the best part! Anyone could be paid to pin!

Home users with enough bandwidth and storage. Existing CDNs. New cloud storage entrants (Backblaze).

Literally anyone with an internet connection and storage would be able to securely serve your content.

EDIT: I just saw your profile :) Thanks for the work you do at the IA!

Post reply on HN