|
|
|
@ -105,7 +105,7 @@ An online transport is transporting messages synchronously to receivers
|
|
|
|
|
if those are online. If receivers are offline, no message can be
|
|
|
|
|
transported. The connection status of an receiver is available to the
|
|
|
|
|
sender. Examples are Jabber and IRC.
|
|
|
|
|
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
pEp is supposed to solve three problems <!-- for both types of transports -->:
|
|
|
|
|
|
|
|
|
@ -223,6 +223,7 @@ In contrast to security, non-repudiation can be a threat to a user's privacy for
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- =================================================================== -->
|
|
|
|
|
|
|
|
|
|
# Specific security and privacy requirements
|
|
|
|
|
|
|
|
|
|
## Messages Exchange
|
|
|
|
@ -287,7 +288,7 @@ In contrast to security, non-repudiation can be a threat to a user's privacy for
|
|
|
|
|
{{synchronization-management}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Synchronization Mangagement
|
|
|
|
|
## Synchronization Management
|
|
|
|
|
|
|
|
|
|
A device group is a group of devices of the same user that share the
|
|
|
|
|
same key pairs in order to synchronize data among them. In a device
|
|
|
|
@ -295,8 +296,10 @@ group devices of the same user mutually grant authentication.
|
|
|
|
|
|
|
|
|
|
* Form a device group of two (yet ungrouped) devices of the same user
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
Note: Preconditions for forming a device group are outlined in
|
|
|
|
|
{{preconditions-for-forming-a-device-group}}.
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
* Join another device of the same user to existing device group
|
|
|
|
|
|
|
|
|
|