News for hackers. Stuff that matters.
Re:The New TextSecure: Privacy Beyond SMS by xnyhps on Monday February 24, 2014 @06:18PM (#7294074)
Not if you want it to be “SMS based”, by which I mean: use phone numbers as identifiers. A server can’t easily prove to another that it serves the user with a specific phone number. There’s no cryptographic proof possible, there’s no hostname part like in email. You can verify by sending a text message, but that gets expensive if you need to do it often.

This is trying to combine 3 points on Zooko's Triangle [1]: You want human-meaningful names (which phone numbers are, because they map to existing things), so you have to make a trade-off between decentralization and security. WhisperSystems opted for security for some reduced decentralization. For something that’s aiming to replace text messaging, I can’t really blame them for that choice.

[1] = https://en.wikipedia.org/wiki/Zooko%27s_triangle

Re:The New TextSecure: Privacy Beyond SMS by nly on Monday February 24, 2014 @10:27PM (#7295220)
It's a shame there isn't a standard means to associate keypairs with existing phone numbers in a way that doesn't involve establishing new trust. A <your_phone_number_here>.yourcarrier.com DNSSEC secured subdomain provided by your existing carrier that can be coupled with BrowserID perhaps. All you need is a cryptographic tie-in, right?
Re:The New TextSecure: Privacy Beyond SMS by xnyhps on Tuesday February 25, 2014 @03:57AM (#7296427)
Getting carriers on board to make a texting replacement? Well, you can dream. ;)