Works for me with that version.

Make sure if you're using blocking extensions (Noscript, etc) that they are allowing frames and JS from gstatic.com and google.com.

Also make sure WebGL is working (I dunno if it uses it or not but it looks 3D) in chrome://gpu/).

A quick Google search (yeah, not exactly unbiased) doesn't seem to show anything in the top results. I found a reddit thread if you want to look through it, though.

I think the idea is you'd let the user know. "This password would take approximately 4.5 days to crack. For your security, you will be required to change this password after 3 days. Alternatively, you may pick a longer, more secure password to lengthen this interval (for example, a 16 character password will only require a change after XX years)." Or something.

This is for desktop... not sure about the mobile ports of Chrome.

Bad guys can already do this right now, and the url still shows the bank's domain, so non-technically inclined users are no less protected.

Technically inclined users probably never navigated to the url in the first place.

Your specific example is a flaw in the specific website, and there is little Chrome can do when a website is coded in a insecure way that persists across all browsers (and web standards).

You type in the URL just like normal. This only affects how urls are displayed while you navigate around. Clicking on the "chip" shows the full url and allows you to edit it as normal.

The "chip" is just the domain name, which is trivial to work out client-side.

I imagine it is to help combat phishing. Seeing store.steampowered.com with the green lock will, for sure, mean you're actually logging onto Steam, while any attempt to phish with a different domain will show something different (and many phishing domains are quite different, they just try to prey off of people not knowing how to isolate the domain).

I don't even see how that line is relevant to anything. If you're accessing it through VPN, the link from the VPN to Hulu is still going to be unencrypted due to lack of SSL.

640K ought to be enough for anybody.

Going after the people who wrote the software will have no effect, since they do not and cannot control how the software is used. What happened to Napster etc all but ensured that was how future file sharing software would be written.

It is in the works. You can check their progress by opening chrome://flags/#high-dpi-support and enabling the experiment.

Noscript and many similar tools allow selective blocking of JS based on domain... 99.9% of ads are served from dedicated domains so you just block them and the main site is unaffected.

There is a reason lights already don't alert you to how long until they turn green. If you know when a light is going to turn green, you'll be ready to immediately speed through. But the guy crossing the other way is trying to beat the red light. Suddenly your chances of getting into an accident go way up. Without knowing when the light turns green, it will probably take you a bit longer to get going.

encfs looks really cool in that it will transparent encrypt files and they look like regular files to dropbox etc, but they can go on any file system and encfs will still recognize the encryption when they come out. So that's always an option.

Sadly, the Windows port of it that I've tried is really buggy. I had to use it inside a Linux VM to really use it.