&gt; Most if not all techniques that would allow for not transmitting the password in a server-decryptable fashion would require the password or a password equivalent to be stored in clear on the server.<p>That&#x27;s not true at all! SRP[1][2] allows the server to not have the plaintext password ever, even during account creation.<p>Kerberos&#x27; KDC doesn&#x27;t know the plain-text password either[3].<p>Even HTTP Digest didn&#x27;t require the password to be stored in plain text [4]. [Edit: though if you leaked HA1 that effectively becomes the credential]<p>Moreover, client TLS certificates would also fit the bill, as the client key is never transmitted.<p>Don&#x27;t spread FUD if you aren&#x27;t sure. If you don&#x27;t know, don&#x27;t say anything or say you don&#x27;t know.<p>[1] <a href="http:&#x2F;&#x2F;srp.stanford.edu&#x2F;" rel="nofollow">http:&#x2F;&#x2F;srp.stanford.edu&#x2F;</a>
[2] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Secure_Remote_Password_protocol" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Secure_Remote_Password_protoco...</a>
[3] <a href="http:&#x2F;&#x2F;security.stackexchange.com&#x2F;questions&#x2F;15849&#x2F;does-the-kerberos-kdc-know-the-users-plaintext-passwords" rel="nofollow">http:&#x2F;&#x2F;security.stackexchange.com&#x2F;questions&#x2F;15849&#x2F;does-the-k...</a>
[4] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Digest_access_authentication" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Digest_access_authentication</a>