Enhanced security for a secure token code
Patent 5485519 Issued on January 16, 1996. Estimated Expiration Date: 
May 25, 2013. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.
May 25, 2013. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesUnitary, self-contained card verification and validation system and method Identification card and authentication system therefor Self verifying transaction card with disabling capability Patent #: 5180902 InventorAssigneeApplicationNo. 067517 filed on 05/25/1993US Classes:713/185, Using record or token235/379, Banking systems235/380, Credit or identification card systems235/382, Permitting access340/5.26, Code rotating or scrambling340/5.74, Access to electrical information380/30, Public key713/159Including intelligent tokenExaminersPrimary: Gregory, Bernarr E.Attorney, Agent or FirmInternational ClassH04L 009/32AbstractA method and apparatus are provided for enhancing security for a private key or other multibit secure token code stored in a token by (a) assuring that the secure token code is not stored in the token except for short intervals when the token is actually in use by an authorized user and (b) by assuring that the secure token code cannot be obtained from the token except by an authorized user. This is accomplished by algorithmically combining a PIN or other secret code memorized by the user with the secure token code, either in the token or at a suitable terminal, to generate a meaningless multibit sequence/token secret which is stored in the token. The multibit sequence stored in the token is selected such that when it is algorithmically combined with the secret memorized code known only to the user, either in the token or at a terminal, it produces the private key or other secure token code. | |
