Live data from Hacker News

You have exactly three passwords, don't you?

pcmag.com

61–70 of 86 posts

Re: You have exactly three passwords, don't you?

#61
post #57

I thought the second part of his conclusion was a bit hasty: "... and change all your logins every six months at least." Does he have any idea how impractical this is? If I could even remember every login I ever made, it would probably take more than 12 hours to do the manual labor of changing the password for them. No thank you!

Forced changing of passwords every x months is pretty common in the workplace, especially if the company is Windows based. The problem is it's so easy to make your passwords be +1, then +2, etc. I've worked at places that detected that pattern and didn't allow it, so I would just hold down the shift key and iterate anyway, yielding +!, then +@, +#, etc. So even forcing your users to change their passwords will most l…

biometrics will still require a fallback for any general purpose system. For example, you can't require fingerprints because there's a chance you'll get users without fingers. You can't require retinal scans because there's a chance you'll get users without eyes. You could probably ask the user to spit and check their DNA, but there's a higher chance of spreading disease that way. Eventually you'll need a fallback of a password/key, and if I were an attacker, I'd always attack the fallback (it's often the least well thought out part of auth).

Re: You have exactly three passwords, don't you?

#64

Yes. This is why I use a password hash function. The exact Hash function is in my head (and only my head), although it requires a lookup table for random bits. The lookup table is typically a poem, (when I was younger, I would use digits of pi, but I consider that insecure now), but can really be any sequence of words about 50+ that I can reproduce pretty much instantaneously. The exact hash algorithm is my secret, b…

How do you deal with the url if it can change? For example, you register for example.com on http://register.example.com and then login on https://login.example.com and in the future they may change it to https://examplelogin.com/auth/ Or what if the company changes name? For example, I used to log into my bank on http://wamu.com and now they are bought by Chase so it's http://chase.com

I employ a similar tactic, and I can't recall ever one single site that I use changing its name. If it happened, I would then just change the password to reflect the name change, but it would be so infrequent that I'm not worried about it.

Re: You have exactly three passwords, don't you?

#65
post #23
post #12

Earlier quoted context omitted.

Out of curiosity, what's keeping you from switching banks? If my bank did this, I'd switch immediately. Any bank that shows that level of concern for my finances doesn't deserve to be controlling them.

If you work in the US, you tend not to have that luxury with your 401k. Your employer picks the financial institution and you're stuck with it. See also health insurance.

Mention your concern to your employer. It may come to nothing, but if another provider was offering better terms anyway...

Re: You have exactly three passwords, don't you?

#66
I used to keep a list of individual passwords in a GPG-encrypted container. Then I would copy-pasta them around, as needed. I realized this is just a huge security hole, particularly since I use ClipX (multi-clipboard tool, shows a clipboard history on Ctrl+Shift+V). Also, GPG would mysteriously eat the file on one machine every now and then.

Now I mostly use pwdhash.com and three or so tiers of passwords. Works well. I still have the GPG file, but I use it mostly for keeping track of my gibberish answers to dumb security questions ("who was your senior prom date/where did you meet your wife").

Re: You have exactly three passwords, don't you?

#69
post #57

I thought the second part of his conclusion was a bit hasty: "... and change all your logins every six months at least." Does he have any idea how impractical this is? If I could even remember every login I ever made, it would probably take more than 12 hours to do the manual labor of changing the password for them. No thank you!

Forced changing of passwords every x months is pretty common in the workplace, especially if the company is Windows based. The problem is it's so easy to make your passwords be +1, then +2, etc. I've worked at places that detected that pattern and didn't allow it, so I would just hold down the shift key and iterate anyway, yielding +!, then +@, +#, etc. So even forcing your users to change their passwords will most l…

There's always a really simple solution to those rules: post-its.
Post reply on HN