summaryrefslogtreecommitdiff
path: root/docs/auth-framework.rst
diff options
context:
space:
mode:
authorSoby Mathew <soby.mathew@arm.com>2019-04-26 12:40:04 +0000
committerTrustedFirmware Code Review <review@review.trustedfirmware.org>2019-04-26 12:40:04 +0000
commit28dab587e94552966b01c30b4e8d51463036d0f7 (patch)
tree8f3991ccfbde1626d513fcf0bdbd306bb1039ef8 /docs/auth-framework.rst
parentc3e4e0888d92f5e82fdd626e2eb5fdee3892bb2a (diff)
parentc1491ebaa76018965e3fea0c695705f48d26dfbf (diff)
Merge "Doc: Update link to TBBR-CLIENT specification" into integration
Diffstat (limited to 'docs/auth-framework.rst')
-rw-r--r--docs/auth-framework.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/auth-framework.rst b/docs/auth-framework.rst
index 317ac189..0142fbd3 100644
--- a/docs/auth-framework.rst
+++ b/docs/auth-framework.rst
@@ -80,7 +80,7 @@ Chain of Trust
A CoT is basically a sequence of authentication images which usually starts with
a root of trust and culminates in a single data image. The following diagram
illustrates how this maps to a CoT for the BL31 image described in the
-TBBR-Client specification.
+`TBBR-Client specification`_.
::
@@ -969,3 +969,4 @@ of SHA-256 with smaller memory footprint (~1.5 KB less) but slower (~30%).
.. _Trusted Board Boot: ./trusted-board-boot.rst
.. _Platform Porting Guide: ./porting-guide.rst
+.. _TBBR-Client specification: https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a