News for hackers. Stuff that matters.
Re:Egypt has blocked encrypted messaging app Signal by mi100hael on Tuesday December 20, 2016 @10:29AM (#13220617)
Signal's use of GCM may not be particularly intrusive, but it still requires a phone with Google's services running. LibreSignal works on a Google-free phone, and Moxie told them to fuck off.

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

Re:Egypt has blocked encrypted messaging app Signal by Techonomicon on Tuesday December 20, 2016 @12:11PM (#13221723)
Telling them to fuck off seems far far farrrrr from the truth. Moxie's points seem pretty fair all around.

I urge people to read through these comments in the github issue yourselves versus believe the commenter here at face value.

Re:Egypt has blocked encrypted messaging app Signal by mi100hael on Tuesday December 20, 2016 @12:39PM (#13222000)
From Moxie:

> If you think running servers is difficult and expensive (you're right), ask yourself why you feel entitled for us to run them for your product.

Moxie knowingly and willingly runs a free service. Why should he feel entitled to tell people how they interact with his service? What's the point of publishing your source code under the GPL if no one can do anything with it? Keep in mind the phone server still isn't open source either, so the client source on its own is about as useful as a literal brick for phone calls.

Re:Egypt has blocked encrypted messaging app Signal by sliken on Tuesday December 20, 2016 @01:08PM (#13222305)
For a bunch of reasons:

1) he doesn't want the signal community to fracture with incompatibilities (like say XMPP)

2) he doesn't want the security of signal users compromised with less secure clients. Thus he's against SMS since it leaks metadata like crazy to 100s or 1000s of entities.

3) he doesn't particularly trust f-droid to distribute clients since they use a central key (an attractive target) instead of the developers key.

4) he wants to be able to quickly iterate improving the clients and server in sync, on his own schedule.

So generally he wants to target a large number of users with a very secure client and doesn't want to sponsor anyone that takes his source with free server infrastructure.

So he believes in audits, security, and opensource. He even will allow a GCM replacement, as long as it only runs when GCM is not available. He expects the battery life and user experience to be terrible. The main problem seems to be that google negotiates with cellular providers to not time out connections to GCM, but they silently do that (without an RST) to other connections. Thus any GCM replacement will have to spend much more power/battery maintaining a connection. Moxie specifically mentioned that even 50 seconds was too long and that some providers time out connections even quicker than that.