WO2004006536A2 - Method of preventing unauthorized distribution and use of electronic keys using a key seed - Google Patents

Method of preventing unauthorized distribution and use of electronic keys using a key seed Download PDF

Info

Publication number
WO2004006536A2
WO2004006536A2 PCT/US2003/021088 US0321088W WO2004006536A2 WO 2004006536 A2 WO2004006536 A2 WO 2004006536A2 US 0321088 W US0321088 W US 0321088W WO 2004006536 A2 WO2004006536 A2 WO 2004006536A2
Authority
WO
WIPO (PCT)
Prior art keywords
key
host
electronic
seed
transaction
Prior art date
Application number
PCT/US2003/021088
Other languages
French (fr)
Other versions
WO2004006536A3 (en
Inventor
Alexander Medvinsky
Original Assignee
General Instrument Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by General Instrument Corporation filed Critical General Instrument Corporation
Priority to JP2004519897A priority Critical patent/JP5295479B2/en
Priority to EP03763224.7A priority patent/EP1520392B1/en
Priority to MXPA05000472A priority patent/MXPA05000472A/en
Priority to AU2003256388A priority patent/AU2003256388A1/en
Priority to CA002491049A priority patent/CA2491049C/en
Publication of WO2004006536A2 publication Critical patent/WO2004006536A2/en
Publication of WO2004006536A3 publication Critical patent/WO2004006536A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/083Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/06Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/061Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0866Generation of secret information including derivation or calculation of cryptographic keys or passwords involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0869Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H04L9/0897Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56Financial cryptography, e.g. electronic payment or e-cash
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/061Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption

Definitions

  • the present invention relates to the field of electronic interaction cryptology. More specifically, the present invention relates to the field of electronic interactions that require the use of electronic keys.
  • Cryptography is the study of techniques and applications that can be used to protect sensitive information, maintain privacy in communications, authenticate users in transactions, and perform other security measures in information transfer.
  • Cryptanalysis is the study of how to compromise, or defeat, cryptographic mechanisms.
  • a hacker for example, is a person who studies and practices cryptanalysis.
  • Cryptology is the discipline of cryptography and cryptanalysis combined.
  • Cryptography allows people to carry over the confidence found in the physical world to the electronic world, thus allowing people to do business electronically without undue worries of deceit, breaches in privacy, or lack of security.
  • the perpetual increase of information transmitted electronically has led to an increased reliance on cryptography.
  • cryptography techniques help make web sites secure and electronic transmissions safe. This allows people to do online banking, online trading, and make online purchases with their credit cards without worrying that their account information is being compromised. Cryptography is very important to the continued growth of the Internet and electronic commerce.
  • Cryptography is also used in phones, televisions, and a variety of other common household items. Without cryptography, hackers could much more readily access someone else's private e-mail, listen in on phone conversations, tap into cable companies and acquire free cable service, or break into bank accounts.
  • a major emphasis in cryptography includes encryption and decryption.
  • Encryption is the transformation of data into a form that is apparently unintelligible and extremely difficult, if not impossible to access in a reasonable amount of time without the appropriate knowledge, e.g., a key. Keys will be explained further below.
  • Decryption is the reverse of encryption; it is the transformation of encrypted data back into an intelligible form.
  • all of the data transmitted between the computers where the data is stored and where it is received must be encrypted. The receiving computers must then be capable of decrypting the data.
  • a key is usually a sequence of random or pseudorandom bits. Thus, a person without the right key cannot send, receive, or interpret someone else's sensitive information. Keys are also used for electronic authentication, digital signatures, digital timestamps, and for other electronic security purposes. As used hereafter and in the appended claims, unless otherwise specifically denoted, the term "electronic transaction" will be used to refer expansively to all possible electronic communication that requires the use of one or more keys.
  • secret-key cryptography also referred to as symmetric session cryptography
  • symmetric session cryptography the same key is used for both encryption and decryption.
  • the main challenge of symmetric session cryptography is getting the sender and receiver to agree on the symmetric session key without anyone else discovering the symmetric session key. If they are in separate physical locations, for example, they must trust a courier, a phone system, or some other transmission medium to prevent the disclosure of the symmetric session key.
  • An overhears or intercepts the key in transit can later read, modify, and forge all messages encrypted or authenticated using that key.
  • the generation, transmission, and storage of keys are called key management. All cryptosystems must deal with key management issues. Because all keys in 80113-0359 (D2828.1)
  • a symmetric system cryptosystem must preferably remain secret, symmetric session cryptography often has difficulty providing secure key management, especially in open systems with a large number of users.
  • symmetric session keys and private keys can be stored on the hard drive or other non- volatile storage unit of a user's computer or other electronic device, such as a cable set-top box (STB).
  • STB cable set-top box
  • the user can then use these keys to securely communicate electronically.
  • the storage of keys on a user's computer or other device in the control of the user presents various problems.
  • the user can copy a key residing on his or her computer or other device, for example, and distribute the copied key to other people. These people may then be able to assume the user's electronic identity and send or receive information that is intended for use by the original user only. Such situations could occur in cases where a person pays a monthly subscription rate to receive content over the Internet or via a cable television system. If this person distributes the key that allows access to the paid content, multiple users could receive the content without paying for it.
  • a second problem with storing keys on a user's computer or other electronic device involves tampering and theft. An unauthorized person could copy a user's 80113-0359 (D2828.1)
  • a host could be a computer that is connected to the Internet, for example, or a STB connected to a cable network.
  • a host could be a computer that is connected to the Internet, for example, or a STB connected to a cable network.
  • the term "host” will be used to refer expansively to any electronic device used by a user to communicate electronically.
  • fraud management detects fraud after the fraud has already occurred and does little to prevent the illegal use of keys from happening in the first place. Fraud management also requires additional cost and overhead and is not foolproof.
  • tamper-resistant key storage device Another protection against the illegal distribution and use of keys is the use of a tamper-resistant key storage device that would make it preferably infeasible for a hacker to extract and then copy keys.
  • the device preferably destroys its contents if ever opened and shields against attacks using electromagnetic radiation.
  • tamper-resistant key storage including key-containing hosts that are activated by the use of a special physical key or by the detection of a unique physical trait of an authorized user.
  • the present invention provides a method of generating an electronic key used in an electronic transaction.
  • the method comprises executing a one-way function on a host that derives the electronic key from a key seed saved in a non- volatile storage unit of the host and a unique host identification that is resident on the host.
  • the function is preferably executed each time an electronic transaction requiring the use of the electronic key is made.
  • Another embodiment of the present invention provides a system for generating an electronic key used in an electronic transaction.
  • the system comprises a host that has a unique host identification resident on the host for making the electronic transaction, a non- volatile storage unit of the host for storing a key seed, and a one-way function for deriving the electronic key from the key seed and the host identification.
  • the host preferably executes the one-way function each time an electronic transaction requiring the use of the electronic key is made.
  • Fig. 1 is a block diagram of an exemplary electronic interaction configuration that could be used to implement an embodiment of the present invention. 80113-0359 (D2828.1)
  • Fig. 2 is a flow chart illustrating an exemplary method of symmetric session cryptography with which the present invention can be implemented.
  • FIG. 3 is a flow chart illustrating an exemplary method of public-key cryptography with which the present invention can be implemented.
  • Fig. 4 is a flow chart illustrating a method of the present invention that entails storing a key seed, instead of a key, in a host's non- volatile storage unit and then deriving a key based on the key seed and the host's unique identification.
  • Fig. 5 is a flow chart illustrating an exemplary method of the present invention as applied to public-key cryptography.
  • Fig. 6 is a flow chart illustrating a second exemplary method of the present invention as applied to public-key cryptography.
  • Fig. 7 is a flow chart illustrating an exemplary method of the present invention as applied to symmetric session cryptography.
  • the present invention provides a method and system whereby a host saves a key seed instead of a key in a non- volatile storage unit.
  • the key seed will be explained in more detail below in connection with Fig. 4.
  • a user runs a one-way function on the host using the key seed and a host identification (host ID) as inputs to the function.
  • host ID host identification
  • the one-way function only generates a valid key on the host for which the use of the key is intended. Because the key itself is not stored in the non- volatile storage unit of the host, the key cannot be copied and distributed to other hosts.
  • Another advantage of the present invention is its relatively low economic cost of implementation.
  • Fig. 1 is a block diagram of an exemplary electronic interaction configuration that could be used to implement an embodiment of the present invention.
  • a host 100
  • a client or user, desiring to electronically interact 80113-0359 (D2828.1)
  • the host (100) can be a personal computer, server, automatic teller machine (ATM), cellular phone, cable or satellite set-top box (STB) or any other electronic device capable of electronic communication.
  • the server (101) can also be a personal computer, server, ATM, cellular phone, cable headend or any other electronic device capable of electronic communication.
  • the host (100) preferably contains a non- volatile storage unit (103) designed to function with or within the host (100).
  • the non- volatile storage unit (103) can be, for example, a hard drive, floppy disk, compact disk (CD), flash memory unit, or any other storage unit (103) capable of non- volatile storage.
  • a key seed (106) can be stored in the non-volatile storage unit (100).
  • the host (100) also preferably contains random access memory (RAM) (104) for temporary storage of information.
  • RAM random access memory
  • the RAM (104) could temporarily store a key generated by the function, for example.
  • the host also preferably contains a processor (105), such as a CPU for example, for running the function that generates a key.
  • the server (101) could also have a non-volatile storage unit (103), RAM (104), and a processor (105) that could be used in completing an electronic transaction with the host (100).
  • a protocol (102) is used to facilitate electronic communication between the host (100) and the server (101), as shown in Fig.l.
  • a protocol (102) is a formal set of conventions governing the format and control of interaction among electronic communication devices.
  • a protocol (102) is a method and system by which two dissimilar or non-identical electronic systems can communicate.
  • these protocols (102) that are used to ensure security and privacy in the exchange of information between electronic devices may be referred to as key management protocols (102).
  • key management protocols (102) Examples of possible key management protocols (102) that are currently in use are Kerberos, DOCSIS BPI+, and Internet Key Exchange (IKE).
  • the present invention can be implemented using any of these protocols (102) or any other protocol (102) that involves storing a key on a nonvolatile storage unit.
  • the present invention can be implemented using protocols (102) that allow for the private key seed to be randomly generated and for the public key to be derived from the private key.
  • Fig. 2 is a flow chart illustrating an exemplary method of symmetric session cryptography with which the present invention can be implemented. Although the method of Fig. 2 illustrates the encryption and decryption of confidential data, this method can be applied to any other type of electronic transaction using symmetric session cryptology.
  • the process begins with a client requesting confidential data from a server (120).
  • This request can be performed in a variety of ways including, but not limited to, selecting an option on a web page, sending e-mail, transmitting a request from a STB, making a phone call, or sending a letter on paper.
  • the server After the request for confidential data has been made, the server encrypts the data to be sent to the client using a symmetric session key (121). The server then electronically sends the encrypted data to the client's host (122).
  • the client's host attempts to decrypt the encrypted data using a key (123). Successful decryption depends on the key that the host uses to decrypt the data. In a symmetric session cryptosystem, the host will use a key that is identical to the key used by the server to encrypt the data. Thus, if the host's key matches the key used by the server (124), successful decryption and recovery of the requested data (125) is possible. However, if a host does not have or use a key to decrypt the encrypted data that is identical to the key used by the server, the encrypted data cannot be decrypted and is unreadable (126).
  • FIG. 3 is a flow chart illustrating an exemplary method of public-key cryptography with which the present invention can be implemented. Although the method of 80113-0359 (D2828.1)
  • Fig. 3 illustrates the encryption and decryption of confidential data, this method can be applied to any other type of electronic transaction using public-key cryptology.
  • the process begins with a client requesting confidential data from a server (120).
  • This request can be performed in a variety of ways including, but not limited to, selecting an option on a web page, sending e-mail, transmitting a request from a STB, making a phone call, or sending a letter on paper.
  • the server After the request for confidential data has been made, the server encrypts the data to be sent to the client using a public key (130) associated with the client requesting the confidential data. The server then electronically sends the encrypted data to the client's host (122).
  • the client's host attempts to decrypt the encrypted data using a private key that corresponds to the public key used to encrypt the confidential data (131). Successful decryption depends on the private key that the host uses to decrypt the data. In a public-key cryptosystem, the host uses a private key that is mathematically related to the public key used by the server to encrypt the data. Thus, if the host's private key is correctly correlated to the public key used by the server (132), successful decryption and recovery of the requested data (125) is possible. However, if a host does not have or use the correct private key to decrypt the encrypted data, the encrypted data is preferably not capable of being decrypted and is unreadable (126).
  • a symmetric session key for a symmetric cryptosystem or a private key for a public-key cryptosystem is stored on the host of a user, that user may attempt to share that secret or private key to allow others access to the communications from the server.
  • a symmetric session key for a symmetric cryptosystem or a private key for a public-key cryptosystem is stored on the user's host, someone without the user's consent may find a way to access the user's host and obtain the secret or private key so as to gain access to the confidential data being transmitted from the server to the authorized user.
  • FIG. 4 is a flow chart illustrating a method according to an embodiment of the present invention that entails storing a key seed, instead of a key, in a host's non- volatile storage unit to mitigate the chances that a user's key will be compromised, with or without the user's cooperation.
  • the process begins with a host preferably storing a key seed in a non- volatile storage unit (140).
  • the key seed is preferably a random bit sequence used to generate another bit sequence.
  • the key seed is used to generate a key, which is also a sequence of bits.
  • the key may be either a symmetric session key used in a symmetric cryptosystem or a private key used in a public-key cryptosystem.
  • the host runs a one-way function that generates a key (141) when the key is needed to perform an electronic transaction.
  • the key is preferably not stored in any non-volatile memory unit of the host and consequently, the key is not accessible to the user at any time. Rather, the key might be temporarily stored in random access memory (RAM), for example, which would make it difficult or even impossible for the client or anyone else to copy the key by accessing the client's host.
  • RAM random access memory
  • the one-way function is a function of two inputs — the key seed and a host identification (host ID).
  • the host ID is preferably a permanent and unique identifier resident in the host and is difficult or impossible to change without adversely affecting the operation of the host.
  • Most electronic host devices currently contain a unique electronic host ID that is generated and placed in the host device by its manufacturer. Where this host ID is stored and how it may be accessed will vary depending on the make and model of the host device. However, one of ordinary skill in the art, with the benefit of this disclosure, will be able to identify where the host ID is stored and how it can be accessed for use by an embodiment of the present invention given any particular host device.
  • a host ID may be generated by a dedicated algorithm that bases the host ID on information gathered from the host that defines or describes the hardware and configuration of the host device.
  • the command syntax can be modified to fit the language of the desired key management protocol. 80113-0359 (D2828.1)
  • the fact that the function that generates the key is one-way means that it is difficult, if not impossible, to derive the key seed from the key. For example, if given the key and a value of a new host LD a hacker could obtain the corresponding new value of the key seed, he or she could possibly derive new key seeds for many unauthorized hosts.
  • the function if the host has a correct key seed (142) and a correct host ID (143), the function produces a valid key (144) that can be used in electronic communication. However, if either the key seed or the host ID is wrong, the function generates an invalid key (145).
  • An exemplary application of the key generation process shown in Fig. 4 is the interaction of a client with a web site on the Internet. If, for example, a client orders monthly paid content from website, the website operators can send a key seed and a key- generating function to the client to install on his or her host. The function takes as inputs the client's host ID and the key seed. The host is queried for its ID by the function when needed. If the correct host ID and key seed are not accurately input to the function, the function will not generate a valid key. The client must preferably run this function and use the generated key every time he or she desires to obtain the monthly paid content.
  • the function only works with the client's host ID and key seed, it is difficult or impossible to transfer the function to a different host with a different host ID and obtain a valid key when the function is executed. This is because even if the client copies the key seed and function and distributes them to other people, they will not be able to generate a valid key because their host IDs are different than the host ID with which the function is designed to work and provide a valid key.
  • Fig. 5 is a flow chart illustrating an exemplary method of the present invention as applied to public-key cryptography. More specifically, Fig. 5 illustrates a 80113-0359 (D2828.1)
  • a key pair preferably consists of a private and public key.
  • a client initially generates a PKS (150) on his or her host.
  • the PKS is preferably randomly generated by the host.
  • the client then derives a private key from the PKS (151) using a one-way function with the PKS and host ID as inputs to the function.
  • the function can be called using a command found in the chosen key management protocol that employs public-key cryptography.
  • Protocol examples are Kerberos with PKINIT extension that allows support for public-key cryptography, Internet Key Exchange (IKE) and Transport Layer Security (TLS).
  • public key algorithms that may be used in combination with these functions include Elliptic Curve Digital Signature Algorithm (ECDSA), Elliptic Curve Diffie-Hellman (ECDH) and Elliptic Curve Authenticated Encryption Scheme (ECAES).
  • EDSA Elliptic Curve Digital Signature Algorithm
  • ECDH Elliptic Curve Diffie-Hellman
  • ECAES Elliptic Curve Authenticated Encryption Scheme
  • the Point-Order parameter is specific to Elliptic Curve cryptology. Each Elliptic Curve has its own value
  • the present invention does not depend on the choice of the PKGenO function.
  • the function is preferably fast enough to regenerate the private key every time an electronic transaction requires the use of a private key.
  • the client preferably derives a public key from the private key (152). This can be done by using a variety of mathematical functions known to cryptography.
  • the public key is then registered with a trusted authority (153).
  • the trusted authority is usually referred to as a Certifying Authority (CA). 80113-0359 (D2828.1)
  • the CA returns to the client a certificate attesting to the validity of the generated public key or stores the public key in a trusted database (154). Certificates are digital documents attesting to the binding of a public key to a client or other entity. Certificates allow verification of the claim that a specific public key does in fact belong to a specific client. They help prevent someone from using a phony key to impersonate someone else.
  • certificates contain a public key and a name.
  • a certificate might also contain an expiration date, the name of the CA that issued the certificate, a serial number, the digital signature of the certificate issuer, and perhaps other information.
  • CAs can be any trusted central administration willing to vouch for the identities of those clients to whom it issues certificates and their association with a given key. For example, a company may issue certificates to its employees, or a university to its students.
  • a Key Distribution Center (KDC) may for example be extended to include the functionality of a CA. KDCs are dedicated to key generation, verification, and distribution.
  • the client's host saves the randomly generated PKS in a non- volatile storage unit (155).
  • the PKS can now be used to generate the private key that is to be used in future electronic transactions.
  • Fig. 6 is a flow chart illustrating a second exemplary method of the present invention as applied to public-key cryptography. More specifically, Fig. 6 illustrates a method whereby a client preferably uses a randomly generated PKS stored in a non- volatile storage unit to generate a private key that he or she can use in an electronic transaction.
  • the process starts with a client's host reading the PKS from a non- volatile storage unit (160).
  • the client derives the same private key based on the stored PKS (151).
  • the client can now preferably use the private key in an electronic transaction (161). If, as shown in Fig. 6, the private key correlates correctly with the registered public key (162), the server and client can use the private and public key pair to 80113-0359 (D2828.1)
  • Fig. 7 is a flow chart illustrating an exemplary method of the present invention as applied to symmetric session cryptography. More specifically, Fig. 7 illustrates a method whereby a client preferably receives, stores, and uses a symmetric session key seed (SKS) to generate a symmetric session key that can be used to make an electronic transaction.
  • the client in this embodiment preferably generates a key that is identical to the key used by a server with which the client desires to make the electronic transaction.
  • the process starts with a client receiving a SKS from a KDC or other source (170).
  • the client preferably does not generate the key seed that is to be used to generate a key. Instead, the KDC sends the SKS to the client.
  • the client's host After the client's host receives the SKS from the KDC, the host stores the SKS in a non- volatile storage unit (171). To make an electronic transaction, then, the client reads the SKS from the non- volatile storage unit (172) and derives a symmetric session key from the SKS (173) by running a one-way function on the host with the SKS and host ID as inputs to the function.
  • the one-way function is preferably a program that is sent to the client by a KDC, server, or other source and is installed on the user's host.
  • the function can be called using a command found in the chosen key management protocol.
  • the syntax of the function call command might vary depending on the chosen key management protocol.
  • the function is preferably fast enough to regenerate the symmetric session key every time an electronic transaction requires the use of a symmetric session key.
  • the client can now preferably use the derived symmetric session key in an electronic transaction (174) with a server that also uses a symmetric session key.
  • a server that also uses a symmetric session key.
  • One method is for the KDC to execute the same one-way function that the host executes and generate the session key from the SKS. This method requires the KDC to have access to or a copy of the client's host ID.
  • the KDC can then send the generated symmetric 80113-0359 (02828.1)
  • the KDC can take the symmetric session key and encrypt it using a symmetric session key used by the server that is not known to any of the clients.
  • This encrypted symmetric session key along with the client and server identities and other related information, is called a ticket.
  • the ticket can be then sent to the client's host. The host cannot modify the ticket because it does not know the server's symmetric session key. The client can then send this ticket to the server. The server then uses its key to decrypt the ticket and extract its copy of the session key.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Storage Device Security (AREA)
  • Computer And Data Communications (AREA)

Abstract

A method and system for generating an electronic key used in an electronic transaction can be created by executing a one-way function on a host that derives the electronic key from a key seed saved in a on-volatile storage unit of the host and a unique host identification that is resident on the host. The function is preferably executed each time an electronic transaction requiring the use of the electronic key is made.

Description

80113-0359 (D2828.1)
TITLE OF THE INVENTION
Method of Preventing Unauthorized Distribution and Use of Electronic Keys Using a Key Seed
FIELD OF THE INVENTION
[0001] The present invention relates to the field of electronic interaction cryptology. More specifically, the present invention relates to the field of electronic interactions that require the use of electronic keys.
BACKGROUND OF THE INVENTION
[0002] Every day hundreds of thousands of people interact electronically. For example, people use electronic mail (e-mail) to correspond with one another and to send information. People and businesses rely heavily on networks of computers or other electronic devices to manage, protect, and transfer important information. Millions of dollars are electronically transferred daily via bank networks and automatic teller machines (ATMs). People use cellular phones and other wireless personal digital assistants (PDAs) to communicate and transfer information on a daily basis.
[0003] The advent of the Internet, comprised of millions of interconnected computers, has accelerated electronic interaction dramatically. The Internet allows nearly instantaneous communication and transfer of information to virtually anywhere in the world. The World Wide Web (www) is used for online business, data distribution, marketing, stock exchange, online banking, gaming, research, learning, and a myriad of other activities.
[0004] When parties interact face to face or by using a physical medium such as paper, it is relatively easy to authenticate the credentials of those who are interacting. For example, if a person walks into a bank and tries to make a withdrawal, the bank teller can ask for and verify his or her identification before giving the requested funds. A person's signature on a contract is considered sufficient to guarantee his or her approval of the contract. Likewise, if a person goes into a store and buys an item with a credit card, it is easy for a cashier to take precautions so as to be reasonably sure that the person is the true owner of that credit card. 80113-0359 (D2828.1)
[0005] However, in the realm of electronic interaction, such physical means of authentication cannot be used. People and businesses will not transfer funds, buy an item over the Internet, or otherwise manage and transfer confidential information using any electronic device unless they feel that their electronic interactions are secure and safe. Thus, in a world where decisions and agreements are communicated electronically, electronic techniques for providing authentication, security, and privacy are needed.
[0006] Cryptography is the study of techniques and applications that can be used to protect sensitive information, maintain privacy in communications, authenticate users in transactions, and perform other security measures in information transfer. Cryptanalysis is the study of how to compromise, or defeat, cryptographic mechanisms. A hacker, for example, is a person who studies and practices cryptanalysis. Cryptology is the discipline of cryptography and cryptanalysis combined.
[0007] Cryptography allows people to carry over the confidence found in the physical world to the electronic world, thus allowing people to do business electronically without undue worries of deceit, breaches in privacy, or lack of security. The perpetual increase of information transmitted electronically has led to an increased reliance on cryptography.
[0008] For example, cryptography techniques help make web sites secure and electronic transmissions safe. This allows people to do online banking, online trading, and make online purchases with their credit cards without worrying that their account information is being compromised. Cryptography is very important to the continued growth of the Internet and electronic commerce.
[0009] Cryptography is also used in phones, televisions, and a variety of other common household items. Without cryptography, hackers could much more readily access someone else's private e-mail, listen in on phone conversations, tap into cable companies and acquire free cable service, or break into bank accounts.
[0010] A major emphasis in cryptography includes encryption and decryption. Encryption is the transformation of data into a form that is apparently unintelligible and extremely difficult, if not impossible to access in a reasonable amount of time without the appropriate knowledge, e.g., a key. Keys will be explained further below. Encryption's 80113-0359 (D2828.1)
purpose is to ensure privacy by keeping information hidden from anyone for whom it is not intended, even those who have access to the encrypted data. Decryption is the reverse of encryption; it is the transformation of encrypted data back into an intelligible form. For a web site to be secure, for example, all of the data transmitted between the computers where the data is stored and where it is received must be encrypted. The receiving computers must then be capable of decrypting the data.
[0011] While modern cryptography is growing increasingly diverse, cryptography is fundamentally based on problems that are difficult to solve. A problem may be difficult because its solution requires the use of some secret knowledge. A problem may also be difficult because it is intrinsically difficult to complete, such as finding the factors of an extremely large number.
[0012] As explained above, successful encryption and decryption depend on some sort of secret knowledge ideally known by only the parties performing the encryption and decryption. This piece of knowledge is referred to as a key. A key is usually a sequence of random or pseudorandom bits. Thus, a person without the right key cannot send, receive, or interpret someone else's sensitive information. Keys are also used for electronic authentication, digital signatures, digital timestamps, and for other electronic security purposes. As used hereafter and in the appended claims, unless otherwise specifically denoted, the term "electronic transaction" will be used to refer expansively to all possible electronic communication that requires the use of one or more keys.
[0013] Currently, there are two types of cryptosystems: secret-key and public-key cryptography. In secret-key cryptography, also referred to as symmetric session cryptography, the same key is used for both encryption and decryption. The main challenge of symmetric session cryptography is getting the sender and receiver to agree on the symmetric session key without anyone else discovering the symmetric session key. If they are in separate physical locations, for example, they must trust a courier, a phone system, or some other transmission medium to prevent the disclosure of the symmetric session key. Anyone who overhears or intercepts the key in transit can later read, modify, and forge all messages encrypted or authenticated using that key. The generation, transmission, and storage of keys are called key management. All cryptosystems must deal with key management issues. Because all keys in 80113-0359 (D2828.1)
a symmetric system cryptosystem must preferably remain secret, symmetric session cryptography often has difficulty providing secure key management, especially in open systems with a large number of users.
[0014] As a result of the key management issues associated with symmetric session cryptography, public-key cryptography was developed. In public-key cryptography, each user has a public key and a private key. The public key is made public while the private key remains secret. Encryption is performed with the public key while decryption can only be performed with the private key. In public-key cryptography, the need for the sender and receiver to share secret information is eliminated; all communications involve only public keys, and no private key is ever transmitted or shared. Thus, it is not necessary to trust the security of some means of communicating a symmetric session key. Anyone can send a confidential message by just using public information. The message can only be decrypted using a private key, which is in the sole possession of the intended recipient.
[0015] One current disadvantage, however, with public-key cryptography is that the private key is linked mathematically to the public key. Therefore, it is possible to attack a public-key system by deriving the private key from the public key. However, this typically requires unreasonably large amounts of time or other resources.
[0016] Currently, symmetric session keys and private keys can be stored on the hard drive or other non- volatile storage unit of a user's computer or other electronic device, such as a cable set-top box (STB). The user can then use these keys to securely communicate electronically. However, the storage of keys on a user's computer or other device in the control of the user presents various problems. First, the user can copy a key residing on his or her computer or other device, for example, and distribute the copied key to other people. These people may then be able to assume the user's electronic identity and send or receive information that is intended for use by the original user only. Such situations could occur in cases where a person pays a monthly subscription rate to receive content over the Internet or via a cable television system. If this person distributes the key that allows access to the paid content, multiple users could receive the content without paying for it.
[0017] A second problem with storing keys on a user's computer or other electronic device involves tampering and theft. An unauthorized person could copy a user's 80113-0359 (D2828.1)
key if the user accidentally leaves his or her computer or other electronic device unattended or electronically unprotected. This unauthorized person could then send and receive potentially private information intended for the original user.
[0018] Thus, there is a need in the art for a method and system of preventing the unauthorized distribution and use of keys, including symmetric session keys and private keys, used in secure electronic communications. As used hereafter and in the appended claims, unless otherwise specifically denoted, the term "key" will be used to refer expansively to all possible electronic communication keys, including symmetric session keys and private keys.
[0019] There are several approaches to prevent unauthorized distribution and use of keys. One approach is to use fraud management. Fraud management is the detection of multiple active hosts who have assumed the same identity. A host could be a computer that is connected to the Internet, for example, or a STB connected to a cable network. As used hereafter and in the appended claims, unless otherwise specifically denoted, the term "host" will be used to refer expansively to any electronic device used by a user to communicate electronically.
[0020] There are several disadvantages of fraud management. First, fraud management detects fraud after the fraud has already occurred and does little to prevent the illegal use of keys from happening in the first place. Fraud management also requires additional cost and overhead and is not foolproof.
[0021] Another protection against the illegal distribution and use of keys is the use of a tamper-resistant key storage device that would make it preferably infeasible for a hacker to extract and then copy keys. The device preferably destroys its contents if ever opened and shields against attacks using electromagnetic radiation. There are many possible designs for tamper-resistant key storage, including key-containing hosts that are activated by the use of a special physical key or by the detection of a unique physical trait of an authorized user.
[0022] However, it is not currently economically viable to require that every user who wants to send and receive sensitive information have a tamper-resistant key storage device. Thus, this protection method is not preferable for large numbers of users.
[0023] The fact is that no security measure to combat unauthorized distribution and use of keys is completely foolproof. This is generally accepted in the field of cryptology. 80113-0359 (D2828.1)
Thus, implementing more than one security measure to prevent unauthorized key distribution and use would provide better protection than would using only one method of security.
SUMMARY OF THE INVENTION
[0024] In one of many possible embodiments, the present invention provides a method of generating an electronic key used in an electronic transaction. The method comprises executing a one-way function on a host that derives the electronic key from a key seed saved in a non- volatile storage unit of the host and a unique host identification that is resident on the host. The function is preferably executed each time an electronic transaction requiring the use of the electronic key is made.
[0025] Another embodiment of the present invention provides a system for generating an electronic key used in an electronic transaction. The system comprises a host that has a unique host identification resident on the host for making the electronic transaction, a non- volatile storage unit of the host for storing a key seed, and a one-way function for deriving the electronic key from the key seed and the host identification. The host preferably executes the one-way function each time an electronic transaction requiring the use of the electronic key is made.
[0026] Additional advantages and novel features of the invention will be set forth in the description which follows or may be learned by those skilled in the art through reading these materials or practicing the invention. The advantages of the invention may be achieved through the means recited in the attached claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings illustrate preferred embodiments of the present invention and are a part of the specification. Together with the following description, the drawings demonstrate and explain the principles of the present invention. The illustrated embodiments are examples of the present invention and do not limit the scope of the invention.
[0028] Fig. 1 is a block diagram of an exemplary electronic interaction configuration that could be used to implement an embodiment of the present invention. 80113-0359 (D2828.1)
[0029] Fig. 2 is a flow chart illustrating an exemplary method of symmetric session cryptography with which the present invention can be implemented.
[0030] Fig. 3 is a flow chart illustrating an exemplary method of public-key cryptography with which the present invention can be implemented.
[0031] Fig. 4 is a flow chart illustrating a method of the present invention that entails storing a key seed, instead of a key, in a host's non- volatile storage unit and then deriving a key based on the key seed and the host's unique identification.
[0032] Fig. 5 is a flow chart illustrating an exemplary method of the present invention as applied to public-key cryptography.
[0033] Fig. 6 is a flow chart illustrating a second exemplary method of the present invention as applied to public-key cryptography.
[0034] Fig. 7 is a flow chart illustrating an exemplary method of the present invention as applied to symmetric session cryptography.
[0035] Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0036] The present invention provides a method and system whereby a host saves a key seed instead of a key in a non- volatile storage unit. The key seed will be explained in more detail below in connection with Fig. 4. To obtain a desired key, a user runs a one-way function on the host using the key seed and a host identification (host ID) as inputs to the function. Thus, the one-way function only generates a valid key on the host for which the use of the key is intended. Because the key itself is not stored in the non- volatile storage unit of the host, the key cannot be copied and distributed to other hosts. Another advantage of the present invention is its relatively low economic cost of implementation.
[0037] Using the drawings, the preferred embodiments of the present invention will now be explained.
[0038] Fig. 1 is a block diagram of an exemplary electronic interaction configuration that could be used to implement an embodiment of the present invention. As shown in Fig. 1, a host (100) is used by a client, or user, desiring to electronically interact 80113-0359 (D2828.1)
with a server (101). The host (100) can be a personal computer, server, automatic teller machine (ATM), cellular phone, cable or satellite set-top box (STB) or any other electronic device capable of electronic communication. The server (101) can also be a personal computer, server, ATM, cellular phone, cable headend or any other electronic device capable of electronic communication. As used hereafter and in the appended claims, unless otherwise specifically denoted, the term "host" will be used to refer expansively to all possible electronic communication devices used by a client and the term "server" will be used to refer expansively to all possible electronic communication devices with which the client desires to communicate.
[0039] As shown in Fig. 1, the host (100) preferably contains a non- volatile storage unit (103) designed to function with or within the host (100). The non- volatile storage unit (103), as referred to hereafter and in the appended claims, can be, for example, a hard drive, floppy disk, compact disk (CD), flash memory unit, or any other storage unit (103) capable of non- volatile storage. According to an embodiment of the present invention and as shown in Fig. 1, a key seed (106) can be stored in the non-volatile storage unit (100).
[0040] The host (100) also preferably contains random access memory (RAM) (104) for temporary storage of information. The RAM (104) could temporarily store a key generated by the function, for example. The host also preferably contains a processor (105), such as a CPU for example, for running the function that generates a key.
[0041] As shown in Fig. 1, the server (101) could also have a non-volatile storage unit (103), RAM (104), and a processor (105) that could be used in completing an electronic transaction with the host (100).
[0042] Because the host (100) and the server (101) can be different systems, a protocol (102) is used to facilitate electronic communication between the host (100) and the server (101), as shown in Fig.l. A protocol (102) is a formal set of conventions governing the format and control of interaction among electronic communication devices. In other words, a protocol (102) is a method and system by which two dissimilar or non-identical electronic systems can communicate.
[0043] hi the field of cryptology, there are a number of different protocols (102) that can be used to ensure security and privacy in the exchange of information between the 80113-0359 (D2828.1)
host (100) and the server (101). Where the exchange is based on a key or keys, these protocols (102) that are used to ensure security and privacy in the exchange of information between electronic devices may be referred to as key management protocols (102). Examples of possible key management protocols (102) that are currently in use are Kerberos, DOCSIS BPI+, and Internet Key Exchange (IKE). The present invention can be implemented using any of these protocols (102) or any other protocol (102) that involves storing a key on a nonvolatile storage unit. In the case of public-key cryptography, the present invention can be implemented using protocols (102) that allow for the private key seed to be randomly generated and for the public key to be derived from the private key.
[0044] Fig. 2 is a flow chart illustrating an exemplary method of symmetric session cryptography with which the present invention can be implemented. Although the method of Fig. 2 illustrates the encryption and decryption of confidential data, this method can be applied to any other type of electronic transaction using symmetric session cryptology.
[0045] As shown in Fig. 2, the process begins with a client requesting confidential data from a server (120). This request can be performed in a variety of ways including, but not limited to, selecting an option on a web page, sending e-mail, transmitting a request from a STB, making a phone call, or sending a letter on paper.
[0046] After the request for confidential data has been made, the server encrypts the data to be sent to the client using a symmetric session key (121). The server then electronically sends the encrypted data to the client's host (122).
[0047] Once the client's host receives the encrypted data, it attempts to decrypt the encrypted data using a key (123). Successful decryption depends on the key that the host uses to decrypt the data. In a symmetric session cryptosystem, the host will use a key that is identical to the key used by the server to encrypt the data. Thus, if the host's key matches the key used by the server (124), successful decryption and recovery of the requested data (125) is possible. However, if a host does not have or use a key to decrypt the encrypted data that is identical to the key used by the server, the encrypted data cannot be decrypted and is unreadable (126).
[0048] Fig. 3 is a flow chart illustrating an exemplary method of public-key cryptography with which the present invention can be implemented. Although the method of 80113-0359 (D2828.1)
Fig. 3 illustrates the encryption and decryption of confidential data, this method can be applied to any other type of electronic transaction using public-key cryptology.
[0049] As shown in Fig. 3, the process begins with a client requesting confidential data from a server (120). This request can be performed in a variety of ways including, but not limited to, selecting an option on a web page, sending e-mail, transmitting a request from a STB, making a phone call, or sending a letter on paper.
[0050] After the request for confidential data has been made, the server encrypts the data to be sent to the client using a public key (130) associated with the client requesting the confidential data. The server then electronically sends the encrypted data to the client's host (122).
[0051] Once the client's host receives the encrypted data, it attempts to decrypt the encrypted data using a private key that corresponds to the public key used to encrypt the confidential data (131). Successful decryption depends on the private key that the host uses to decrypt the data. In a public-key cryptosystem, the host uses a private key that is mathematically related to the public key used by the server to encrypt the data. Thus, if the host's private key is correctly correlated to the public key used by the server (132), successful decryption and recovery of the requested data (125) is possible. However, if a host does not have or use the correct private key to decrypt the encrypted data, the encrypted data is preferably not capable of being decrypted and is unreadable (126).
[0052] However, as noted above, if a symmetric session key for a symmetric cryptosystem or a private key for a public-key cryptosystem is stored on the host of a user, that user may attempt to share that secret or private key to allow others access to the communications from the server. Additionally, if a symmetric session key for a symmetric cryptosystem or a private key for a public-key cryptosystem is stored on the user's host, someone without the user's consent may find a way to access the user's host and obtain the secret or private key so as to gain access to the confidential data being transmitted from the server to the authorized user. Fig. 4 is a flow chart illustrating a method according to an embodiment of the present invention that entails storing a key seed, instead of a key, in a host's non- volatile storage unit to mitigate the chances that a user's key will be compromised, with or without the user's cooperation. The key needed to decrypt incoming encrypted 80113-0359 (D2828.1)
transmissions can be derived from the key seed. This method will be explained in more detail below using Fig. 4.
[0053] As shown in Fig. 4, the process begins with a host preferably storing a key seed in a non- volatile storage unit (140). The key seed is preferably a random bit sequence used to generate another bit sequence. In the present invention, the key seed is used to generate a key, which is also a sequence of bits. The key may be either a symmetric session key used in a symmetric cryptosystem or a private key used in a public-key cryptosystem.
[0054] After the key seed has been stored by the host in a non-volatile storage unit, the host then runs a one-way function that generates a key (141) when the key is needed to perform an electronic transaction. The key is preferably not stored in any non-volatile memory unit of the host and consequently, the key is not accessible to the user at any time. Rather, the key might be temporarily stored in random access memory (RAM), for example, which would make it difficult or even impossible for the client or anyone else to copy the key by accessing the client's host.
[0055] The one-way function is a function of two inputs — the key seed and a host identification (host ID). The host ID is preferably a permanent and unique identifier resident in the host and is difficult or impossible to change without adversely affecting the operation of the host. Most electronic host devices currently contain a unique electronic host ID that is generated and placed in the host device by its manufacturer. Where this host ID is stored and how it may be accessed will vary depending on the make and model of the host device. However, one of ordinary skill in the art, with the benefit of this disclosure, will be able to identify where the host ID is stored and how it can be accessed for use by an embodiment of the present invention given any particular host device. Alternatively, a host ID may be generated by a dedicated algorithm that bases the host ID on information gathered from the host that defines or describes the hardware and configuration of the host device.
[0056] In some embodiments, the one-way function that obtains the host ID and the key seed and then generates the corresponding key can be called using the following general command: Key = KeyGen(Host HO, Key Seed). The command syntax can be modified to fit the language of the desired key management protocol. 80113-0359 (D2828.1)
[0057] A function (F) is said to be one-way if it is hard to invert. In other words, if the result of F is f, it is computationally infeasible to find some input x such that F(x) = f, where F(x) means that F is a function of x. In this embodiment of the present invention, the fact that the function that generates the key is one-way means that it is difficult, if not impossible, to derive the key seed from the key. For example, if given the key and a value of a new host LD a hacker could obtain the corresponding new value of the key seed, he or she could possibly derive new key seeds for many unauthorized hosts. These new key seeds could be combined with their corresponding host IDs to generate valid keys that could be used in an electronic transaction. A one-way function, however, makes it computationally infeasible to determine a key seed, given a value of a key and a host ID.
[0058] Returning to Fig. 4, if the host has a correct key seed (142) and a correct host ID (143), the function produces a valid key (144) that can be used in electronic communication. However, if either the key seed or the host ID is wrong, the function generates an invalid key (145).
[0059] An exemplary application of the key generation process shown in Fig. 4 is the interaction of a client with a web site on the Internet. If, for example, a client orders monthly paid content from website, the website operators can send a key seed and a key- generating function to the client to install on his or her host. The function takes as inputs the client's host ID and the key seed. The host is queried for its ID by the function when needed. If the correct host ID and key seed are not accurately input to the function, the function will not generate a valid key. The client must preferably run this function and use the generated key every time he or she desires to obtain the monthly paid content. Because the function only works with the client's host ID and key seed, it is difficult or impossible to transfer the function to a different host with a different host ID and obtain a valid key when the function is executed. This is because even if the client copies the key seed and function and distributes them to other people, they will not be able to generate a valid key because their host IDs are different than the host ID with which the function is designed to work and provide a valid key.
[0060] Fig. 5 is a flow chart illustrating an exemplary method of the present invention as applied to public-key cryptography. More specifically, Fig. 5 illustrates a 80113-0359 (D2828.1)
method that can be used to initially generate private and public keys with a private key seed (PKS) and then store the PKS on a client's non-volatile storage unit. The client in this embodiment generates his or her own key pair. A key pair preferably consists of a private and public key.
[0061] As shown in Fig. 5, a client initially generates a PKS (150) on his or her host. The PKS is preferably randomly generated by the host. The client then derives a private key from the PKS (151) using a one-way function with the PKS and host ID as inputs to the function.
[0062] The function can be called using a command found in the chosen key management protocol that employs public-key cryptography. Protocol examples are Kerberos with PKINIT extension that allows support for public-key cryptography, Internet Key Exchange (IKE) and Transport Layer Security (TLS). Examples of public key algorithms that may be used in combination with these functions include Elliptic Curve Digital Signature Algorithm (ECDSA), Elliptic Curve Diffie-Hellman (ECDH) and Elliptic Curve Authenticated Encryption Scheme (ECAES). In the case of Elliptic Curve-based algorithms, the command that generates a private key from a PKS is the following: "Private Key = PKGen(Host ID, PKS) modulo Point-Order". The Point-Order parameter is specific to Elliptic Curve cryptology. Each Elliptic Curve has its own value for the Point-Order parameter.
[0063] However, the present invention does not depend on the choice of the PKGenO function. The following general command calls the function that generates the private key from the PKS: "Private Key = F(PkGen(Host ID, PKS))", where the function F is dependent on a particular public-key cryptosystem. The function is preferably fast enough to regenerate the private key every time an electronic transaction requires the use of a private key.
[0064] Returning to Fig. 5, after the private key is derived from the PKS (151), the client preferably derives a public key from the private key (152). This can be done by using a variety of mathematical functions known to cryptography. The public key is then registered with a trusted authority (153). The trusted authority is usually referred to as a Certifying Authority (CA). 80113-0359 (D2828.1)
[0065] The CA returns to the client a certificate attesting to the validity of the generated public key or stores the public key in a trusted database (154). Certificates are digital documents attesting to the binding of a public key to a client or other entity. Certificates allow verification of the claim that a specific public key does in fact belong to a specific client. They help prevent someone from using a phony key to impersonate someone else.
[0066] In their simplest form, certificates contain a public key and a name. A certificate might also contain an expiration date, the name of the CA that issued the certificate, a serial number, the digital signature of the certificate issuer, and perhaps other information.
[0067] CAs can be any trusted central administration willing to vouch for the identities of those clients to whom it issues certificates and their association with a given key. For example, a company may issue certificates to its employees, or a university to its students. A Key Distribution Center (KDC) may for example be extended to include the functionality of a CA. KDCs are dedicated to key generation, verification, and distribution.
[0068] After the client receives the certificate or the public key is saved in a trusted database (154), as shown in Fig. 5, the client's host saves the randomly generated PKS in a non- volatile storage unit (155). The PKS can now be used to generate the private key that is to be used in future electronic transactions.
[0069] Fig. 6 is a flow chart illustrating a second exemplary method of the present invention as applied to public-key cryptography. More specifically, Fig. 6 illustrates a method whereby a client preferably uses a randomly generated PKS stored in a non- volatile storage unit to generate a private key that he or she can use in an electronic transaction.
[0070] As shown in Fig. 6, the process starts with a client's host reading the PKS from a non- volatile storage unit (160). Using the same function that was used to initially generate the private key, which was used to generate the public key (explained in connection with Fig. 5), the client derives the same private key based on the stored PKS (151).
[0071] The client can now preferably use the private key in an electronic transaction (161). If, as shown in Fig. 6, the private key correlates correctly with the registered public key (162), the server and client can use the private and public key pair to 80113-0359 (D2828.1)
complete the electronic transaction (163). On the other hand, if the private key does not correlate correctly with the registered public key, the electronic transaction fails (164).
[0072] Fig. 7 is a flow chart illustrating an exemplary method of the present invention as applied to symmetric session cryptography. More specifically, Fig. 7 illustrates a method whereby a client preferably receives, stores, and uses a symmetric session key seed (SKS) to generate a symmetric session key that can be used to make an electronic transaction. The client in this embodiment preferably generates a key that is identical to the key used by a server with which the client desires to make the electronic transaction.
[0073] As shown in Fig. 7, the process starts with a client receiving a SKS from a KDC or other source (170). Unlike the process used in public-key cryptography described in connection with Fig. 5, the client preferably does not generate the key seed that is to be used to generate a key. Instead, the KDC sends the SKS to the client.
[0074] After the client's host receives the SKS from the KDC, the host stores the SKS in a non- volatile storage unit (171). To make an electronic transaction, then, the client reads the SKS from the non- volatile storage unit (172) and derives a symmetric session key from the SKS (173) by running a one-way function on the host with the SKS and host ID as inputs to the function. The one-way function is preferably a program that is sent to the client by a KDC, server, or other source and is installed on the user's host.
[0075] The function can be called using a command found in the chosen key management protocol. A general command that generates a symmetric session key from a SKS is the following: "Symmetric Session Key = SKGen(Host LD, SKS)". However, the syntax of the function call command might vary depending on the chosen key management protocol. The function is preferably fast enough to regenerate the symmetric session key every time an electronic transaction requires the use of a symmetric session key.
[0076] The client can now preferably use the derived symmetric session key in an electronic transaction (174) with a server that also uses a symmetric session key. There are various possible methods of how the server obtains the same symmetric session key that the client uses. One method is for the KDC to execute the same one-way function that the host executes and generate the session key from the SKS. This method requires the KDC to have access to or a copy of the client's host ID. The KDC can then send the generated symmetric 80113-0359 (02828.1)
session key to the server. Alternatively, as is the case in the Kerberos protocol, the KDC can take the symmetric session key and encrypt it using a symmetric session key used by the server that is not known to any of the clients. This encrypted symmetric session key, along with the client and server identities and other related information, is called a ticket. The ticket can be then sent to the client's host. The host cannot modify the ticket because it does not know the server's symmetric session key. The client can then send this ticket to the server. The server then uses its key to decrypt the ticket and extract its copy of the session key.
[0077] Returning to Fig. 7, if the client's symmetric session key matches the symmetric session key used by the server (175) with which the client desires to complete an electronic transaction, the server and client can use the symmetric session keys to complete the electronic transaction (163). On the other hand, if the derived symmetric session key does not match the server's symmetric session key, the electronic transaction fails (164).
[0078] The preceding description has been presented only to illustrate and describe the invention. It is not intended to be exhaustive or to limit the invention to any precise form disclosed. Many modifications and variations are possible in light of the above teaching.
[0079] The preferred embodiment was chosen and described in order to best explain the principles of the invention and its practical application. The preceding description is intended to enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims.

