| 1 |
Hi, |
| 2 |
|
| 3 |
I'm the maintainer of mirror.mdfnet.se. The future of this mirror is not |
| 4 |
entirely clear (it may have to be removed in a few weeks/months), but |
| 5 |
for now I've added a letsencrypt certificate, opened it up for https and |
| 6 |
will make sure to maintain it for as long as the mirror is available. |
| 7 |
|
| 8 |
/Feffe |
| 9 |
|
| 10 |
|
| 11 |
On 2019-04-13 08:28, Robin H. Johnson wrote: |
| 12 |
> Hi! |
| 13 |
> |
| 14 |
> Upstream Chrome is discussing a potential change that we try to block |
| 15 |
> users following a HTTPS->HTTP for high-risk files, including tarballs. |
| 16 |
> https://lists.w3.org/Archives/Public/public-webappsec/2019Apr/0004.html |
| 17 |
> |
| 18 |
> Further below is some quick analysis I did on the state of HTTP for the mirrors |
| 19 |
> that are presently listed only as HTTP. |
| 20 |
> |
| 21 |
> In the era of LetsEncrypt, how many mirror administrators have a little time to |
| 22 |
> add HTTPS to their mirrors, along with a cronjob to auto-refresh the |
| 23 |
> certificates? |
| 24 |
> |
| 25 |
> The state of HTTP/HTTPS on Gentoo mirrors: |
| 26 |
> 59 mirrors total |
| 27 |
> ===== |
| 28 |
> 1 HTTPS-only |
| 29 |
> 27 HTTP+HTTPS |
| 30 |
> 31 HTTP-only |
| 31 |
> |
| 32 |
> Of the HTTP-only mirrors, only 1 is on a non-standard port. |
| 33 |
> |
| 34 |
> Of the HTTP-only mirrors, I went to test if of them had working HTTPS |
| 35 |
> that wasn't documented in distfiles.xml, and if not, what responses |
| 36 |
> there were (I think I got an off-by-one try to summarize the errors). |
| 37 |
> |
| 38 |
> 2 200 OK |
| 39 |
> 24 No connection: Connection refused, Connection timed out, No route to host |
| 40 |
> 3 Horrible SSL certs |
| 41 |
> 2 SSL_ERROR_BAD_CERT_DOMAIN/The name in the certificate does not match the expected, but everything else was otherwise good. |
| 42 |
> 1 HTTP on port 443 (SSL_ERROR_RX_RECORD_TOO_LONG) |
| 43 |
> ==== |
| 44 |
> 32 errors |
| 45 |
> |
| 46 |
> Horrible SSL certs, error breakdown; some mirrors had MORE than one error in their cert: |
| 47 |
> 3 - SEC_ERROR_UNKNOWN_ISSUER/The certificate issuer is unknown [1] |
| 48 |
> 2 - The certificate chain uses insecure algorithm (RSA-SHA1) |
| 49 |
> 3 - SEC_ERROR_EXPIRED_CERTIFICATE/The certificate chain uses expired certificate [2] |
| 50 |
> 3 - SSL_ERROR_BAD_CERT_DOMAIN/The name in the certificate does not match the expected. |
| 51 |
> 1 - SEC_ERROR_UNRECOGNIZED_OID [3] |
| 52 |
> |
| 53 |
> [1] SEC_ERROR_UNKNOWN_ISSUER: |
| 54 |
> - self-signed |
| 55 |
> - defunct CA |
| 56 |
> - missing intermediate |
| 57 |
> |
| 58 |
> [2] SEC_ERROR_EXPIRED_CERTIFICATE: |
| 59 |
> Past-expiry ranges 1 month to 4 years ago! |
| 60 |
> |
| 61 |
> [3] SEC_ERROR_UNRECOGNIZED_OID: |
| 62 |
> OpenSSL & GnuTLS handled this cert, but NSS failed on it. |
| 63 |
> |
Archives