Don’t worry, the authorities already have the slightly less convenient way to backdoor things.
Why make a fake release when you can just include it in the real release for the price of just a little coercion?
You could host the release on the police servers and they still couldn’t get a client with a pinned public key to download a malicious version, because releases are signed.
That said, while TAILS takes security seriously, you shouldn’t just expect all package managers to update themselves securely. This is why you want to avoid these new tools that don’t care about security, like flatpak, snap, brew, chocolaty, docker, pip, npm, etc
What a convenient way for police to ship you a backdoored version.
/s ?
Don’t worry, the authorities already have the slightly less convenient way to backdoor things. Why make a fake release when you can just include it in the real release for the price of just a little coercion?
Thats why we use cryptography.
You could host the release on the police servers and they still couldn’t get a client with a pinned public key to download a malicious version, because releases are signed.
That said, while TAILS takes security seriously, you shouldn’t just expect all package managers to update themselves securely. This is why you want to avoid these new tools that don’t care about security, like flatpak, snap, brew, chocolaty, docker, pip, npm, etc