Re:AmEx: "We discourage the use of special characters becaus...
by Alex3917 on Sunday February 07, 2010 @08:56PM
(#1108688)
Couldn't you just salt the user database with 100 fake accounts for every one real account, so that way as soon as someone tries to log into a fake account the bank knows its system has been compromised?
Re:AmEx: "We discourage the use of special characters becaus...
by pingou on Monday February 08, 2010 @11:10AM
(#1109968)
Interesting idea, but you need to save in your database which accounts are fake accounts, so if an hacker get an access to the database he will get this information too, unless this information is saved elsewhere.
Re:AmEx: "We discourage the use of special characters becaus...
by dmoney on Sunday February 07, 2010 @09:36PM
(#1108742)
They could block whatever location the fake account was accessed from, but the attacker could try one account each from lots of different locations (perhaps through a botnet). For this to be useful the bank would have to lock all account access from everywhere when a fake one was accessed.
Re:AmEx: "We discourage the use of special characters becaus...
by calcnerd256 on Sunday February 07, 2010 @11:30PM
(#1108948)
at which point the only thing to say is "denial of service"
Re:AmEx: "We discourage the use of special characters becaus...
by staticshock on Monday February 08, 2010 @08:37AM
(#1109662)
Additionally, the mined usernames / passwords could still be used to brute force other banking / credit card web sites.
And if you think it's unlikely that AmEx will ever lose control of their user database, you clearly have not been paying attention the last few years.