GPG Keys for Almalinux 9.1 are SHA1 #1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
osbuild-composer seems not to be too happy with SHA1 keys (or maybe it's related to /etc/crypto-policy? Can't figure it out so far).
Anyway: The PublicKey used in for osbuild for Alma 9 is actually the one for 8. So bouth sources use the same, even though there are specific keys for each version to use (I guess because the key for 8 is using SHA1 which is not supported by Alma 9 anymore?)
https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux-8
https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux-9
Not completly sure if that is the problem and I'll try to patch my local version tomorrow, but here I said it.
The culprit:
Cheers,
Benji
I can confirm now that indeed there is a problem with the Alma9 key in the patch.
When changing it the building process of osbuild-composer runs through. I now was able to build a ostree alma based upon the redhat edge configuration.
I would need some help anyway since I'm new to patching packages.
My understanding is that I've got to deflate the package somehow, fix it and then ask rpm to create a diff? Any pointers?
This would be the patched
/usr/share/osbuild-composer/repository/almalinux-91.json
(I'm failing to attach the file)