[Cryptography] upgrade mechanisms and policies

Ryan Carboni ryacko at gmail.com
Tue Apr 28 22:25:43 EDT 2015

On 4/28/15 at 6:42 AM, iang at iang.org (ianG) wrote:

Indeed.  But take the well-known case of SSL.  The industry bends over
> backwards to state that authentication of the server is the key benefit.
>   Yet, they fail to authenticate the server in phishing - a simple
> bypass attack.  And for most webservers, they couldn't care less about
> their own authentication, what they care about is the client
> authentication.  SSL completely muffs client authentication, leaving the
> users to come up with ad hoc password stuff.
> (Yeah, now poeple will chime in and repeat the marketing about how it's
> hard because of multiple devices and and and ... the point is, every
> which way you look at the SSL story, it isn't about what the users need,
> it's about what was easy to convince to be sold.)

Yeah, it would be nice if affidavits and background checks were used to
authenticate people applying for certificates.

If you want security solutions to be widely deployed, nothing
> beats having a revenue model for someone. With a revenue model,
> you have a champion who will work hard to sell the solution to
> the world. Without a revenue model, you just have a bunch of
> geeks with a good idea. We have TLS with CAs because there is a
> revenue model, not because it is the best solution.
> Cheers - Bill

 If a standard is terrible, there can be three reasons:
1. Stupidity
2. Corruption
3. Greed

TLS with CAs could very well be any or all three. SSL did not standardize
padding. Corruption to allow state actors to violate trust (our CA was
accidentally hacked). You explained how greed could be a motive.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20150428/f08e23c1/attachment.html>

More information about the cryptography mailing list