|
|
|
|
@ -128,7 +128,7 @@ these use cases will be discussed in further detail in
|
|
|
|
|
|
|
|
|
|
## Use Cases for pEp KeySync
|
|
|
|
|
|
|
|
|
|
### Forming Device Group
|
|
|
|
|
### Form Device Group
|
|
|
|
|
|
|
|
|
|
Our user, Alice, has two devices that are configured with
|
|
|
|
|
pEp-implementing messaging clients and share the same identity for her
|
|
|
|
|
@ -145,10 +145,10 @@ among its members. Thus, allowing both devices to have full
|
|
|
|
|
communication capability, and Alice to use her devices as she desires.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Adding New Device to Existing Device Group
|
|
|
|
|
### Add New Device to Existing Device Group
|
|
|
|
|
|
|
|
|
|
Sometime after devices Alice_R and Alice_O have formed a Device Group
|
|
|
|
|
(cf. {{forming-device-group}}), Alice buys another device, Alice_J,
|
|
|
|
|
(cf. {{form-device-group}}), Alice buys another device, Alice_J,
|
|
|
|
|
which is also configured with pEp-implementing messaging clients and
|
|
|
|
|
shares the same identity for her preferred communication channel (the
|
|
|
|
|
aforementioned email address). Alice_J also has a key pair, which was
|
|
|
|
|
@ -158,7 +158,7 @@ each other and have exchanged private keys, Alice_J and the grouped
|
|
|
|
|
devices don't know anything each other. Thus, Alice does not have full
|
|
|
|
|
communication capability across the three devices.
|
|
|
|
|
|
|
|
|
|
<!-- Editorial NOTE: Reference forming-device-group may change due to
|
|
|
|
|
<!-- Editorial NOTE: Reference form-device-group may change due to
|
|
|
|
|
autonumbering, ensure it is pointing to the one in this section -->
|
|
|
|
|
|
|
|
|
|
As before with devices Alice_R and Alice_O, Alice will use pEp Keysync
|
|
|
|
|
@ -170,8 +170,8 @@ to her messages from any of them.
|
|
|
|
|
### Exchange Private Keys
|
|
|
|
|
|
|
|
|
|
All devices from Alice are part of a Device Group
|
|
|
|
|
(cf. {{forming-device-group}} and
|
|
|
|
|
{{adding-new-device-to-existing-device-group}}). However, as keys may
|
|
|
|
|
(cf. {{form-device-group}} and
|
|
|
|
|
{{add-new-device-to-existing-device-group}}). However, as keys may
|
|
|
|
|
expire or get reset <!-- TODO: Key Reset Reference, when out --> ,
|
|
|
|
|
occasionally new key pairs are generated. For Alice to be able to read
|
|
|
|
|
all encrypted messages on all devices, any new private key needs to be
|
|
|
|
|
@ -179,8 +179,8 @@ shared with the other devices in the device group. All devices of
|
|
|
|
|
Alice will keep the other devices updated with the latest private
|
|
|
|
|
keys.
|
|
|
|
|
|
|
|
|
|
<!-- Editorial NOTE: References forming-device-group /
|
|
|
|
|
adding-new-device-to-existing-device-group may change due to
|
|
|
|
|
<!-- Editorial NOTE: References form-device-group /
|
|
|
|
|
add-new-device-to-existing-device-group may change due to
|
|
|
|
|
autonumbering, ensure it is pointing to the one in this section -->
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@ -228,9 +228,9 @@ The following interaction diagrams depict the implementations of the
|
|
|
|
|
above Use Case in a simplified manner (as mentioned above, some
|
|
|
|
|
aspects are skipped for the sake of better readability):
|
|
|
|
|
|
|
|
|
|
### Forming Device Group
|
|
|
|
|
### Form Device Group
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
\[\[TODO]\]: Interaction diagrams and descriptions for the use cases above
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
|
|
|
|
|
@ -268,7 +268,7 @@ was involved in some former communications with the outside world.
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Adding New Device to Existing Device Group
|
|
|
|
|
### Add New Device to Existing Device Group
|
|
|
|
|
|
|
|
|
|
\[\[TODO]\]: Interaction diagrams and descriptions for the use cases above
|
|
|
|
|
|
|
|
|
|
@ -298,7 +298,7 @@ The States and Events that fire a transition are described in
|
|
|
|
|
{{full-finite-state-machine}}.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### FSM Forming Device Group
|
|
|
|
|
### FSM Form Device Group
|
|
|
|
|
|
|
|
|
|
#### Requester's Side
|
|
|
|
|
|
|
|
|
|
|
