Skip to content

Commit

Permalink
remove references to solution in the intro for this overview document
Browse files Browse the repository at this point in the history
Signed-off-by: Marina Moore <mnm678@gmail.com>
  • Loading branch information
mnm678 committed Jun 7, 2021
1 parent f7340ac commit eb7e969
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion key-revocation.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

One of the goals of Notary v2 is to build in solutions for key revocation that are easy to use and ensure that users will always use non-compromised keys. This document discusses some potential mechanisms for key revocation.

In existing systems, there are three main approaches to key revocation: automatic revocation through key expiration, key revocation lists, and providing a list of trusted keys. This document discusses some of the benefits and pitfalls of each of these techniques, and how some of these techniques are combined to provide a holistic approach to key revocation in TUF.
In existing systems, there are three main approaches to key revocation: automatic revocation through key expiration, key revocation lists, and providing a list of trusted keys. This document discusses some of the benefits and pitfalls of each of these techniques, and how some of these techniques are combined to provide a holistic approach to key revocation.


## Key Expiration
Expand Down

0 comments on commit eb7e969

Please sign in to comment.