- https://www.ssllabs.com/ssltest/analyze.html?d=bitcointalk.org&hideResults=on&latest
Except for sni. cloudfartsssl .com not Lets Encrypt for bitcointalk.org ... etc.,
@Cøbra (others?)
Wakey wakey!
Notification - Kindly fix up your Lets Encrypt SSL Certificate ... it is currently capped to a grade B ...
- https://www.ssllabs.com/ssltest/analyze.html?d=bitcoin.org&hideResults=on
SSL Labs Grade Change for TLS 1.0 and TLS 1.1 Protocols ...
- https://blog.qualys.com/ssllabs/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols
Has insecure cypher suites ...
- https://en.wikipedia.org/wiki/Cipher_suite
Is therefore vulnerable to the BEAST attack ...
- https://blog.qualys.com/ssllabs/2013/09/10/is-beast-still-a-threat
Your also using an RSA 2048 bits publickey certificate despite Lets Encrypt supporting RSA 4096 bits publickey certificates, out-of-the box ...
...
How to Guide ...
See: https://ssl-config.mozilla.org/
Example;
You need to update the # intermediate configuration ssl_protocols and ssl_ciphers .
Then use certbot to upgrade your certificate publickey to RSA 4096 bit
Cheers!
Wakey wakey!
Notification - Kindly fix up your Lets Encrypt SSL Certificate ... it is currently capped to a grade B ...
- https://www.ssllabs.com/ssltest/analyze.html?d=bitcoin.org&hideResults=on
SSL Labs Grade Change for TLS 1.0 and TLS 1.1 Protocols ...
- https://blog.qualys.com/ssllabs/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols
Has insecure cypher suites ...
- https://en.wikipedia.org/wiki/Cipher_suite
Is therefore vulnerable to the BEAST attack ...
- https://blog.qualys.com/ssllabs/2013/09/10/is-beast-still-a-threat
Your also using an RSA 2048 bits publickey certificate despite Lets Encrypt supporting RSA 4096 bits publickey certificates, out-of-the box ...
...
How to Guide ...
See: https://ssl-config.mozilla.org/
Example;
Code:
# generated 2020-06-18, Mozilla Guideline v5.4, nginx 1.17.7, OpenSSL 1.1.1d, intermediate configuration
# https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1d&guideline=5.4
server {
listen 80 default_server;
listen [::]:80 default_server;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
ssl_certificate /path/to/signed_cert_plus_intermediates;
ssl_certificate_key /path/to/private_key;
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m; # about 40000 sessions
ssl_session_tickets off;
# curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam
ssl_dhparam /path/to/dhparam;
# intermediate configuration
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;
# HSTS (ngx_http_headers_module is required) (63072000 seconds)
add_header Strict-Transport-Security "max-age=63072000" always;
# OCSP stapling
ssl_stapling on;
ssl_stapling_verify on;
# verify chain of trust of OCSP response using Root CA and Intermediate certs
ssl_trusted_certificate /path/to/root_CA_cert_plus_intermediates;
# replace with the IP address of your resolver
resolver 127.0.0.1;
}
# https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1d&guideline=5.4
server {
listen 80 default_server;
listen [::]:80 default_server;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
ssl_certificate /path/to/signed_cert_plus_intermediates;
ssl_certificate_key /path/to/private_key;
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m; # about 40000 sessions
ssl_session_tickets off;
# curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam
ssl_dhparam /path/to/dhparam;
# intermediate configuration
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;
# HSTS (ngx_http_headers_module is required) (63072000 seconds)
add_header Strict-Transport-Security "max-age=63072000" always;
# OCSP stapling
ssl_stapling on;
ssl_stapling_verify on;
# verify chain of trust of OCSP response using Root CA and Intermediate certs
ssl_trusted_certificate /path/to/root_CA_cert_plus_intermediates;
# replace with the IP address of your resolver
resolver 127.0.0.1;
}
You need to update the # intermediate configuration ssl_protocols and ssl_ciphers .
Then use certbot to upgrade your certificate publickey to RSA 4096 bit
Code:
sudo certbot --nginx -d bitcoin.org -d www.bitcoin.org --rsa-key-size 4096
Cheers!
