Signal can add backdoors to their own app and, if the app get compromised (or the device) the security of the encryption model is not relevant. It’s the reason because I see comparable Signal and Telegram.
Signal is open source, but (info based in this 3 years old thread on f-droid):
Have binary blobs and propietary dependencies.
Don’t let reproducible builds.
It’s hostile to forks (they blocked libreSignal from their servers)
Don’t want independent builds from f-droid (nor any fork in f-droid)
I’ve already addressed this but i guess i’ll expand on it.
Signal would not be able to add backdoors to all its users. Security researchers would see pretty quickly (more below) and that would be pretty big news because Signal is quite popular with people who care about their privacy.
They could in theory backdoor an individual’s Signal app but, again, that’s pretty inefficient. If anyone ever noticed it would be a big black mark against Signal, though they may not have much choice in the matter if it really came to it. However, we know that big governments and other sophisticated attackers usually prefer to just stick spyware on your phone. It’s easier, more comprehensive, and doesn’t require collaboration with Signal.
In contrast, you don’t need to do any of that with Telegram because it’s not E2EE. Your argument is basically “security features can be defeated by a sufficiently advanced attacker so use this other service that doesn’t have them to begin with.” This makes no fucking sense.
I don’t know what you’re talking about with FOSS stuff. Yeah, Telegram is open source. Signal is too. Some Signal forks (particularly the ones with “Signal” in their names) have been killed but others still exist, ex molly.im.
Signal client does have reproducible builds and has since 2016, as far as i know. This is another point against Signal being backdoored.
Finally, Telegram itself. Telegram could simply enable E2EE for all chats. They choose not to and that is concerning if you care about your privacy or security.
Yeah Signal could be better but that isn’t a case to use Telegram over Signal when Telegram is worse in almost every respect.
I agree that signal has a more robust security model. What I mean is that itbhasbalso habe risks, and a lot of people are ignoring it.
The backdoor could be a sleeping function activated from outside to targets of interest or ‘special’ updates from the google store (i.e.: with the help of google install a different version of the app to the target). But I’m not a security nor android expert, and it’s all theoretical if this attack vector is possible, but I think that is unlikely.
Also, if the NATO country where I live wants to spy my mobile, it would use Pegasus 🤷🏽♀️
Off topic: The Signal reproducible builds don’t work since, at least, may.
Signal can add backdoors to their own app and, if the app get compromised (or the device) the security of the encryption model is not relevant. It’s the reason because I see comparable Signal and Telegram.
Signal is open source, but (info based in this 3 years old thread on f-droid):
Which no seems FOSS friendly.
I’ve already addressed this but i guess i’ll expand on it.
Signal would not be able to add backdoors to all its users. Security researchers would see pretty quickly (more below) and that would be pretty big news because Signal is quite popular with people who care about their privacy.
They could in theory backdoor an individual’s Signal app but, again, that’s pretty inefficient. If anyone ever noticed it would be a big black mark against Signal, though they may not have much choice in the matter if it really came to it. However, we know that big governments and other sophisticated attackers usually prefer to just stick spyware on your phone. It’s easier, more comprehensive, and doesn’t require collaboration with Signal.
In contrast, you don’t need to do any of that with Telegram because it’s not E2EE. Your argument is basically “security features can be defeated by a sufficiently advanced attacker so use this other service that doesn’t have them to begin with.” This makes no fucking sense.
I don’t know what you’re talking about with FOSS stuff. Yeah, Telegram is open source. Signal is too. Some Signal forks (particularly the ones with “Signal” in their names) have been killed but others still exist, ex molly.im.
Signal client does have reproducible builds and has since 2016, as far as i know. This is another point against Signal being backdoored.
Beyond that, Signal has gone through a number of formal security audits. As far as i know, Telegram has not.
Finally, Telegram itself. Telegram could simply enable E2EE for all chats. They choose not to and that is concerning if you care about your privacy or security.
Yeah Signal could be better but that isn’t a case to use Telegram over Signal when Telegram is worse in almost every respect.
I agree that signal has a more robust security model. What I mean is that itbhasbalso habe risks, and a lot of people are ignoring it.
The backdoor could be a sleeping function activated from outside to targets of interest or ‘special’ updates from the google store (i.e.: with the help of google install a different version of the app to the target). But I’m not a security nor android expert, and it’s all theoretical if this attack vector is possible, but I think that is unlikely.
Also, if the NATO country where I live wants to spy my mobile, it would use Pegasus 🤷🏽♀️
Off topic: The Signal reproducible builds don’t work since, at least, may.