Commit 4a6ba5b2 authored by David Goulet's avatar David Goulet

Update blog index with new blog post

Signed-off-by: default avatarDavid Goulet <dgoulet@ev0ke.net>
parent 4f2bb77f
......@@ -43,60 +43,69 @@
<div class="hero-unit faq">
<div class="ac">
<h2><a href="2014-07-14-tails otr hackfest meeting.html">OTR meeting notes - Tails hackfest in Paris 2014</a></h2>
<h2><a href="2014-07-25-hopex mpotr.html">mpOTR progress report - HOPE X in New York 2014</a></h2>
</div>
</div>
<div class="post firstpost">
<p>Attendees:
- jvoisin
- trevp
- infinity0
- DrWhax
- dgoulet
- drwhax
- vmon</p>
<p>1) Modern cryptography</p>
<p>Migrating current OTR protocol to use modern cryptography. We would like to
replace the DSA signature to "ed25519". The DH exchange should be replaced by
"curve25519". libgcrypt supports ed25519 since version 1.6 (package
libgcrypt20). The curve25519 is unclear if it's merged or a work in progress.</p>
<p>The new key(s) should be derived from the old one so users can keep their
current fingerprint.</p>
<p>For that, we discussed the need to cross sign keys for the transition.</p>
<p>Also, should chacha20 and/or poly1305 should be considered as well? No one had
a strong opinion on that.</p>
<p>A proposal of these changes should be written first before any code starts and
Acked-by maintainers/developers/contributors off the community.</p>
<p>2) Tests suite</p>
<p>You can find here a branch of the test suite started by dgoulet which contains
some basic unit tests now integrated with libtap.</p>
<pre><code>git://git.otr.im/libotr-next.git
(branch: test-suites)
</code></pre>
<p>We agree that an "OTR fuzzer" would be great also to basically hunt bug and
also be able to add this to a continious integration system.</p>
<p>There is a bunch of open bugs/features on
https://bugs.otr.im/projects/libotr/issues that we need to tackle but we all
agree that we should <em>first</em> make the test suite with a descent code coverage
so we can actually confirm that what we are fixing/implementing is not breaking
anything.</p>
<p>Once we have that, there is some kniffing to do especially on some part of the
internal ABI (for instance, second comments of this
https://bugs.otr.im/issues/23). Memory allocation used without checks, stuff
like that. Mostly this kniffing would be simply to improve the code to make it
more easily maintainable and robust.</p>
<p>3) OTR.im</p>
<p>We have a twitter account now to tweet about some stuff that's going on in the
OTR community I guess and news/update... So send anything you think might be
worth tweeting :).</p>
<pre><code>https://twitter.com/otr_im
</code></pre>
<p>Also, we discussed having more action on the blog (https://otr.im/blog)
especially maybe putting a "Call to action" for testing.</p>
<p>A new git repository containing the specifications would be a good idea to
create so we can have people looking at the progress of the modern crypto spec.
for instance.</p>
<p>This is a progress report on the ongoing mpOTR effort after a meeting at the
HOPE X conference in New York.</p>
<p>First of all, the name of the protocol has not been yet decided thus we'll use
mpOTR in this report so everyone understand what we are talking about.</p>
<p>This initiative was launched by CryptoCat and eQualit.ie in early 2014 with the
help of OTF for the funding. You can find an overview of the project here
<a href="https://github.com/cryptocat/cryptocat/wiki/mpOTR-Project-Plan">mpOTR</a>. Quite
of work has been put into this new protocol and a second draft of the mpOTR
protocol should be release to the public soon.</p>
<p>Now a quick summary of what we discussed. It is divided into roughly two parts,
the key agreement to establish the session, and mechanisms to ensure transcript
consistency during the session. The key agreement can itself by thought as a
combination of a forward-secure confidentiality key agreement, and a deniable
authentication key agreement.</p>
<p>Unlike OTR which is a bidirectionnal data exchange, a cryptographic agreement
between all parties need to be established before having a group chat secure
channel. There are multiple methods to achieve that, such has having each
participant broadcasting her/his key ("sender keys") or using a common key for
the whole chat session ("group key"). It's also important to consider the
transport protocols that support group chat such as IRC and XMPP; these all
have different semantics for reachability, presence, delivery and so on. In
order for mpOTR to be transport agnostic, we need to assume as little as
possible about the transport, and/or think about how to adapt the semantics we
choose for mpOTR, into the semantics of each transport.</p>
<p>mpOTR will most likely introduce new properties on top of the secure channel
that make sure the transcript between all participants is ordered and
consistent. This is to prevent an insider attacker that decides to send
different information to different people in the group chat - this would be as
disastrous as a non-secure communication channel. I won't go into any more
details but I encourage you all to read infinity0
<a href="https://github.com/infinity0/msg-notes">notes</a>.</p>
<p>So back to the HOPE X meeting. The discussion was aimed at trying to get to an
agreement between attendees mostly on two aspects, which key agreement scheme
to use and the transcript consistency property. I'll describe what they are
briefly here but will not go into deep technical details since no decision have
been made.</p>
<p>As mention before, there are multiple key agreement scheme that can be used but
there is still a debate on which one to use in mpOTR, sender keys or a common
group key. Each of these have advantages and disadvantages, but details are
being worked out to decide which one the next draft will follow.</p>
<p>For the transcript consistency, the discussion was mostly about the performance
overhead of the scheme described
<a href="https://github.com/infinity0/msg-notes/blob/master/causal-02-consistency.rst">here</a>,
and whether simpler schemes achieve security guarantees that are strong enough.
Again, I'm not going to go into more details since I feel that this would need
its own blog post/paper and the goal here is to show what's being worked on
right now for mpOTR.</p>
<p>As I said, the second draft will be release soon (hopefully with an official
name) which you, the public, should bring a HUGE amount of scrutiny to it and
we can finally move to an implementation! :)</p>
<div class="postmeta">
<p class="text-muted">published on 2014-07-14 12:00:00 by OTR.im</p>
<p class="text-muted">published on 2014-07-25 00:00:00 by dgoulet, infinity0</p>
</div>
</div>
......@@ -106,6 +115,11 @@ for instance.</p>
<h3 class="subtitle">Older Posts</h3>
<ul class="postlist">
<li>
<span>2014-07-14 12:00:00</span>
<a href="2014-07-14-tails otr hackfest meeting.html">OTR meeting notes - Tails hackfest in Paris 2014</a>
</li>
<li>
<span>2014-04-27 16:00:00</span>
<a href="2014-04-27-LWN.html">Debian OTR team featured on LWN</a>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment