This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Trust anchors and pivots 00005 #21
Open
MikeCamel
wants to merge
6
commits into
enarx-archive:main
Choose a base branch
from
MikeCamel:trust-anchors-and-pivots-00004
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+108
−0
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
612711d
initial template (from 00003) - all TODO
MikeCamel 0dcebc7
First draft of trust pivot intro
MikeCamel 9a160b3
Update and rename rfc#00005-trust-pivot-introduction to rfc#00006-tru…
MikeCamel edc383f
Renamed file to add .md extention
MikeCamel 88401b5
Merge branch 'master' into trust-anchors-and-pivots-00004
MikeCamel 71210eb
Responses to reviews and comments.
MikeCamel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,108 @@ | ||
# 00006 Trust anchors and pivots | ||
- Authors: [Mike Bursell]([email protected]) | ||
- Status: [PROPOSED](/README.md#proposed) | ||
- Since: 2020-03-09 | ||
- Status Note: discussion | ||
- Supersedes: n/a | ||
- Start Date: 2020-03-16 | ||
- Tags: trust | ||
|
||
## Summary | ||
|
||
Trust anchors and trust pivots allow us to discuss how trust domains are | ||
created and modified. | ||
|
||
## Motivation | ||
|
||
In order to describe some of the key features of Enarx, the concepts of | ||
trust anchors and trust pivots need to be defined and explained. This | ||
RFC aims to provide that information. | ||
|
||
## Tutorial | ||
|
||
This RFC introduces three concepts: | ||
- Endorsing authorities | ||
- Trust anchors | ||
- Trust pivots | ||
|
||
These concepts are important to allow us to discuss how the various | ||
components of Enarx work together. These definitions are taken from | ||
"Trust in computer systems and the cloud", Mike Bursell, not yet | ||
published. | ||
MikeCamel marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
### Endorsing authorities | ||
An endorsing authority is a human or organisational entity to | ||
whom a trust relationship has been established. An endorsing | ||
authority can provide one or more trust anchors, endorsing them | ||
as representing properties of another human or organisation | ||
(such as their identity, physical location or ability to access | ||
credit). Endorsing authorities are sometimes referred to as | ||
"trust anchors" - for our purposes, we consider the former as | ||
endorsing the latter. | ||
|
||
### Trust anchor | ||
A trust anchor is a static component in a system whereby an | ||
endorsing authority allows trustors to assume trust in a system | ||
in which the anchor is contained. Trust anchors are static in | ||
terms of their interaction with a trust system, and the trust | ||
relationship to a trust anchor is assumed - based on the endorsing | ||
authority - rather than derived. One example of a trust anchor | ||
Comment on lines
+48
to
+49
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's drop the hyphens and add the word "it" to the end of the sentence, so: "is assumed based on the endorsing authority rather than derived from it." There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm having trouble putting it together @connorkuehl, could you use the built-in suggestion tool to suggest a diff/patch? (<ctrl+g> apparently) |
||
is a root certificate signed by a Certificate Authority (the | ||
endorsing authority in this case). | ||
|
||
### Trust pivot | ||
A trust pivot is a component (or set of components) and associated | ||
process (that is, algorithm, rather than necessarily executing | ||
process) which allows a trust relationship from one entity (trustor | ||
A) to another (trustee X) to be transferred, or added, to | ||
another entity (trustor B), so that trustor B now has the trust | ||
relationship to trustee X. The validity of the pivot assumes | ||
the existence of one or more trust anchors. The concept of a | ||
trust pivot is new, and two examples may help explain it. | ||
|
||
#### A will as a trust pivot | ||
A will (as in "last will and testament") provides a legal | ||
mechanism whereby the ownership and management of property can | ||
be passed from one person to another. In this case, the trust | ||
pivot is the will itself, the trust anchor is the legal recognition | ||
by the state of the validity of properly created and registered wills, | ||
and the endorsing authority is the state. (Note: "Trusts" are | ||
another mechanism, but the name is somewhat confusing in this | ||
context!). | ||
|
||
#### A CPU+firmware as a trust pivot of a TEE | ||
Most relevant to Enarx is the use of TEE-enabled CPU+firmware and | ||
an attestation process to allow a TEE instance to pivot from one | ||
trust domain (the host's) to another (the workload owner's). An | ||
example of a trust anchor in this case is the cryptographic | ||
key or certificate which the CPU+firmware component uses to sign | ||
aspects of the attestation. | ||
|
||
|
||
## Reference | ||
|
||
n/a | ||
|
||
## Drawbacks | ||
|
||
n/a | ||
|
||
## Rationale and alternatives | ||
|
||
n/a | ||
|
||
## Prior art | ||
|
||
n/a | ||
|
||
## Unresolved questions | ||
|
||
n/a | ||
|
||
## Implementations | ||
|
||
n/a | ||
|
||
## Future Possibilities | ||
|
||
n/a |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The RFC number here is different than the RFC number in the title of this PR.