4 ms·
The problem is that my mom does not need to use git or github or even know what they are. I would not mind it if my mom encrypted her emails though, or at leas
by davidw 13y ago
The problem is that my mom does not need to use git or github or even know what they are. I would not mind it if my mom encrypted her emails though, or at least knew how. Offhand, keybase.io looks nice but still a far ways away from a "mom friendly" system.
- skrebbel 13y agoIt's a step in the right direction. I'm a coder yet I don't understand much about encryption and certificates and signing. Keybase makes it more accessible to me. If you assume that there's many people like me (I bet there are: non-security obsessed coders, geeks, whatnot), then the existence of Keybase makes these concepts accessible to a larger crowd than before. That's a win.
- ndeine 13y agoI think the target userbase for Keybase is nerds who found GPG too horribly unintuitive to figure out how to use it for themselves. I know I was like that for a while. The other target userbase is people who want to verify GPG keys that don't have a web of trust. This is useful for, say, me - I'm not part of the Debian dev team or anything, so I don't have many people around who can sign my GPG key. It's nice to be able to publish a link to Keybase on my website and have people be able to be pretty sure it's me.
- edraferi 13y agoI actually really like the trust model that keybase.io uses. You control a lot of a distinct spaces on the web: github, twitter, email, personal domain, etc. It makes a lot of sense to have those reinforce a single public cryptologic identity.
- conorgil145 13y agoI am working for Virtru, a startup building the "mom friendly" way to send encrypted email directly from your existing Gmail account (and others!). My Mom does not understand encryption at all, but has no problem using Virtru to communicate securely with some of her business co-workers. Basically, it works like this (for example, with browser extension client): 1) the client generates a symmetric AES-256 key and uses that to encrypt the email locally 2) Gmail traffics the email to recipients normally, except the body of the email is now encrypted before it even leaves the client (the body also includes the unique id of the key, unencrypted) 3) the key is sent to a third party key store (Virtru) which controls access to the key based on identity (OAuth/OpenID) https://www.virtru.com/what-is-virtru https://www.virtru.com/what-is-virtru It could be interesting to do some type of mash-up with Virtru and Keybase.io so that Virtru could automatically pull recipients' public keys and use a PGP type flow as opposed to the default of a symmetric key. Happy to answer questions if anyone gives Virtru a try.
- napoleond 13y agoWhat we really need is an intermediary. The people who develop crypto primitives are currently too far removed from the people who develop consumer apps (obviously excepting guys like 'moxie), and (rightly or wrongly) the majority of consumer app developers don't know how or don't care about bridging the gap. A central key repository with de-centralized identity proofing like keybase would be an interesting idea if it had a good developer API (which I assume is in the works) and if good cross-platform PGP libraries existed (a bit trickier... GPG is not iOS-friendly and any lib which ignores that market is not serious about being accessible to consumers). So, in other words, keybase could be a valuable and important step toward a "mom friendly" system, but it's a bit early to say.