News for hackers. Stuff that matters.
Re:OpenPGP best practices by schwarrrtz on Tuesday April 05, 2016 @11:52PM (#11436488)
Moxie on GPG:

> The protocol reflects layers of cruft built up over the 20 years that it took for cryptography (and software engineering) to really come of age, and the fundamental architecture of PGP also leaves no room for now critical concepts like forward secrecy. [0]

> We could try to slap a GUI on top of it, but I don't believe great products are made that way. Good UX requires thinking about interactions all the way down to the protocol. [1]

[0] http://www.thoughtcrime.org/blog/gpg-and-me/

[1] https://news.ycombinator.com/item?id=9104562

Re:OpenPGP best practices by DyslexicAtheist on Wednesday April 06, 2016 @02:07AM (#11436940)
>> We could try to slap a GUI on top of it, but I don't believe great products are made that way. Good UX requires thinking about interactions all the way down to the protocol.

unsure if I agree. A lot of the user-space Unix/Linux Gui applications are built that way: command line interface first and GUI to control that. (the opposite of windows where often a cmdline interface is built to control the functionality provided by the GUI application).

So by that logic the majority of applications that have a GUI are labelled "not great products". Hmmmm ...

Re:OpenPGP best practices by schwarrrtz on Wednesday April 06, 2016 @02:36AM (#11437033)
I think what he means is that building a GUI wrapper around a CLI can't make up for deficiencies in the CLI itself. I don't think he's against GUIs in general.
Re:OpenPGP best practices by masklinn on Wednesday April 06, 2016 @04:08AM (#11437386)
> So by that logic the majority of applications that have a GUI are labelled "not great products". Hmmmm ...

When it comes to Linux GUI applications, that's a pretty fair description. Understated and over-praising if anything.

Re:OpenPGP best practices by pmoriarty on Wednesday April 06, 2016 @12:08AM (#11436538)
What's a good alternative?
Re:OpenPGP best practices by ashitlerferad on Wednesday April 06, 2016 @12:26AM (#11436601)
moxie's stuff is, but it is designed for the always-online mobile world:

https://whispersystems.org/

Re:OpenPGP best practices by xorcist on Wednesday April 06, 2016 @06:17AM (#11437824)
That's not an alternative to PGP. PGP is not meant for streaming data, it is for store and forward systems (traditional email, signing packages, etc.).

Alternatives to PGP should probably include S/MIME and Signify, depending on what you want to do with it.

Re:OpenPGP best practices by simoncion on Wednesday April 06, 2016 @02:24AM (#11437000)
> ...it is designed for the always-online mobile world

Soft disagree with that. Signal text and voice chat works just fine if all of your communicating party's machines are offline. (Well, I mean, obviously your voice call won't be answered, but otherwise...)

Re:OpenPGP best practices by Freak_NL on Wednesday April 06, 2016 @03:42AM (#11437270)
You can't use Signal without a smartphone running Android or IOS. Even the webapp requires a linked smartphone; a phone number is a hard requirement of Signal.
Re:OpenPGP best practices by masklinn on Wednesday April 06, 2016 @04:11AM (#11437397)
1. that's not a property of the protocol, it's the way they implemented verification

2. it absolutely doesn't require a smartphone, just a routable phone number, that can be a cell phone, a landline, a voip number or a google voice number: http://support.whispersystems.org/hc/en-us/articles/21247611...

Re:OpenPGP best practices by simoncion on Wednesday April 06, 2016 @03:40PM (#11441299)
> Even the webapp requires a linked smartphone; a phone number is [currently] a hard requirement of Signal.

I never said otherwise. What I said was:

> Signal text and voice chat works just fine if all of your communicating party's machines are offline.

This was in response to an assertion that Signal was designed for the "always-online" world. Signal works just fine when your contact is completely offline for extended periods of time.

Re:OpenPGP best practices by kpcyrd on Wednesday April 06, 2016 @07:17AM (#11437993)
The jolla store for sailfish has a patched version of signal that doesn't require the google play service.
Re:OpenPGP best practices by wtbob on Wednesday April 06, 2016 @07:02AM (#11437943)
moxie's stuff is great (I use it), but it's not ideal. Among the issues is that it essentially ignores some hard problems like identity (or seems to): AFAICT everything is keyed off of phone numbers; if I control a number then I control its identity, and anyone who talks to me has to use the identity Open Whisper Systems publishes, or not talk to me at all.
Re:OpenPGP best practices by rakoo on Wednesday April 06, 2016 @11:11AM (#11439280)
minilock (https://github.com/kaepora/miniLock/), see the video for a good overview of how easy it is to use.

I'm with moxie and Matthew Green (http://blog.cryptographyengineering.com/2014/08/whats-matter...), I think that we should seriously thank PGP for what it's done, understand what to do and what to not do (I believe Web of Trust is part of these) and take advantage of the fact that PGP has relatively few users to create something better.

Re:OpenPGP best practices by joveian on Wednesday April 06, 2016 @12:33PM (#11439850)
Unfortunately there isn't really one at this point that I know about. There are some in development. The one I am most hopeful about is briar: https://briarproject.org
Re:OpenPGP best practices by bkeroack on Wednesday April 06, 2016 @12:22AM (#11436582)
Amateurs aren't allowed to write any crypto, so unless one of the few accredited elite like djb decide to write an alternative, we're all out of luck.
Re:OpenPGP best practices by ycmbntrthrwaway on Wednesday April 06, 2016 @01:48AM (#11436869)
Look at how OTR was created. It failed the first version hard, but it was fixed in later versions because authors published their protocol and it was reviewed by "elite". Now it is an easy to use and secure protocol, which "elite" builds upon. TextSecure is based on OTR.
Re:OpenPGP best practices by viraptor on Wednesday April 06, 2016 @01:41AM (#11436835)
That's not true. Everyone's allowed to write crypto as long as they understand what they're doing. The difference is that if djb releases new crypto code, I believe it will be correct and he's going to publish a few papers on why it's correct.

If anyone else does it, they better write some really good papers about it and get reviews from the trusted people. (and they usually don't)