Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Hackathon] How does Agent get unneeded-ta-list #81

Closed
dthaler opened this issue Nov 11, 2020 · 1 comment
Closed

[Hackathon] How does Agent get unneeded-ta-list #81

dthaler opened this issue Nov 11, 2020 · 1 comment
Assignees
@tireddy2
Labels
ready to close

Comments

@dthaler
Copy link
Collaborator

dthaler commented Nov 11, 2020

Issue #16 originally raised the issue of passing a deletion wish from Agent to TAM, and PR #47 added support in the protocol.

However in trying to implement this, the question arises of where the Agent gets this information from. The installation wish comes from the RequestTA abstract API mentioned in the arch doc and transport spec when the wish comes from an untrusted app, or from the SUIT manifest dependency list of a trusted component (i.e., one that depends on another trusted component from a different TAM, such as for personalization data). However there is no "UnrequestTA" abstract API in any document.

Should we add "UnrequestTA" to the arch doc, transport spec, and protocol spec for symmetry?
@dthaler dthaler mentioned this issue Nov 11, 2020
Closed
@dthaler dthaler changed the title How does Agent get unneeded-ta-list [Hackathon] How does Agent get unneeded-ta-list Nov 11, 2020
@dthaler dthaler mentioned this issue Nov 11, 2020
Closed
dthaler added a commit that referenced this issue Nov 19, 2020
@dthaler
Add beginnings of behavioral specification
c461eb4 
Addresses issue #81

Adds a TODO where issue #43 resolution would affect text
(possibly among other places)

Signed-off-by: Dave Thaler <dthaler@ntdev.microsoft.com>
@dthaler dthaler mentioned this issue Nov 19, 2020
Merged
@dthaler dthaler self-assigned this Nov 19, 2020
dthaler added a commit that referenced this issue Nov 19, 2020
@dthaler
Add beginnings of behavioral specification
df4cf49 
Addresses issue #81

Adds a TODO where issue #43 resolution would affect text
(possibly among other places)

Signed-off-by: Dave Thaler <dthaler@ntdev.microsoft.com>
dthaler added a commit that referenced this issue Jan 8, 2021
@dthaler
Add beginnings of behavioral specification
d956db1 
Addresses issue #81

Adds a TODO where issue #43 resolution would affect text
(possibly among other places)

Signed-off-by: Dave Thaler <dthaler@ntdev.microsoft.com>
@dthaler
Copy link
Collaborator Author

dthaler commented Feb 23, 2021

Fixed in draft -05

@dthaler dthaler assigned tireddy2 and unassigned dthaler Feb 23, 2021
@tireddy2 tireddy2 closed this as completed Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tireddy2 tireddy2

Labels
ready to close
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dthaler @tireddy2