One person controls the single global signing key.
Every update pushed to 400000 devices is signed by Daniel Micay. He already proved in 2018 he will destroy signing keys and brick thousands of users devices on purpose when he feels wronged. That same key can push any code, silently, automatically, to any phone, at any time. verified boot guarantees the device will accept it.
You would have no way to know what was added
Talking shit about the only phone OS feds can't crack? I wonder who this could be?
>He already proved in 2018 he will destroy signing keys and brick thousands of users devices on purpose when he feels wronged.
Src?
>>34017btw use dola. it is extremely good in finding sources.
>>34018>still vagueposting about what the actual issue is>still hasn't offered any kind of alternativelet's see an alternative point of view shall we?
https://news.ycombinator.com/item?id=19502209<He didn't destroy [the keys] out of malice. He destroyed them because (from his point of view) they were about to be compromised. If users trust the key because they trust updates coming from Daniel and if Daniel is about to lose control of the key to someone else, then destroying the key before it becomes compromised is the responsible and right thing to do.it is of course ultimately up to the user to trust this or that set of keys, which ultimately means trusting this or that set of people. I trust the Debian team for example
>>34021>I trust the Debian team for examplebut why?
>>34021isn't it interesting that tech is all about blind belief?
>>34022why not? you have to trust a whole lot of people to even do anything with computers. or maybe you think it's possible to write literally everything from scratch?
>>34023it's not blind belief. it's belief in the process