docs: adding a threat model diagram for Ubuntu Frame #3484
Conversation
|
Everyone contributing to this PR have now signed the CLA. Thanks! |
mattkae
force-pushed
the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
4 times, most recently
from
996f7ee to
0d29e46
Compare
mattkae
changed the title
|
Dropping a screenshot so we can talk about it: The links between OSK and Mir should be both content and input, or go both ways? We're also missing app that communicates with Mir for input, window management and window contents. |
mattkae
force-pushed
the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
from
0d29e46 to
83feb90
Compare
|
@Saviq Like this? |
I think two were better for OSK, unidirectional content and bidirectional input. Also app needs input / window management one way, and content the other. |
mattkae
force-pushed
the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
from
83feb90 to
0ffb9b5
Compare
|
|
mattkae
force-pushed
the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
from
0ffb9b5 to
14be68b
Compare
|
OK, so bidirectional doesn't look too good. Let's just mark the unidirectional edges with We should jump on a call to whack those out, this is too much overhead :) |
| osk--content-->shell | ||
| shell<--input-->osk |
There was a problem hiding this comment.
| osk--content-->shell | |
| shell<--input-->osk | |
| osk--content/input-->shell | |
| shell--input-->osk |
| snapd--configuration-->shell | ||
| display--visuals-->user | ||
| operator_app--help message-->shell | ||
| user--io events-->shell |
There was a problem hiding this comment.
| user--io events-->shell | |
| user--input events-->shell |
mattkae
force-pushed
the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
from
14be68b to
c27ba1a
Compare
mattkae
deleted the
MIRENG-581-convert-the-threat-model-diagram-into-mermaid-on-rtd
branch
To view: https://canonical-mir--3484.com.readthedocs.build/3484/explanation/threat-model/