News for hackers. Stuff that matters.
Re:WhisperPush – End of Life by Arnt on Wednesday January 20, 2016 @05:58AM (#10937242)
AIUI the leaked data is recipient and approximate length of the body. Is there more?
Re:WhisperPush – End of Life by makomk on Wednesday January 20, 2016 @08:21AM (#10937830)
Sender and recipient's mobile phone number, length of the body, time and date of communication - for every conversation using Signal. Which is pretty much all the metadata you need.
Re:WhisperPush – End of Life by simoncion on Wednesday January 20, 2016 @11:22PM (#10943339)
Can you point to the parts in the spec for the TextSecure protocol where this information is leaked? I was under the impression that a passive adversary could get

* Time of Tx to Signal server

* Rough message length

* Time of Tx of message from Signal server to recipient (assuming that they were listening on that path, too)

Is my understanding incorrect? Can a passive adversary inspect the data from a TextSecure/Signal client and determine more (or just the above) information from the data sent from the TS client to the TS server?

Re:WhisperPush – End of Life by Arnt on Thursday January 21, 2016 @03:53AM (#10944113)
No single passive adversary gets all three. The information moves from the phones to *.whispersystems.org, then in a big fat stream to Google, then from Google to the recipient phones.
Re:WhisperPush – End of Life by simoncion on Thursday January 21, 2016 @05:20PM (#10948943)
> No single passive adversary gets all three.

If the passive adversary has enough listening posts, it's totally possible for them to be reasonably certain that they probably got all three, unless some sufficiently clever stuff is happening either at the WS servers, or in Google's servers.

Re:WhisperPush – End of Life by Arnt on Wednesday January 20, 2016 @08:31AM (#10937888)
I looked at the source code on github, and it seems as if the sender's phone number is part of the encrypted blob. What am I missing?
Re:WhisperPush – End of Life by exo762 on Wednesday January 20, 2016 @11:55AM (#10939426)
This is good since it protects you from snooping from ISPs/carriers.

You are still exposed to Google/Apple, since it can easily combine your contact information with traffic information and with great deal of probability detect who was the recipient.

I still would take it over encrypted SMS, where this data is open to carriers and carriers are basically perma-owned by everyone.

Re:WhisperPush – End of Life by Arnt on Wednesday January 20, 2016 @01:52PM (#10940376)
The recipient is clear. Google can known with perfect certainty whether you receive messages using Signal. The sender of a message is not; only Moxie has any real ability to see who communicates with who. Google and those pwn Google can only see who receives messages, how many, how long, when.
Re:WhisperPush – End of Life by exo762 on Wednesday January 20, 2016 @02:09PM (#10940500)
This are my assumptions:

1) Google can see Alice send message via Signal

2) Google can see Bob receive message via Signal

3) Google knows that Alice is in Bob's contacts, and Bob is in Alice's contacts

Those three pieces of data should be enough. I don't see why Google can't do time correlation of those messages. Both Alice's and Bob's contact lists are very finite. It might be not obvious for single message, but for series of messages (and people chat this way) it should be very obvious who is talking to whom.

Re:WhisperPush – End of Life by Arnt on Wednesday January 20, 2016 @03:25PM (#10941060)
Number 1 is wrong, if I read the code correctly. The messages go from the sending phone to a whispersystems server via a protocol on top of HTTP, not via Google.
Re:WhisperPush – End of Life by exo762 on Wednesday January 20, 2016 @06:01PM (#10942077)
And this is awesome. Amen.