Live data from Hacker News

Password Chart

passwordchart.com

31–40 of 47 posts

Re: Password Chart

#31
Use undefinedundefinedundefinedundefinedundefinedundefinedundefinedundefinedundefinedundefinedundefined as your password.

That happens if Cookies are disabled.

Re: Password Chart

#32
Ugh, garbage. Use a HMAC with a master password and a parameter (e.g. the site name) to generate a site specific password. Forget about shitty crypto.

My humble attempt (based on others work): http://python.ca/nas/tmp/pw.html

Edit: just to be clear, the page linked above needs to be hosted on a server you trust and served by something like SSL. Do not use it directly over HTTP and expect some security.

Re: Password Chart

#33

SuperGenPass is a much better, simpler, and safer alternative, IMO. http://supergenpass.com

I've been using PwdHash. It's basically the same thing, but it's a Firefox addon. It will automatically hash a password field with the domain if you start the password with "@@" or hit F2. It also has a bunch of guards to warn you if you're entering your password in a field that might be insecure.

https://www.pwdhash.com/

Re: Password Chart

#35

Another easier and more secure is to use a sha1 hash on every password you generate and just use that as your password.

It depends what your defending against and what your original password is.

If the purpose is to turn a short password into something more secure it is pointless. As tptacek is always saying; Sha1 is cheap. It is trivial to incorporate it into an attack :)

Your better off choosing a random long sentence as your password. Easier to remember and much more secure.

Re: Password Chart

#36
Why the hell one opens a website to choose password and serve it over clear-text (HTTP)?

Isn't that ironic? Trying to make something secure by actually making it totally insecure?

(Before someone jumps, even it's JS it doesn't mean safe against MITM as someone can inject JS before it loads and send all keystrokes to another server)

Re: Password Chart

#37

Why the hell one opens a website to choose password and serve it over clear-text (HTTP)? Isn't that ironic? Trying to make something secure by actually making it totally insecure? (Before someone jumps, even it's JS it doesn't mean safe against MITM as someone can inject JS before it loads and send all keystrokes to another server)

Seems like the real threat here is training a user that it's ok to use third party web sites to tell them what password to use. That's a very bad habit.

Re: Password Chart

#38

SuperGenPass is a much better, simpler, and safer alternative, IMO. http://supergenpass.com

1Password is quite good for the Mac: http://agilewebsolutions.com/products/1Password

It integrates well with Firefox & Safari, and will sync over wi-fi to an iPhone for an encrypted backup.

Post reply on HN