Claims

80113-0359 (D2828.1)WHAT IS CLAIMED IS:
1. A method of generating an electronic key used in an electronic transaction, said method comprising executing a one-way function on a host that derives said electronic key from a key seed saved in a non- volatile storage unit of said host and a unique host identification, said function being executed to derive said electronic key each time an electronic transaction requiring the use of said electronic key is made.
2. The method of claim 1 , further comprising: randomly generating said key seed on said host; generating said electronic key with said one-way function, said one-way function having said key seed and said unique host identification as inputs; deriving a public key from said electronic key; registering said public key with a certifying authority to produce a registered public key; and saving said key seed in said non- volatile storage unit of said host to produce a saved key seed.
3. The method of claim 2, further comprising executing said one-way function with said saved key seed and said unique host identification as inputs to generate said electronic key used in said electronic transaction between said host and an electronic device that uses said registered public key in said electronic transaction.
4. The method of claim 3, further comprising allowing a successful completion of said electronic transaction only if said electronic key correlates correctly with said public key.
5. The method of claim 1 , further comprising: receiving said key seed from a key distribution center; and 80113-0359 (D2828.1)
saving said key seed in said non- volatile storage unit of said host to produce a saved key seed.
6. The method of claim 5, further comprising executing said one-way function with said saved key seed and said unique host identification as inputs to generate said electronic key used in said electronic transaction between said host and an electronic device that uses a symmetric session key in said elecfronic transaction.
7. The method of claim 6, further comprising allowing a successful completion of said electronic transaction only if said electronic key matches said symmetric session key.
8. The method of claim 1, further comprising not saving said electronic key in non- volatile memory of said host.
9. The method of claim 1, further comprising deleting said electronic key from said host device following said transaction.
10. A system for generating an electronic key used in an electronic transaction, said system comprising: a host for making said electronic transaction, said host having a unique host identification; a non- volatile storage unit of said host for storing a key seed; and a one-way function, stored on said host, for deriving said electronic key from said key seed and said host identification, said host executing said one-way function to derive said electronic key each time an electronic transaction requiring the use of said electronic key is made.
11. The system of claim 10, wherein said key seed comprises a private key seed. 80113-0359 (D2828.1)
12. The system of claim 11 , wherein said host randomly generates said private key seed.
13. The system of claim 12, wherein said one-way function derives a private key from said private key seed and said host identification.
14. The system of claim 13, wherein said host derives a public key from said private key.
15. The system of claim 14, wherein a certifying authority registers said public key to produce a registered public key.
16. The system of claim 15, wherein said certifying authority comprises a key distribution center.
17. The system of claim 15, wherein said certifying authority saves said public key in a trusted database.
18. The system of claim 15, wherein said certifying authority sends a digital certificate to said host attesting to the binding of said public key to said host.
19. The system of claim 15, wherein said host saves said private key seed in said non- volatile storage unit.
20. The system of claim 15, wherein said host executes said one-way function to generate said private key used in said electronic transaction between said host and an electronic device that uses said registered public key in said elecfronic transaction. 80113-0359 (D2828.1)
21. The system of claim 20, wherein said electronic transaction is successfully completed successfully only if said private key correlates correctly with said public key.
22. The system of claim 10, wherein said key seed comprises a symmetric session key seed.
23. The system of claim 22, said system further comprising a key distribution center for sending said symmetric session key seed to said host, said host saving said symmetric session key seed in said non- volatile storage unit.
24. The system of claim 23, wherein said host executes said one-way function to generate said symmetric session key used in said electronic transaction between said host and an electronic device, said electronic device also using a symmetric session key in said electronic transaction.
25. The system of claim 24, wherein said electronic transaction is completed successfully only if said symmetric session key used by said host matches said symmetric session key used by said electronic device.
26. The system of claim 10, wherein said non- volatile storage unit comprises a hard drive.
27. The system of claim 10, wherein said host comprises a personal computer.
28. The system of claim 10, wherein said host comprises a set-top box.
29. The system of claim 10, wherein said electronic key is not saved in said nonvolatile storage unit. 80113-0359 (D2828.1)
30. A system for securing an electronic transaction, said system comprising: means for generating an electronic key based on a first electronic input and an electronic identifier unique to a host participating in said electronic transaction; and means for using said electronic key for security in said electronic transaction
31. The system of claim 30, wherein said means for generating further comprise means for executing a one-way function on said host that derives said electronic key from a key seed saved in a non- volatile storage unit of said host and a unique host identification, said function being executed to derive said electronic key each time an electronic transaction requiring the use of said electronic key is made.
32. The system of claim 31 , further comprising: means for randomly generating said key seed on said host; means for generating said elecfronic key with said one-way function, said one-way function having said key seed and said unique host identification as inputs; means for deriving a public key from said electronic key; means for registering said public key with a certifying authority to produce a registered public key; and means for saving said key seed in said non- volatile storage unit of said host to produce a saved key seed.
33. The system of claim 32, further comprising means for executing said one-way function with said saved key seed and said unique host identification as inputs to generate said electronic key used in said electronic transaction between said host and an elecfronic device that uses said registered public key in said elecfronic transaction.
34. The system of claim 33, further comprising means for allowing a successful completion of said elecfronic transaction only if said electronic key correlates correctly with said public key. 80113-0359 (D2828.1)
35. The system of claim 31 , further comprising: means for receiving said key seed from a key distribution center; and means for saving said key seed in said non- volatile storage unit of said host to produce a saved key seed.
36. The system of claim 35, further comprising means for executing said one-way function with said saved key seed and said unique host identification as inputs to generate said electronic key used in said electronic fransaction between said host and an elecfronic device that uses a symmetric session key in said electronic transaction.
37. The system of claim 36, further comprising means for allowing a successful completion of said electronic transaction only if said elecfronic key matches said symmetric session key.
38. The system of claim 31, further comprising means for using said electronic key in said electronic transaction without saving said electronic key in said non- volatile storage unit.
PCT/US2003/021088 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed WO2004006536A2 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2004519897A JP5295479B2 (en) 2002-07-10 2003-07-08 Method and system for preventing unauthorized delivery and use of electronic keys with key seeds
EP03763224.7A EP1520392B1 (en) 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed
MXPA05000472A MXPA05000472A (en) 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed.
AU2003256388A AU2003256388A1 (en) 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed
CA002491049A CA2491049C (en) 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/192,920 2002-07-10
US10/192,920 US7352867B2 (en) 2002-07-10 2002-07-10 Method of preventing unauthorized distribution and use of electronic keys using a key seed

