[146347] in cryptography@c2.net mail archive

home help back first fref pref prev next nref lref last post

Re: [Cryptography] PRISM PROOF Email

daemon@ATHENA.MIT.EDU (Phillip Hallam-Baker)
Fri Aug 23 19:20:29 2013

X-Original-To: cryptography@metzdowd.com
In-Reply-To: <CAG5KPzwaVEN00tfMX2vt51PvXEugEeQ-KQ9PJEQgWcNC3yvfaQ@mail.gmail.com>
Date: Fri, 23 Aug 2013 18:51:25 -0400
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <ben@links.org>
Cc: cryptography@metzdowd.com
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com

--===============1388118513291019840==
Content-Type: multipart/alternative; boundary=001a11c2677e16a51604e4a53f5d

--001a11c2677e16a51604e4a53f5d
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Aug 23, 2013 at 3:34 PM, Ben Laurie <ben@links.org> wrote:

>
> On 22 August 2013 10:36, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>> Preventing key substitution will require a combination of the CT ideas
>> proposed by Ben Laurie (so catenate proof notaries etc) and some form of
>> 'no key exists' demonstration.
>
>
> We have already outline how to make verifiable maps as well as verifiable
> logs, which I think is all you need.
> http://www.links.org/files/RevocationTransparency.pdf.
>

Yeah, I think it is just a matter of being clear about the requirements and
making sure that we fully justify the requirements for email rather than
assume that email is the same.


-- 
Website: http://hallambaker.com/

--001a11c2677e16a51604e4a53f5d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 23, 2013 at 3:34 PM, Ben Laurie <span dir=3D"ltr">&lt;<=
a href=3D"mailto:ben@links.org" target=3D"_blank">ben@links.org</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"im"><br><div class=3D"gmail_quote">On 22 August 2013 10:36, P=
hillip Hallam-Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.co=
m" target=3D"_blank">hallam@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Preventing key substitution will require a combination of =
the CT ideas proposed by Ben Laurie (so catenate proof notaries etc) and so=
me form of &#39;no key exists&#39; demonstration.</blockquote>

</div><br></div>We have already outline how to make verifiable maps as well=
 as verifiable logs, which I think is all you need.=A0<a href=3D"http://www=
.links.org/files/RevocationTransparency.pdf" target=3D"_blank">http://www.l=
inks.org/files/RevocationTransparency.pdf</a>.</div>

</div>
</blockquote></div><br>Yeah, I think it is just a matter of being clear abo=
ut the requirements and making sure that we fully justify the requirements =
for email rather than assume that email is the same.</div><div class=3D"gma=
il_extra">
<br></div><div class=3D"gmail_extra"><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2677e16a51604e4a53f5d--

--===============1388118513291019840==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============1388118513291019840==--

home help back first fref pref prev next nref lref last post