http://thoughtcrime.org/blog/telegram-crypto-challenge/
I don't think you should use Telegram.
http://thoughtcrime.org/blog/telegram-crypto-challenge/
I don't think you should use Telegram.
WhatsApp (most popular?) doesn't. ChatSecure (most secure?) doesn't.
I'd say 'Use Telegram' with the caveat that you shouldn't trust it blindly? Use it as a better and cross-platform SMS/text experience, which might or might not be more secure.
Edited to add: The same could well be true for someone using plaintext.
Compared to the alternatives of Skype, WhatsApp, SMS, Hangouts, iMessage, etc it's a good chat service, with a relatively lightweight native client on multiple platforms, actual working sync, and good recovery when used on poor Internet connection.
It is unethical to market snake oil.
Are they super-duper safe? No. Will driving our cars grant you immortality? also, No.
But no car can promise this, and driving any car inherently runs the risk of dying - No car is provably 100% safe! If you're really worried about this, just don't drive!
Most car drivers won't care anyway, very few people crash their cars on a day-to-day basis, so it's not really relevant.
</good-natured-sarcasm> exaggerated/straw-man comparisons, or appeal-to-low-standards doesn't really satisfy these kind of concerns... <good-natured-sarcasm>
If it's not actually secure then they shouldn't advertise it as secure.
An app that advertises itself as secure but isn't is naturally going to attract more hate than an app which doesn't advertise security in the first place.
Nobody forced them to advertise security. If they just wanted to be a a good chat service with the advantages you listed, they could just do that. But if you advertise security, you had better deliver!
The hate stems from two main sources:
1. They're claiming to be secure in a very flamboyant (even arrogant) manner by challenging the world's cryptographers to break their protocol, but the contest is structured to be unwinnable regardless of how shitty their crypto actually is.
2. Telegram spends less time improving their crypto (which is full of WTFs) and instead markets themselves to people who aren't technical enough to figure out how shitty it really is.
Seriously, avoid Telegram. If you want Signal to work on more platforms, send a check to Open Whisper Systems and help them build up their team to cover more area.
The 4 or 5 people in the nsa that actually do any work don't stand a chance against several hundred million baby breeders with ak47s.
I think I agree that using encryption on Telegram singles you out though!
Claiming to be secure, and then taking what's mine away from my control is unacceptable to me.
I'm going to write up the protocol and publish a reference server I wrote in Go in a few days. I'll post it here and send it to Open Whisper Systems as well, they may want to integrate it.
Obviously, if you're extremely liberal with the upvote button, this may not be useful as a bookmark....
Useful?
I would call it Show.hn :-)
Yes, Signal The App reads your contacts to construct the blinded signature query. Does it then do something nefarious with them? No: https://github.com/WhisperSystems
What alternative solution to the PKI key introduction problem would you rather see? You could go the iMessage central key broker route, but that means trusting that Apple won't introduce the wrong key to you (or be compelled to do so). [2] Or, you could let users exchange keys in person a la key signing parties. That's a reasonable feature request at this point, but advanced usage and not something that gets you traction with normal people. TextSecure/Signal wouldn't have gotten to where it is today with that much friction around key introduction.
For RedPhone, our user base is still manageable enough (for now) to use the bloom filter technique. For TextSecure, however, we’ve grown beyond the size where that remains practical, so the only thing we can do is write the server such that it doesn’t store the transmitted contact information, inform the user, and give them the choice of opting out.
I would expect that Signal does share contact information with the server.
But now you've got me curious. I'll dig back into the code and find out for sure.
[1] http://support.whispersystems.org/hc/en-us/articles/21274348...
[2] http://support.whispersystems.org/hc/en-us/articles/21247614...
It'd be nice to figure it out, but I guess it isn't that important, Signal still leaks lots of metadata, so anyone that would be burned by sharing their contacts isn't gaining much by using it (or any other mobile comm...).
There's even an fdroid repository[1] you can add to track libreSignal apks.
----
[0] https://github.com/JavaJens/TextSecure [1] https://fdroid.eutopia.cz/
This tendency to talk about the name/brand of the client instead of the protocol is a current problem with IM. The ISIS people should really be writing articles about OTR and TOR to address their particular application.
I have a friend that thinks I use the Pidgin chat system because that is what she uses when she chats with me on XMPP. Since Pidgin does not run on her phone she thinks she can only chat with me when she is at her computer. So far all attempts to explain the idea of an interoperable protocol have failed.
I remember years back when I attempted the same problem with a thing called Wire, for activists, that I posted on here and combined Facebook/Twitter type stuff with "secure" messaging, which was a web based UI that implemented AES256 based browser encryption based on the Stanford JS library. I got thoroughly roasted by people that knew what they were doing, so I shut the project down realising that what I was doing was dangerous due to lack of qualification. It's interesting seeing all the projects that have sprouted up since, and clearly I was on the money with the initial idea.
FB Messenger works fine but of course is not private w.r.t. FB
Seems a good enough reason to use something different
https://threema.ch/en/faq/why_secure https://threema.ch/validation/