ppa.launchpad.net has incorrect SSL cert applied

[Peter]

It has been noticed that the ssl cert on https://ppa.launchpad.net is either for the wrong domain, or missing the SAN ppa.lauchpad.net. This is causing problems with other tools like chef when adding public from PPA.

$ curl --verbose https://ppa.launchpad.net/
* Trying 91.189.95.85:443...
* TCP_NODELAY set
* Connected to ppa.launchpad.net (91.189.95.85) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=private-ppa.launchpad.net <----- Wrong name.
* start date: Sep 19 02:50:43 2021 GMT
* expire date: Dec 18 02:50:42 2021 GMT
* subjectAltName does not match ppa.launchpad.net
* SSL: no alternative certificate subject name matches target host name 'ppa.launchpad.net'
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name 'ppa.launchpad.net'

[Colin Watson (cjwatson)]

ppa.launchpad.net is not intended to support being used over HTTPS. We have a plan in progress for allowing access to public PPAs over HTTPS, but it will involve a different host name. See bug 1473091.