Global Encryption Day: Demand End-to-End Encryption in DMs
blog.torproject.org
Global Encryption Day: Demand End-to-End Encryption in DMs
1–10 of 78 posts
Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#2Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#3Kind of meaningless if you can't trust the software running on your device though, since it could be scanning locally or relaying to remote services.
Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#4Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#5Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#6Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#7Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#8What if someone changed the open source before shipping it to the app store?
Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#9Kind of meaningless if you can't trust the software running on your device though, since it could be scanning locally or relaying to remote services.
It's not enough that a FOSS alternative _exists_; it needs to be the case that closed-source encryption is not considered as an actual encryption "end".
Re: Global Encryption Day: Demand End-to-End Encryption in DMs
#10How do you know if the Signal client running on your phone right now doesn't include a backdoor? Sure it's open source. But how do you know how it was compiled? What if someone changed the open source before shipping it to the app store?