diff options
| author |  http://joeyh.name/ <joey@web> | 2013-06-10 23:50:27 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-06-10 23:50:27 +0000 |
| commit | ed2c33a0e44599cffb7785f56d665ce80a6523c7 (patch) | |
| tree | 370caf1330d5e1d54f59270364be20757e691d99 | |
| parent | 1bd97557fbc61a5650d090612cc807878a4e95f7 (diff) | |
Added a comment
| -rw-r--r-- | doc/design/assistant/blog/day_281__back/comment_2_6d0bbdf6ebaff9da399804570f0e606d._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_281__back/comment_2_6d0bbdf6ebaff9da399804570f0e606d._comment b/doc/design/assistant/blog/day_281__back/comment_2_6d0bbdf6ebaff9da399804570f0e606d._comment new file mode 100644 index 000000000..884b2484e --- /dev/null +++ b/doc/design/assistant/blog/day_281__back/comment_2_6d0bbdf6ebaff9da399804570f0e606d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 2" + date="2013-06-10T23:50:27Z" + content=""" +David, along those lines, if a value derived from the D-H key were committed to the git repo, then the MITM would need to maintain two distinct git trees, and translate between them on an ongoing basis. Which is harder. And then if both clients at any point communicated via another channel (ie, local pairing), the forgery would be very noticeable. + +Which is not to say that this is necessarily good enough.. +"""]] |