US2013191639A1PendingUtilityA1

System and method for securing communications between devices

Individually held — no corporate assignee on recordPriority: Nov 1, 2002Filed: Aug 20, 2012Published: Jul 25, 2013
Est. expiryNov 1, 2022(expired)· nominal 20-yr term from priority
H04L 63/0428H04L 63/08H04L 63/166H04L 9/0861
35
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system and method for providing an improved way to secure messages being transmitted between communicating devices. Security mechanisms, operating below the session establishment level, provide fast encryption that is unconditionally secure or becomes stronger over time as devices continue to communicate. After random or arbitrary characters are used to encrypt an initial message, each new message communicated between two devices is encrypted with the most recent message communicated there-between as well as the changing key. Moreover, an exclusive dyadic relationship between the devices is obtained which prevents the cloning or piracy of the devices or the data communicated between them. The disclosed system and method also provide a multi-threading capability, thereby reducing the likelihood of a denial of service of attack.

Claims

exact text as granted — not AI-modified
1 .- 3 . (canceled) 
     
     
         4 . A method of encrypting a multi-digit plaintext string of multi-bit digits stored on a sending computer device using at least one multi-digit encryption key having a plurality of multibit encryption key digits, comprising:
 (a) on the sending computer device, adding one multi-bit digit of said plaintext string to a corresponding multi-bit digit of the at least one multi-digit encryption key to produce at least one ciphertext result digit;   (b) on the sending computer device, truncating the most significant digit of the at least one ciphertext result digit if the at least one ciphertext result digit is longer than one digit;   (c) storing the at least one ciphertext result digit on the sending computer device; and   (d) repeating steps (a) and (b) and (c) for the next multibit digit in the plaintext string until the end of the plaintext string is reached.   
     
     
         5 . The method of  claim 4 , further comprising:
 prior to (b), as part of producing the at least one ciphertext result digit, adding a corresponding digit of a second encryption key.   
     
     
         6 . The method of  claim 4 , where the encryption is performed without the use of an encryption table. 
     
     
         7 . A method of updating an encryption key stored on a computer device, the key being formed of a plurality of multi-bit digits, comprising:
 (a) on the computer device, adding one digit of said key to a corresponding digit of a cyphertext data string stored on the computer device to produce at least one key update result digit;   (b) on the computer device, truncating the most significant digit of the at least one key update result digit if the at least one key update result digit is longer than one digit;   (c) storing the key update result digit on the computer device in place of the one digit of said key; and   (d) repeating steps (a) through (c) for the next digit in the key until the end of the key is reached.   
     
     
         8 . The method of  claim 7  further comprising:
 prior to (b), as part of producing the at least one key update result digit, adding at least one digit of another data string to the at least one one digit of said key. 
 
     
     
         9 . The method of  claim 7 , where the encryption is performed without the use of an encryption table. 
     
     
         10 . A method of encrypting a plaintext string of multi-bit digits stored on a sending computer device_using a multi-digit encryption key, comprising:
 (a) on the sending computer device, adding one digit of said plaintext string to a corresponding digit of at least one encryption key to produce a ciphertext result;   (b) on the sending computer device, truncating the most significant digit of the ciphertext result if the ciphertext result is longer than one digit;   (c) storing the ciphertext result on the computer device;   (d) updating the corresponding digit of said multi-digit encryption key using the at least one of the plaintext string or the ciphertext result to produce a key update result;   (e) if the end of the key is reached, repeating steps (a) through (d) with the updated key;   (f) repeating steps (a) through (e) until the end of the plaintext string is reached; and   (g) sending the ciphertext toward a receiving device.   
     
     
         11 . The method of  claim 10 , where the encryption is performed without the use of an encryption table. 
     
     
         12 . The method  claim 10 , wherein the updating the one digit of said key further comprises
 adding the corresponding digit of said key to a corresponding digit of the at least one of the plaintext string or the ciphertext result to produce the key update result; and   truncating the most significant digit of the key update result if the key update result is longer than one digit.   
     
     
         13 . The method of  claim 10  wherein the encryption of information passing from the first device to the second device becomes more secure as the amount of plaintext which is encrypted and sent from the first device to the second device increases. 
     
     
         14 . The method of  claim 10 , wherein the digits of the encryption key do not repeat periodically as the key is updated. 
     
     
         15 . The method of  claim 10 , wherein the encryption and decryption require at most 6 integer arithmetic operations per digit of plaintext encrypted and per digit of cyphertext decrypted. 
     
     
         16 . The method of  claim 10 , wherein the encryption and decryption require at most 2 integer arithmetic operations per digit of plaintext encrypted and per digit of cyphertext decrypted.

Join the waitlist — get patent alerts

Track US2013191639A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.