You could use a nonce when you have two password boxes, so that the two boxes match, but the hash cannot be reversed by someone who just sees the sequence. However, this would mean the hash is different each time, so it would be no good for confirming your password is correct before you login. For the registration case, just show a tick when the fields are equal. Or just wait for the round-trip, it's not that bad. Fr…
Someone at my company looked at password requests last week, and it looks like about 50% of login attempts fail.
Chroma-Hash: a sexy, non-reversible, live visualization of password field input
41–50 of 70 posts
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#42Earlier quoted context omitted.
Um, what? The old method is a warning symbol or a checkmark to ensure the password fields match. Replacing that nice, intuitive, more accessible feature with this would be, excuse me, retarded. And it's not just colorblind people who would suffer. Do you really want to spend brain cycles trying to figure out if you're looking at the same shade of blue?
It's not very well presented in the demo (there's no need for the Confirm inputbox), but the point is not for password creation, but for login. From the author's github page ( http://github.com/mattt/Chroma-Hash/tree/master ): Chroma-Hash displays a series of colored bars at the end of field inputs so you can instantly see if your password is right... Your password will display the same sequence each time, so you can…
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#43You could use a nonce when you have two password boxes, so that the two boxes match, but the hash cannot be reversed by someone who just sees the sequence. However, this would mean the hash is different each time, so it would be no good for confirming your password is correct before you login. For the registration case, just show a tick when the fields are equal. Or just wait for the round-trip, it's not that bad. Fr…
Someone at my company looked at password requests last week, and it looks like about 50% of login attempts fail.
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#44This is pretty, but non-reversible it isn't. The colors update with every keystroke, making it easy to determine letter by letter, which keys are being pressed. This is a significant hole in many situations (screencasts, recorded presentations, or anywhere someone can point a camera at your screen). Simple fix: Wait for 300ms of keyboard inactivity before computing the colors. This way you only get the colors when th…
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#45What an incredibly good idea! It would probably not be too difficult to build this as a firefox plugin, so that all password fields (or all blanked out input fields) on the web will automatically get this feature... Anyone? :-)
It seems to rely on jQuery, so a Firefox plugin, greasemonkey script, or Opera userjs would need to bundle or src jQuery. Whether or not that is okay I will leave on the table for debate and discussion. :)
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#46I'd love it if my keyring showed me the color combo for my password at each site --- then if my computer is stolen my passwords don't go with it; but when I get to a site I haven't logged in to for a few months, I don't have to try ten different passwords to remember which one I used.
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#47Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#48Neat css trick, though!
Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#49Re: Chroma-Hash: a sexy, non-reversible, live visualization of password field input
#50Earlier quoted context omitted.
I don't see how this follows -- the colours are changing with each keypress (just as an md5 digest would change if you added a letter to the message) but surely you cannot know the key pressed without brute-forcing / breaking the hash, which is computationally impractical? He's also scraping the hash for a run of 6 hex characters, so surely there's quite a few colour collisions for different hashes, making it even ha…
Because you can see the color code at each step, it's easy to compare results very quickly, even by hand. Did I get letter 1 right? Ok, move on to letter two, try each key until the colors match the recording. Do this for each step. At most, you have to try about 64 key presses to crack each letter. Also, because each step is only 1 character different, it's very unlikely that you will get collisions, even with a tru…
Amusement aside, it also allows a cracking attempt to be done without running up against server authentication. Even if the same series of color patterns can occur for multiple passwords, the quantity of attempted server authentications is greatly reduced.