4 ms·
I think people get the need for a password, it's just that for the average office job, you have something like at least half a dozen different passwords, with d
by imgabe 17y ago
I think people get the need for a password, it's just that for the average office job, you have something like at least half a dozen different passwords, with different complexity requirements and different reset schedules. At work I have different passwords for:
Windows login
Expense report system
Timesheet system
Employee information system (where I can view my pay stub, w2, etc)
401(k) provider
Insurance provider
Various ftp or other file sharing services for shuttling data back and forth with clients.
And that's in addition to the all the normal passwords I have for personal stuff. What's worse is most of that is used infrequently so the login process never has a chance to sink into muscle memory. The login process is pretty much forgot/reset password every time I use it.
- shade 17y agoI run into this a lot and it's quite frustrating, so I just gave up and started keeping everything in a Keepass database. Works well enough.
- ghfdrvtsyup 17y agoIf you have that many passwords, why not make some sort of base password and then riff off of the base password for everything that needs access (and have a mental sequence for when an item needs a reset)? If your base password is at the highest complexity requirement, the only thing you need to remember is the individual sequences. I do this for my passwords and it's been working for me for years ...
- imgabe 17y agoThat's more or less what I do. Not everyone cottons on to this scheme though. With the logins I might use once every 6 months or so, it can still be hard to remember which variation I'm on, especially if it's a "three tries then you're locked out" system.
- itgoon 17y agoWorth every penny: http://passwordsafe.sourceforge.net/ http://passwordsafe.sourceforge.net/