• 微信支付HTTPS服务器证书验证指引
• 证书FAQ_常见问题_负载均衡-阿里云产品文档

买证书：

• https://www.startssl.com 只对个人免费，需要用 whois 邮箱验证域名属于我
• https://github.com/certbot/certbot

证书安卓 android 不认问题：

• 链式证书问题
  • android - SSL certificate is not trusted - on mobile only - Stack Overflow
  • ubuntu - Why does Android Chrome say my site's security certificate is not trusted? - Server Fault
• 检查证书
  • SSL Server Test (Powered by Qualys SSL Labs)
  • SSL Checker - SSL Certificate Verify

• 看网站支持什么版本：https://www.ssllabs.com/ssltest/
• 看自己支持什么版本：https://www.ssllabs.com/ssltest/viewMyClient.html
• 首页：https://www.ssllabs.com/

• 参考 nategood/sleep-tight
• 吊销证书 Certificate revocation lists — OpenSSL Certificate Authority — Jamie Nguyen
• 一篇比较全的使用 node.js 做 https server 的文章（包括客户端证书、revoke）：HTTPS Authorized Certs with Node.js – Circle Engineering
• 客户端证书的真实使用场景：安装数字证书的操作流程 - 服务大厅 - 支付宝

• 创建链式证书这个文档比较全：Create the root pair — OpenSSL Certificate Authority — Jamie Nguyen
• 按以下脚本生成证书的问题：CA、服务端、客户端都要求密码
• 不要密码的方法：apache 2.2 - Is it possible to generate RSA key without pass phrase? - Server Fault
• 那些证书相关的玩意儿(SSL,X.509,PEM,DER,CRT,CER,KEY,CSR,P12等) - guogangj - 博客园

create-certs.sh

#! /usr/bin/env bash
 
# Create the CA Key and Certificate for signing Client Certs
openssl genrsa -des3 -out ca.key 4096
openssl req -new -x509 -days 365 -key ca.key -out ca.crt
 
# 或者
 
# Create the Server Key, CSR, and Certificate
openssl genrsa -des3 -out server.key 1024
openssl req -new -key server.key -out server.csr
 
# We're self signing our own server cert here.  This is a no-no in production.
openssl x509 -req -days 365 -in server.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out server.crt
 
# Create the Client Key and CSR
openssl genrsa -des3 -out client.key 1024
openssl req -new -key client.key -out client.csr
 
# Sign the client certificate with our CA cert.  Unlike signing our own server cert, this is what we want to do.
# Serial should be different from the server one, otherwise curl will return NSS error -8054
openssl x509 -req -days 365 -in client.csr -CA ca.crt -CAkey ca.key -set_serial 02 -out client.crt
 
# Verify Server Certificate
openssl verify -purpose sslserver -CAfile ca.crt server.crt
 
# Verify Client Certificate
openssl verify -purpose sslclient -CAfile ca.crt client.crt

create-certs-nopwd.sh

#! /usr/bin/env bash
 
# Create the CA Key and Certificate for signing Client Certs
openssl req -nodes -new -x509 -keyout ca.key -out ca.crt
 
# Create the Server Key, CSR, and Certificate
openssl req -nodes -new -keyout server.key -out server.csr
 
# We're self signing our own server cert here.  This is a no-no in production.
openssl x509 -req -days 365 -in server.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out server.crt
 
# Create the Client Key and CSR
openssl req -nodes -new -keyout client.key -out client.csr
 
# Sign the client certificate with our CA cert.  Unlike signing our own server cert, this is what we want to do.
# Serial should be different from the server one, otherwise curl will return NSS error -8054
openssl x509 -req -days 365 -in client.csr -CA ca.crt -CAkey ca.key -set_serial 02 -out client.crt
 
# Verify Server Certificate
openssl verify -purpose sslserver -CAfile ca.crt server.crt
 
# Verify Client Certificate
openssl verify -purpose sslclient -CAfile ca.crt client.crt

openssl x509 -noout -text -in $YOUR_CERT
 
X509v3 extensions:
  X509v3 Basic Constraints:
-    CA:TRUE
+    CA:FALSE

nginx.conf

# Bare Bones nginx config file.  Replace with your appropriate paths
 
user www-data www-data;
worker_processes  1;
 
events {
    worker_connections  1024;
}
 
 
http {
    include       mime.types;
    default_type  application/octet-stream;
 
    sendfile        on;
    keepalive_timeout  65;
 
    server {
        listen        443;
        ssl on;
        server_name example.com;
 
        error_page 495 496 497 https://www.google.com; # 定制 HTTPS 握手失败错误页
 
        ssl_certificate      /etc/nginx/certs/server.crt;
        ssl_certificate_key  /etc/nginx/certs/server.key;
        ssl_client_certificate /etc/nginx/certs/ca.crt;
        ssl_verify_client optional;
        # ssl_verify_depth 2;
 
        location / {
            root           /var/www/example.com/html;
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_param  SCRIPT_FILENAME /var/www/example.com/lib/Request.class.php;
            fastcgi_param  VERIFIED $ssl_client_verify;
            fastcgi_param  DN $ssl_client_s_dn;
            include        fastcgi_params;
        }
    }    
}

