On 25/03/2019 14.54, Hermann-Josef Beckers wrote:
[>] ... [>] > [>]
I don't see the relation between your own certificate and zypper. Zypper can only >complain about certificates of repos.
[>]
Wget is more verbose:
wget --no-check-certificate https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-opensuse/* Warning: wildcards not supported in HTTP. --2019-03-25 14:43:48-- https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-opensuse/* Connecting to 10.X.Y.Z:3128... connected. WARNING: cannot verify www.collaboraoffice.com's certificate, issued by ‘CN=mwg.MYGATEWAY.lokal,C=DE,ST=NRW,L=Steinfurt,O=Kreis Steinfurt’: Self-signed certificate encountered.
I doubt that collaboraoffice.com is self signed. Seems the (perhaps not) self signed certificate of my gateway must be inserted somewhere into the chain of trust?
I doubt that very much. Can't be, the certificate of the site has to be chained to its own certificate authority, defined on the certificate itself. Unless there is some name collision :-? Anyway, I can not replicate: cer@Telcontar:~/tmp/hjb> wget https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-opensuse/* Warning: wildcards not supported in HTTP. --2019-03-25 14:58:59-- https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-opensuse/* Resolving www.collaboraoffice.com (www.collaboraoffice.com)... 46.235.227.219, 2a00:1098:0:82:1000:25:2eeb:e3db Connecting to www.collaboraoffice.com (www.collaboraoffice.com)|46.235.227.219|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2019-03-25 14:58:59 ERROR 404: Not Found. cer@Telcontar:~/tmp/hjb> It seems for you the connection is intranet, though, so maybe the site is not available for me. CN=mwg.MYGATEWAY.lokal -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)