From 59f839d80a6b9af309acd785b53283d2e422bb41 Mon Sep 17 00:00:00 2001 From: Mike Hearn Date: Fri, 21 Jun 2019 15:14:46 +0100 Subject: [PATCH] Add remark about flow deniability. --- docs/source/whitepaper/corda-technical-whitepaper.tex | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/source/whitepaper/corda-technical-whitepaper.tex b/docs/source/whitepaper/corda-technical-whitepaper.tex index 0e2b79b4a6..eb4b7485ef 100644 --- a/docs/source/whitepaper/corda-technical-whitepaper.tex +++ b/docs/source/whitepaper/corda-technical-whitepaper.tex @@ -377,6 +377,10 @@ itself, for example in case of database deadlocks that require a retry. The abil useful for cases where the other side isn't sure why you are contacting them, for example, the specified reason for sending a payment is not recognised, or when the asset used for a payment is not considered acceptable. +For performance reasons messages sent over flows are protected only with TLS. This means messages sent via flows +are deniable unless explicitly signed by the application. Automatic signing and recording of flow contents may be +added in future. + Flows are identified using Java class names i.e. reverse DNS notation, and several are defined by the base protocol. Note that the framework is not required to implement the wire protocols, it is just a development aid.