I tried to download a distfile from https://distcache.freebsd.org/
I got an SSL error
distcache.freebsd.org uses an invalid security certificate. The certificate is only valid for pkg.freebsd.org Error code: SSL_ERROR_BAD_CERT_DOMAIN
The CDN sites have the same SSL problem:
In bsd.port.mk, the distcache urls use HTTP, not HTTPS.
Also, for non maintainers/committers, SSL_NO_VERIFY_PEER=1 and SSL_NO_VERIFY_HOSTNAME=1 are used when fetching distfiles from https sites (distinfo already ensures the integrity of the distfiles).
So I don't think this is a problem.
(In reply to Antoine Brodin from comment #2)
> In bsd.port.mk, the distcache urls use HTTP, not HTTPS.
this is another bug, but lets fix the SSL errors first.
The issue is about privacy, not integrity. It is our duty to protect our users. E.g. in some countries it is illegal to use, or even install VPN clients.
This issue still persists.
This is not actually an issue. As Antoine pointed out in #2, the distfiles are fetched over HTTP.
The ports system doesn't need SSL for integrity. SSL doesn't provide any privacy for distfile downloads: the filesize alone will fingerprint files with reasonable accuracy.
Maybe if the distcache could *not* be used with https, it would end this.
(In reply to Philip Paeps from comment #5)
That's correct, but many people assume that a non-matching certificate compromises security. I am not one of those ;-)
We could probably also add distcache.freebsd.org as a san but it would indeed be easier simply not to offer https.
I believe the only reason https is on is because people apparently expect that http runs over port 443 wrapped in tls these days.
Well, it would be nice if the vhost for distcache did not exist in https, or actualy did not point to the same place than the http version.