Publisher signature or attestation for the exact Windows wheel, opencv-python 4.14.0.94

Offen
  • Stimmt etwas nicht?
#1,277 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, python
Bereich
release, security

Rechercherichtung

Start by reviewing the repository’s release and Windows CI workflow for the specified wheel and run, then check the official PyPI and GitHub attestation sources named in the issue. Determine whether an existing signature or attestation and an independent publisher verification policy cover the exact wheel bytes. Done means providing an official pointer to both, or confirming that no existing proof was found.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hello opencv-python maintainers,

We are preparing a reproducible offline Python environment and need to locate
publisher-authenticated evidence for this existing, unmodified wheel:

Field Exact value
Package opencv-python 4.14.0.94
Filename opencv_python-4.14.0.94-cp37-abi3-win_amd64.whl
Size 41,166,165 bytes
SHA256 ace53616cdffc9643e17e075397b493e607c427d388c7508798ef7ad2ed577cc
Official repository opencv/opencv-python
Release / tag 4.14.0.94 / 94
Commit 2ba8bf62f2f1215ab620416b041c9659005fa25c
Windows CI run 30346216575, attempt 1
CI artifact wheel-0-0-0-x64, ID 8683370453

We already established byte-for-byte equality between this PyPI wheel and the
wheel inside the official CI artifact. We retain that evidence separately from
publisher signature verification.

Could you point us to an existing signature/attestation bundle and the official
publisher verification policy for this exact wheel? We need the original signed
statement or detached signature, its certificate/public verification material,
and the required transparency or timestamp evidence. The policy should identify
the authorized public key or signer identity, issuer and predicate, as applicable,
through an official source independent of the candidate bundle itself.

Our dated public observations returned HTTP 404 for this wheel's PyPI provenance
endpoint and for the repository's GitHub attestation queries on the wheel and CI
container digests. The legacy Rekor index returned no UUIDs for those two digests.
We recognize that these results are incomplete discovery observations and do
not establish that no signature exists elsewhere.

If there is no existing proof, please let us know. If the project can issue a
new authorized publisher endorsement of the same bytes, we can assess it in a
new review while retaining its actual issue time and scope. We would not present
a later endorsement as proof that the original historical build/publication was
signed when it occurred. We are not asking for a wheel rebuild or replacement.

Only public verification material is needed; please do not provide any private
key, credential, password or access token. A pointer to the appropriate official
policy or existing artifact is sufficient for the next review.

Thank you.

Vorherrschende Sprache
Python
Sterne
5.4k
Forks
1.1k
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opencv/opencv-python

Alle Issues in opencv/opencv-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.