From 9b18f13d819d3ee863fcf54751e5cd0b80e23672 Mon Sep 17 00:00:00 2001 From: Sagi Date: Tue, 23 Jul 2013 23:53:12 +0000 Subject: [PATCH] Added a comment: Why not use OTR? --- ...comment_1_c714e86553c02600249795efb224be8a._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/design/assistant/xmpp_security/comment_1_c714e86553c02600249795efb224be8a._comment diff --git a/doc/design/assistant/xmpp_security/comment_1_c714e86553c02600249795efb224be8a._comment b/doc/design/assistant/xmpp_security/comment_1_c714e86553c02600249795efb224be8a._comment new file mode 100644 index 0000000000..92cff201df --- /dev/null +++ b/doc/design/assistant/xmpp_security/comment_1_c714e86553c02600249795efb224be8a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Sagi" + ip="2001:610:1908:8001:25ce:8a0b:53cc:c010" + subject="Why not use OTR?" + date="2013-07-23T23:53:12Z" + content=""" +[OTR](http://www.cypherpunks.ca/otr/) seems a natural fit for end-to-end encryption over xmpp. I can't find Haskell bindings for libotr at this moment, but creating those instead of inventing new protocols might be worth considering. There are also several [native implementations](http://www.cypherpunks.ca/otr/software.php) (Python, Go, Scheme), but I'm not sure if that's worth the effort. + + +"""]]