SSL is a messed up protocol, relying on trust in central authorities.  SSH did it right:  it only ensures that the server you connect with today is the same one you connected with yesterday, and it does not aim to do anything more.<p>An SSL certificate "verified by King George" does not mean that you can trust the vendor with your money or your data.  <i>I</i> have to decide to trust the vendor that much, and nobody else can do it for me.  All I want the crypto to do is verify that I am now talking with the same vendor I talked with yesterday.<p>I don't mind using a certified signed by someone not crowned as a king, for example <a href="https://secure.loom.cc" rel="nofollow">https://secure.loom.cc</a>.  Or I could use this one <a href="https://loom.cc/" rel="nofollow">https://loom.cc/</a> "verified by Equifax" which means nothing special to me.<p>I don't care that <i>someone else</i> decreed that "this is the One True loom.cc site."  All I care is that the site I initially decided to trust is the same site I'm connecting with now.