From 09a97ba4366b18dd590945c7ac48f7ec4add02df Mon Sep 17 00:00:00 2001
From: Oskar Thoren <ot@oskarthoren.com>
Date: Thu, 29 Aug 2019 13:41:10 +0200
Subject: [PATCH] add todos

---
 status-secure-transport-spec.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/status-secure-transport-spec.md b/status-secure-transport-spec.md
index 8dff1c8..805309a 100644
--- a/status-secure-transport-spec.md
+++ b/status-secure-transport-spec.md
@@ -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/).