Post
Topic
Board Web Wallets
Re: Blockchain.info - Bitcoin Block explorer & Currency Statistics
by
piuk
on 18/01/2013, 21:23:19 UTC
No verifier extension installed on this particular computer or Chromium and running Chromium Version 22.0.1215.0 (147829). Still cannot seem to get this to work for whatever reason.

Sorry not sure what the problem would be. Anyone else running Chromium that can test it?

I don't think saving your password is a good option to have.  No banking website would ever allow that, and Blockchain.info is a similar type of site.  One thing that annoys me about the password input box, however, is that it doesn't work with Lastpass (ie, Lastpass can't automatically fill it in).  Additionally, you still have to click the login button after two-factor auth with a Yubikey, which isn't necessary on many sites.

Lastpass incompatibility is because the login fields are not wrapped in a
tag, it would be very easy to fix if it wasn't for the fact that the verifier disallows form tags. The yubikey issue will be fixed in the next update.

How about a remember password checkbox for the session? Session, as in if you don't access it for 4 hours it is automatically logged out.

Storing it in a server session or in cookies would violate the never share password with the server rule. It would have to be stored in localStorage which unfortunately does not have support for automatic expiry of values stored. I will heed the advice and forget remember password functionality for the time being.

piuk I don't seem to be able to find the verifier link anywhere anymore: https://blockchain.info/wallet/support-pages

Did you remove it?

The support link was removed but the page is still up (https://blockchain.info/wallet/verifier). Once the chrome extension is packaged for firefox (Easy bounty if someone wants to pick it up) the verifier will be depreciate. It's a hard sell convincing people the verifier is actually working and cannot be circumvent whereas a packaged extension is full proof.

Is this some sort of bug? (1Ny5LAo8pW6kk2oLpXouXuEFHH6wgbYaTD)

Seems to be a wrapping issue.