Publications (2)

Publication Number Publication Date
WO2004006536A2 true WO2004006536A2 (en) 2004-01-15
WO2004006536A3 WO2004006536A3 (en) 2004-04-08

Family

ID=30114424

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/021088 WO2004006536A2 (en) 2002-07-10 2003-07-08 Method of preventing unauthorized distribution and use of electronic keys using a key seed

Country Status (8)

Country Link
US (1) US7352867B2 (en)
EP (1) EP1520392B1 (en)
JP (1) JP5295479B2 (en)
CN (1) CN1689297B (en)
AU (1) AU2003256388A1 (en)
CA (1) CA2491049C (en)
MX (1) MXPA05000472A (en)
WO (1) WO2004006536A2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006120535A1 (en) * 2005-05-09 2006-11-16 Nokia Corporation System and method for efficient encryption and decryption of drm rights objects
EP2393031A1 (en) * 2010-06-04 2011-12-07 Nagravision S.A. Method for activating at least a function on a chipset and chipset for the implementation of the method

Families Citing this family (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060025159A (en) * 2003-06-05 2006-03-20 마쯔시다덴기산교 가부시키가이샤 User terminal for receiving license
US20050135622A1 (en) * 2003-12-18 2005-06-23 Fors Chad M. Upper layer security based on lower layer keying
WO2005076518A1 (en) * 2004-02-10 2005-08-18 Ntt Communications Corporation Secret information management scheme based on secret sharing scheme
US8407752B2 (en) * 2004-03-18 2013-03-26 Digimarc Corporation Synchronizing broadcast content with corresponding network content
WO2006074150A1 (en) * 2005-01-03 2006-07-13 Falkin Systems, Llc Method, system and device for identification from multiple data inputs
US8332355B2 (en) * 2005-03-28 2012-12-11 Symantec Corporation Method and apparatus for generating readable, unique identifiers
US20080031451A1 (en) * 2005-11-14 2008-02-07 Jean-Francois Poirier Method and system for security of data transmissions
US8788807B2 (en) * 2006-01-13 2014-07-22 Qualcomm Incorporated Privacy protection in communication systems
JP4829639B2 (en) * 2006-02-24 2011-12-07 キヤノン株式会社 Data processing apparatus and data processing method
US7853800B2 (en) * 2006-06-30 2010-12-14 Verint Americas Inc. Systems and methods for a secure recording environment
US8826023B1 (en) * 2006-06-30 2014-09-02 Symantec Operating Corporation System and method for securing access to hash-based storage systems
US7848524B2 (en) * 2006-06-30 2010-12-07 Verint Americas Inc. Systems and methods for a secure recording environment
US7769176B2 (en) 2006-06-30 2010-08-03 Verint Americas Inc. Systems and methods for a secure recording environment
US7953750B1 (en) 2006-09-28 2011-05-31 Verint Americas, Inc. Systems and methods for storing and searching data in a customer center environment
US7613915B2 (en) * 2006-11-09 2009-11-03 BroadOn Communications Corp Method for programming on-chip non-volatile memory in a secure processor, and a device so programmed
US8291227B2 (en) * 2007-02-02 2012-10-16 Red Hat, Inc. Method and apparatus for secure communication
US8281405B1 (en) 2007-06-13 2012-10-02 Mcafee, Inc. System, method, and computer program product for securing data on a server based on a heuristic analysis
US20090034852A1 (en) * 2007-07-31 2009-02-05 Chris Brock Method and System for Identifying the Source of an Image
EP2179533B1 (en) * 2007-08-14 2015-09-16 Triton Systems of Delaware, LLC Method and system for secure remote transfer of master key for automated teller banking machine
JP2009070119A (en) * 2007-09-13 2009-04-02 Riso Kagaku Corp Image forming system
CN101222324B (en) * 2008-01-23 2012-02-08 中兴通讯股份有限公司 Method and apparatus for implementing end-to-end media stream safety
US20090202081A1 (en) * 2008-02-08 2009-08-13 Ayman Hammad Key delivery system and method
US8625785B2 (en) * 2008-05-15 2014-01-07 Qualcomm Incorporated Identity based symmetric cryptosystem using secure biometric model
US8401155B1 (en) 2008-05-23 2013-03-19 Verint Americas, Inc. Systems and methods for secure recording in a customer center environment
US9704159B2 (en) 2009-05-15 2017-07-11 Entit Software Llc Purchase transaction system with encrypted transaction information
EP2438580A2 (en) * 2009-06-02 2012-04-11 Voltage Security, Inc. Purchase transaction system with encrypted payment card data
KR101727130B1 (en) * 2010-01-20 2017-04-14 인트린직 아이디 비브이 Device and method for obtaining a cryptographic key
CN102163178A (en) * 2010-02-24 2011-08-24 上海果壳电子有限公司 Secure storage method of data
US10318932B2 (en) 2011-06-07 2019-06-11 Entit Software Llc Payment card processing system with structure preserving encryption
IL213497A0 (en) 2011-06-12 2011-08-31 Eliphaz Hibshoosh Light public key cryptography
US8914635B2 (en) * 2011-07-25 2014-12-16 Grey Heron Technologies, Llc Method and system for establishing secure communications using composite key cryptography
ES2691046T3 (en) * 2011-11-11 2018-11-23 Soprano Design Limited Secure messaging
US8953790B2 (en) * 2011-11-21 2015-02-10 Broadcom Corporation Secure generation of a device root key in the field
CN102660714B (en) * 2012-06-05 2013-12-18 河南理工大学 High-carbon and high-vanadium wear-resistant steel
JP5908376B2 (en) * 2012-09-06 2016-04-26 Kddi株式会社 Secret key generation apparatus, secret key generation method and program
US9197408B2 (en) * 2013-05-10 2015-11-24 Sap Se Systems and methods for providing a secure data exchange
US9906372B2 (en) * 2013-06-03 2018-02-27 Intel Deutschland Gmbh Authentication devices, key generator devices, methods for controlling an authentication device, and methods for controlling a key generator
EP3086585B1 (en) * 2015-04-23 2019-12-11 Nxp B.V. Method and system for securing data communicated in a network
JP2017118312A (en) * 2015-12-24 2017-06-29 日本電気株式会社 Radio communication system, server, terminal, radio communication method, and program
US10880090B2 (en) 2016-03-14 2020-12-29 Arris Enterprises Llc Cable modem anti-cloning
US11387996B2 (en) 2016-03-14 2022-07-12 Arris Enterprises Llc Cable modem anti-cloning
CA3016611C (en) * 2016-03-14 2021-01-19 Arris Enterprises Llc Cable modem anti-cloning
US9978192B1 (en) * 2016-07-14 2018-05-22 Guestof, LLC Method and apparatus for streamlining guest entry into a building
US20180097621A1 (en) * 2016-09-30 2018-04-05 Sony Interactive Entertainment America Llc Obfuscated secret key derivation for non-secure commercial off-the-shelf (cots) devices
US10498533B2 (en) * 2016-12-16 2019-12-03 Keysight Technologies Singapore (Sales) Pte. Ltd. Methods, systems, and computer readable media for increasing the rate of established network connections in a test simulation environment
JP2021177581A (en) * 2018-07-23 2021-11-11 株式会社AndGo Apparatus for managing secret information, method and program therefor
DE112019006051T5 (en) * 2019-01-09 2021-09-30 Mitsubishi Electric Corporation SECURE COMPUTING SETUP AND CLIENT SETUP
CN109768863A (en) * 2019-01-16 2019-05-17 杭州趣链科技有限公司 A kind of block chain key based on elliptic curve is shared and dynamic updating method
US11063753B2 (en) * 2019-03-20 2021-07-13 Arris Enterprises Llc Secure distribution of device key sets over a network
JP7160443B2 (en) * 2020-04-24 2022-10-25 日本電気株式会社 Wireless communication system, server, terminal, wireless communication method, and program

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2355905A (en) * 1999-10-05 2001-05-02 Authoriszor Ltd Providing network site security using pseudo uniform resource locators (PURLs)

Family Cites Families (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4634808A (en) * 1984-03-15 1987-01-06 M/A-Com Government Systems, Inc. Descrambler subscriber key production system utilizing key seeds stored in descrambler
JP2862141B2 (en) * 1989-12-29 1999-02-24 富士通株式会社 Identification number-based key management device using conventional encryption
US5265164A (en) * 1991-10-31 1993-11-23 International Business Machines Corporation Cryptographic facility environment backup/restore and replication in a public key cryptosystem
US5418854A (en) * 1992-04-28 1995-05-23 Digital Equipment Corporation Method and apparatus for protecting the confidentiality of passwords in a distributed data processing system
CA2176032A1 (en) * 1994-01-13 1995-07-20 Bankers Trust Company Cryptographic system and method with key escrow feature
US5598473A (en) * 1994-08-17 1997-01-28 Ibm Corporation Digital signature generator/verifier/recorder (DS-GVR) for analog transmissions
US5727065A (en) * 1994-11-14 1998-03-10 Hughes Electronics Deferred billing, broadcast, electronic document distribution system and method
US5701343A (en) * 1994-12-01 1997-12-23 Nippon Telegraph & Telephone Corporation Method and system for digital information protection
JPH08223151A (en) * 1995-02-13 1996-08-30 Nippon Telegr & Teleph Corp <Ntt> Ciphering communication system and method therefor
CN1869997A (en) * 1995-02-13 2006-11-29 英特特拉斯特技术公司 Systems and methods for secure transaction management and electronic rights protection
GB9507885D0 (en) * 1995-04-18 1995-05-31 Hewlett Packard Co Methods and apparatus for authenticating an originator of a message
US6487661B2 (en) * 1995-04-21 2002-11-26 Certicom Corp. Key agreement and transport protocol
US6292893B1 (en) * 1995-10-24 2001-09-18 Silvio Micali Certificate revocation system
FR2744818B1 (en) * 1996-02-12 1998-03-27 Bull Sa PROCESS FOR VERIFYING THE CONSERVATION OF THE INTEGRITY OF A QUERY ISSUED WITHOUT PROTECTION BY A CUSTOMER TO A SERVER BY MEANS OF INTEGRITY OF THE RESPONSE
JP3486043B2 (en) * 1996-03-11 2004-01-13 株式会社東芝 Operating method of software distribution system and software system
US6002768A (en) * 1996-05-07 1999-12-14 International Computer Science Institute Distributed registration and key distribution system and method
US6085320A (en) * 1996-05-15 2000-07-04 Rsa Security Inc. Client/server protocol for proving authenticity
US5809495A (en) * 1996-06-04 1998-09-15 Oracle Corporation Method for obtaining information regarding the current activity of a database management system from a viritual table in a memory of the database management system
SG67354A1 (en) * 1996-06-27 1999-09-21 Inst Of Systems Science Nation Computationally efficient method for trusted and dynamic digital objects dissemination
US6600823B1 (en) * 1996-10-22 2003-07-29 Unisys Corporation Apparatus and method for enhancing check security
US6240513B1 (en) * 1997-01-03 2001-05-29 Fortress Technologies, Inc. Network security device
WO1998047259A2 (en) * 1997-03-10 1998-10-22 Fielder Guy L File encryption method and system
JP2001514834A (en) * 1997-03-10 2001-09-11 ガイ・エル・フィールダー Secure deterministic cryptographic key generation system and method
US6028933A (en) * 1997-04-17 2000-02-22 Lucent Technologies Inc. Encrypting method and apparatus enabling multiple access for multiple services and multiple transmission modes over a broadband communication network
JPH10327147A (en) * 1997-05-21 1998-12-08 Hitachi Ltd Electronic authenticating and notarizing method and its system
US6282295B1 (en) * 1997-10-28 2001-08-28 Adam Lucas Young Auto-recoverable and auto-certifiable cryptostem using zero-knowledge proofs for key escrow in general exponential ciphers
US6122742A (en) * 1997-06-18 2000-09-19 Young; Adam Lucas Auto-recoverable and auto-certifiable cryptosystem with unescrowed signing keys
US6243466B1 (en) * 1997-08-29 2001-06-05 Adam Lucas Young Auto-escrowable and auto-certifiable cryptosystems with fast key generation
US6202150B1 (en) * 1997-05-28 2001-03-13 Adam Lucas Young Auto-escrowable and auto-certifiable cryptosystems
US6389136B1 (en) * 1997-05-28 2002-05-14 Adam Lucas Young Auto-Recoverable and Auto-certifiable cryptosystems with RSA or factoring based keys
TW338865B (en) * 1997-06-03 1998-08-21 Philips Eloctronics N V Authentication system
US6370249B1 (en) * 1997-07-25 2002-04-09 Entrust Technologies, Ltd. Method and apparatus for public key management
US6681017B1 (en) * 1997-09-03 2004-01-20 Lucent Technologies Inc. Simplified secure shared key establishment and data delivery protocols for electronic commerce
US6263437B1 (en) * 1998-02-19 2001-07-17 Openware Systems Inc Method and apparatus for conducting crypto-ignition processes between thin client devices and server devices over data networks
US6230269B1 (en) * 1998-03-04 2001-05-08 Microsoft Corporation Distributed authentication system and method
US6167518A (en) * 1998-07-28 2000-12-26 Commercial Electronics, Llc Digital signature providing non-repudiation based on biological indicia
IL126472A0 (en) * 1998-10-07 1999-08-17 Nds Ltd Secure communications system
JP2000113085A (en) * 1998-10-08 2000-04-21 Sony Corp Electronic cash system
FI109278B (en) * 1998-11-25 2002-06-28 Veikkaus Ab Oy Method and arrangement for organizing electronic instant lottery
JP2000165373A (en) * 1998-11-25 2000-06-16 Toshiba Corp Enciphering device, cryptographic communication system, key restoration system and storage medium
US6473508B1 (en) * 1998-12-22 2002-10-29 Adam Lucas Young Auto-recoverable auto-certifiable cryptosystems with unescrowed signature-only keys
JP2000286830A (en) * 1999-03-29 2000-10-13 Seiko Epson Corp Encryption processing method in encryption communication system
CA2267395C (en) * 1999-03-30 2002-07-09 Ibm Canada Limited-Ibm Canada Limitee Method and system for managing keys for encrypted data
CN1175613C (en) * 1999-06-03 2004-11-10 叶季青 Method and device for generating antiforge authentication data, its authentication method and device, and its system
US6914985B1 (en) * 1999-12-14 2005-07-05 International Business Machines Corporation Method and system for presentation and manipulation of PKCS enveloped-data objects
US6775771B1 (en) * 1999-12-14 2004-08-10 International Business Machines Corporation Method and system for presentation and manipulation of PKCS authenticated-data objects
US6772340B1 (en) * 2000-01-14 2004-08-03 Microsoft Corporation Digital rights management system operating on computing device and having black box tied to computing device
JP2001211153A (en) * 2000-01-25 2001-08-03 Murata Mach Ltd Secret key generating method
JP4457474B2 (en) * 2000-04-04 2010-04-28 ソニー株式会社 Information recording apparatus, information reproducing apparatus, information recording method, information reproducing method, information recording medium, and program providing medium
US20020196935A1 (en) * 2001-02-25 2002-12-26 Storymail, Inc. Common security protocol structure and mechanism and system and method for using
CN1283827A (en) * 2000-08-18 2001-02-14 郝孟一 Universal electronic information network authentication system and method
US6895504B1 (en) * 2000-09-29 2005-05-17 Intel Corporation Enabling secure communications with a client
US20030133576A1 (en) * 2000-10-18 2003-07-17 Frederic Grumiaux Generation of a common encryption key
US6904419B1 (en) * 2000-10-23 2005-06-07 Pitney Bowes Inc. Postal counter postage evidencing system with closed loop verification
JP2002185443A (en) * 2000-12-11 2002-06-28 Hitachi Ltd Secret key managing system
US6931128B2 (en) * 2001-01-16 2005-08-16 Microsoft Corporation Methods and systems for generating encryption keys using random bit generators
US7269736B2 (en) * 2001-02-28 2007-09-11 Microsoft Corporation Distributed cryptographic methods and arrangements
GB2367986B (en) * 2001-03-16 2002-10-09 Ericsson Telefon Ab L M Address mechanisms in internet protocol
US8255989B2 (en) * 2001-09-26 2012-08-28 General Instrument Corporation Access control and key management system for streaming media
US7487363B2 (en) * 2001-10-18 2009-02-03 Nokia Corporation System and method for controlled copying and moving of content between devices and domains based on conditional encryption of content key depending on usage
US6871206B2 (en) * 2001-11-20 2005-03-22 Ip-First, Llc Continuous multi-buffering random number generator
US20030123667A1 (en) * 2001-12-28 2003-07-03 Cable Television Laboratories, Inc. Method for encryption key generation

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2355905A (en) * 1999-10-05 2001-05-02 Authoriszor Ltd Providing network site security using pseudo uniform resource locators (PURLs)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BRUCE SCHNEIER: "applied cryptography, second edition" 1996 , JOHN WILEY & SONS , NEW YORK XP002265704 275760 page 115 *
SHAMIR A: "IDENTITY-BASED CRYPTOSYSTEMS AND SIGNATURE SCHEMES" LECTURE NOTES IN COMPUTER SCIENCE, SPRINGER VERLAG, NEW YORK, NY, US, 1985, pages 47-53, XP000675444 ISSN: 0302-9743 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006120535A1 (en) * 2005-05-09 2006-11-16 Nokia Corporation System and method for efficient encryption and decryption of drm rights objects
EP2393031A1 (en) * 2010-06-04 2011-12-07 Nagravision S.A. Method for activating at least a function on a chipset and chipset for the implementation of the method
KR101845556B1 (en) * 2010-06-04 2018-05-18 나그라비젼 에스에이 method for activating at least a function on a chipset and chipset for the implementation of the method

Also Published As

Publication number Publication date
US20040008846A1 (en) 2004-01-15
JP2005532742A (en) 2005-10-27
AU2003256388A1 (en) 2004-01-23
US7352867B2 (en) 2008-04-01
EP1520392B1 (en) 2018-10-03
MXPA05000472A (en) 2005-03-23
CA2491049A1 (en) 2004-01-15
AU2003256388A8 (en) 2004-01-23
CN1689297A (en) 2005-10-26
CN1689297B (en) 2014-01-08
WO2004006536A3 (en) 2004-04-08
CA2491049C (en) 2009-09-29
EP1520392A2 (en) 2005-04-06
JP5295479B2 (en) 2013-09-18

Similar Documents

Publication Publication Date Title
US7352867B2 (en) Method of preventing unauthorized distribution and use of electronic keys using a key seed
Das et al. A dynamic ID-based remote user authentication scheme
CN101421968B (en) Authentication system for networked computer applications
US6073237A (en) Tamper resistant method and apparatus
US5784463A (en) Token distribution, registration, and dynamic configuration of user entitlement for an application level security system and method
US7293176B2 (en) Strong mutual authentication of devices
US10116445B2 (en) Method and system for protected exchange of data
US20060195402A1 (en) Secure data transmission using undiscoverable or black data
RU2584500C2 (en) Cryptographic authentication and identification method with real-time encryption
JP2000357156A (en) System and method for authentication sheet distribution
WO1995028784A1 (en) Computer network cryptographic key distribution system
CN101393628A (en) Novel network safe transaction system and method
US20020018570A1 (en) System and method for secure comparison of a common secret of communicating devices
US7519815B2 (en) Challenge-based authentication without requiring knowledge of secret authentication data
CN103188212A (en) Security management method and service terminal of electronic wallet, and electronic wallet system
Dandash et al. Fraudulent Internet Banking Payments Prevention using Dynamic Key.
JP2001069138A (en) User verifying system on internet for shared key enciphered ic card
Gaskell et al. Integrating smart cards into authentication systems
Khan et al. A tamper-resistant digital token-based rights management system
US7657745B2 (en) Secure electronic transfer without requiring knowledge of secret data
WO2000067447A1 (en) Improvements in and relating to secure data transmission
Cheng et al. Security enhancement of an IC-card-based remote login mechanism
KR20050018982A (en) Method of preventing unauthorized distribution and use of electronic keys using a key seed
Kravitz et al. Secure open systems for protecting privacy and digital services
CN117078254A (en) Digital currency hard wallet and opening method thereof

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2491049

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2004519897

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: PA/a/2005/000472

Country of ref document: MX

Ref document number: 1020057000473

Country of ref document: KR

Ref document number: 20038163586

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2003763224

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1020057000473

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2003763224

Country of ref document: EP