That 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.
Pretty Curved Privacy
11–20 of 47 posts
Re: Pretty Curved Privacy
#12back 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 - there's even an axolotl implementation available - but not integrated yet: https://github.com/stef/saxolotl
Instead of adding new comments you should be able to edit your comment. At least as long as the comment is not many hours old.
Re: Pretty Curved Privacy
#13This package, by Watson Ladd, is the same idea implemented by an expert:
Re: Pretty Curved Privacy
#14This package, by Watson Ladd, is the same idea implemented by an expert: https://github.com/wbl/cpgb
And this one is the same idea implemented using TweetNaCl instead of NaCl, so much smaller code base, and audited.
Re: Pretty Curved Privacy
#15I 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...…
I built flycrypt as a highly simplified PGP based on NaCl. I've used it to send credit card numbers and passwords over email.
Re: Pretty Curved Privacy
#16Read Pretty Curved Piracy multiple times. I'm kind of disappointed. I... don't know what I expected.
Re: Pretty Curved Privacy
#17My 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.
Re: Pretty Curved Privacy
#18Could somebody please change the URL to https://github.com/TLINDEN/pcp instead?
Thanks, we updated the link from https://github.com/TLINDEN.
Re: Pretty Curved Privacy
#19This package, by Watson Ladd, is the same idea implemented by an expert: https://github.com/wbl/cpgb
The 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.
Re: Pretty Curved Privacy
#20My 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.
the 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.