Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10363
| From | Dominik George <natureshadow@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: the new PyPI, coming next month |
| Date | 2018-04-01 08:30 +0200 |
| Message-ID | <vzEF3-7zt-3@gated-at.bofh.it> (permalink) |
| References | <vzB4t-5b9-7@gated-at.bofh.it> <vzBQS-5JA-11@gated-at.bofh.it> <vzC0y-5ML-1@gated-at.bofh.it> |
| Organization | Debian |
[Multipart message — attachments visible in raw view] - view raw
Hi, > To be clear, PGP signatures can still be uploaded and they are still > available for download, they just don’t appear in the UI anymore. So, what does the pypi.debian.net redirector use for uscan? I imagine it used to scrape the website. Can it be changed to use the JSON API? > Longer term I’d *like* to get rid of PGP signatures, because I think > their value here is actually pretty low. I partially share this opinion, but that's a question to be discusses with the Debian policy people in general. While checking a GPG signature on the source tarball in general is a good idea, I am afraid some developers just drop any key they find on first glance into the package and are done with it, which actually provides nothing but a false sense of safety. > In that case they’d be replaced with TUF, but that’s a longer term > project. That one?: https://github.com/theupdateframework/tuf Well, I can only say *please* do not remove the possibility to upload signed source tarballs, but leave that to the developers! -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Phone: +49 228 92934581 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. · Debian Developer LPIC-3 Linux Enterprise Professional (Security)
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
the new PyPI, coming next month Sumana Harihareswara <sh@changeset.nyc> - 2018-04-01 04:40 +0200
Re: the new PyPI, coming next month Scott Kitterman <debian@kitterman.com> - 2018-04-01 05:30 +0200
Re: the new PyPI, coming next month Donald Stufft <donald@stufft.io> - 2018-04-01 05:40 +0200
Re: the new PyPI, coming next month Dominik George <natureshadow@debian.org> - 2018-04-01 08:30 +0200
Re: the new PyPI, coming next month Donald Stufft <donald@stufft.io> - 2018-04-01 15:40 +0200
Re: the new PyPI, coming next month Sumana Harihareswara <sh@changeset.nyc> - 2018-04-01 05:50 +0200
Re: the new PyPI, coming next month Sumana Harihareswara <sh@changeset.nyc> - 2018-04-01 13:20 +0200
Re: the new PyPI, coming next month Sumana Harihareswara <sh@changeset.nyc> - 2018-04-03 15:40 +0200
csiph-web