status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

add todos

This commit is contained in:
Oskar Thoren 2019-08-29 13:41:10 +02:00
parent 416dd321af
commit 09a97ba436
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
status-secure-transport-spec.md
View File

@ -59,6 +59,9 @@ In this document we describe how a secure channel is established, and how variou
- **Authenticity**: The adversary should not be able to cause either endpoint of a Status 1:1 chat to accept data from any third party as though it came from the other endpoint.
- **Forward Secrecy**: The adversary should not be able to learn what data was exchanged between two Status clients if, at some later time, the adversary compromises one or both of the endpoint devices.
<!-- TODO: Integrity should be here -->
<!-- TODO: It is not clearly stated in this spec how we achieve confidentiality, authenticity and integrity. State this clearly. -->
### Conventions
Types used in this specification are defined using [Protobuf](https://developers.google.com/protocol-buffers/).