2 ms·
I think there is a value in upgrading the cheeseshop to use "verified maintainers" - it should be simple to do a first pass of "the person who signed the hash o
by lifeisstillgood 9y ago
I think there is a value in upgrading the cheeseshop to use "verified maintainers" - it should be simple to do a first pass of "the person who signed the hash of this module has also verified they own the domain requests.kreitz.org by publishing that public key at that domains root"
Even more useful might be domain/keys/kreitz/publickeylisting
The key signing party is much harder to arrange but is easier to be confident about
Personally I am surprised the Post Office does not do key signing
Edit: I thought pip did do cryptographic checks?!
- ubernostrum 9y agopip allows you to specify, along with package name and version, the expected hash of the downloaded package. If you do that, then pip will download the package, calculate the hash, and check against what you specified. In case of mismatch, pip will refuse to install the package. PyPI also supports adding GPG signatures alongside packages, but with no trust/verification process to assert "this key really is the key of the person who should be releasing this package", the signature is literally worthless; anyone who could put up a fake package could also generate a signature for it, and you'd have no way of knowing that the key which signed that package shouldn't be trusted for that package. It is a very very hard problem, and people need to appreciate that.
- falsedan 9y ago> I think there is a value in upgrading the cheeseshop to use "verified maintainers" - it should be simple to do a first pass of "the person who signed the hash of this module has also verified they own the domain requests.kreitz.org by publishing that public key at that domains root" That sounds useless. An attacker could verify that they own evilattacker.com & publish their malicious packages there. I don't think a web of trust is the answer here, because it doesn't really matter if the attack is anonymous or not, and if only trusted people can publish packages, trust will be given more readily to encourage new programmers to contribute. I think a reputation/review system is better, like docker search's star count, or metacpan's ++ rating.