Earlier quoted context omitted.
It's not TLS.
Ugh. Should we be scared then?
Viber adds end-to-end encryption
91–100 of 114 posts
Re: Viber adds end-to-end encryption
#92Earlier quoted context omitted.
WhatsApp's "E2E" code is from Signal, which is open source. This zealous belief that all secure cryptography must be open source is something I hear a lot from open source advocates, but not so much from cryptography engineers.
You keep saying this, but how do we know they are actually using the code from Signal without access to source and reproducible builds? Last time you told me it was easy and legal to reverse engineer the code. I then asked you what tools you use to do that and you ignored the question.
I think it's great when people further verify WhatsApp's client security, please share your analysis!
Re: Viber adds end-to-end encryption
#93Earlier quoted context omitted.
It's not TLS.
Ugh. Should we be scared then?
When we're talking about End-to-End Encryption, we usually mean:
* Application Layer Security (between users)
* Transport Layer Security (between each user and the server)
And here, Security should mean public key authenticated encryption (e.g. crypto_box() from NaCl)Re: Viber adds end-to-end encryption
#94Re: Viber adds end-to-end encryption
#95Earlier quoted context omitted.
WhatsApp's "E2E" code is from Signal, which is open source. This zealous belief that all secure cryptography must be open source is something I hear a lot from open source advocates, but not so much from cryptography engineers.
The value is not just the public display of the source code for auditing, but the validation that what you are running was indeed compiled from that code.
Re: Viber adds end-to-end encryption
#96This is fantastic news, as others have said, maybe they should really open source the portions of code that have to deal with E2E encryption so it may be audited.
Re: Viber adds end-to-end encryption
#97Earlier quoted context omitted.
You keep saying this, but how do we know they are actually using the code from Signal without access to source and reproducible builds? Last time you told me it was easy and legal to reverse engineer the code. I then asked you what tools you use to do that and you ignored the question.
To reverse engineer code? For big projects, I used IDA, like everyone else does. For smaller projects, I used Hopper, or, for architectures that IDA and Hopper didn't support, I'd postprocess binutils output. For an example of a more sophisticated approach, look at: https://sourcedna.com/ Remember, in this case, it's especially easy to reverse, because you have the source code ; all you're doing is matching the contr…
I imagine I won't ever get to it, but that sounds like an interesting problem to try to work on.
Re: Viber adds end-to-end encryption
#98Earlier quoted context omitted.
To reverse engineer code? For big projects, I used IDA, like everyone else does. For smaller projects, I used Hopper, or, for architectures that IDA and Hopper didn't support, I'd postprocess binutils output. For an example of a more sophisticated approach, look at: https://sourcedna.com/ Remember, in this case, it's especially easy to reverse, because you have the source code ; all you're doing is matching the contr…
Do you know if there exist tools that take a binary and a source code file and attempt to automatically compare the control flow graphs? I imagine I won't ever get to it, but that sounds like an interesting problem to try to work on.
Re: Viber adds end-to-end encryption
#99I always enjoyed using Viber, but I never liked that it featured no encryption. It is an alternative for Skype for me, I could video call from my phone, laptop, tablet, etc and do audio calls. Skype became insecure, it leaks your IP address and it's got terrible synchronization issues, and now chatting is really buggy, messages show up in the wrong place for me, as well as the Linux client for it sucks. Viber has a g…
Re: Viber adds end-to-end encryption
#100So will EFF now endorse Viber as strongly as they endorsed Whatsapp?