Why the first working day of the month sucks today
-
... because it's password changing day. Our domain policy is that passwords expire every 45 days :thumbsdown:. You start getting warnings at 30 days. Since I despise annoying warning messages, I make a habit of changing my password on the first workday of the month. To change my password, I have to enter the old one four times, and the new one 13 times: - Corporate intranet web site to actually change the domain password. - Change Blotus Goatse X| password to match domain, otherwise Bad Things Happen to your e-mail. - Change password on 3 scheduled tasks on desk computer. - Change password on scheduled task on department build machine.
Software Zen:
delete this;The best way to secure a system is to make it such a PITA that no one will ever use it. Microsoft tried that with Vista, but could only get it partially secure. They're trying again with Weven and have Christian beta testing the attempt.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Copywriting Services
-
... because it's password changing day. Our domain policy is that passwords expire every 45 days :thumbsdown:. You start getting warnings at 30 days. Since I despise annoying warning messages, I make a habit of changing my password on the first workday of the month. To change my password, I have to enter the old one four times, and the new one 13 times: - Corporate intranet web site to actually change the domain password. - Change Blotus Goatse X| password to match domain, otherwise Bad Things Happen to your e-mail. - Change password on 3 scheduled tasks on desk computer. - Change password on scheduled task on department build machine.
Software Zen:
delete this;Drives me nuts too. With the scheduled tasks, providing they don't need to access any network shares etc you could always create a local user with a non-expiring password and run the tasks as that user. That's what I've done before for defrag tasks etc.
-
Drives me nuts too. With the scheduled tasks, providing they don't need to access any network shares etc you could always create a local user with a non-expiring password and run the tasks as that user. That's what I've done before for defrag tasks etc.
In my role as the DSJB*, I use scheduled tasks a lot. All of mine unfortunately require domain credentials. * DSJB = Departmental Shit Job Boy
Software Zen:
delete this; -
... because it's password changing day. Our domain policy is that passwords expire every 45 days :thumbsdown:. You start getting warnings at 30 days. Since I despise annoying warning messages, I make a habit of changing my password on the first workday of the month. To change my password, I have to enter the old one four times, and the new one 13 times: - Corporate intranet web site to actually change the domain password. - Change Blotus Goatse X| password to match domain, otherwise Bad Things Happen to your e-mail. - Change password on 3 scheduled tasks on desk computer. - Change password on scheduled task on department build machine.
Software Zen:
delete this; -
Our password rules: >= 6 characters, must include at least one each upper case letter, lower case letter, numeric digit, and punctuation character. Passwords may not be re-used within the last 50 passwords. The end result is that almost everyone develops a formula for their password that includes the numeric month: "01:Crap", "Crap.01", that sort of thing.
Software Zen:
delete this;Gary Wheeler wrote:
Passwords may not be re-used within the last 50 passwords.
OMG :omg: Luckily we have only 10 to deal with
-
Gary Wheeler wrote:
Passwords may not be re-used within the last 50 passwords.
OMG :omg: Luckily we have only 10 to deal with
I think they were trying to prevent people from changing their password 'N' times in order to clear the list, and then restore their original password.
Software Zen:
delete this; -
Our password rules: >= 6 characters, must include at least one each upper case letter, lower case letter, numeric digit, and punctuation character. Passwords may not be re-used within the last 50 passwords. The end result is that almost everyone develops a formula for their password that includes the numeric month: "01:Crap", "Crap.01", that sort of thing.
Software Zen:
delete this;I used to use a book or song title, using upper case for the first letter of each word and replacing vowels with numeric digits: A=4, E=3, i=1, o=0 (i don't have a replacement for u). You could use '!' in place of 'i' and try to always use a title with 'i' in it. What ever i happened to be listening to on my MP3 player when the change password prompt showed up usually became my password for the month.
Pete
-
... because it's password changing day. Our domain policy is that passwords expire every 45 days :thumbsdown:. You start getting warnings at 30 days. Since I despise annoying warning messages, I make a habit of changing my password on the first workday of the month. To change my password, I have to enter the old one four times, and the new one 13 times: - Corporate intranet web site to actually change the domain password. - Change Blotus Goatse X| password to match domain, otherwise Bad Things Happen to your e-mail. - Change password on 3 scheduled tasks on desk computer. - Change password on scheduled task on department build machine.
Software Zen:
delete this;Gary Wheeler wrote:
have to enter the old one four times, and the new one 13 times
Messy :wtf: That's not fair. :confused:
Believe Yourself™
-
I think they were trying to prevent people from changing their password 'N' times in order to clear the list, and then restore their original password.
Software Zen:
delete this; -
... because it's password changing day. Our domain policy is that passwords expire every 45 days :thumbsdown:. You start getting warnings at 30 days. Since I despise annoying warning messages, I make a habit of changing my password on the first workday of the month. To change my password, I have to enter the old one four times, and the new one 13 times: - Corporate intranet web site to actually change the domain password. - Change Blotus Goatse X| password to match domain, otherwise Bad Things Happen to your e-mail. - Change password on 3 scheduled tasks on desk computer. - Change password on scheduled task on department build machine.
Software Zen:
delete this; -
Gary Wheeler wrote:
have to enter the old one four times, and the new one 13 times
Messy :wtf: That's not fair. :confused:
Believe Yourself™
Gandalf - The White wrote:
Messy
Agreed. The bits and pieces that need the password are sufficiently awkward to automate that I've never written a script or an application to deal with the problem.
Software Zen:
delete this; -
Did that a week ago myself: Domain: 1 + 2 Legacy Intranet: 1 + 1 Time collection: 1 + 2 Irrational Clearquest: 0 + 2 Irrational Train ReqPro (1 + 2) * 5 Total: 9x old, 17x new X| OTOH 90 days, 24 non-repeats.
3x12=36 2x12=24 1x12=12 0x12=18
Ewww. Clearquest and 'Train ReqPro'? Sucks to be you :-D.
Software Zen:
delete this; -
Is that check performed on each application? I suspect they underestimate the power of human stupidity. What they need is a you can't use any password from the last 6 years type policy. :rolleyes:
3x12=36 2x12=24 1x12=12 0x12=18
They also limit how often you are allowed to change your password. With my current password 'formula', I'm good until I retire.
Software Zen:
delete this; -
I used to use a book or song title, using upper case for the first letter of each word and replacing vowels with numeric digits: A=4, E=3, i=1, o=0 (i don't have a replacement for u). You could use '!' in place of 'i' and try to always use a title with 'i' in it. What ever i happened to be listening to on my MP3 player when the change password prompt showed up usually became my password for the month.
Pete
I'd laugh if you were listning to something with a name like Pink Floyd's "Several Species of Small Furry Animals Gathered Together in a Cave and Grooving with a Pict" when the password change prompt turned up!
-
The best way to secure a system is to make it such a PITA that no one will ever use it. Microsoft tried that with Vista, but could only get it partially secure. They're trying again with Weven and have Christian beta testing the attempt.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Copywriting Services
Christopher Duncan wrote:
They're trying again with Weven and have Christian beta testing the attempt.
That's a guaranteed big success. :)
My .NET Business Application Framework My Home Page My Younger Son & His "PET"
-
Ewww. Clearquest and 'Train ReqPro'? Sucks to be you :-D.
Software Zen:
delete this;Gary Wheeler wrote:
Ewww. Clearquest and 'Train ReqPro'? Sucks to be you Big Grin.
Could be worse, and it was... Dev recently moved to SVN from clearcase (ordinary documents are still in it though, and it sucks less than using SharedPointOfFailure for that). The Irrational FoulNet service recently got axed; it made all of the above seem good. A few years ago I experimented with Disfunctional Tester; which got sacked because after doing the initial script development I found myself wasting several hours every other week having to reinstall the POS. :wtf: I'm hoping the rumor about senior management wanting to axe the irrational stuff over the next few years is true. :cool: I'm also hoping they'll remember the lessons from the FoulNet shutdown and won't initially go to users telling us that we have to manually migrate any data we want to keep. With contractual requirements to keep data for X years after the contract terminates you can imagine the reception they got at the first users meeting about the shutdown. :doh:
3x12=36 2x12=24 1x12=12 0x12=18
-
I'd laugh if you were listning to something with a name like Pink Floyd's "Several Species of Small Furry Animals Gathered Together in a Cave and Grooving with a Pict" when the password change prompt turned up!
:laugh: I have a vague memory of Pearl Jam's 'Elderly woman behind the counter in a small town' playing when a password change came up, but i try to limit the length of my password to at most 14 characters, and in cases like this, I will check the rest of the album for a more suitable title.
Pete
-
I used to use a book or song title, using upper case for the first letter of each word and replacing vowels with numeric digits: A=4, E=3, i=1, o=0 (i don't have a replacement for u). You could use '!' in place of 'i' and try to always use a title with 'i' in it. What ever i happened to be listening to on my MP3 player when the change password prompt showed up usually became my password for the month.
Pete
Pros: Your password is easy to remember Cons: you can end up replacing your vowels with numbers everywhere.
Pete
-
Gary Wheeler wrote:
Ewww. Clearquest and 'Train ReqPro'? Sucks to be you Big Grin.
Could be worse, and it was... Dev recently moved to SVN from clearcase (ordinary documents are still in it though, and it sucks less than using SharedPointOfFailure for that). The Irrational FoulNet service recently got axed; it made all of the above seem good. A few years ago I experimented with Disfunctional Tester; which got sacked because after doing the initial script development I found myself wasting several hours every other week having to reinstall the POS. :wtf: I'm hoping the rumor about senior management wanting to axe the irrational stuff over the next few years is true. :cool: I'm also hoping they'll remember the lessons from the FoulNet shutdown and won't initially go to users telling us that we have to manually migrate any data we want to keep. With contractual requirements to keep data for X years after the contract terminates you can imagine the reception they got at the first users meeting about the shutdown. :doh:
3x12=36 2x12=24 1x12=12 0x12=18
Dan Neely wrote:
Dev recently moved to SVN from clearcase
Our corporate 'standard' for source control is ClearCase. We successfully made a business case for maintaining our own source control (SourceSafe, stop laughing, dammit!) since we have a substantial body of code stored, a reliable automatic build process, and there was no business justification for mingling our code with the corporate code. Besides, I let it be known that ClearCase sucked ass.
Software Zen:
delete this; -
Dan Neely wrote:
Dev recently moved to SVN from clearcase
Our corporate 'standard' for source control is ClearCase. We successfully made a business case for maintaining our own source control (SourceSafe, stop laughing, dammit!) since we have a substantial body of code stored, a reliable automatic build process, and there was no business justification for mingling our code with the corporate code. Besides, I let it be known that ClearCase sucked ass.
Software Zen:
delete this;I think CC might still be the officially preferred solution here; but I heard they're trying to push everyone on the VSS server to SVN... AFAIK the svn server started out as one dev team doing it behind ITs back and eventually enough stuff ending up on it that they had to take it over as an official server. I know that's where the VSS server came from. My project ditched CC over a series of epic fails relating to VS2k8 integration and Rational 7.1 series tools having a new installer that couldn't be automated and didn't work reliably. Eventually the boss got disgusted with how much of his budget trying to make it work was wasting and ordered the switch.
3x12=36 2x12=24 1x12=12 0x12=18
