Commit beffdce6 authored by David Goulet's avatar David Goulet

Update mpOTR blog post with right template

Signed-off-by: default avatarDavid Goulet <dgoulet@ev0ke.net>
parent 4a6ba5b2
<!DOCTYPE html>
<html>
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8 ie-7"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie13 ie-8"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->
<html lang="en">
<head>
<title>My Blog</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link href="css/bootstrap.min.css" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet" type="text/css">
<link href="https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz" rel="stylesheet" type="text/css">
<style>
body {
font-family: Open Sans;
background-color: #f3f3f3;
}
h1, h2, h3, h4 {
font-family: Yanone Kaffeesatz;
}
.container {
max-width: 730px;
}
.footer {
margin-top: 50px;
font-size: 11px;
text-align: center;
}
</style>
<title>Otr.im - Blog</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link href="https://otr.im/assets/css/style.css" rel="stylesheet">
<link href="css/style.css" rel="stylesheet">
</head>
<body>
<div class="container">
<div class="hero-unit faq">
<div class="ac" style="text-align: center;">
<h1>My Blog</h1>
<a href="index.html">Home</a> &bull; <a href="about.html">About</a> &bull; <a href="feed.xml">Feed</a>
<body class="blog">
<div class="navbar-wrapper">
<div class="container">
<div class="navbar navbar-inverse navbar-static-top" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="#">OTR.im</a>
</div>
<div class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li><a href="https://otr.im/">Home</a></li>
<li><a href="https://otr.im/clients.html">Clients</a></li>
<li><a href="https://otr.im/about.html">About</a></li>
<li class="active"><a href="https://otr.im/blog/">Blog</a></li>
</ul>
</div>
</div>
</div>
</div>
</div>
<div class="container" id="container">
<div class="container-inner">
<div class="hero-unit faq">
<div class="ac">
<h2>mpOTR progress report - HOPE X in New York 2014</h2>
<h2 class="maintitle">mpOTR progress report - HOPE X in New York 2014</h2>
</div>
</div>
<div>
<div class="post">
<p>Attendees:
- trevp
- infinity0
......@@ -57,7 +64,7 @@ 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
consistency during the session. The key agreement can itself be 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
......@@ -82,10 +89,10 @@ 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>As mentionned 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>,
......@@ -96,14 +103,20 @@ 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>
<div class="postmeta">
<p class="text-muted">published on 2014-07-25 00:00:00 by dgoulet, infinity0</p>
</div>
</div>
</div>
</div>
<div class="footer">
<p class="text-muted">powered by <a href="https://github.com/botherder/habu">habu</a>.</p>
</div>
<footer class="footer">
<div class="container-inner">
<p class="pull-right"><a href="#">Back to top</a></p>
<p>OTR - Free and open source software.</p>
<p>We would like to thank <a href="https://www.gandi.net/">Gandi</a> for providing us with a wildcard SSL certificate.</p>
<p class="text-muted">Blog powered by <a href="https://github.com/botherder/habu">habu</a>.</p>
</div>
</footer>
</body>
</html>
\ No newline at end of file
......@@ -65,7 +65,7 @@ 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
consistency during the session. The key agreement can itself be 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
......@@ -90,10 +90,10 @@ 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>As mentionned 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>,
......
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