ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-29 09:18:58 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Updated

Browse Source
This commit is contained in:
David Lee 2017-11-17 15:17:55 +00:00 committed by GitHub
parent 9497f34698
commit 218a432f89
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/source/design/float/decisions/drb-meeting-20171116.md
View File

@ -72,11 +72,11 @@ MH viewed the use-case for extra encryption as the consumer/SME market, where us
MH advised against offering clients support for their own firewall since it would likely require R3 effort to test support and help with customisations. MH advised against offering clients support for their own firewall since it would likely require R3 effort to test support and help with customisations.
MN described option 2b to tunnel through to the internal trusted portion of the float over a connection initiated from inside the internal network; this would require a bit more code. MN described option 2b to tunnel through to the internal trusted portion of the float over a connection initiated from inside the internal network in order for the key to be loaded into memory at run-time; this would require a bit more code.
MH advocated option 2c - just to accept risk and store on file system – on the basis of time constraints, maintaining that TLS handshakes are complicated to code and hard to proxy. MH suggested upgrading to 2b or 2a later if needed. MH described how keys were managed at Google. MH advocated option 2c - just to accept risk and store on file system – on the basis of time constraints, maintaining that TLS handshakes are complicated to code and hard to proxy. MH suggested upgrading to 2b or 2a later if needed. MH described how keys were managed at Google.
**DECISION CONFIRMED**: Accept option 2c - Terminate on float, leave keys on file system (RGB, JC, MH agreed) **DECISION CONFIRMED**: Accept option 2b - Terminate on float, inject key from internal portion of the float (RGB, JC, MH agreed)
### [E2E encryption](./e2e-encryption.md) ### [E2E encryption](./e2e-encryption.md)
@ -152,4 +152,4 @@ JoC questioned whether the Bridge Manager locked the design to Artemis? MO highl
RGB questioned the rationale for moving the broker out of the node. MN provided clarification. RGB questioned the rationale for moving the broker out of the node. MN provided clarification.
**DECISION CONFIRMED**: Design to proceed as discussed (RGB, JC, MH agreed) **DECISION CONFIRMED**: Design to proceed as discussed (RGB, JC, MH agreed)