Conversation

Replying to and
Most Linux distributions fully trust the packagers and a central build / signing server, along with not verifying signatures for sources. I think you're unfamiliar with how it works elsewhere if you think trusting 20 vetted people to sign builds of packages is bad.
2
Having a central build / signing server doesn't mean a developer wasn't also fully trusted with what they told the server to build, without anyone reviewing what they asked it to build. It's usually not the case that a central build server is trusted *instead* of developers.
2
Replying to and
I don't know what else to say beyond that I didn't say that. I don't understand why you're mad at me. I've been trying my best to clarify what I said initially and I wasn't trying to turn it into something hostile.
1
Part of my point was that these are imperfect systems without fancy things like reproducible builds + multisig, but yet they're still very useful and a lot better than the alternative of not having package signing. Even just having TOFU via the lock files would be quite useful.
1
I was curious about what exactly the old developer had to do in order to hand off control and was surprised by there not being a mechanism for even doing TOFU pinning. I thought they'd have had to hand over a key, but it's mostly just a username/password protecting each package.
1
Show replies
Replying to and
The original Android signing system is a textbook anti-pattern and an example of your "done is better than perfect" attitude gone awry. Keys couldn't be rotated, developers were locked out of updating their apps, or stolen and irrevocable. Replacing it took nearly a decade.