6 ms·
Pretty Curved Privacy
- e12e 10y agoI was sure I'd came across this on HN, but apparently I found it when I wondered if anyone had taken a crack at taking NaCl and made a PGP work-alike using the primitives NaCl provides. And here it is. Anyone have any experience with it? Done a cursory review? At this point I'm a fan of the idea (a set of protocols to mirror some of the good parts of PGP, married with the good parts of NaCl. At least in ... theory...).
- lazard 10y agoI built flycrypt as a highly simplified PGP based on NaCl. I've used it to send credit card numbers and passwords over email. https://github.com/davidlazar/flycrypt https://github.com/davidlazar/flycrypt
- 0xmohit 10y agoCould somebody please change the URL to https://github.com/TLINDEN/pcp https://github.com/TLINDEN/pcp instead?
- mstef 10y agoback in the days i consulted with tom on pcp a bit. Why, because i took it a bit further with: https://github.com/stef/pbp https://github.com/stef/pbp - there's even an axolotl implementation available - but not integrated yet: https://github.com/stef/saxolotl https://github.com/stef/saxolotl
- mstef 10y agoalso there will be soon (in 1-2 months) a hardware token available based on this. look for project: PITCHFORK
- mstef 10y agoi also gave a talk on pbp: https://www.youtube.com/watch?v=Kl_gLMef1mI https://www.youtube.com/watch?v=Kl_gLMef1mI
- dfc 10y agoInstead of adding new comments you should be able to edit your comment. At least as long as the comment is not many hours old.
- xorcist 10y agoIf you need a "real" PGP, GnuPG 2.1 has had experimental support for Curve25519 since 2014. In the most recent version the experimental warning label was gone, so it should be pretty stable by now. Many keyservers still barf on the keys though.
- mstef 10y agothe problem is not that "pgp doesn't use 25519" the problem is the openpgp format as per rfc4880 and the whole thing being from the naive nineties, not suited for advanced adversaries we have since then.
- smcl 10y agoThat example in the README.md of Alicia and Bob generating a keypair, importing each others public keys, then encrypting/descripting a simple note is really well laid out.
- tptacek 10y agoThis package, by Watson Ladd, is the same idea implemented by an expert: https://github.com/wbl/cpgb https://github.com/wbl/cpgb
- lisper 10y agoAnd this one is the same idea implemented using TweetNaCl instead of NaCl, so much smaller code base, and audited. https://github.com/Spark-Innovations/SC4 https://github.com/Spark-Innovations/SC4
- sigcode 10y agoThe use of the word "expert" here gives me pause. I thought one of the motivations behind this library was that you did not need to be an "expert" to use it.
- buu700 10y agoWhile NaCl/Sodium does simplify the crypto aspect in particular, it's dangerous to assume that it entirely solves the broader problem of writing secure code. Implementing anything securely is hard enough before involving crypto that the level of expertise required doesn't change all that much. (Most catastrophic vulnerabilities in security software aren't directly in the cryptographic implementations.) Even using NaCl, one needs to understand enough of what's happening under the hood to properly reason about the security of the whole system they've built.
- sigcode 10y agoAgreed. Now kindly point to the mistakes the author has made so others can learn from them.
- buu700 10y agoI wasn't actually commenting on this project in particular or whether or not the author happens to be an expert (tptacek may have more to say about that), just on the idea of NaCl as a replacement for expertise.
- jaredwindover 10y agoRead Pretty Curved Piracy multiple times. I'm kind of disappointed. I... don't know what I expected.
- X86BSD 10y agoMy question is: People don't even use PGP and it's been around for over 20 years. What makes this more adoptable, if it all? The problem with most encryption is, it's not transparent to the end user. The second users have to start goofing around with key generation, uploading keys, etc you lost. I get that using Curve25519 is "better" but none of this still solves the fundamental problem of end user adoption.
- mstef 10y agothe problem with "transparent to the end user" is a variation of Geers Law: "Any security technology whose effectiveness can't be empirically determined is indistinguishable from blind luck." if you do not control your keys, then someone else does.
- rakoo 10y agoFrom the README: > In fact, I wrote it just to learn about the curve and see how it works. I don't think the author seriously considers replacing PGP with this.
- Sir_Cmpwn 10y agoAre these algorithms resistant to quantum attacks?
- mstef 10y agonot the curve25519 based ones, the symmetric salsa based ones should be.
- Sir_Cmpwn 10y agoCool. I suspect that's going to start being a problem in the next decade or two, assuming that government entities haven't already made sophisticated quantum computers in secret.
- deleted 10y ago[deleted]
- curried_haskell 10y agoWhat are Alice and Bob talking about, anyway, that's so damned important?
- AtticHacker 10y ago> Please note the big difference to GPG though: both Alicia AND Bobby have to enter the passphrase for their secret key! That's the way CURVE25519 works: you encrypt a message using your secret key and the recipients public key and the recipient does the opposite, he uses his secret key and your public key to actually decrypt the message. Forgive my ignorance, but I assume that this is to ensure that the message is from Alicia. How is this different from signing + encrypting a message in PGP?
- bascule 10y agoDespite all the claims in the README, Curve25519 has in fact been standardized (at least informationally) by the IRTF CFRG in RFC 7748: https://tools.ietf.org/html/rfc7748 https://tools.ietf.org/html/rfc7748