linux-openssl命令行
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了linux-openssl命令行相关的知识,希望对你有一定的参考价值。
参考技术A title: linux-openssl
date: 2020-09-16 11:02:15
categories:
% note info %
OpenSSL是一个健壮的、商业级的、功能齐全的开源工具包,用于传输层安全(TLS)协议,以前称为安全套接字层(Secure Sockets Layer, SSL)协议。协议实现基于全强度通用密码库,也可以单独使用。
openssl是一个功能丰富且自包含的开源安全工具箱。它提供的主要功能有:SSL协议实现(包括SSLv2、SSLv3和TLSv1)、大量软算法(对称/非对称/摘要)、大数运算、非对称算法密钥生成、ASN.1编解码库、证书请求(PKCS10)编解码、数字证书编解码、CRL编解码、OCSP协议、数字证书验证、PKCS7标准实现和PKCS12个人数字证书格式实现等功能。
<span style="color:red;">项目地址</span> <span style="color:red;">官方网址</span> <span style="color:red;">手册</span>
% endnote %
% tabs configtab, 1 %
对称算法使用一个密钥。给定一个明文和一个密钥,加密产生密文,其长度和明文大致相同。解密时,使用读密钥与加密密钥相同。
ECB\\CBC\\CFB\\OFB
摘要算法是一种能产生特殊输出格式的算法,这种算法的特点是:无论用户输入什么长度的原始数据,经过计算后输出的密文都是固定长度的,这种算法的原理是根据一定的运算规则对原数据进行某种形式的提取,这种提取就是摘要,被摘要的数据内容与原数据有密切联系,只要原数据稍有改变,输出的“摘要”便完全不同,因此,基于这种原理的算法便能对数据完整性提供较为健全的保障。但是,由于输出的密文是提取原数据经过处理的定长值,所以它已经不能还原为原数据,即消息摘要算法是不可逆的,理论上无法通过反向运算取得原数据内容,因此它通常只能被用来做数据完整性验证。
如今常用的“消息摘要”算法经历了多年验证发展而保留下来的算法已经不多,这其中包括MD2、MD4、MD5、SHA、SHA-1/256/383/512等。
常用的摘要算法主要有MD5和SHA1。MD5的输出结果为16字节,sha1的输出结果为20字节。
在公钥密码系统中,加密和解密使用的是不同的密钥,这两个密钥之间存在着相互依存关系:即用其中任一个密钥加密的信息只能用另一个密钥进行解密。这使得通信双方无需事先交换密钥就可进行保密通信。其中加密密钥和算法是对外公开的,人人都可以通过这个密钥加密文件然后发给收信者,这个加密密钥又称为公钥;而收信者收到加密文件后,它可以使用他的解密密钥解密,这个密钥是由他自己私人掌管的,并不需要分发,因此又成称为私钥,这就解决了密钥分发的问题。
主要的公钥算法有:RSA、DSA、DH和ECC。
Openssl中大量用到了回调函数。回调函数一般定义在数据结构中,是一个函数指针。通过回调函数,客户可以自行编写函数,让openssl函数来调用它,即用户调用openssl提供的函数,openssl函数再回调用户提供的函数。这样方便了用户对openssl函数操作的控制。在openssl实现函数中,它一般会实现一个默认的函数来进行处理,如果用户不设置回调函数,则采用它默认的函数。
% endtabs %
linux-openssl
openssl组件:
openssl: 多用途命令行工具,各功能分别使用子命令实现
libcrypto: 公共加密库
libssl: ssl协议的实现
PKI:Public Key Infrastructure
签证机构:CA
注册机构:RA
证书吊销列表:CRL
证书存取库:
openssl建立私有CA:
1、生成密钥 2、自签署证书 节点: 1、生成密钥对儿 2、生成证书签署请求 3、把请求发送给CA CA: 1、验正请求者信息;RA 2、签署证书; 3、把签好的证书发送给请求者;
[[email protected] ~]# cat /etc/pki/tls/openssl.cnf #openssl配置文件/etc/pki/tls/openssl.cnf # # 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‘, ‘req‘ and ‘ts‘. # Add a simple OID like this: # testoid1=1.2.3.4 # Or use config file substitution like this: # testoid2=${testoid1}.5.6 # Policies used by the TSA examples. tsa_policy1 = 1.2.3.4.1 tsa_policy2 = 1.2.3.4.5.6 tsa_policy3 = 1.2.3.4.5.7 #################################################################### [ ca ] default_ca = CA_default # The default ca section #默认CA配置 #################################################################### [ CA_default ] dir = /etc/pki/CA # Where everything is kept #CA目录 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 #CA证书 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 #CA的私钥 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 = default # use public key default MD 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 = 2048 default_md = sha1 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 (PKIX recommendation before 2004) # utf8only: only UTF8Strings (PKIX recommendation after 2004). # nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings). # MASK:XXXX a literal mask value. # WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings. string_mask = utf8only # req_extensions = v3_req # The extensions to add to a certificate request [ req_distinguished_name ] countryName = Country Name (2 letter code) countryName_default = XX countryName_min = 2 countryName_max = 2 stateOrProvinceName = State or Province Name (full name) #stateOrProvinceName_default = Default Province localityName = Locality Name (eg, city) localityName_default = Default City 0.organizationName = Organization Name (eg, company) 0.organizationName_default = Default Company 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 or your server\‘s hostname) 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 # This is required for TSA certificates. # extendedKeyUsage = critical,timeStamping [ v3_req ] # Extensions to add to a certificate request basicConstraints = CA:FALSE keyUsage = nonRepudiation, digitalSignature, keyEncipherment [ v3_ca ] # Extensions for a typical CA # PKIX recommendation. subjectKeyIdentifier=hash authorityKeyIdentifier=keyid:always,issuer # 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 [ crl_ext ] # CRL extensions. # Only issuerAltName and authorityKeyIdentifier make any sense in a CRL. # issuerAltName=issuer:copy authorityKeyIdentifier=keyid: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 # 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 #################################################################### [ tsa ] default_tsa = tsa_config1 # the default TSA section [ tsa_config1 ] # These are used by the TSA reply generation only. dir = ./demoCA # TSA root directory serial = $dir/tsaserial # The current serial number (mandatory) crypto_device = builtin # OpenSSL engine to use for signing signer_cert = $dir/tsacert.pem # The TSA signing certificate # (optional) certs = $dir/cacert.pem # Certificate chain to include in reply # (optional) signer_key = $dir/private/tsakey.pem # The TSA private key (optional) default_policy = tsa_policy1 # Policy if request did not specify it # (optional) other_policies = tsa_policy2, tsa_policy3 # acceptable policies (optional) digests = md5, sha1 # Acceptable message digests (mandatory) accuracy = secs:1, millisecs:500, microsecs:100 # (optional) clock_precision_digits = 0 # number of digits after dot. (optional) ordering = yes # Is ordering defined for timestamps? # (optional, default: no) tsa_name = yes # Must the TSA name be included in the reply? # (optional, default: no) ess_cert_id_chain = no # Must the ESS cert id chain be included? # (optional, default: no) [[email protected] ~]#
自签证书
一、建立CA服务器: # 1、初始化工作环境 # touch /etc/pki/CA/{index.txt,serial} # echo 01 > /etc/pki/CA/serial [[email protected] ssl]# cd /etc/pki/ [[email protected] pki]# ls CA ca-trust java nssdb rpm-gpg rsyslog tls [[email protected] pki]# cd CA/ [[email protected] CA]# touch index.txt [[email protected] CA]# ll total 16 drwxr-xr-x. 2 root root 4096 Oct 15 2014 certs drwxr-xr-x. 2 root root 4096 Oct 15 2014 crl -rw-r--r--. 1 root root 0 Jul 9 12:58 index.txt drwxr-xr-x. 2 root root 4096 Oct 15 2014 newcerts drwx------. 2 root root 4096 Oct 15 2014 private [[email protected] CA]# echo 01 > serial [[email protected] CA]# ll total 20 drwxr-xr-x. 2 root root 4096 Oct 15 2014 certs drwxr-xr-x. 2 root root 4096 Oct 15 2014 crl -rw-r--r--. 1 root root 0 Jul 9 12:58 index.txt drwxr-xr-x. 2 root root 4096 Oct 15 2014 newcerts drwx------. 2 root root 4096 Oct 15 2014 private -rw-r--r--. 1 root root 3 Jul 9 12:58 serial # 2、生成密钥 # (umask 077; openssl genrsa -out /etc/pki/CA/private/cakey.pem 2048) [[email protected] CA]# (umask 077; openssl genrsa -out private/cakey.pem 2048) Generating RSA private key, 2048 bit long modulus ...................................................+++ ............................................................+++ e is 65537 (0x10001) [[email protected] CA]# ls private/ cakey.pem [[email protected] CA]# cat private/cakey.pem -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEA1bZFGHP+9o0mntc6ActIvSKwZMdSH/axlPHtk1S61FwGMBh0 vc0eUhm0AbFi+ftrOhvVKWPPy6Lv1A6z/fwMwOW/318PMimyKDE0K6UxNF/sfDHC y6u68e4syUu6X4MKzPgy2plIjV+1iLvbWjwwDstkRXH93s9gBvihMnu5R0KL4Usp rLF54ZyZigy0ADxBdL3fObljM0KPRxrd5B0foLkEnm8vb1CUyPhgMIdh3PFsFKA3 3hUDQg4JpUilSRO3T/yt5zaJFZVwirYwHQsPwVhKGGxxB+6N2wcRV59lziMRx9v/ u5NmyfJnn21xLWzyMeoi6tZBXW93jLkvsyR3JQIDAQABAoIBAQCaEp4d0wKtnXWK boBTass2EBw7i7eZc7DzQLeW0C8hinarlfYUIB0L85vi3JAOyUO00PwMqvjURtPA fhklsuE+8GQ0FcRO1eCrOU3zaVTf/Yfwwa8+RsCwSpXfSclDsqXGv+lpz7iOs8Gc olKx61J6WAgiSNxOFhOU8wrD6o7Y37/DSDLcPDWdJd+YrgYBouLIwWD46w6aDr1N QjX1MkBs2qwdUHhb+ma4wiyhBCPkQMiaLsi0Y+ZpBjGwDUWKVtdvB8fNNME7ls/D nm+4NhVi9Tnt9DZP11+KtrSbEZcY4uuyUMdp8zA8ReW5OxxSChwSRL2Bx5sKdWUF nPmul7jBAoGBAO7IRp7R971sollb6WGel5poCvqw6EPvfcKydjgDC+My+TosxK8b zTy0rKL/d6isKQc+SDFYS9qpj6AbTvQVp7Y7JGSfAXyNpb8xs1C2lrI6RGYX0gWu 37JI339sGx636+EMKykSivV/leByG4cG7gVastEat4KIk3cSk4Y53GXnAoGBAOUf N2WjxKY2lYhm7w3PbuE+Q4cy1yZYgJ6n5CznhlNoJAtVKbvQ2qC1qs93XTLyVu6H 2RfuLkTfr5hRi3ocS3w8/L8RnDhlISHRFrT42FVqldupqWTS9XXe17sWvgCi8sQU kZOtIwBryoda6knJWrLG6efBAhFZwU2/DliHJQETAoGBAMgMbm38xyuh6donkL1C Wwz3gctJjy3rZVdKoJSIqNruB7NfcmCqUCY90Cy3Dw73PWBeI6mDqflF+ZhPiLQh uGKJ5hGOzXYGTgiCoRJMBrDG9Cr8Ze5w9eSt/OEKNyZjPHFM+pPsfxLykyR5NOrJ OXyu4gUh9wCbX8Bwhbv8mdOdAoGANI9Wq/BHmkGHSAUk7awaKX2ZDBizlk5TIxIs m8h43gVTz2235yfgH2HNT054iMli+9EaEg1He/E8XNrH/jkjb9qluEcX6S/5y8Il TVqQdfe/bOacv05NlL6MCpUK/SZkPmrhglkDYINZsHdAq7CPJ9fNrKZwDP7kAyvC 5LgL2xUCgYBrjlidSko0KiXFf29rTnbs6KuKvX931MKxSnGIbGN31ckYcjdk0cOC ituFk60AYQl+scj1ifF7ZACPDNqecKa0farSo/8UDH1VFhMGQneTMQz8Wqryn+xe z1WlwGBgCODXzTb/c930YW/3+T7N2PW7hCj7IG6kMs3Y5bJ9+Kdivg== -----END RSA PRIVATE KEY----- # 3、生成自签证书 # openssl req -new -x509 -key /etc/pki/CA/private/cakey.pem -days 7300 -out /etc/pki/CA/cacert.pem req: 生成证书签署请求 -news: 新请求 -key /path/to/keyfile: 指定私钥文件 -out /path/to/somefile: -x509: 生成自签署证书 -days n: 有效天数 [[email protected] CA]# whatis req #从私钥中提取公钥 req (1ssl) - PKCS#10 certificate request and certificate generating utility [[email protected] CA]# openssl req -new -x509 -key /etc/pki/CA/private/cakey.pem -days 7300 -out /etc/pki/CA/cacert.pem You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, If you enter ‘.‘, the field will be left blank. ----- Country Name (2 letter code) [XX]:CN State or Province Name (full name) []:BJ Locality Name (eg, city) [Default City]:beijing Organization Name (eg, company) [Default Company Ltd]:ICBC Organizational Unit Name (eg, section) []:wl2 Common Name (eg, your name or your server‘s hostname) []:www.icbc.com.cn Email Address []:[email protected] [[email protected] CA]#
二、节点申请证书: (一) 节点生成请求 1、生成密钥对儿 # (umask 077; openssl genrsa -out /etc/httpd/ssl/httpd.key 2048) 2、生成证书签署请求 # openssl req -new -key /etc/httpd/ssl/httpd.key -out /etc/httpd/ssl/httpd.csr 3、把签署请求文件发送给CA服务 # scp (二) CA签署证书 1、验正证书中的信息; 2、签署证书 # openssl ca -in /path/to/somefile.csr -out /path/to/somefile.crt -days N 3、发送给请求者; 三、吊销证书 (一)节点 1、获取证书serial # openssl x509 -in /path/to/certificate_file.crt -noout -serial -subject (二) CA 2、根据节点提交的serial和subject信息来验正与index.txt文件中的信息是否一致; 3、吊销证书 # openssl ca -revoke /etc/pki/CA/newcerts/SERIAL.pem 4、生成吊销证书的编号(如果是第一次吊销) # echo 00 > /etc/pki/CA/crlnumber 5、更新证书吊销列表 # cd /etc/pki/CA/crl/ # openssl ca -gencrl -out thisca.crl 如果需要,查看crl文件的内容: # openssl crl -in /path/to/crlfile.crl -noout -text
以上是关于linux-openssl命令行的主要内容,如果未能解决你的问题,请参考以下文章