<p dir="ltr">Generally agreed. Criterion is this: editor must be so easy to use that a 70-yo judge whose undergrad was in French Lit. could use it. <br></p>
<p dir="ltr">On Jun 26, 2014 5:11 PM, "Guy K. Kloss" <<a href="mailto:gk@mega.co.nz">gk@mega.co.nz</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> last night in a discussion (in meat space) the issue of plausible<br>
> deniability came up again. As far as it stands, I guess most people are<br>
> of the opinion that even if a protocol features the capability for<br>
> plausible deniability, it probably won't hold up in court.<br>
><br>
> We've been thinking what could be done to "better" the chances that<br>
> something like this might actually hold up. That one could believably<br>
> argue that one for example has been framed through a<br>
> doctored/manufactured transcript.<br>
><br>
> One thought was, that it's too difficult to make anybody believe that<br>
> somebody has actually tampered with a transcript. So, an idea came up<br>
> that one actually might just need to provide a tool that's reasonably<br>
> easy to use for an average Joe to read a recorded transcript, edit it,<br>
> and save the modified version again.<br>
><br>
> I could imagine this to work reasonably easy, if one can actually use an<br>
> existing session transcript as a "seed", which includes the initial<br>
> session key negotiation, and in the following only authenticates<br>
> messages through session secrets, rather than using the long term static<br>
> secrets (like private OTR key, or any other personal authentication<br>
> mechanism).<br>
><br>
> Any thoughts on this?<br>
><br>
> I think this might in scope actually make a nice student project for<br>
> some final year comp sci students.<br>
><br>
> Guy<br>
><br>
><br>
> _______________________________________________<br>
> Messaging mailing list<br>
> <a href="mailto:Messaging@moderncrypto.org">Messaging@moderncrypto.org</a><br>
> <a href="https://moderncrypto.org/mailman/listinfo/messaging">https://moderncrypto.org/mailman/listinfo/messaging</a><br>
><br>
</p>