Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 48e4780

Browse filesBrowse files
tniessentargos
tniessen
authored and
targos
committed
doc: remove statement about client private keys
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>
1 parent ba7160e commit 48e4780
Copy full SHA for 48e4780

File tree

Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Open diff view settings
Collapse file

‎doc/api/tls.md‎

Copy file name to clipboardExpand all lines: doc/api/tls.md
+1-1Lines changed: 1 addition & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ const tls = require('tls');
1717
## TLS/SSL concepts
1818

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

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

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.