Skip to content

Conversation

@rbikar
Copy link
Member

@rbikar rbikar commented Dec 8, 2025

For PQC signed RPMs (not only), Errata tool API will provide a string called
"key alias" on sig_key field in format "name1,name2,...". In order support
this following changes are now implemented:

For Errata source:

  • replace , with + in string provided from sig_key field, this is
    later provided to Koji source as a signing key argument.

For Koji source:

  • keep backwards compatible behavior for parsing signing_key argument
  • replace + with , for each value in signing_key (later used for
    path to RPM file)
  • extract signing key ID from RPM headers every time as we don't know
    whether caller passed alias or actual key ID, as the alias can be
    formed as one name only ("sig_key":"alias_name")

@rbikar rbikar marked this pull request as ready for review December 8, 2025 15:29
@rbikar
Copy link
Member Author

rbikar commented Dec 8, 2025

pre-commit issue will be fixed in #687

@rbikar rbikar requested a review from MichalHaluza December 8, 2025 15:29
For PQC signed RPMs (not only), Errata tool API will provide a string called
"key alias" on `sig_key` field in format "name1,name2,...". In order support
this following changes are now implemented:

For Errata source:
* replace `,` with `+` in string provided from `sig_key` field, this is
   later provided to Koji source as a signing key argument.

For Koji source:
* keep backwards compatible behavior for parsing `signing_key` argument
* replace `+` with `,` for each value in `signing_key` (later used for
   path to RPM file)
* extract signing key ID from RPM headers every time as we don't know
   whether caller passed alias or actual key ID, as the alias can be
   formed as one name only ("sig_key":"alias_name")
@rbikar rbikar merged commit cac304f into release-engineering:master Dec 9, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants