News for hackers. Stuff that matters.
Re:MEGAChat now includes end-to-end encryption by jpgvm on Saturday January 23, 2016 @06:08AM (#10957992)
It sounds reasonable? If anything this highlights the problem with all the new encrypted communications options, even highly technical people can't really know how good it is from a cursory look. Just because it says end to end encryption and uses some nice ciphers it doesn't mean the implementation is not critically flawed.

I use Signal right now (from Moxie Marlinspike/Whisper Systems) and would only really consider alternatives if they were endorsed by other cryptographers I know because I really just don't have a strong enough grasp of how all the machinery interacts.

Re:MEGAChat now includes end-to-end encryption by pointernil on Saturday January 23, 2016 @06:59AM (#10958102)
Is there any information on the guaranties Moxie Marlinspike/Whisper Systems provide on the Apps downloaded from the App-Store? I get that their source is open and reviewed and trusted but what is this worth when there is no way to tell if users are actually using their version/builds when installed from App-Stores. Same holds true for the necessary servers they maintain.

Don't get this wrong please: this is still probably THE best solution right now, which simply as well has its security limitations, right?

Is there any work ongoing on a kind of "verification process" for Apps like these? How can an end-user tell if the binaries running on their device are untempered with?

/sorry for hijacking ;)

Re:MEGAChat now includes end-to-end encryption by hannob on Saturday January 23, 2016 @07:25AM (#10958149)
The solution is called reproducible builds. I'm aware f-droid is working on these, but most of the work is currently happening more in the Linux distribution space (Debian is leading that cause). I hope in the future we will be able to say "if it doesn't have a reproducible build process it's not to be considered trustworthy".

(Also: I think this question is mostly independent from the disagreements between moxie and f-droid - they were regarding other issues.)

Re:MEGAChat now includes end-to-end encryption by buu700 on Saturday January 23, 2016 @08:45AM (#10958363)
Reproducible builds are on our very-near-future roadmap at Cyph, which will be important to mitigate a hypothetical scenario in which we somehow lose our minds and deploy code that differs from the GitHub repo.

We control the whole packaging/signing framework (WebSign), so there isn't any need for us to wait on a third party to roll this out.

Re:MEGAChat now includes end-to-end encryption by alkonaut on Saturday January 23, 2016 @08:25AM (#10958301)
Aren't builds typically reproducible? What makes builds non-reproducible? I know the Debian folks are very enthusiastic about reproducible builds, and for a huge system I can see that things can vary -- but what tends to be varying in the case of individual components? If I build a library from the same revision of a source tree I expect the exact bits to come out, if the same compiler version was used? When does it not?

Is it a problem with C/C++ in particular, where toolchains are complex? Or would non-reproducible also be a problem e.g for a Java library?

Googling reproducible builds mainly gets you Debian info, not a general description of the issue

Re:MEGAChat now includes end-to-end encryption by wila on Saturday January 23, 2016 @09:09AM (#10958431)
No builds are not easy to reproduce bit by bit as there are much more factors as the actual source.

For example:

  - compiler version used
  - date / timestamps at the time of compile
  - build id's
A good article on this can be found here: https://blogs.kde.org/2013/06/19/really-source-code-software
Re:MEGAChat now includes end-to-end encryption by sandworm101 on Saturday January 23, 2016 @08:30AM (#10958318)
A build is not reproducible where it incorporates both open and closed code. A company may "open source" some important stuff (encryption algorithms) but keep enough code closed that the final build cannot be duplicated from the "open" code. It is therefore difficult to judge whether the open code has actually been adopted properly, or whether any closed code hasn't created new bugs.
Re:MEGAChat now includes end-to-end encryption by tomjen3 on Saturday January 23, 2016 @08:33AM (#10958331)
You can always compile the programs yourself - you will have to pay for a dev account for iPhone (I think) but Android is free and you can sideload the new app you trust.
Re:MEGAChat now includes end-to-end encryption by ikeboy on Saturday January 23, 2016 @09:16AM (#10958445)
If you have the source code, Apple now allows you to install it on your own device without paying for an account.
Re:MEGAChat now includes end-to-end encryption by treenyc on Saturday January 23, 2016 @06:44AM (#10958073)
It is great that Whisper Systems/Signal implement cryptography properly.

However, the NEWER versions of Signal requires access to your contact to work.

For many users that is a show stopper.

Implement a way for user to search by User ID and allow user to find each other by ID in addition to phone number.

Re:MEGAChat now includes end-to-end encryption by brbsix on Saturday January 23, 2016 @10:12AM (#10958589)
Recent updates also show disconcerting "Joe is on Signal!" messages for everyone in your contacts (who is registered with Signal) regardless of whether or not you've had any contact with them. They've stated that this is not a security issue (I don't recall the specifics) but it was pretty disturbing nonetheless. I'll definitely be paying closer attention and consider switching to an alternative if this trend continues.
Re:MEGAChat now includes end-to-end encryption by asddubs on Saturday January 23, 2016 @02:03PM (#10959530)
Why specifically are you worried about that?
Re:MEGAChat now includes end-to-end encryption by brbsix on Sunday January 24, 2016 @01:52AM (#10961755)
I've recommended Signal (then TextSecure) to a number of non-technically savvy friends as a trustworthy app that takes security seriously. Moxie is somewhat unique in this respect, among the sea of proprietary apps put out by larger shops. Upon seeing these "X is on Signal" messages, I had a number of people contacting me with concerns. At least the outward appearance is that Signal is somehow leaking contact data to their servers. Presumably it is also alerting people to the fact that "Joe" is a Signal user, despite no communication with that user having taken place.

I realize that phone numbers are probably hashed before being sent, with only local contact data being displayed, but it has people concerned nonetheless. It starts to err more towards convenience, ease of use, and network building above security.

Re:MEGAChat now includes end-to-end encryption by cyphar on Sunday January 24, 2016 @02:39AM (#10961846)
I think we should push for Axolotl (the cryptosystem used by Signal, which is an improvement on OTR) support in Ricochet and get a Ricochet phone app.

Ricochet uses Tor hidden services to anonymise your social graph, which is something you don't do with Signal (not to mention that Signal does identity key lookups with phone numbers). I'm not sure there's a low-latency way to do VOIP anonymously. The best method I know of is to literally record and send audio files, which have a few seconds of latency.

Re:MEGAChat now includes end-to-end encryption by asddubs on Thursday January 28, 2016 @05:54PM (#10992125)
you can easily enumerate this data anyway, though. Just go through your contact list and try to add people. You could come up with an elaborate system where the other person has to confirm you, but everyone knows that's rubbish and users hate it. Sorry for the late response, I forgot I made this comment.
Re:MEGAChat now includes end-to-end encryption by brbsix on Friday January 29, 2016 @09:26AM (#10995309)
Yes I'm well aware at the ease in which someone could build a client that would provide such a feature had it not been included. Moxie takes great care not to provide mere illusions of security (or in this case obscurity) such as self-destructing messages or other features of that ilk. I appreciate it, and it's a big part of why I use and recommend projects affiliated with Open Whisper. Still don't believe it was the right decision to blast users with a notification from every Signal user in your contacts. Let Telegram or Whatsapp or some other crap play that game.
Re:MEGAChat now includes end-to-end encryption by Freak_NL on Saturday January 23, 2016 @07:44AM (#10958197)
The requirement of a phone number is strange and disconcerting from a privacy standpoint. It is a red flag for me.

A well-designed encrypted chat-protocol should work on any modern networked computing device, not just smartphones or computing devices linked to a smartphone.

Re:MEGAChat now includes end-to-end encryption by Tepix on Saturday January 23, 2016 @07:37AM (#10958170)
Not on iOS. It's not Signal's fault that Android permissions are a mess. Google has no interest in providing good privacy to their customers. They only want to appear to provide privacy. In reality, they want to know everything there is to know about everything and everyone. To improve their service, of course...
Re:MEGAChat now includes end-to-end encryption by lelf on Saturday January 23, 2016 @08:21AM (#10958289)
> Not on iOS

Tried just now. It does require it and doesn't work without it.

             Sorry!

  Signal requires access to your
  contacts. We do not store your
  contacts on our servers.

         [Give access]
Re:MEGAChat now includes end-to-end encryption by jimktrains2 on Saturday January 23, 2016 @06:46AM (#10958081)
While you can't know without looking at the code, my first-pass test is asking how keys are handled and if the code handling those keys is coming from an untrusted source (in this case the server as JS)(for the sake of this discussion I will admit I implicitly trust Debian and the gpg folks).

If there isn't a good answer to key management, or my key is handled by JS, then it's a no-go for me.

If there is a half-way decent answer to key management, I ask what the threat vectors the system was designed for are. If a broad political statement is made, then I walk away.

While it doesn't actually vet the technical merit of the code, I feel it catches a lot of funniness.

Re:MEGAChat now includes end-to-end encryption by pdkl95 on Saturday January 23, 2016 @08:26AM (#10958307)
> a good answer to key management

The problem with key management is that everyone tries to solve the management problem with a single solution. A single method will always have to make choices about the threat model, which can only truly be known by the user. A single user can even have more than one threat model, depending on what they are doing.

What we need instead is some sort of configurable layer that allows the user to specify how keys should be managed by selecting what they want to trust.

They could use a default delegation to a public trust root (the PKI model, no configuration needed) for most things. Receiving a call from the bank could instead be authenticated with the key they got when they physically walked into the local branch. Chat with their immediate friends who can exchange keys on their phone when they meet up in person is easy, and a web of trust can extend that to a friend-of-a-friend. People understand the concept of vouching for someone, and over time more than one method can be used to cross-check.

Key management shouldn't be "PKI vs web-of-trust vs out-of-band-keybase-style vs manual-key-exchange vs ..."; it should be "all of the above, with the chain-of-trust exposed". Anything else is making assumptions about what the user's current needs.

Re:MEGAChat now includes end-to-end encryption by biokoda on Saturday January 23, 2016 @07:21AM (#10958141)
Probably the best key handling method is employed by Biocoded app. It uses the same encryption protocol as signal (Axolotl ratchet) and it only stores half of the decryption key locally. The other half is on the server.