ssl证书制作

1 概述

本文讲述ssl tcp如何测试及使用，重点在于讲解实际操作及相关概念；适合初次接触ssl的读者。

2 环境准备

2.1 Ssl协议详解

(https://blog.csdn.net/qq_38265137/article/details/90112705)网站导航1 网站导航2 2）

2.2 SSL server测试工具

2.3 Java

安装最新的java包，配置如下环境变量（请根据具体安装目录修改）
JAVA_HOME：C:\Program Files\Java\jdk1.8.0_171
CLASSPATH：.;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar;
Path中添加：;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;

2.4 支持SSL TCP功能的模块

2.5 Openssl（制作证书）

(https://img-blog.csdnimg.cn/1c5d6d2536284fa4b146501d25fba77b.png)

3 如何制作证书

3.1 安装win32openssl-0_9_8.exe软件包，默认配置安装即可

3.2 配置openssl环境

（网站导航[(https://blog.csdn.net/xiongya8888/article/details/82432637)）

3.2.1 设置openssl的环境变量，

OPENSSL_CONF=C:\OpenSSL\bin\openssl.cnf
(https://img-blog.csdnimg.cn/6128536568414023ac9d96c49726ed8f.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L1dtbGwxMjM0NTY3,size_16,color_FFFFFF,t_70)

3.2.2 Path中添加：;C:\OpenSSL\bin

3.2.3 修改openssl配置文件（用如下附件替换C:\OpenSSL\bin\openssl.cnf）

3.3 一键生成ca证书、服务端证书、客户端证书

执行脚本：
，需要输入y确认。
脚本需要根据具体情况修改的地方：

3.4 脚本内容

```bash
@echo off

echo  -----------自制CA证书、svr证书、clt证书-----------
::密码至少4位
set CA_KEY_PASSWORD=123456
::set CA_COMMON_NAME=localhost
set CA_COMMON_NAME=neoway

::密码至少4位
set SERVER_KEY_PASSWORD=123456
::必须与服务端IP或域名一致！！

::set SERVER_COMMON_NAME=192.168.13.54
::set SERVER_COMMON_NAME=183.239.240.40
set SERVER_COMMON_NAME=127.0.0.1

::密码至少4位
set CLIENT_KEY_PASSWORD=123456
::必须与客户端IP或域名一致！！(针对内部特殊测试环境，该值需按如下配置，而非客户端实际IP)
::set CLIENT_COMMON_NAME=183.239.240.40
set CLIENT_COMMON_NAME=127.0.0.1
::set CLIENT_COMMON_NAME=192.168.13.54

::CA证书路径
set CA_CRT_PATH=ca.crt
set CA_KEY_PATH=ca.key
set CA_CSR_PATH=ca.csr

::服务器证书路径
set SERVER_CRT_PATH=server.crt
set SERVER_KEY_PATH=server.key
set SERVER_CSR_PATH=server.csr
set SERVER_PFX_PATH=server.pfx

::客户端证书路径
set CLIENT_CRT_PATH=client.crt
set CLIENT_KEY_PATH=client.key
set CLIENT_CSR_PATH=client.csr
set CLIENT_PFX_PATH=client.pfx

::----------------------
Rem 
::----------------------
::1.生成根证书私钥
openssl genrsa -des3 -passout pass:%CA_KEY_PASSWORD% -out %CA_KEY_PATH% 2048
::2.生成证书签名请求
openssl req -new -passin pass:%CA_KEY_PASSWORD% -key %CA_KEY_PATH% -out %CA_CSR_PATH% -subj "/C=CN/ST=Shenzhen/L=Shenzhen/O=neoway/OU=IT/CN=%CA_COMMON_NAME%"
::3.根证书签名
openssl x509 -req -in %CA_CSR_PATH% -sha256 -extensions v3_ca  -passin pass:%CA_KEY_PASSWORD% -signkey %CA_KEY_PATH% -out %CA_CRT_PATH% -days 3650 


::4.生成服务端证书私钥
::openssl genrsa -des3 -passout pass:%SERVER_KEY_PASSWORD% -out %SERVER_KEY_PATH% 2048
openssl genrsa -out %SERVER_KEY_PATH% 2048
::5.生成服务端证书签名请求
openssl req -new -key %SERVER_KEY_PATH% -out %SERVER_CSR_PATH% -subj "/C=CN/ST=Shenzhen/L=Shenzhen/O=neoway/OU=IT/CN=%SERVER_COMMON_NAME%"
::6.服务端证书签名
openssl x509 -req -in %SERVER_CSR_PATH% -sha256 -extensions usr_cert -CA %CA_CRT_PATH% -passin pass:%CA_KEY_PASSWORD% -CAkey %CA_KEY_PATH% -CAcreateserial -out %SERVER_CRT_PATH% -days 3650 

::7.生成客户端证书私钥
::openssl genrsa -des3 -passout pass:%CLIENT_KEY_PASSWORD% -out %CLIENT_KEY_PATH% 2048
openssl genrsa -out %CLIENT_KEY_PATH% 2048
::8.生成客户端证书签名请求
openssl req -new -key %CLIENT_KEY_PATH% -out %CLIENT_CSR_PATH% -subj "/C=CN/ST=Shenzhen/L=Shenzhen/O=neoway/OU=IT/CN=%CLIENT_COMMON_NAME%"
::9.客户端证书签名
openssl x509 -req -in %CLIENT_CSR_PATH% -sha256 -extensions usr_cert -CA %CA_CRT_PATH% -passin pass:%CA_KEY_PASSWORD% -CAkey %CA_KEY_PATH% -CAcreateserial -out %CLIENT_CRT_PATH% -days 3650 

::10.服务器证书加密
::openssl pkcs12 -export -out %SERVER_PFX_PATH% -inkey %SERVER_KEY_PATH% -in %SERVER_CRT_PATH%
openssl pkcs12 -export -out %SERVER_PFX_PATH% -inkey %SERVER_KEY_PATH% -in %SERVER_CRT_PATH% -passin pass:%SERVER_KEY_PASSWORD% -password pass:%SERVER_KEY_PASSWORD%

::11.客户端证书加密
::openssl pkcs12 -export -out %CLIENT_PFX_PATH% -inkey %CLIENT_KEY_PATH% -in %CLIENT_CRT_PATH%
openssl pkcs12 -export -out %CLIENT_PFX_PATH% -inkey %CLIENT_KEY_PATH% -in %CLIENT_CRT_PATH% -passin pass:%CLIENT_KEY_PASSWORD% -password pass:%CLIENT_KEY_PASSWORD%

::12 根证书入库
keytool -keystore root.truststore -keypass %CA_KEY_PASSWORD% -storepass %CA_KEY_PASSWORD% -alias ca -import -trustcacerts -file %CA_CRT_PATH%

pause

openssl.conf 文件

#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# This definition stops the following lines choking if HOME isn't
# defined.
HOME			= .
RANDFILE		= $ENV::HOME/.rnd

# Extra OBJECT IDENTIFIER info:
#oid_file		= $ENV::HOME/.oid
oid_section		= new_oids

# To use this configuration file with the "-extfile" option of the
# "openssl x509" utility, name here the section containing the
# X.509v3 extensions to use:
# extensions		= 
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by 'ca' and 'req'.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section

####################################################################
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
					# several ctificates with same subject.
new_certs_dir	= $dir/newcerts		# default place for new certs.

certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
crlnumber	= $dir/crlnumber	# the current crl number
					# must be commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
RANDFILE	= $dir/private/.rand	# private random number file

x509_extensions	= usr_cert		# The extentions to add to the cert

# Comment out the following two lines for the "traditional"
# (and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions	= crl_ext

default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= sha1			# which md to use.
preserve	= no			# keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that :-)
policy		= policy_match

# For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

# For the 'anything' policy
# At this point in time, you must list all acceptable 'object'
# types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional

####################################################################
[ req ]
default_bits		= 1024
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extentions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options. 
# default: PrintableString, T61String, BMPString.
# pkix	 : PrintableString, BMPString.
# utf8only: only UTF8Strings.
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: current versions of Netscape crash on BMPStrings or UTF8Strings
# so use this option with caution!
string_mask = nombstr

req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= AU
countryName_min			= 2
countryName_max			= 2

stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State

localityName			= Locality Name (eg, city)

# 0.organizationName		= Organization Name (eg, company)
# 0.organizationName_default	= Internet Widgits Pty Ltd

# we can do this but it is not needed normally :-)
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd

organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=

commonName			= Common Name (eg, YOUR name)
commonName_max			= 64

emailAddress			= Email Address
emailAddress_max		= 64

# SET-ex3			= SET extension number 3

[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20

unstructuredName		= An optional company name

[ usr_cert ]

# These extensions are added when 'ca' signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

[ v3_req ]

# Extensions to add to a certificate request
extendedKeyUsage=serverAuth
subjectAltName = @alt_names
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_ca ]
basicConstraints = CA:true

# Extensions for a typical CA


# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer:always

# This is what PKIX recommends but some broken software chokes on critical
# extensions.
#basicConstraints = critical,CA:true
# So we do this instead.
basicConstraints = CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where 'obj' is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ alt_names ]
DNS.1 = 127.0.0.1
IP.1 = 127.0.0.1

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always,issuer:always

[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType			= server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape's comment listbox.
nsComment			= "OpenSSL Generated Certificate"

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer:always

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren't
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl		= http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo