Bugzilla – Bug 1215627
Repositories refer to http:// instead to https:// libcurl not accepting
Last modified: 2023-09-23 09:29:04 UTC
Good morning, I have manually changed the standard opensuse tumbleweed repositories from http to https, this works. When enabling the codecs repository, then there is a redirect to an http site, which is rejected by libcurl Cut and paste from terminal: Retrieving: libopenh264-7-2.3.1-2.suse1699.30.x86_64.rpm ..................................................................................................................[error] Download (curl) error for 'https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/x86_64/libopenh264-7-2.3.1-2.suse1699.30.x86_64.rpm': Error code: Unsupported protocol or redirect (location: http://ciscobinary.openh264.org/libopenh264-7-2.3.1-2.suse1699.30.x86_64.rpm) Error message: Redirect to protocol "http" not supported or disabled in libcurl Hugo
HTTPS downgrade “support“ is a bad idea, so recommend that this is not manually changed in this way *** This bug has been marked as a duplicate of bug 1207567 ***
On a clean installation of OpenSue Tumbleweed (not an upgrade) the repositories are set up by default in the system as http:// In order to use "sudo zypper ref" I first have to upgrade manually all the repositories from http:// to https:// Once the "s" has been added, it is possible to do a "sudo zypper ref" followed by a "sudo zypper dup" Then it works like charm. Except when the codec repository is enabled, that probably has to do with a redirect to a http:// site.
Why do you think you "have" to make this change? What seems to be failing if you have it? Using https over http offers no additional integrity or authenticity compared to package and repository metadata signing.
Otherwise the system would not preform an upgrade, either using yast or zypper. Maybe there is a restriction on libcurl not allowing unsecure sites. In previous editions (prior 2022) of the 4.5GiB iso file the repositories would show up as https:// I have reset the url to the original http version and now the issue has been resolved. Also reset the other urls to http versions and was able to install a piece of software. No problem either. If it pops up again, I will report it under "installation"