potiuk opened a new issue, #157: URL: https://github.com/apache/tooling-trusted-release/issues/157
Some of our signatures are deemed invalid - even if kys seem to be present in the KEYS file and the KEYS file has been uploaded: * The KEYS file has been uploaded from https://dist.apache.org/repos/dist/release/airflow/KEYS Example bad signature: * https://release-test.apache.org/report/airflow/3.0.2/apache_airflow-3.0.2-py3-none-any.whl.asc <img width="1381" alt="Image" src="https://github.com/user-attachments/assets/4f87db56-7bd4-4175-92b8-bc2d3764e480"; /> Thos signatures are validated after importing KEYS file to local `gpg`: ``` gpg --verify *.asc gpg: assuming signed data in 'apache_airflow-3.0.2-py3-none-any.whl' gpg: Signature made Fri Jun 6 11:50:36 2025 CEST gpg: using RSA key CDE15C6E4D3A8EC4ECF4BA4B6674E08AD7DE406F gpg: issuer "[email protected]" gpg: Good signature from "Kaxil Naik <[email protected]>" [unknown] gpg: aka "Kaxil Naik <[email protected]>" [unknown] gpg: WARNING: The key's User ID is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: CDE1 5C6E 4D3A 8EC4 ECF4 BA4B 6674 E08A D7DE 406F ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
