Re:WhatsApp's Signal Protocol integration is now complete
by pfg on Tuesday April 05, 2016 @03:15PM
(#11433458)
if the client encryption is reliable
It's not[1].
Re:WhatsApp's Signal Protocol integration is now complete
by janinge on Tuesday April 05, 2016 @04:36PM
(#11434147)
It is not, or was not? Did this issue get rectified by Telegram?
Re:WhatsApp's Signal Protocol integration is now complete
by CiPHPerCoder on Tuesday April 05, 2016 @04:38PM
(#11434166)
No, they still use MTProto and not an AEAD construction.
Re:WhatsApp's Signal Protocol integration is now complete
by janinge on Wednesday April 06, 2016 @11:20AM
(#11439338)
I was referring to the padding attack. Did they patch this?
And are there any property of MTProto that makes it infeasible to replace AES IGE in a later revision of the protocol?
Re:WhatsApp's Signal Protocol integration is now complete
by CiPHPerCoder on Thursday April 07, 2016 @07:40AM
(#11446443)
The problem isn't IGE. It's that they're using SHA1 (not HMAC-SHA1) in a "MAC and Encrypt" construction.
Re:WhatsApp's Signal Protocol integration is now complete
by nickik on Tuesday April 05, 2016 @03:36PM
(#11433635)
Its still their own crypto. Even if you have the code, their could be a mathematical weakness that is unknwon to anybody outside the company. The protocol has not been studied a lot.
Re:WhatsApp's Signal Protocol integration is now complete
by nxzero on Thursday April 07, 2016 @05:00PM
(#11450677)
Has anyone offer to fund an audit of the code/crypto/workflow? If not, it'd be nice Moxie would spec out a public request for funds via some sort of crowdfunding and means to post public offers to audit the code based on the funds raised.
Re:WhatsApp's Signal Protocol integration is now complete
by nickik on Friday April 08, 2016 @06:36AM
(#11453736)
Moxie has asked them multible times but they dont seem to care.
Re:WhatsApp's Signal Protocol integration is now complete
by nxzero on Friday April 08, 2016 @10:50AM
(#11454985)
Oh, interesting, not a huge suprise, though guess I wasn't clear, I was talking about auditing the open source stuff, not Facebook.
Basically, crowdfunded audits of open source crypto tech have been done before; I'd be up for helping with this if it made sense, since currently my sec dev skill are not that useful:
https://www.indiegogo.com/projects/the-truecrypt-audit#/
--
Might be worth funding a exploitable bug bounty too.
Whatever the server, if the client encryption is reliable, data can't be read on the server side.