From 090c2a331f3bcc1bf2c402fcf33705df5b7ff2cb Mon Sep 17 00:00:00 2001 From: Abhisman <53483248+abs007@users.noreply.github.com> Date: Tue, 19 Apr 2022 00:13:01 +0530 Subject: [PATCH] Updated tuf-spec.md (#218) * Updated tuf-spec.md Added the full-form for the PKI acronym. * Update tuf-spec.md * Update tuf-spec.md --- tuf-spec.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tuf-spec.md b/tuf-spec.md index 1ca9b0a..81a0bec 100644 --- a/tuf-spec.md +++ b/tuf-spec.md @@ -3,7 +3,7 @@ Title: The Update Framework Specification Shortname: TUF Status: LS Abstract: A framework for securing software update systems. -Date: 2021-12-14 +Date: 2022-04-08 Editor: Justin Cappos, NYU Editor: Trishank Karthik Kuppusamy, Datadog Editor: Joshua Lock, VMware @@ -16,7 +16,7 @@ Boilerplate: copyright no, conformance no Local Boilerplate: header yes Markup Shorthands: css no, markdown yes Metadata Include: This version off, Abstract off -Text Macro: VERSION 1.0.28 +Text Macro: VERSION 1.0.29 Note: We strive to make the specification easy to implement, so if you come @@ -200,7 +200,7 @@ when a client is unable to update. + **Wrong software installation.** An attacker cannot provide a file (trusted or untrusted) that is not the one the client wanted. -### Goals for PKI ### {#goals-for-pki} +### Goals for PKI (Public key infrastructure) ### {#goals-for-pki} * Software update systems using the framework's client code interface should never have to directly manage keys.