SRP is cool stuff, but if we're going to do SRP I would be more interested in doing it right.
I think that would mean having browsers support a standard SRP protocol binding (eg http://www.ietf.org/rfc/rfc5054.txt) and then really nailing the browser user interface.
I could see using SRP as an alternative to private keys, or as a strong "something you know" factor in addition to private keys (a "something you have" factor) in order to establish ownership of an account.
However, this doesn't strike me as a credible first step in getting through the aforementioned "deployment deadlock" issue.
I think that would mean having browsers support a standard SRP protocol binding (eg http://www.ietf.org/rfc/rfc5054.txt) and then really nailing the browser user interface.
I could see using SRP as an alternative to private keys, or as a strong "something you know" factor in addition to private keys (a "something you have" factor) in order to establish ownership of an account.
However, this doesn't strike me as a credible first step in getting through the aforementioned "deployment deadlock" issue.