[148180] in cryptography@c2.net mail archive
Re: [Cryptography] Moving forward on improving HTTP's security
daemon@ATHENA.MIT.EDU (Tony Arcieri)
Thu Nov 14 15:02:32 2013
X-Original-To: cryptography@metzdowd.com
In-Reply-To: <C5DF885A-7641-4BD6-A81D-6755AD9588A1@kinostudios.com>
From: Tony Arcieri <bascule@gmail.com>
Date: Thu, 14 Nov 2013 11:50:33 -0800
To: Greg <greg@kinostudios.com>
Cc: John Kelsey <crypto.jmk@gmail.com>,
Cryptography <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============3882951656508517389==
Content-Type: multipart/alternative; boundary=001a11c1bc64396ccb04eb2866b6
--001a11c1bc64396ccb04eb2866b6
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Nov 13, 2013 at 9:46 PM, Greg <greg@kinostudios.com> wrote:
>
> The basics would be to not use the CAs. Working on rest of details,
> they're mostly finished, just gotta make 'em nice 'n pretty. And some code
> would be good, too.
>
And what of other solutions like CT or Tack?
Given Google's power to influence change via Chrome and its share of the
browser market, I think we'll see CT as the the primary solution for what
ails the existing PKI.
Tack looks cool too and I like Trevor and Moxie. But they don't have the
sort of influence Google does unfortunately.
--
Tony Arcieri
--001a11c1bc64396ccb04eb2866b6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Nov 13, 2013 at 9:46 PM, Greg <span dir=3D"ltr"><<a href=3D"mailto:g=
reg@kinostudios.com" target=3D"_blank">greg@kinostudios.com</a>></span> =
wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><div>The basics would be to not us=
e the CAs. Working on rest of details, they're mostly finished, just go=
tta make 'em nice 'n pretty. And some code would be good, too.</div=
>
</div></div></blockquote><div><br></div><div>And what of other solutions li=
ke CT or Tack?</div><div><br></div><div>Given Google's power to influen=
ce change via Chrome and its share of the browser market, I think we'll=
see CT as the the primary solution for what ails the existing PKI.</div>
<div>=A0</div><div>Tack looks cool too and I like Trevor and Moxie. But the=
y don't have the sort of influence Google does unfortunately.</div><div=
><br></div></div>-- <br>Tony Arcieri<br>
</div></div>
--001a11c1bc64396ccb04eb2866b6--
--===============3882951656508517389==
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
--===============3882951656508517389==--
