andersk commented on issue #41678:
URL: https://github.com/apache/arrow/issues/41678#issuecomment-6873083298

   This is still valid. The specific signature from the original report no 
longer matters, but the underlying problem hasn’t changed. Many current 
artifacts are signed by keys that aren’t in 
https://apache.jfrog.io/artifactory/arrow/debian/apache-arrow-keyring.gpg, 
which still has the same 9 keys as in 2024.
   
   - `apache-arrow-apt-source-latest-noble.deb.asc` (26.0.1, 2026-10-30) and 
the `noble`/`trixie` `InRelease` files are signed by 
`7BD1A9A50E4F701BCBFD90EF9E922B2D60E9FD1C`, a key created 2026-02-11.
   - `bookworm/InRelease` (2026-07-24) is signed by 
`BE7EF45DBAD38E4EECED390E9CBA4EF977CA20B8`.
   
   All of these verify against the current `KEYS`, but `KEYS` has grown from 16 
to 25 keys since this issue was opened. So a keyring fetched at any point in 
the past still eventually stops working, and there is no secure way to fetch a 
new keyring without being exposed to the very threats that the keyring is 
supposed to defend against (server compromise, SSL vulnerability, etc.).
   
   Please create a single stable key whose role is to sign the Arrow artifacts, 
not to represent the personal identity one of many rotating developers 
unverifiably associated with the project.


-- 
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]

Reply via email to