Patent Application
20200127837
The present disclosure relates to computing systems, and, in particular, to computing systems supporting secure transactions.
Various types of data processing systems support user transactions where the user is required to submit some type of authorization code. For example, an Interactive Voice Response (IVR) system may request a user to provide a payment card for a transaction along with a Personal Identification Number (PIN) code, which may serve as an authorization code for the transaction. The PIN code, however, may be transmitted over the communication network without any protection from eavesdropping by one or more hostile parties.
In some embodiments of the inventive subject matter, a method comprises receiving, from a data processing system, a request for an authorization code, the authorization code comprising a sequence of a plurality of characters, generating a plurality of one-time passwords, wherein respective ones of the plurality of one-time passwords correspond to respective ones of the plurality of characters, generating a plurality of modified passwords, wherein generating the plurality of modified passwords comprises concatenating, for each of the plurality of one-time passwords and each of the plurality of characters, the one of the plurality of characters to the corresponding one of the plurality of one-time passwords, generating a plurality of hash values, wherein generating the plurality of hash values comprises performing a hash function on each of the plurality of modified passwords, and sending the plurality of hash values to the data processing system.
In other embodiments of the inventive subject matter, a method comprises sending a request for an authorization code to a mobile device, the authorization code comprising a sequence of a plurality of characters, generating a plurality of one-time passwords, wherein respective ones of the plurality of one-time passwords correspond to respective ones of the plurality of characters, generating, for each of the plurality of one-time passwords, a plurality of modified passwords, wherein generating the plurality of modified passwords comprises concatenating the respective one of the plurality of one-time passwords to each of a plurality of numerical digits of a base ten numeral system, generating a first plurality of hash values, wherein generating the first plurality of hash values comprises performing a hash function on each of the plurality of modified passwords for each of the plurality of one-time passwords, receiving a second plurality of hash values from the mobile device corresponding to the plurality of one-time passwords, respectively, comparing, for each of the second plurality of hash values, the respective one of the second plurality of hash values to respective ones of the first plurality of hash values generated for the respective one of the one-time passwords corresponding to the respective one of the second plurality of hash values, determining, for each of the second plurality of hash values, a match between the respective one of the second plurality of hash values and one of the first plurality of hash values generated for the respective one of the one-time passwords corresponding to the respective one of the second plurality of hash values, and determining the sequence of the plurality of characters of the authorization code based on the ones of the first plurality of hash values generated for the respective ones of the one-time passwords corresponding to the respective ones of the second plurality of hash values that match the respective ones of the second plurality of hash values.
In further embodiments of the inventive subject matter, an electronic device includes a processor and a memory coupled to the processor and comprising computer readable program code embodied in the memory that is executable by the processor to perform operations comprising: receiving, from a data processing system, a request for an authorization code, the authorization code comprising a sequence of a plurality of characters, generating a plurality of counter values, the plurality of counter values corresponding to a plurality of one-time passwords, respectively, wherein respective ones of the plurality of one-time passwords correspond to respective ones of the plurality of characters, performing, for each of the plurality of counter values, a Hash-Based Message Authentication Code (HMAC) protocol, the HMAC protocol having a secret key as a first input and a respective one of the plurality of counter values as a second input, generating a plurality of modified passwords, wherein generating the plurality of modified passwords comprises concatenating, for each of the plurality of one-time passwords and each of the plurality of characters, the one of the plurality of characters to the corresponding one of the plurality of one-time passwords, generating a plurality of hash values, wherein generating the plurality of hash values comprises performing a hash function on each of the plurality of modified passwords, and sending the plurality of hash values to the data processing system
Other methods, systems, devices, articles of manufacture, and/or computer program products according to embodiments of the inventive subject matter will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, articles of manufacture, and/or computer program products be included within this description, be within the scope of the present inventive subject matter, and be protected by the accompanying claims. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
Other features of embodiments will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure embodiments of the present invention. It is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
As used herein, the term “data processing system” includes, but it not limited to, a hardware element, firmware component, and/or software component.
As used herein, the term “mobile terminal” or “mobile device” may include a satellite or cellular radiotelephone with or without a multi-line display; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA or smart phone that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. Mobile terminals or mobile devices may also be referred to as “pervasive computing” devices.
Some embodiments of the inventive subject matter stem from a realization that user transactions that involve the transmission of an authorization code, such as a Personal Identification Number (PIN), may result in the authorization code being unprotected and subject to being compromised due to eavesdropping by one or more hostile parties. An electronic device, such as a mobile terminal, and a data processing system, such as an Interactive Voice Response (IVR) system may each be provisioned with a capability to generate one-time passwords. In some embodiments, the electronic device and the data processing system may each have synchronized counter and may share a secret key. A hash-Based Message Authentication Code (HMAC) protocol may be used to generate the one-time passwords at both the electronic device and the data processing system based on counter values from the synchronized counter and the shared secret key. For each input character of an authorization code, for example, the electronic device may append the input character to a one-time password and perform a hash function on the resultant string. The hash value generated may then be transmitted to the data processing system, which may generate all possible hash values corresponding to combinations of the one-time password with all possible values of one character of an authorization code. For example, if each character of an authorization code corresponds to one numerical digit of a base ten numeral system, then the data processing system may generate ten different hash values corresponding to the ten combinations of the one-time password with digits 0-9. The data processing system may then compare the hash values generated locally with the received hash value to determine the character of the authorization code that was transmitted from the electronic device. Embodiments of the inventive subject matter may, therefore, provide a two phase cryptographic hash protection for transmitting characters of an authorization code based on the use of one-time passwords and hashing the one-time passwords with respective digits of the authorization code. As a result, the authorization code may be better protected from hostile parties attempting to eavesdrop on the communications between the electronic device and the data processing system.
Referring now to
Referring now to
As shown in
The authentication protocol module 325 may be configured to manage communications between a data processing system 180, such as an IVR system, and another entity, such as mobile terminals or devices 120 and 150 to facilitate a secure transaction in which a use authorization code is protected using one-time passwords. In some embodiments, the authentication protocol module 325 may support the use of one or more authentication standards, such as those supported by the Initiative for Open Authentication (OATH). OATH supports two open authentication standards: Time-based One-time Password Algorithm (TOTP) and HMAC-based One-time Password Algorithm (HOTP). When authenticating using TOTP, a user may enter a code that changes every thirty seconds. The code may be generated using HMAC in which a shared secret key and a timestamp are used as inputs. The timestamp may change every thirty seconds. The use of a timestamp in TOTP involves the use of a synchronized clock between the authenticating system and the devices, terminals, etc. being authenticated. HOTP works similarly to TOTP, but an authentication counter is used instead synchronized clock. Similar to the clocks, the counters on both the authenticating system and the devices, terminals, etc. being authenticated do need to remain synchronized.
The OTP generator module 330 may be configured to generate one-time passwords using, for example in some embodiments, the HMAC protocol in which counter values from the synchronized counter 335 and a secret key 340 are used as inputs.
The synchronized counter module 335 may be configured to generate counter values in synchronization with a corresponding counter on another entity, such as a mobile terminal or device 120 and 150.
The secret key 340 may be a value that is generated in concert with another entity, such as a mobile terminal or device 120 and 150. The agreed upon secret key between an authenticating entity, such as a data processing system 180, and an entity being authenticated, such as mobile terminals or devices 120 and 150, may be used as an input value to the HMAC protocol.
The hash generator 345 may be configured to perform a hash function on the passwords output from the OTP generator 330 as respectively modified with possible characters of an authorization or authentication code that may be entered by a user of a mobile terminal or device, such as the mobile terminals or devices 120 and 150 of
Although
Referring now to
The processor 440 communicates with the memory 435 via an address/data bus. The processor 440 may be, for example, a commercially available or custom microprocessor. The memory 435 is representative of the one or more memory devices containing the software and data used to facilitate protection of a user authorization code using one-time passwords, in accordance with some embodiments of the present invention. The memory 435 may include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash, SRAM, and DRAM.
As shown in
The secure IVR module 470 may be configured to manage communications between the mobile terminal 400 and a data processing system 180, such as an IVR system to facilitate a secure transaction in which a use authorization code is protected using one-time passwords. The secure IVR module 470 may include an authentication protocol module 475, an OTP generator module 480, a synchronized counter module 485, a secret key 490, and a hash generator module 495. The authentication protocol module 475, OTP generator module 480, synchronized counter module 485, secret key 490, and hash generator module 495 may be analogs of the authentication protocol module 325, the OTP generator module 330, the synchronized counter module 335, the secret key 340, and the hash generator module 345.
The authentication protocol module 475 may support the use of one or more authentication standards, such as TOTP and HOTP supported by OATH.
The OTP generator module 480 may be configured to generate one-time passwords using, for example in some embodiments, the HMAC protocol in which counter values from the synchronized counter 485 and a secret key 490 are used as inputs.
The synchronized counter module 485 may be configured to generate counter values in synchronization with a corresponding counter on another entity, such as the synchronized counter 335 on a data processing system 180, such as an IVR system.
The secret key 490 may be a value that is generated in concert with another entity, such as a data processing system 180, which may be an IVR system. The agreed upon secret key between an authenticating entity, such as a data processing system 180, and an entity being authenticated, such as mobile terminals or devices 120 and 150, may be used as an input value to the HMAC protocol. Thus, the secret key 490 and the secret key 340 represent the agreed upon key value between a data processing system 180, such as an IVR system (authenticating or authorizing entity), and a mobile terminal or device 120, 150 (entity being authenticated or authorized).
The hash generator 345 may be configured to perform a hash function on the passwords output from the OTP generator 330 as respectively modified with characters of an authorization or authentication code entered by a user of a mobile terminal or device, such as the mobile terminals or devices 120 and 150 of
Although
Computer program code for carrying out operations of data processing systems, mobile terminals, and/or electronic devices discussed above with respect to
Moreover, the functionality of the mobile terminals or devices 120 and 150 of
The operations of blocks 505, 510, 515, and 520 may be performed in various orders in accordance with different embodiments of the inventive concept. For example, upon receiving a first character or digit of a PIN code, the mobile terminal or device 120, 15, 400 may generate a one-time password (block 505), modify the one-time password by appending the first digit of the PIN code thereto (block 510), generate a hash value based on the modified one-time password (block 515), and then send the hash value to the data processing system, e.g., the IVR system (block 520). These operations may then be repeated for the next digit in the PIN code sequence. In other embodiments, multiple one-time passwords may be generated in advance and all digits or characters of an authorization or authentication code may be received before the modified passwords and hash values are generated.
Referring now to
The operations of blocks 605, 610, 615, 620, 625, 630, and 635 may be performed in various orders in accordance with different embodiments of the inventive concept. For example, at block 605, a one-time password may be generated for a first character or digit of a PIN code using the HMAC protocol with a synchronized counter value and a secret key value as inputs. At block 610, modified one-time passwords may be generated corresponding to the one-time password appended with each of the possible values of the first digit of the PIN code. For example, if the PIN code may take on values of numerical digits of the base ten numeral system, then ten modified one-time passwords may be generated corresponding to the one-time password appended with each of the digits 0-9. Hash values may be generated using the same hash function used to generate the hash values on the mobile terminal or device 120, 150 for the modified one-time passwords at block 615. When the hash value corresponding to the first digit of the authorization or authentication code is received at block 620 from the mobile terminal or device 120, 150, then a comparison is made at block 625 between the received hash value and the ten hash values generated for the modified one-time password for the first digit of the authorization code to determine at match at block 630. Based on the matching hash value, the first character or digit can be determined for the PIN code at block 635. The operations of blocks 605, 610, 615, 620, 625, 630, and 635 can be repeated for each of the sequence of characters or digits of the authorization or authentication code.
Embodiments of the inventive subject matter may, therefore, provide a mechanism for communicating personal user information, such as PIN codes and the like, in a protected manner through use of one-time passwords and hash functions that may be difficult for hostile parties to decode if the information is intercepted on a communication path between a user device, such as a mobile terminal or device, and a data processing system, such as a transaction processing system and/or IVR.
In the above-description of various embodiments of the present disclosure, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or contexts including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product comprising one or more computer readable media having computer readable program code embodied thereon.
Any combination of one or more computer readable media may be used. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Peri, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Like reference numbers signify like elements throughout the description of the figures.
The corresponding structures, materials, acts, and equivalents of any means or step plus function elements in the claims below are intended to include any disclosed structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated.
