kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ewe...@apache.org
Subject kafka git commit: MINOR: Fixed misleading reference to HTTPS instead of SSL support in the doc
Date Fri, 21 Jul 2017 03:16:21 GMT
Repository: kafka
Updated Branches:
  refs/heads/trunk 8a8156621 -> 1d2d0bac9


MINOR: Fixed misleading reference to HTTPS instead of SSL support in the doc

Author: ppatierno <ppatierno@live.com>

Reviewers: Ewen Cheslack-Postava <ewen@confluent.io>

Closes #3487 from ppatierno/ssl-doc-https


Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/1d2d0bac
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/1d2d0bac
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/1d2d0bac

Branch: refs/heads/trunk
Commit: 1d2d0bac9ea61de38b1afa6ab301a0a9a05f5758
Parents: 8a81566
Author: ppatierno <ppatierno@live.com>
Authored: Thu Jul 20 20:16:15 2017 -0700
Committer: Ewen Cheslack-Postava <me@ewencp.org>
Committed: Thu Jul 20 20:16:15 2017 -0700

----------------------------------------------------------------------
 docs/security.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/1d2d0bac/docs/security.html
----------------------------------------------------------------------
diff --git a/docs/security.html b/docs/security.html
index 5e2b202..dab00dd 100644
--- a/docs/security.html
+++ b/docs/security.html
@@ -40,7 +40,7 @@
 
     <ol>
         <li><h4><a id="security_ssl_key" href="#security_ssl_key">Generate
SSL key and certificate for each Kafka broker</a></h4>
-            The first step of deploying HTTPS is to generate the key and the certificate
for each machine in the cluster. You can use Java's keytool utility to accomplish this task.
+            The first step of deploying one or more brokers with the SSL support is to generate
the key and the certificate for each machine in the cluster. You can use Java's keytool utility
to accomplish this task.
             We will generate the key into a temporary keystore initially so that we can export
and sign it later with CA.
             <pre class="brush: bash;">
             keytool -keystore server.keystore.jks -alias localhost -validity {validity} -genkey
-keyalg RSA</pre>


Mime
View raw message