What is this I don't even
Jan. 11th, 2010 11:21 amAnd here I thought nothing could top this...
...I just found this gem on the page where I order my lunch coupons.
"Change password: The system can't distinguish between the letters I, L and the number 1, and the letter O and the number 0. You may not use these symbols."
...what?
...what???
...WHAT??????
...I just found this gem on the page where I order my lunch coupons.
"Change password: The system can't distinguish between the letters I, L and the number 1, and the letter O and the number 0. You may not use these symbols."
...what?
...what???
...WHAT??????
no subject
Date: 2010-01-11 10:22 am (UTC)That reeks of manual psw changes done by a monkey.
no subject
Date: 2010-01-11 10:41 am (UTC)no subject
Date: 2010-01-11 10:53 am (UTC)It's quite common for outsourcing companies to just throw manpower at a problem they don't have the skills to solve programmatically*, and if that means lots of people sat at desks with reams of printouts from one system on one side and text entry screen on the other ... then that's what happens.
Yeah, yeah, I know, [[citation needed]]
This is one of the many reasons why I thought it was INSANE for the last company for whom I worked to have their help desk system hosted by the outsourcing company off shore. That thing could have been (and quite probably was) hosted on a 486 under someone's desk as far as they knew.
* GNU Aspell does not think this is a word
no subject
Date: 2010-01-11 10:58 am (UTC)Alternative explanation: Someone's having a big laugh at the (sadly few) people who will read that message and actually understand how utterly nonsensical a claim it is.
no subject
Date: 2010-01-11 11:27 am (UTC)no subject
Date: 2010-01-11 11:39 am (UTC)But still.
;)
no subject
Date: 2010-01-11 11:43 am (UTC)no subject
Date: 2010-01-11 12:32 pm (UTC)But that's just stupid. And impossible.
What it probably is, is that the system designers anticipated that people would write down their passwords, and didn't want to allow them to confuse themselves by using ambiguous characters.
I used to have this very problem back in the day when I'd write down my save state password for various NES games. I had to learn pretty early on that unless I used special notation and looked carefully when recording my password, I could lose many hours of progress.
no subject
Date: 2010-01-11 12:58 pm (UTC)no subject
Date: 2010-01-11 01:29 pm (UTC)no subject
Date: 2010-01-11 02:05 pm (UTC)no subject
Date: 2010-01-11 02:28 pm (UTC)That's fairly clever stuff.
Date: 2010-01-11 03:12 pm (UTC)For his unit and mission, inputting a wrong password or passphrase in a transmission cost a significant amount of money, compromised operational security, and could even cause entire sets of codebooks to have to be invalidated and replaced, at significant cost, or for a set of operational security authentication exchanges to have to be made, at significant time and cost.
Oftentimes, non-technical officers were able to have their own private access to the teletype system in order to "better secure" their communications (read: they were using the TTY to run betting pools / arrange for furloughs / whatever) and had the ability to order TTY operators to set the officer's passwords to whatever the officer damned well pleased.
Oftentimes these kinds of things would be accomplished through writing out - or typing out on some ancient typewriter the officer had hauled around through his entire career - a set of orders for the officer's personal functionary.
No matter how many birds or clusters or stars were on the lapel of an officer, however, they absolutely cannot order a machine to over-ride its' own limitations.
Thus, the operational commandment that the system cannot distinguish between the letters I, L, and the number 1, and 0 and O, and you may not use these symbols in your password.
no subject
Date: 2010-01-11 03:16 pm (UTC)For Computer Sciences Corporation.
Every day was an adventure in head-asplodey.
no subject
Date: 2010-01-11 09:00 pm (UTC)I used to confuse my math teachers with that. :)
no subject
Date: 2010-01-11 09:03 pm (UTC)no subject
Date: 2010-01-11 09:38 pm (UTC)no subject
Date: 2010-01-16 02:27 pm (UTC)