pkgrepo.managed should support key_fingerprint for key_url #67531
Replies: 8 comments
|
@mitar Thanks for the report. This would be a good feature to have. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
|
I still think this would be a good feature to have. |
|
Thank you for updating this issue. It is no longer marked as stale. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
|
Unstale. |
|
Thank you for updating this issue. It is no longer marked as stale. |
|
Agreed - this is generally considered best practice, with many significant software sources publishing a fingerprint for their signing key (or raw download checksum signing etc) and it's strongly recommended to test against it. My current example is InfluxData (prompted by their recent rotation of signing key). We currently make an explicit check of the fingerprint in our (Ansible) image building environment, but reproducing that in Salt (used for service provisioning and maintenance) is clumsy with |
Uh oh!
There was an error while loading. Please reload this page.
Currently one can use
key_urlto specify which key to install. But there is no way to assure that the key obtained is really the one you expected. Ideally, you could also provide something likekey_fingerprintso that the key would be checked against it before installing.Related: #14677
All reactions