On Thu, May 28, 2020 at 1:57 PM Nuno Higgs
Hello all.
I've recently came over form spacewalk to suse manager, and found an issue, regarding spacewalk-repo-sync, because some of my inhouse software providers do not sign their repomd.xml file:
# spacewalk-repo-sync --channel inhousechannel
06:42:48 ======================================
06:42:48 | Channel: inhousechannel
06:42:48 ======================================
06:42:48 Sync of channel started.
Preparing custom SSL CAPATH at /var/cache/rhn/reposync/.ssl-certs/1
Retrieving repository 'inhousechannel' metadata ----------------------------------------------------------------[]
Warning: File 'repomd.xml' from repository 'inhousechannel' is unsigned.
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise.
Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the whole repo.
Warning: We can't verify that no one meddled with this file, so it might not be trustworthy anymore! You should not continue unless you know it's safe.
File 'repomd.xml' from repository 'inhousechannel' is unsigned, continue? [yes/no] (no):
If i press y, the sync will occur, but i was wondering if there is a flag i can pass for the missing xml signature being ignored?
I know that is a BAD security error to do so, but at the present i really do not have any choice.
Can you help me please?
This is technically a behavioral breakage and shouldn't have happened. GPG checking the metadata will fail for virtually all non-SUSE repositories, because it's *really* uncommon to sign the repository metadata. This should be fixed. :( -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org