<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Techy Things &#187; openssl</title>
	<atom:link href="https://tech.yipp.ca/category/openssl/feed/" rel="self" type="application/rss+xml" />
	<link>https://tech.yipp.ca</link>
	<description>Just another Yipp.ca Blogs site</description>
	<lastBuildDate>Thu, 01 May 2025 18:06:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.38</generator>
	<item>
		<title>TXT_DB error number 2</title>
		<link>https://tech.yipp.ca/openssl/txt_db-error-number-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=txt_db-error-number-2</link>
		<comments>https://tech.yipp.ca/openssl/txt_db-error-number-2/#comments</comments>
		<pubDate>Tue, 26 Jul 2016 17:58:11 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2516</guid>
		<description><![CDATA[<p>TXT_DB error number 2 Solution, edit your CA config to allow dupplicate commonName unique_subject = no</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/txt_db-error-number-2/">TXT_DB error number 2</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>TXT_DB error number 2</p>
<p>Solution, edit your CA config to allow dupplicate commonName</p>
<p>unique_subject = no</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/txt_db-error-number-2/">TXT_DB error number 2</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/txt_db-error-number-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a P7B certificates bundle</title>
		<link>https://tech.yipp.ca/openssl/create-p7b-certificates-bundle/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-p7b-certificates-bundle</link>
		<comments>https://tech.yipp.ca/openssl/create-p7b-certificates-bundle/#comments</comments>
		<pubDate>Sat, 18 Jun 2016 05:11:48 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2460</guid>
		<description><![CDATA[<p>P7B certificates file can contain one or more certificates and a revocation list. The difference with P12 (PKCS#12), P7B (PKCS#7) cannot contain private keys. To create a P7B file Assuming you have frank.pem and&#46;&#46;&#46;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-p7b-certificates-bundle/">Create a P7B certificates bundle</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>P7B certificates file can contain one or more certificates and a revocation list. The difference with P12 (PKCS#12), P7B (PKCS#7) cannot contain private keys.</p>
<h2>To create a P7B file</h2>
<p>Assuming you have frank.pem and intermediate-cert.pem</p>
<p>$&gt; openssl crl2pkcs7 -nocrl -certfile frank.pem -certfile intermediate-cert.pem -out frank-bundle.p7b</p>
<p>You then have a fresh new P7B file !</p>
<h2>Extract certificates from the P7B file</h2>
<p>This is more complex and is a three step process</p>
<p>$&gt; openssl pkcs7 -in frank-bundle.p7b -out frank-bundle-p7b.crt</p>
<p>Then use a regexp to change the delimiters</p>
<p>data = data.replace(/-----BEGIN PKCS7.*?-----/, "-----BEGIN CERTIFICATE-----");<br />
data = data.replace(/-----END PKCS7.*?-----/, "-----END CERTIFICATE-----");</p>
<p>Then finish him with</p>
<p>$&gt; openssl pkcs7 -in frank-bundle-p7b.crt -print_certs -out frank-bundle.crt</p>
<p>&nbsp;</p>
<h2>Possible options for extraction</h2>
<p>Usage: pkcs7 [options] &lt;infile &gt;outfile'<br />
'where options are',<br />
'-inform arg input format - DER or PEM',<br />
'-outform arg output format - DER or PEM',<br />
'-in arg input file',<br />
'-out arg output file',<br />
'-print_certs print any certs or crl in the input',<br />
'-text print full details of certificates',<br />
'-noout don\'t output encoded data',<br />
'-engine e use engine e, possibly a hardware device.'</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-p7b-certificates-bundle/">Create a P7B certificates bundle</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/create-p7b-certificates-bundle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a DER encoded X509 certificate</title>
		<link>https://tech.yipp.ca/openssl/create-der-encoded-x509-certificate/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-der-encoded-x509-certificate</link>
		<comments>https://tech.yipp.ca/openssl/create-der-encoded-x509-certificate/#comments</comments>
		<pubDate>Fri, 17 Jun 2016 18:34:20 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2457</guid>
		<description><![CDATA[<p>Two types of X509 certificates There are base64 encoded certificates which look like -----BEGIN CERTIFICATE----- MIIFcDCCA1gCAhAAMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkdCMRAwDgYD (...) lcH2kxKqa1CWUQGz3S9raNtesOI7jbO9d2HRVPPTPVTliHukS8tlBouq5tU6IFgH I61lVg== -----END CERTIFICATE----- Then there are DER encoded certificates which look like To convert base64 to&#46;&#46;&#46;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-der-encoded-x509-certificate/">Create a DER encoded X509 certificate</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<h2>Two types of X509 certificates</h2>
<p>There are <span style="color: #ff6600;"><strong>base64</strong> </span>encoded certificates which look like</p>
<pre>-----BEGIN CERTIFICATE-----
 MIIFcDCCA1gCAhAAMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkdCMRAwDgYD
 (...)
 lcH2kxKqa1CWUQGz3S9raNtesOI7jbO9d2HRVPPTPVTliHukS8tlBouq5tU6IFgH
 I61lVg==
 -----END CERTIFICATE-----</pre>
<p>Then there are DER encoded certificates which look like</p>
<h2>To convert base64 to DER</h2>
<pre>openssl x509 -outform der -in <u>certificate.crt</u> -out <u>certificate.der</u></pre>
<p>&nbsp;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-der-encoded-x509-certificate/">Create a DER encoded X509 certificate</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/create-der-encoded-x509-certificate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create an intermediate CA</title>
		<link>https://tech.yipp.ca/openssl/create-intermediate-ca/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-intermediate-ca</link>
		<comments>https://tech.yipp.ca/openssl/create-intermediate-ca/#comments</comments>
		<pubDate>Tue, 07 Jun 2016 21:21:25 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2434</guid>
		<description><![CDATA[<p>First step is required. If you don't I wrote the instructions to setup a root CA. 1. Create folders (you are free to choose where) and add basic files: cd /etc/pki/tls/ mkdir intermediate-ca cd intermediate-ca&#46;&#46;&#46;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-intermediate-ca/">Create an intermediate CA</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>First step is required. If you don't I wrote the <a href="http://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/">instructions to setup a root CA</a>.</p>
<p>1. Create folders (you are free to choose where) and add basic files:</p>
<pre>cd /etc/pki/tls/
mkdir intermediate-ca
cd intermediate-ca
mkdir certs crl csr newcerts private conf
chmod 700 private
touch conf/index
echo 1000 &gt; conf/serial
echo 1000 &gt; conf/crlnumber

2. Create a new openssl.cnf file with content:

[ ca ]
# `man ca`
default_ca = CA_default

[ CA_default ]
# Directory and file locations.
dir = /etc/pki/tls/intermediate-ca
certs = $dir/certs
crl_dir = $dir/crl
new_certs_dir = $dir/newcerts
database = $dir/conf/index
serial = $dir/conf/serial
RANDFILE = $dir/private/.rand

# The root key and root certificate.
private_key = $dir/private/intermediate.key.pem
certificate = $dir/certs/intermediate.cert.pem

# For certificate revocation lists.
crlnumber = $dir/conf/crlnumber
crl = $dir/crl/intermediate.crl.pem
crl_extensions = crl_ext
default_crl_days = 30

# SHA-1 is deprecated, so use SHA-2 instead.
default_md = sha256

name_opt = ca_default
cert_opt = ca_default
default_days = 375
preserve = no
policy = policy_loose

[ policy_strict ]
# The root CA should only sign intermediate certificates that match.
# See the POLICY FORMAT section of `man ca`.
countryName = match
stateOrProvinceName = match
organizationName = match
organizationalUnitName = optional
commonName = supplied
emailAddress = optional

[ policy_loose ]
# Allow the intermediate CA to sign a more diverse range of certificates.
# See the POLICY FORMAT section of the `ca` man page.
countryName = optional
stateOrProvinceName = optional
localityName = optional
organizationName = optional
organizationalUnitName = optional
commonName = supplied
emailAddress = optional

[ req ]
# Options for the `req` tool (`man req`).
default_bits = 2048
distinguished_name = req_distinguished_name
string_mask = utf8only

# SHA-1 is deprecated, so use SHA-2 instead.
default_md = sha256

# Extension to add when the -x509 option is used.
x509_extensions = v3_ca

[ req_distinguished_name ]
# See &lt;https://en.wikipedia.org/wiki/Certificate_signing_request&gt;.
countryName = Country Name (2 letter code)
stateOrProvinceName = State or Province Name
localityName = Locality Name
0.organizationName = Organization Name
organizationalUnitName = Organizational Unit Name
commonName = Common Name
emailAddress = Email Address

# Optionally, specify some defaults.
countryName_default = GB
stateOrProvinceName_default = England
localityName_default =
0.organizationName_default = Alice Ltd
organizationalUnitName_default =
emailAddress_default =

[ v3_ca ]
# Extensions for a typical CA (`man x509v3_config`).
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints = critical, CA:true
keyUsage = critical, digitalSignature, cRLSign, keyCertSign

[ v3_intermediate_ca ]
# Extensions for a typical intermediate CA (`man x509v3_config`).
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints = critical, CA:true, pathlen:0
keyUsage = critical, digitalSignature, cRLSign, keyCertSign

[ usr_cert ]
# Extensions for client certificates (`man x509v3_config`).
basicConstraints = CA:FALSE
nsCertType = client, email
nsComment = "OpenSSL Generated Client Certificate"
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid,issuer
keyUsage = critical, nonRepudiation, digitalSignature, keyEncipherment
extendedKeyUsage = clientAuth, emailProtection

[ server_cert ]
# Extensions for server certificates (`man x509v3_config`).
basicConstraints = CA:FALSE
nsCertType = server
nsComment = "OpenSSL Generated Server Certificate"
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid,issuer:always
keyUsage = critical, digitalSignature, keyEncipherment
extendedKeyUsage = serverAuth

[ crl_ext ]
# Extension for CRLs (`man x509v3_config`).
authorityKeyIdentifier=keyid:always

[ ocsp ]
# Extension for OCSP signing certificates (`man ocsp`).
basicConstraints = CA:FALSE
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid,issuer
keyUsage = critical, digitalSignature
extendedKeyUsage = critical, OCSPSigning


Create intermediate private key
$&gt; openssl genrsa -aes256 -out intermediate-ca/private/intermediate.key.pem 4096

Enter pass phrase for intermediate.key.pem: secretpassword
Verifying - Enter pass phrase for intermediate.key.pem: secretpassword

$&gt; chmod 400 intermediate-ca/private/intermediate.key.pem

Use the intermediate key to create a certificate signing request (CSR).
The details should generally match the root CA. 
The Common Name, however, must be different.

Create the intermediate code signing request

cd /etc/pki/tls/intermediate-ca
# openssl req -config conf/openssl.cnf -new -sha256 -key private/intermediate.key.pem -out csr/intermediate.csr.pem

Enter pass phrase for intermediate.key.pem: secretpassword
You are about to be asked to enter information that will be incorporated
into your certificate request.
-----
Country Name (2 letter code) [XX]:GB
State or Province Name []:England
Locality Name []:
Organization Name []:Alice Ltd
Organizational Unit Name []:Alice Ltd Certificate Authority
Common Name []:Alice Ltd Intermediate CA
Email Address []:

From the root CA, sign the intermediate CSR

Login on root CA (or cd to its directory if on same computer)

# cd /etc/pki/tls/root-ca
# openssl ca -config conf/openssl.cnf -extensions v3_intermediate_ca -days 3650 -notext -md sha256 -in intermediate.csr.pem -out certs/intermediate.cert.pem

Enter pass phrase for ca.key.pem: secretpassword
Sign the certificate? [y/n]: y

chmod 444 certs/intermediate.cert.pem

Verify the intermediate certificate against the root certificate. An OK indicates that the chain of trust is intact.

# openssl verify -CAfile certs/ca.cert.pem certs/intermediate.cert.pem
intermediate.cert.pem: OK

You can now sign code signing request (CSR) from clients on the intermediate CA:

$&gt; cd intermediate-ca
$&gt; openssl ca -batch -config conf/openssl.cnf -in ~/frank-csr-623.csr -out frank-623-signed.cert

</pre>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-intermediate-ca/">Create an intermediate CA</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/create-intermediate-ca/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenSSL add password to private key</title>
		<link>https://tech.yipp.ca/openssl/openssl-add-password-private-key/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=openssl-add-password-private-key</link>
		<comments>https://tech.yipp.ca/openssl/openssl-add-password-private-key/#comments</comments>
		<pubDate>Wed, 25 May 2016 21:45:44 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2425</guid>
		<description><![CDATA[<p>openssl pkey -des3 -in /etc/pki/tls/private/localhost.key -passout pass:WE213JDZO324IEKRWDO -out /etc/pki/tls/private/password-protected.key &#160;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/openssl-add-password-private-key/">OpenSSL add password to private key</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>openssl pkey -des3 -in /etc/pki/tls/private/localhost.key -passout pass:WE213JDZO324IEKRWDO -out /etc/pki/tls/private/password-protected.key</p>
<p>&nbsp;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/openssl-add-password-private-key/">OpenSSL add password to private key</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/openssl-add-password-private-key/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to install a CA signed SSL certificate</title>
		<link>https://tech.yipp.ca/openssl/install-ca-signed-ssl-certificate/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=install-ca-signed-ssl-certificate</link>
		<comments>https://tech.yipp.ca/openssl/install-ca-signed-ssl-certificate/#comments</comments>
		<pubDate>Tue, 17 May 2016 17:40:52 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2413</guid>
		<description><![CDATA[<p>Apache (...) SSLEngine on SSLCertificateFile /path/to/website.crt SSLCertificateKeyFile /path/to/private.key SSLCACertificateFile /path/to/root_bundle.crt What is the use of you might say ? It is primary the same as SSLCertificateChainFile but it also permits the use of the&#46;&#46;&#46;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/install-ca-signed-ssl-certificate/">How to install a CA signed SSL certificate</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<h2>Apache</h2>
<p><VirtualHost><br />
(...)<br />
SSLEngine on<br />
SSLCertificateFile /path/to/website.crt<br />
SSLCertificateKeyFile /path/to/private.key<br />
SSLCACertificateFile /path/to/root_bundle.crt<br />
</VirtualHost></p>
<p>What is the use of you might say ? It is primary the same as SSLCertificateChainFile but it also permits the use of the certificate in question to sign client certificates. That file "root_bundle.crt" will be sent along with the certificate to any clients that connect.<br />
&nbsp;</p>
<h2>Nginx</h2>
<p>&nbsp;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/install-ca-signed-ssl-certificate/">How to install a CA signed SSL certificate</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/install-ca-signed-ssl-certificate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create your own CA certificate authority to sign SSL</title>
		<link>https://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=create-ca-certificate-authority-sign-ssl</link>
		<comments>https://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/#comments</comments>
		<pubDate>Tue, 17 May 2016 02:57:49 +0000</pubDate>
		<dc:creator><![CDATA[frank]]></dc:creator>
				<category><![CDATA[openssl]]></category>

		<guid isPermaLink="false">http://tech.yipp.ca/?p=2411</guid>
		<description><![CDATA[<p>mkdir -p root-ca/{conf,private,public} chmod 600 root-ca/private/ cd root-ca/ mkdir signed-keys echo "01" &#62; conf/serial touch conf/index Create a new file in root-ca/conf/openssl.cnf with the following content [ req ]default_bits            = 2048 default_keyfile         = ./private/root.pem&#46;&#46;&#46;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/">Create your own CA certificate authority to sign SSL</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>mkdir -p root-ca/{conf,private,public}<br />
chmod 600 root-ca/private/<br />
cd root-ca/<br />
mkdir signed-keys<br />
echo "01" &gt; conf/serial<br />
touch conf/index</p>
<p>Create a new file in root-ca/conf/openssl.cnf with the following content</p>
<pre>[ req ]default_bits            = 2048
default_keyfile         = ./private/root.pem
default_md              = sha256
prompt                  = no
distinguished_name      = root_ca_distinguished_name
x509_extensions = v3_ca

[ root_ca_distinguished_name ]
countryName             = CA
stateOrProvinceName     = Quebec
localityName            = Brighton
0.organizationName      = Example Inc
commonName              = Example Inc Root CA
emailAddress            = frank@example.com

[ v3_ca ]
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer:always
basicConstraints = CA:true

[ ca ]
default_ca              = CA_default

[ CA_default ]
dir                     = .
new_certs_dir           = ./signed-keys/
database                = ./conf/index
certificate             = ./public/root.pem
serial                  = ./conf/serial
private_key             = ./private/root.pem
x509_extensions         = usr_cert
name_opt                = ca_default
cert_opt                = ca_default
default_crl_days        = 30
default_days            = 365
default_md              = sha256
preserve                = no
policy                  = policy_match

[ policy_match ]
countryName             = optional
stateOrProvinceName     = optional
organizationName        = optional
organizationalUnitName  = optional
commonName              = supplied
emailAddress            = optional

[ usr_cert ]
basicConstraints=CA:FALSE
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer:always
nsCaRevocationUrl     = https://www.example.com/example-ca-crl.pem
</pre>
<p># create root certificate CA<br />
openssl req  -nodes -config conf/openssl.cnf -days 1825 -x509 -newkey rsa:1024 -out public/root.pem -outform PEM</p>
<p>Be sure that your openssl.cnf specifies the default_md = sha256 or better. If sha1 is used, you will get errors in Chrome such as</p>
<p>Congratulation your root certificate is done! The next steps are how to process Certificate Signing Requests (.csr files).</p>
<h3>First Inspect the certificate signing request to see for which HOST it is for</h3>
<pre>
$&gt; openssl req -in ~/client.csr -noout -text
</pre>
<h3>Then sign the certificate</h3>
<pre>
$&gt; openssl ca -batch -config conf/openssl.cnf -in ~/client.csr -out client-signed.cert
</pre>
<p>All this for this !<br />
&nbsp;</p>
<p>The post <a rel="nofollow" href="https://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/">Create your own CA certificate authority to sign SSL</a> appeared first on <a rel="nofollow" href="https://tech.yipp.ca">Techy Things</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://tech.yipp.ca/openssl/create-ca-certificate-authority-sign-ssl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
