This is an automated email from the ASF dual-hosted git repository.

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new 6860a90  Typo in CSR generation docs (#2530) (#2531)
6860a90 is described below

commit 6860a90bc685003afef17ab8bfa33e2701c99bfe
Author: Ivan Kelly <[email protected]>
AuthorDate: Thu Sep 6 19:56:52 2018 +0200

    Typo in CSR generation docs (#2530) (#2531)
    
    The output file for CSR generation was .cert.pem rather than .csr.pem,
    which causes confusion. It should be .csr.pem
---
 site2/docs/security-tls-authentication.md                               | 2 +-
 site2/docs/security-tls-transport.md                                    | 2 +-
 .../version-2.1.0-incubating/security-tls-authentication.md             | 2 +-
 .../versioned_docs/version-2.1.0-incubating/security-tls-transport.md   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/site2/docs/security-tls-authentication.md 
b/site2/docs/security-tls-authentication.md
index d5eb7d7..10578d2 100644
--- a/site2/docs/security-tls-authentication.md
+++ b/site2/docs/security-tls-authentication.md
@@ -30,7 +30,7 @@ Generate the certificate request. When asked for a **common 
name**, enter the **
 
 ```bash
 $ openssl req -config openssl.cnf \
-      -key admin.key.pem -new -sha256 -out admin.cert.pem
+      -key admin.key.pem -new -sha256 -out admin.csr.pem
 ```
 
 Sign with request with the certificate authority. Note that that client certs 
uses the **usr_cert** extension, which allows the cert to be used for client 
authentication.
diff --git a/site2/docs/security-tls-transport.md 
b/site2/docs/security-tls-transport.md
index 70db61f..460d2d0 100644
--- a/site2/docs/security-tls-transport.md
+++ b/site2/docs/security-tls-transport.md
@@ -96,7 +96,7 @@ Generate the certificate request...
 
 ```bash
 $ openssl req -config openssl.cnf \
-      -key broker.key.pem -new -sha256 -out broker.cert.pem
+      -key broker.key.pem -new -sha256 -out broker.csr.pem
 ```
 
 ... and sign it with the certificate authority.
diff --git 
a/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-authentication.md
 
b/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-authentication.md
index a9af2b7..121ab17 100644
--- 
a/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-authentication.md
+++ 
b/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-authentication.md
@@ -31,7 +31,7 @@ Generate the certificate request. When asked for a **common 
name**, enter the **
 
 ```bash
 $ openssl req -config openssl.cnf \
-      -key admin.key.pem -new -sha256 -out admin.cert.pem
+      -key admin.key.pem -new -sha256 -out admin.csr.pem
 ```
 
 Sign with request with the certificate authority. Note that that client certs 
uses the **usr_cert** extension, which allows the cert to be used for client 
authentication.
diff --git 
a/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-transport.md
 
b/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-transport.md
index 9924ed5..6981b8f 100644
--- 
a/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-transport.md
+++ 
b/site2/website/versioned_docs/version-2.1.0-incubating/security-tls-transport.md
@@ -97,7 +97,7 @@ Generate the certificate request...
 
 ```bash
 $ openssl req -config openssl.cnf \
-      -key broker.key.pem -new -sha256 -out broker.cert.pem
+      -key broker.key.pem -new -sha256 -out broker.csr.pem
 ```
 
 ... and sign it with the certificate authority.

Reply via email to