# 不用证书访问
$ http --verify=no https://example.com/
 
# 用证书，会提示输入密码
$ http --verify=no --cert=client.crt --cert-key=client.key https://example.com/
 
# curl（on mac）可能不正常
$ curl -v -s -k --key client.key --cert client.crt https://example.com/

• CVE - CVE-2000-0649
• Microsoft IIS Internal IP Address Disclosure Vulnerability
• nginx 也有这个问题，但如果是 https 就没法用 telnet 测试了，可以用 openssl s_client，但这个命令在 mac 上不正常，需要 linux 运行

  $ openssl s_client -connect foo.bar.com:443
  # 能看到算法、服务端客户端的签名信息等
  HEAD /static/css HTTP/1.0
   
  HTTP/1.1 301 Moved Permanently
  Server: nginx
  Date: Thu, 10 May 2018 05:57:50 GMT
  Content-Type: text/html
  Content-Length: 178
  Location: https://10.10.1.123/static/css/  <-- 暴露了内网信息
  Connection: close
   
  closed

• 解决方法是 server_name_in_redirect on
  • A possible fix for CVE-2000-0649 in NGINX – Home of a code hacker, not a real hacker.
  • Module ngx_http_core_module

$ openssl pkcs12 -export -clcerts -in client.crt -inkey client.key -out client.p12
# 需要输入一个 p12 提取密码
 
$ openssl pkcs12 -export -clcerts -in client.crt -inkey client.key -out client.p12 -passout pass:
# 不输或者用 pass:，最后生成的用不了
 
# 测试，123123 是密码 ---> 不一定行，还是用浏览器测试更准确
$ curl -v -s -k --cert client.p12:123123 https://example.com/
 
# 上面的命令可能不行，命令行还是得用 crt/key
$ openssl pkcs12 -in mycert.p12 -out file.key.pem -nocerts -nodes
$ openssl pkcs12 -in mycert.p12 -out file.crt.pem -clcerts -nokeys
$ http --verify=no --cert=file.crt.pem --cert-key=file.key.pem  https://www.secure.com/
 
# 或者双击、输入密码导入 mac，
# 使用 safari 访问时，会要求
# 选证书。但用 chrome 还不行

• Certificate Management and Generation with OpenSSL

使用 CRL 必须有个 openssl 的配置文件：

Not all of the files you need for doing CRLs can be specified on the command line, however the config file to use can be (with -config <file>). Therefore, you really need to customise an openssl.cnf file for each CA you run before doing this step, otherwise you'll come unstuck. For an old but good guide on how to do this, see this archived page, or you can also look at this alternate guide.

生成这个配置文件：

/homw/www/ca/ca.conf

[ ca ]
default_ca      = CA_default           # The default ca section
 
[ CA_default ]
 
dir            = .                     # top dir
database       = $dir/index.txt        # index file.
new_certs_dir	= $dir/newcerts        # new certs dir
 
 
crl_dir          = $dir/revoked
 
 
certificate    = $dir/cacert.pem       # The CA cert
serial         = $dir/serial           # serial no file
private_key    = $dir/private/cakey.pem# CA private key
RANDFILE       = $dir/private/.rand    # random number file
 
default_days   = 365                   # how long to certify for
default_crl_days= 30                   # how long before next CRL
default_md     = md5                   # md to use
 
policy         = policy_any            # default policy
email_in_dn    = no                    # Don't add the email into cert DN
 
name_opt	= ca_default		# Subject name display option
cert_opt	= ca_default		# Certificate display option
copy_extensions = none			# Don't copy extensions from request
 
[ policy_any ]
countryName            = supplied
stateOrProvinceName    = optional
organizationName       = optional
organizationalUnitName = optional
commonName             = supplied
emailAddress           = optional

使用 CRL：

# 创建索引文件（之前没有 conf 就没创建）
$ touch index.txt
 
# 生成 CRL
$ openssl ca -gencrl -config ca.conf -keyfile ca.key -cert ca.crt -out revoked/crl.pem
 
# 查看 CRL
$ openssl crl -in revoked/crl.pem -noout -text
> No Revoked Certificates
 
# 过期一个 client
$ openssl ca -config ca.conf -keyfile ca.key -cert ca.crt -revoke client.crt
 
# 再次查看 CRL
$ openssl crl -in revoked/crl.pem -noout -text
> Revoked Certificates:
>     Serial Number: 02
 
# 包含 CRL 检查客户端证书：
# 需要先拼接 crt 和 crl
$ cat ca.crt revoked/crl.pem > ca-crt-crl.pem
# 再做检查
$ openssl verify -crl_check -CAfile  ca-crt-crl.pem client-crt.pem

参考：OpenSSL: Manually verify a certificate against a CRL - Raymii.org

在 nginx 中使用 CRL：

  ssl_client_certificate /etc/nginx/certs.np/ca.crt;
  ssl_verify_client on;
+ ssl_crl /etc/nginx/certs.np/revoked/crl.pem;

用旧 client.key 访问会和没有 key 一样，被 nginx 拦截。