Re:AmEx: "We discourage the use of special characters becaus...
by amexexployee on Sunday February 07, 2010 @08:29PM
(#1108650)
The reason for the character limitation is a lot more straightforward - on the backend its stored on a very legacy system (in plaintext.. but I didn't tell you that), and to increase the length of the database field would cost 7 figures.
[ Parent
| on HN ]
Re:AmEx: "We discourage the use of special characters becaus...
by rms on Sunday February 07, 2010 @09:17PM
(#1108718)
Wikileaks, dude...
Re:AmEx: "We discourage the use of special characters becaus...
by thaumaturgy on Sunday February 07, 2010 @09:46PM
(#1108758)
It's COBOL, isn't it? (Not being sarcastic; that's the only system I can think of that would cost 7 figures to change a field length in the database.)
Re:AmEx: "We discourage the use of special characters becaus...
by ShabbyDoo on Sunday February 07, 2010 @10:08PM
(#1108794)
At a past job, the mainframe "copybooks" required an extra digit for certain price fields (cars never used to cost > 100K). It was a months-long project which required tons of coordination with other clients systems. One could argue that the 27 other ways the company didn't have its house in order made the project costly, but the 30+ hour flatfile data conversion was an inherent part of the plan.
Edit: Legacy COBOL, of course.
Re:AmEx: "We discourage the use of special characters becaus...
by ams6110 on Monday February 08, 2010 @09:36AM
(#1109774)
This doesn't make sense to me. Any "legacy" systems involved surely pre-date online account access by consumers. They would not have ANY password field or even any notion of a "user" in the sense of someone who is able to access a specific account.
This would have all been built as a web application talking to the backend through a CICS gateway of some sort. The web app would be responsible for authenticating the user, not the legacy mainframe system.
Re:AmEx: "We discourage the use of special characters becaus...
by rbanffy on Monday February 08, 2010 @10:57AM
(#1109946)
They probably keep the password in an 8-char record that used to store something else.
Re:AmEx: "We discourage the use of special characters becaus...
by stgarrity on Monday February 08, 2010 @02:10AM
(#1109249)
why not just throw a hash function in the middle? technically you're not increasing the search space for a brute-force attack (but that's not the goal), but you are probably slightly increasing entropy. and most of all, you avoid bad PR like this. :)
that said, it's probably still quite expensive and this PR isn't that bad.
Re:AmEx: "We discourage the use of special characters becaus...
by eru on Tuesday February 09, 2010 @04:25PM
(#1113378)
Interesting post. But it doesn't make the case that the title promises.
Re:AmEx: "We discourage the use of special characters becaus...
by cliveholloway on Monday February 08, 2010 @09:46AM
(#1109796)
Why not just hash the password and use the first 8 characters of the hash? That would at least stop things from being stored in plain text.
Re:AmEx: "We discourage the use of special characters becaus...
by ErrantX on Monday February 08, 2010 @07:05AM
(#1109550)
C'mon - why is the troll/joke comment being upvoted? It doesn't add much to the discussion :(
Re:AmEx: "We discourage the use of special characters becaus...
by billswift on Monday February 08, 2010 @07:14AM
(#1109557)
It's being upvoted because it is probably true, despite being entertainingly worded.