Uh... no.  That&#x27;s exactly wrong.  If bcrypt or whatever gets broken tomorrow, and my OAuth provider needs to reset all the passwords in the database (Linode literally did this last week, though not because of a hash change, it&#x27;s a common kind of thing), <i>I don&#x27;t need to change a line of code.</i><p>Ergo, if you&#x27;re worried about changes to password hash vogues, OAuth is a good idea.  Thus the point way upthread, which both you and the other poster seem to have missed.