|
Bah! Humbug!
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
How many times? Just two times?So he was a twotimer?
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Oliver Twist for that one at another time; 'tis a Bleak House indeed that Nicholas Nickleby wouldn't carol at Christmas.
Software Zen: delete this;
|
|
|
|
|
from Wikipedia:Quote: The 45-chapter novel was published in 31 weekly instalments in Dickens's new literary periodical titled All the Year Round. From April 1859 to November 1859, Dickens also republished the chapters as eight monthly sections in green covers. All but three of Dickens's previous novels had appeared only as monthly instalments. The first weekly instalment of A Tale of Two Cities ran in the first issue of All the Year Round on 30 April 1859. The last ran thirty weeks later, on 26 November.[1]
Quote: The new weekly magazine had its debut issue on Saturday 30 April 1859, featuring the first instalment of Dickens's A Tale of Two Cities.[5][6] The launch was an immediate success.
“So well has All the Year Round gone that it was yesterday able to repay me, with five per cent. interest, all the money I advanced for its establishment (paper, print etc. all paid, down to the last number), and yet to leave a good £500 balance at the banker's![4]
You are not worthy to lick the mud-stained boot soles of Oliver Twist, let alone besmirch the great Dickens' good name 
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
I have been testing WAVE and Siteimprove Accessibility Checker (Chrome extensions) and they seem very promising.
So, if you have experience with making websites 508 compliant, then please let me know which tools you and your team use to validate your site and pages, etc.
Thanks.
WCAG 2.0 Conformance | Section508.gov[^]
How to Meet WCAG 2.0[^]
|
|
|
|
|
I use drugs to make it go away.
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
|
|
You are right, such a policy serves no real purpose. If someone's account gets hacked then their data is compromised at that point. So changing the password in a week will not do much good.
|
|
|
|
|
We have an ISO, which forces us to change password every 3 months and keep history of eight 'ages', and of course it must be a complex password...
The only result is that now all manage a text/excel file to keep tracking of the 8 'ages' and complexity... also all creates password based on a pattern...
I feel so safe...
The first thing I done after the first period is remove this from my user...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
So change your password every month to My_ridiculous_password_1 through My_ridiculous_password_12 and then start over from the beginning.
|
|
|
|
|
Head of IT at another company I work for sent me a login for one of their systems... the password? W3bl0g1n!
|
|
|
|
|
Nice.
What was the name of the company again?
|
|
|
|
|
|
Jörgen Andersson wrote: My_ridiculous_password_1 through My_ridiculous_password_12
Where I am now had the setting so it wouldn't let you re-use the last 9 passwords until they realized that the majority of employees were just using My_easy_password_1 to My_easy_password_0 then starting over at 1.
So the fix? Change it to not allow you to use the last 20 passwords! Bet you can't guess what changed.
|
|
|
|
|
RJOberg wrote:
So the fix? Change it to not allow you to use the last 20 passwords! Bet you can't guess what changed.
The obvious solution is to not allow numbers at the end or start of a password. Of course that just leads to people using things like my1password, my2password, etc. So obviously you also have to require the first four characters of the password to be different each time as well.
|
|
|
|
|
Oh, there are many solutions: one of my favorites is to require a percentage of all letters to change to force the user to use a completely new password each time. Depending on how that is implemented, the user can just shift the entire password one character left or right and fool the entire mechanism.
Mostly this is a game. It is "wily" network administrators against their own users who endeavor to circumvent the network administrators. You'll notice, while being adversaries in this battle, both are missing the true enemy lurking trying to find a way in!
|
|
|
|
|
Wait, wait... Hold on, if they are salting and hashing the passwords, how can they possibly know if X% of characters changed each time? I mean, you can store the last 10 hashes to compare against, but no good hashing system should give them any possible idea of the number of characters that did or did not change each time. There may be a much bigger problem here than dumb password policy.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: The first thing I done after the first period is remove this from my user...
Ummmm... pregnancy or hysterectomy?
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
|
It's their server, so they're right, so you have to deal with it. It is, however, your right to complain bitterly to whomever will listen.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Exactly. I've been a contractor (Consultant) for most of my 45 year it IT. Early on I learned two things;
1. Behave like a mercenary, if they want you to kill it, as long as its not illegal, unethical or immoral, kill it.
2. They can pay me now or they'll pay me later, either way I get paid.
Every one of my clients were happy with me.
|
|
|
|
|
|
Such passwords will be written down. If someone changes the lock on their front-door each month, I'd be inclined to say that they haven't looked into securing the house at all and are merely copying others.
I'd also be testing their password recovery/reset options at least twice a month 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
It depends. If they're in an industry that has applicable cyber regulation then they may absolutely need to do this to maintain compliance.
Thirty days seems a little on the sharp side, but that's all contingent on the laws in the primary operational area for the company.
Also, the general "wisdom" on the security side is that complex passwords that are changed on a regular basis are still a fundamental security practice. The zeitgeist has not shifted on that; though there are a number of increasingly vocal individuals that advocate for a less complex strategy, they don't represent the viewpoint of the community as a whole.
Use KeePass to keep it easy. I just use the "Generate from last" and go.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
