Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-01 20:13:43 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

make text consistent with image

Browse source
This commit is contained in:
Hubert Chathi 2018-12-14 19:11:17 -05:00
parent f3997cd09e
commit 2d3b5f4481
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
proposals/1756-cross-signing.md
View file

@ -119,19 +119,19 @@ needed to reattach the parts of the graph.
One way to solve this is by registering a "virtual device", which is used to
sign other devices. This solution would be similar to this proposal. However,
real devices would still form an integral part of the attestation graph. For
example, if Alice's phone verifies Bob's tablet, the attestation graph might
example, if Alice's Osborne 2 verifies Bob's Dynabook, the attestation graph might
look like:
![](images/1756-graph1.dot.png)
If Bob replaces his tablet without re-verifying with Alice, this will split the
graph and Alice will not be able to verify Bob's other devices. In contrast,
in this proposal, Alice and Bob's master keys directly sign each other, and the
attestation graph would look like:
If Bob replaces his Dynabook without re-verifying with Alice, this will split
the graph and Alice will not be able to verify Bob's other devices. In
contrast, in this proposal, Alice and Bob's master keys directly sign each
other, and the attestation graph would look like:
![](images/1756-graph2.dot.png)
In this case, Bob's tablet can be replaced without breaking the graph.
In this case, Bob's Dynabook can be replaced without breaking the graph.
With normal cross-signing, it is not clear how to recover from a stolen device.
For example, if Mallory steals one of Alice's devices and revokes Alice's other