Hacker News Reader

The server is misconfigured: it's missing intermediate certificates in its chain. Chrome 6.x should be able to work around this on all platforms at the cost of making the site slower.

Additionally, the server is open to prefix attacks.

For a bank, that's a pretty miserable state of affairs.

Chrome 6.x should be able to work around this on all platforms at the cost of making the site slower.

This sounds, uh, weird. Got a link to more information? I'd like to see the rationale for having the browser subvert misconfigured servers; this would seem to undermine the already precarious SSL state we're in.

Chrome 6 uses NSS on all platforms and NSS will download missing intermediate certificates via HTTP, if the URL is given in an AIA extension.

This is pretty much standard browser behaviour I'm afraid. One of the many unfortunate realities of the web.

Works for me, with current Chrome dev (6.0.472.25). Which version do you have?

Probably... I've got 5.0.375.125 beta. It's not new, but it's at least from this year.

I'd expect VeriSign to be on top of this.

Probably, Chrome's (dev version?) bug.