News for hackers. Stuff that matters.
Re:Anonymous speaks: the inside story of the HBGary hack by gaius on Wednesday February 16, 2011 @02:56AM (#2225592)
That's not a technical problem tho', it's social/organizational. If you make passwords too complex and change too often and enforce it in software, you simply encourage people to write them down, save them in the browser, etc. Or people will be phoning the helpdesk every day to get a reset, and security as a whole will be discredited as a waste of time. NOTE: I'm not saying that it is a waste of time, but the best policies in the world are of no help if people simply refuse to follow them.

The truth is passwords are not like toothbrushes - they don't actually need replacing every three months. Only if some event has occurred (e.g. a sysadmin leaving the company). They don't get weaker over time. Why not let someone keep the same decently strong password for as long as they're an employee? I guarantee this will be actually more secure.

Re:Anonymous speaks: the inside story of the HBGary hack by mjb on Wednesday February 16, 2011 @06:31AM (#2225990)
> They don't get weaker over time.

Passwords do get weaker all the time, to the extent that they are used in multiple places. Changing the password on different systems on different schedules discourages password reuse. It also means the 'active' password is much less likely to be the password the employee used on a random news site they logged into once to comment.

There is obviously a balance to be had, because frequent rotations may encourage people to choose weaker passwords, but there is certainly value in expiring passwords.

Re:Anonymous speaks: the inside story of the HBGary hack by gaius on Wednesday February 16, 2011 @06:40AM (#2226005)
Changing the password on different systems on different schedules discourages password reuse.

But it doesn't, it really doesn't. It just results in people buttonholing sysadmins in the corridor asking "when are you going to stop dicking around and implement SSO?". Not long after that, people just start ignoring security advice altogether.

Re:Anonymous speaks: the inside story of the HBGary hack by mjb on Wednesday February 16, 2011 @07:54AM (#2226168)
You are right about reuse across multiple internal systems not being strongly discouraged.

Where it does discourage reuse is across multiple systems, and with websites. Making me change my corporate password every 90 days is an effective way to ensure that I don't use my current password across a large number of websites. Maybe I'd go to the effort of making my gmail password the same as my corporate password. The password on that random news site account I forgot about? No ways.

It's not a panacea, but password expiry does effectively limit the spread of passwords in many cases.

Re:Anonymous speaks: the inside story of the HBGary hack by Sandman on Wednesday February 16, 2011 @04:07AM (#2225758)
Your last paragraph actually has a very good point - why do companies insist on changing the employee passwords every month? Chances are, if somebody got hold of your password, he/she is not going to wait a month before using that knowledge, right? So, really, I'm curious as to why most companies have this policy.
Re:Anonymous speaks: the inside story of the HBGary hack by count on Thursday February 17, 2011 @10:20AM (#2231185)
Passwords historically got weaker over time, but not in the sense that 'if he got your password hes not going to wait to use it'. They weaken in their hashed form. It used to be (still is, really) trivial to score the passwd file of a system, and get all the hashes of passwords, but no plaintext.

By changing passwords every N months, you eliminated the ability of someone to crack the hashes and obtain a cleartext password where they previously only had a hash.

That time window has gotten absurdly short, however...and with Pass the Hash and MITM, I don't even need your password anymore :(

Re:Anonymous speaks: the inside story of the HBGary hack by gaius on Wednesday February 16, 2011 @05:29AM (#2225893)
Because, let's be honest, most "security consultants" are people who couldn't make it as sysadmins, and they've no idea what they're doing.