Skip to content

Commit 3363c7a

Browse files
authored
Update reviews/tuf-graduation.md
Signed-off-by: Justin Cappos <justincappos@gmail.com>
1 parent 16f6383 commit 3363c7a

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

reviews/tuf-graduation.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,9 @@ These documents may be found here:
7171

7272
Our website has an [adoptions page](https://theupdateframework.github.io/adoptions.html) on it that lists the different projects. We also have an [ADOPTERS.MD](https://github.com/theupdateframework/tuf/blob/develop/docs/ADOPTERS.md) which contains much of the same information. [Uptane](https://uptane.github.io/), the automotive version of TUF, also its own [adoptions page](https://uptane.github.io/adoptions.html).
7373

74+
## Security Audits
75+
There are multiple [security audits](https://theupdateframework.github.io/audits.html) of TUF available on the TUF website.
76+
7477
### Alternatives to TUF
7578

7679
The most common alternative to TUF involves using either a signing key on the server (e.g., TLS) or on a server as part of software creation (e.g., GPG signing in a build farm). Either way, the fundamental difference is that a single key / server compromise can result in an attacker having the ability to install arbitrary code on end user machines. Existing specifications / proposals like OMA-DM, SUIT, ITU-T X.1373, as well as common use patterns for GPG/PGP/RSA signing and TLS all have this flaw.

0 commit comments

Comments
 (0)