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 d40fd75

Browse filesBrowse files
tniessenruyadorno
authored andcommitted
doc: improve TLS/SSL introduction
PR-URL: #41649 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
1 parent b02bf41 commit d40fd75
Copy full SHA for d40fd75

File tree

Expand file treeCollapse file tree

1 file changed

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

1 file changed

+5
-4
lines changed
Open diff view settings
Collapse file

‎doc/api/tls.md‎

Copy file name to clipboardExpand all lines: doc/api/tls.md
+5-4Lines changed: 5 additions & 4 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,9 @@ const tls = require('tls');
1616

1717
## TLS/SSL concepts
1818

19-
The TLS/SSL is a public/private key infrastructure (PKI). For most common
20-
cases, each server must have a _private key_.
19+
TLS/SSL is a set of protocols that rely on a public key infrastructure (PKI) to
20+
enable secure communication between a client and a server. For most common
21+
cases, each server must have a private key.
2122

2223
Private keys can be generated in multiple ways. The example below illustrates
2324
use of the OpenSSL command-line interface to generate a 2048-bit RSA private
@@ -129,8 +130,8 @@ servers can accommodate both, choosing either of them during the normal cipher
129130
negotiation step.
130131

131132
TLS-PSK is only a good choice where means exist to securely share a
132-
key with every connecting machine, so it does not replace PKI
133-
(Public Key Infrastructure) for the majority of TLS uses.
133+
key with every connecting machine, so it does not replace the public key
134+
infrastructure (PKI) for the majority of TLS uses.
134135
The TLS-PSK implementation in OpenSSL has seen many security flaws in
135136
recent years, mostly because it is used only by a minority of applications.
136137
Please consider all alternative solutions before switching to PSK ciphers.

0 commit comments

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