Skip to content

Commit

Permalink
doc: remove statement about client private keys
Browse files Browse the repository at this point in the history
This statement was objectively false. Clients usually only need to
generate and/or own a private key if the server sends a
CertificateRequest during the TLS handshake, which is not a common case.

PR-URL: #41505
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
  • Loading branch information
tniessen authored and targos committed Jan 16, 2022
1 parent ba7160e commit 48e4780
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/api/tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ const tls = require('tls');
## TLS/SSL concepts

The TLS/SSL is a public/private key infrastructure (PKI). For most common
cases, each client and server must have a _private key_.
cases, each server must have a _private key_.

Private keys can be generated in multiple ways. The example below illustrates
use of the OpenSSL command-line interface to generate a 2048-bit RSA private
Expand Down

0 comments on commit 48e4780

Please sign in to comment.