At 11:22 -0800 on 01/08/2010, Charles Mills wrote about Re: y2k10
problem with credit cards in Germany:
But isn't the problem being described backwards? Is the external symptom
expired cards not being recognized as expired, or is it valid cards being
treated as though expired? Assuming the latter, the problem would seem to be
not that an expiration date is being misinterpreted but rather that today's
date is being misinterpreted. The card "knows" it expires in 2010 but
"thinks" today's date is 8 January 2016. If so, you can't "fix" the machines
(other than to provide the mag stripe workaround), you have to "fix" the
cards by reprogramming or reissuing them. There's no "window" solution
possible; the only solution is fixing the chips. Am I wrong?
Yes you are. The machines can be fixed to temporally send a year of
x'0A' in lieu of the x'10' which is being misinterpreted as 2016 (ie:
16 years into 20xx). The x'0a' would then be only 10 years.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
