最新国产好看的视频,伊人天堂AV在线,国产Aaaaaa视频,蜜臀视频在线观看一区,人妻av色图,密臀久久久精品影片,青青视频免费观看毛片,久草在线观看视,国产三级精品色情在线

OpenSSL生成v3證書方法及配置文件詳解

 更新時間:2022年07月18日 08:55:59   作者:時空無限  
本文主要介紹了OpenSSL生成v3證書方法及配置文件詳解,文中通過示例代碼介紹的非常詳細,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧

場景

業(yè)務需要生成v3版的證書,而一般使用OpenSSL生成證書時都是v1版的,不帶擴展屬性。

方法

在使用CA證書進行簽署證書時加入-exfile和-extensions選項,具體命令如下:

openssl x509 -req  -days 365 -sha256 -extfile openssl.cnf -extensions v3_req   -in server.csr -signkey server.key -out server.crt

對應openssl.cnf配置文件

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_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 = 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 ?= 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 (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 ?= CN
countryName_min ? = 2
countryName_max ? = 2

stateOrProvinceName ?= State or Province Name (full name)
stateOrProvinceName_default = BeiJing

localityName ? = Locality Name (eg, city)

0.organizationName ?= Organization Name (eg, company)
0.organizationName_default = myca

# 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 (e.g. server FQDN or 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

# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping

[ svr_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.
# ?digitalSignature nonRepudiation keyEncipherment dataEncipherment ?
# ?keyAgreement keyCertSign cRLSign encipherOnly decipherOnly?
keyUsage = nonRepudiation, digitalSignature, keyEncipherment, dataEncipherment, keyAgreement

# 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 = serverAuth,clientAuth

[ 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)

到此這篇關于OpenSSL生成v3證書方法及配置文件詳解的文章就介紹到這了,更多相關OpenSSL生成v3證書內容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關文章希望大家以后多多支持腳本之家!

相關文章

  • 2018年最值得一讀的互聯網書單

    2018年最值得一讀的互聯網書單

    2018年已經過去了近三分之二了,是不是感覺時光匆匆、一去不復返,過去的時間我們追不回,但是我們可以更加珍惜以后的時間!下面這篇文章主要給大家分享了2018年最值得一讀的互聯網書單,希望以后的日子里大家可以多讀書,讀好書
    2018-08-08
  • Spark在Windows下的環(huán)境搭建方法

    Spark在Windows下的環(huán)境搭建方法

    這篇文章主要介紹了Spark在Windows下的環(huán)境搭建方法,文中通過示例代碼介紹的非常詳細,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧
    2019-06-06
  • 使用Git向GitHub上傳更新內容

    使用Git向GitHub上傳更新內容

    這篇文章介紹了使用Git向GitHub上傳更新內容的方法,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧
    2022-04-04
  • MobaXterm的安裝和使用及問題小結

    MobaXterm的安裝和使用及問題小結

    MobaXterm是一款全能的終端連接工具,支持SSH連接,支持FTP、串口等協(xié)議。接下來通過本文給大家分享MobaXterm的安裝和使用及遇到的問題解決方法,感興趣的朋友跟隨小編一起看看吧
    2021-05-05
  • chatgpt-api使用指南詳解教程【官方泄露版】

    chatgpt-api使用指南詳解教程【官方泄露版】

    chatgpt-api是?OpenAI?ChatGPT?的非官方的?Node.js?包裝器,?chatgpt-api不再需要任何瀏覽器破解它使用泄露出來的OpenAI官方ChatGPT?在后臺使用的模型,這篇文章主要介紹了chatgpt-api使用指南【官方泄露版】,需要的朋友可以參考下
    2023-02-02
  • win10環(huán)境安裝kettle與linux環(huán)境安裝kettle的詳細過程

    win10環(huán)境安裝kettle與linux環(huán)境安裝kettle的詳細過程

    kettle是一款免費開源的、可視化的、國際上比較流行的、功能強大的ETL必備工具,在ETL這一方面做的還不錯,下面介紹一下基于win10操作系統(tǒng)安裝kettle和linux操作系統(tǒng)安裝kettle的詳細過程,感興趣的朋友跟隨小編一起看看吧
    2022-11-11
  • AERGO SHIP:用于開發(fā)智能合約的包管理器

    AERGO SHIP:用于開發(fā)智能合約的包管理器

    AERGO SHIP:用于開發(fā)智能合約的包管理器,用于構建、測試和部署分布式應用程序的客戶端框架和開發(fā)環(huán)境
    2018-11-11
  • 網絡編程基礎(局域網、ip、子網掩碼、網關、DNS)概念理解

    網絡編程基礎(局域網、ip、子網掩碼、網關、DNS)概念理解

    這篇文章主要介紹了網絡編程基礎(局域網、ip、子網掩碼、網關、DNS)概念理解,包括局域網的構成、IP地址的分類和作用、子網掩碼的作用以及網絡通信規(guī)則等
    2025-02-02
  • 圖像檢索之IF-IDF,RootSift,VLAD

    圖像檢索之IF-IDF,RootSift,VLAD

    TF-IDF是一種用于信息檢索的常用加權技術,在文本檢索中,用以評估詞語對于一個文件數據庫中的其中一份文件的重要程度,本文給大家介紹下圖像檢索之IF-IDF,RootSift,VLAD的相關知識,感興趣的朋友一起看看吧
    2021-12-12
  • 深入探究ChatGPT的工作原理

    深入探究ChatGPT的工作原理

    這篇文章主要探討了ChatGPT的工作原理,ChatGPT是基于OpenAI開發(fā)的GPT-4架構的大型語言模型,文中圖文介紹的非常詳細,感興趣的同學跟著小編一起來學習吧
    2023-06-06

最新評論

伊春市| 榆中县| 吉木乃县| 故城县| 莱西市| 江永县| 巩义市| 鹰潭市| 中西区| 上犹县| 平昌县| 浦城县| 仁怀市| 汾西县| 福清市| 洞口县| 泾源县| 江门市| 涞水县| 黔江区| 拜泉县| 顺昌县| 泰兴市| 昔阳县| 绥德县| 河北区| 巴林右旗| 沿河| 鄂伦春自治旗| 沧州市| 灌云县| 榆中县| 宜春市| 邮箱| 哈密市| 泰安市| 龙游县| 古浪县| 常宁市| 白玉县| 潞西市|