3 ms·
Putting up walls in the form of code signing, TPMs, rate limiters, password hash functions designed to slow down iterative guessing, aren't vulnerabilities in w
by cmurf 11y ago
Putting up walls in the form of code signing, TPMs, rate limiters, password hash functions designed to slow down iterative guessing, aren't vulnerabilities in waiting. The government changing the rules by claiming they're entitled to coerce a company to code changes causing these walls to be removed, does not make them pre-existing vulnerabilities.
If the Court rules Apple can be compelled to do the work to create significantly weaker software, and then authenticate it with their signing key, it's pretty reasonable Apple will look for ways to further hard code these walls into the hardware. It's not just in their marketing interest, although that's a factor, it's to get themselves completely out of the business of even having these arguments almost every time they come up, when governments around the world say "gimme!" with a court order. If they refine this so they really can't comply, even by hacking their own products, then the only thing governments have left is to destroy the company. If they go down that road, we have much bigger problems.
- marcoperaza 11y ago>Putting up walls in the form of code signing, TPMs, rate limiters, password hash functions designed to slow down iterative guessing, aren't vulnerabilities in waiting. It's all about threat models. If you're trying to protect your data from the government, anything that allows anyone but you to access the data is a vulnerability. Very few systems try to contend with such a threat model because it's really hard to defend against, and most people don't care about keeping their data from the government. Seamless updates are way more important to them.