News for hackers. Stuff that matters.
Re:Looking back at how Signal works by est31 on Friday June 05, 2020 @07:24PM (#23435156)
> roll their own cryptography

Signal did the same thing. They invented their own cryptographic algorithms. https://en.wikipedia.org/wiki/Double_Ratchet_Algorithm

And the social graph IS sent to servers by Signal. It's protected only by hashing (trivial to circumvent) and by the Intel SGX technology (a bit harder to circumvent, but I doubt that the US govt can't do it).

Re:Looking back at how Signal works by the_why_of_y on Saturday June 06, 2020 @06:19AM (#23438126)
Signal's crypto is an incremental improvement of existing algorithms with good reputation, OTR and SCIMP.

Telegram's crypto is reportedly designed from scratch, with questionable choices such as SHA1 and MAC-then-encrypt.

https://www.cryptofails.com/post/70546720222/telegrams-crypt...

https://eprint.iacr.org/2015/1177.pdf

Re:Looking back at how Signal works by est31 on Sunday June 07, 2020 @01:18AM (#23444957)
I didn't want to claim that Telegram's crypto was better or as good as Signal's. But saying that Telegram rolled their own crypto while Signal did not is misleading as both designed their own protocols.

Also, Telegram uses SHA256 now in the places relevant for security, so that point was resolved.

Re:Looking back at how Signal works by fossuser on Friday June 05, 2020 @07:31PM (#23435205)
My (limited) understanding is numbers are queried to see if accounts exist, but those queries are not connected to the users sending them (and they are obscured in transit).

Am I wrong?

Signal’s cryptography has also gotten a ton of attention, I don’t think the same is true for competitors.

Re:Looking back at how Signal works by est31 on Friday June 05, 2020 @07:44PM (#23435274)
Transit encryption is employed by other services as well. Whether there is de-correlation on the cloud backend I don't know. Maybe there is, but you can't really verify that and it's easy to correlate them again, especially if clients use ipv6 or non-CGNAT ipv4.