Skip to content

Commit 1d274a5

Browse files
committed
Find/replace error
1 parent 1739f03 commit 1d274a5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

explainer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The remainder of this section discusses what this problem statement means, and w
2525

2626
### Background
2727

28-
[TLS](https://www.rfc-editor.org/rfc/rfc8446) uses [X.509 certificates](https://www.rfc-editor.org/rfc/rfc5280) to associate a TLS endpoint's DNS names, or other application identifiers, with its TLS key. These associations are signed by certificate authorities (CAs) and are presented to the peer, known as the *relying party*. Each relying party curates a set of CAs, called *trust anchors*, whose associations the relying party accepts. If the relying party's trust anchors can be trusted to only issue correct associations, the relying party can use TLS to securely connect to the authenticating party, known as the *authenticating party*. The common case in TLS is server certificate authentication, where the authenticating party is the server, and the relying party is the client. The roles are reversed with client certificates. For clarity, this document will primarily discuss the server certificate case, but most of the motivations and solutions apply analogously to client certificates.
28+
[TLS](https://www.rfc-editor.org/rfc/rfc8446) uses [X.509 certificates](https://www.rfc-editor.org/rfc/rfc5280) to associate a TLS endpoint's DNS names, or other application identifiers, with its TLS key. These associations are signed by certificate authorities (CAs) and are presented to the peer, known as the *relying party*. Each relying party curates a set of CAs, called *trust anchors*, whose associations the relying party accepts. If the relying party's trust anchors can be trusted to only issue correct associations, the relying party can use TLS to securely connect to the *authenticating party*. The common case in TLS is server certificate authentication, where the authenticating party is the server, and the relying party is the client. The roles are reversed with client certificates. For clarity, this document will primarily discuss the server certificate case, but most of the motivations and solutions apply analogously to client certificates.
2929

3030
In this system, the client's trust anchors directly impact service availability and user security:
3131

0 commit comments

Comments
 (0)