zatosource / zato

ESB, SOA, REST, APIs and Cloud Integrations in Python
https://zato.io
GNU Affero General Public License v3.0
1.12k stars 240 forks source link

Problem with repo update and GPG key for Zato3.0 #1056

Closed SharpThunder closed 4 years ago

SharpThunder commented 4 years ago

Hello,

I already installed Zato and it's repo in a Ubuntu 16.04 server. During auto update of my zato servers, I encountered repo update error.

Err:12 https://zato.io/repo/stable/3.0/ubuntu xenial/main amd64 Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none Reading package lists... Done W: The repository 'https://zato.io/repo/stable/3.0/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://zato.io/repo/stable/3.0/ubuntu/dists/xenial/main/binary-amd64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none E: Some index files failed to download. They have been ignored, or old ones used instead.

When i try to re-add the key with

curl -s https://zato.io/repo/zato-0CBD7F72.pgp.asc | sudo apt-key add - gpg: no valid OpenPGP data found.

Could you please update the key? Thanks.

dsuch commented 4 years ago

Hello @SharpThunder,

My curl version is:

$
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL 
$
SharpThunder commented 4 years ago

Hello @dsuch

Thanks.

dsuch commented 4 years ago

Ah, I see, thanks, I will relay it to the people responsible for the certificate.

The situation with OpenSSL is that it started to move much faster in the last few years so I imagine that such things may happen from time to time and only four years will mean a lot - although I have not seen it myself prior to this ticket.

As for the newcomers, they tend to use the latest versions of everything so this is less of a concern but you are right that generally, this is something to look into, thanks once more.

dsuch commented 4 years ago

@SharpThunder Could you try it out now? There is a new intermediate certificate uploaded.

SharpThunder commented 4 years ago

Thank you, that fixed the problem.