PyPI's redesigned project pages with clearer security signals are now live

Not very keen that the whole story of trust is basically centralisation - requiring "big cloud" and essentially promoting lock-in.

Did I get that right? Seems a bit anti-pythonic.

Some examples:

dlt (no provenance): https://pypi.org/project/dlt/#files

datasette (yes provenance): https://pypi.org/project/datasette/#files

This is great! I want sigstore-based or at least sigstore-style "keyless" short lived signatures to become more and more popular, so that support gets better everywhere. In particular, if having secure OIDC handling in a CI/CD pipeline becomes something that keeps people on GHA or GitLab then I'd hope third-party hosted CI/CD services begin to take that gap seriously and work on meeting those requirements.

I'm bought in on keyless signing, and I want there to be many more providers, so I like to see more adoption which builds more momentum.

Very cool to see PyPI put more emphasis towards exposing provenance info. It would be even cooler if trusted publishing would finally support reusable workflows (https://github.com/pypi/warehouse/issues/11096).

This is about detecting formerly benign projects that have had their pypi entries hacked, but not their private keys. It does not detect malicious projects.

Am I correct in my understanding that the only trusted publishers are for-profit US companies? And these all use proprietary implementations which cannot easily be replicated elsewhere?

Like, if I want to host on Codeberg, or Sourcehut, what is the process needed for those platforms to become a trusted publisher?

As it happens, I build my releases on my own hardware using a pypa/manylinux release. Can I provide attestation, or am I required to use a third-party service to get that "x Without provenance" removed from my entry?

Not directly the subject but they switched from Material for MkDocs to Zensical.

It’s quite sad to see that one of the main (or the biggest?) documentation system for the Python completely alienated its user base and led to this fork.

Great news! Would love to see provenance on Homebrew (brew) as well.

let me tell you something incredibly important about the attestations / trusted publisher thing:

if you have any of your files published by a trusted publisher with attestations, then you must have all of your files published that way (in that package).

otherwise pypi determines your project may have been compromised and puts some big red warnings up like [1]. it does not try to look at "this particular source file was never part of trusted publishing" or anything like that. and, CRITICALLY, it does not send you an email or anything like that about the non-acceptable file that you just uploaded, which it REALLY should. I mean the model is, they think these uploads are malicious by an attacker. Emailing the project maintainer(s) would be pretty important! (When pypi wanted to get rid of GPG signatures, they started sending me an email for every single signature that got uploaded. so i know you guys know how to send emails).

it's also AFAICT a permanent switch. once you put a single trusted/attested file up there, your account must now do all files in this way forever (or risk big red warnings. which maybe you're OK with that).

It would all be easier to take if trusted publishers weren't limited to solely large for-profit corporations (I'm too lazy to research if they're trying to fix this).

[1] https://fosstodon.org/@zzzeek/117554513935692558

[flagged]

[flagged]

[flagged]

> https://blog.pypi.org/posts/2024-11-14-pypi-now-supports-dig...

Thought we already learned years ago an IP address is not a person?

That is to say; what the screen on my end communicates is not guaranteed to be representative of ground truth.

The IT world was recently making fun of Sam Altman's eye scanner because remote attestation can be faked.

All the layers of abstraction wrapped around the code is security through obscurity.

The code itself must still be verified as safe.

The cloud era has resulted in a lot of people operating at layers of abstraction so far removed from physics this shit has more in common with baseless dogmas, gospels, and spiritualities at this point.

We anthropomorphized the cloud inserting ourselves into it. It's just a bunch of networked computers.

All this stuff is a spoon that doesn't exist.

Nobody is looking at these pages

[flagged]