| ▲ | zbentley a day ago | |||||||||||||||||||||||||
> you need a non technical person put the brakes on some technical teams. Can you expand on that? The general wisdom, true most places I and my peers have worked, is that non-technical business stakeholders are often the ones deprioritizing work that would reduce operational (including security) risk. | ||||||||||||||||||||||||||
| ▲ | rustyhancock a day ago | parent [-] | |||||||||||||||||||||||||
Technical teams are great at solving technical problems. And will always see more technical problems to solve. This article is about how you can put jailbreaking this device out of the reach of a skilled reverse engineer, and require a skilled reverse engineer with some fancier technology. Ironically so it could be cracked by the same guy in all likelihood. ....Why? There is no upside. Only costs. This is obvious to anyone who's common sense isn't blinded by a mind geared to solving technical issues. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||