Skip to content

Commit

Permalink
Fix flow in introduction.
Browse files Browse the repository at this point in the history
  • Loading branch information
msporny committed Oct 28, 2024
1 parent a0d5358 commit f2baa07
Showing 1 changed file with 12 additions and 34 deletions.
46 changes: 12 additions & 34 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -314,43 +314,21 @@
<h2>Introduction</h2>

<p>
The use of shared secrets for [=authentication=] and [=authorization=], such as
the use of passwords, has resulted in a variety of security failures over the
past several decades. To address these security failures, systems can upgrade to
the use of
<a href="https://en.wikipedia.org/wiki/Public-key_cryptography">
asymmetric cryptography</a>, which uses digital signatures that are far more
difficult to compromise. However, one shortcoming of digital signatures is
the difficulty in disseminating the information, such as public cryptographic
keys, to those that would need to verify the security of the digital signature.
[=Controller documents=] enable the verification of proofs created by the
controller of an identifier. They provide [=verification methods=] that express
public cryptographic material, such as public keys, for verifying proofs created
by the controller of the identifier for specific purposes, such as
authentication, attestation, key agreement (for encryption), and capability
invocation and delegation. [=Controller documents=] also provide [=services=]
related to the identifier, for example to request additional information for
verification.
</p>

<p>
A [=controller document=] contains cryptographic material and identifies
service endpoints that can be used to verify proofs from, and interact
with, the [=controller=] of an identifier.
</p>
<p>
[=Controller documents=] enable the verification of proofs created
by the controller of an identifier. They provide [=verification methods=]
that express public cryptographic material, such as public keys, for
verifying proofs created by the controller of the
identifier for specific purposes, such as
authentication, attestation, key agreement (for encryption), and capability invocation
and delegation.
</p>
<p>
Controller Documents also provide [=services=] related to the identifier,
for example to request additional information for verification.
</p>
<p>
In other words, the
controller document contains the information necessary to communicate
with, and/or prove that specific actions were taken by, the controller
of an identifier,
including material for
cryptographic proofs and service endpoints for additional
communications.
In other words, the controller document contains the information necessary to
communicate with, and/or prove that specific actions were taken by, the
controller of an identifier, including material for cryptographic proofs and
service endpoints for additional communications.
</p>

<p>
Expand Down

0 comments on commit f2baa07

Please sign in to comment.