The present invention relates generally to cryptographic systems and methods. More particularly, the present invention relates to public key cryptographic systems and methods that can be used, for example, to build highly secure systems for data storage, access, encryption, decryption, digital signing, and digital signing verification.
Security over the Internet is crucial as everyday life is becoming ever more reliant on the Internet, e.g. remote access, social media, banking, money transfer, stock trading, shopping, researching, medical records transfer, voting, tax filing, identification, etc. There are many aspects of security over the Internet, one of which is safe guarding accessibility of data by blocking unauthorized access to hardware components such as servers. Another aspect is to prevent comprehension of data after unauthorized access has occurred. This second aspect is critical in addressing the ever-evolving illegitimate and malicious means of gaining access to data. Many technologies have been developed to make the Internet safe against such illegitimate and malicious activities.
A common type of malicious activity is inserting spyware into an end-user computer to surreptitiously copy Internet activity such as User Name and Password transmission for various sensitive accounts. Anti-virus programs are one tool used to combat this type of attack. Another common malicious activity is spoofing a web site, such as a banks' online login page, to look the same as the original. When a user enters login credentials, this forged site captures the sensitive login credentials. Digital Certificates are a tool used to secure the Internet against this type of attack. Digital Certificates help to guarantee that the site you are visiting is really the site operated by the original intended organization instead of a “look-a-like” spoofed site operated by a malicious party. Digital Certificates also allow software publishers to digitally sign executable files to prove legitimacy.
Even though there are many ways to block malicious activities, there is an ever-present risk of becoming a victim of a cyber attack. For example, malicious attackers are constantly working on ways to bypass anti-virus software. Malicious parties may also be able to gain access to the database of a public server, such as a bank or a social media site, by-passing the login process. Malicious parties may also be able to tap into a communication session between an end user and a website they are accessing and collect data as a “man in the middle”. It is important, therefore, to implement lower level security, such as encryption, to ensure that no one can understand the content of the communication session even if security has been breached.
There are many different encryption techniques. Symmetrical encryption methods, such as AES and DES, use the same key to encrypt and decrypt. Another form of encryption is the asymmetrical encryption method using a pair of private and public keys. Examples of this type of encryptions include RSA and El Gamal. This type of encryption uses one of the keys to encrypt data so that only the entity having the other key can decrypt it. Banks use this type of encryption in their communication sessions and typically employ an SSL Digital Certificate with a pair of private and public keys. The public key is built into the Certificate and distributed publicly to whoever wants to establish a communication session with the bank's server. When the user is communicating with the bank's server, such as when transmitting the user name and password, the contents will be encrypted and the corresponding session keys of the symmetric encryption will be encrypted using the public key. Only the bank's server, having the private key, will be able to decrypt the data.
In general, a public and private key pair is generated by multiplying two very large randomly selected prime numbers as well as performing some other complex mathematical processes such as hashing. Security of asymmetrical encryption lies in the difficulty of factoring a semi-prime number that is the product of two very large prime numbers, an essential step to reverse engineer a private key from its public key twin. As a result, the time required to factor a semi-prime number into the original prime numbers in order to decrypt the message (“Brute Force Time”) is exponentially related to the size of the public key.
An RSA key size of 4096 bits is believed to be unbreakable in human acceptable time as of the date of this application using brute force factoring. However, this assumption only applies to computer technologies generally available as of the date of this application. A new breed of computer has been in development since early 1980s referred to as quantum computers. Quantum computers employ quantum-mechanical phenomena, such as superposition and entanglement, so that computation can be carried out simultaneously as contrasted with classical computing which is based on just on/off states, i.e., bits, and in which computation is performed sequentially.
A quantum computer is able to factor large numbers in polynomial time and could be used to break the public/private key mechanism. Shor's Algorithm, which is designed to run on a Quantum computer, is the process of period-finding which is done using Quantum Fourier Transform (QFT). The QFT can be used to determine the period of a function f(x). QFT processing can be done efficiently on a quantum computer because all of the experiments can be run at once in superposition, with bad experiments deteriorating from destructive interference effects and the good experiments dominating from constructive interference effects. Once the period-finding mechanism of the QFT becomes available, it can be exploited to find patterns in the mathematical structure of the number being factored. While not yet a commodity item, quantum computers will be at least available via the cloud in the foreseeable future.
Another trend is Distributed Ledger Technology (“DLT”) which involves distributing a database over multiple computers as opposed to being contained in a single central database. This technology is also frequently referred to as “Blockchain” technology. DLT increases security by requiring each new block of data to be digitally signed by the authorized node who posted it, and to also include a hash value for the previous block. Thus, a list is formed that contains the hash values of all of the blocks in this chain going back to the first block. By requiring the hash values of all previous blocks to be included, the history of transactions is greatly secured against editing.
DLT further requires the chain of data blocks be replicated among numerous computers with a self-correcting mechanism. This way, not only is a natural redundancy built-in but, importantly, a consensus is also required to legitimize a new block. In other words, malicious activities must simultaneously attack a large number of nodes for the fake transaction to “appear as legitimate.” Otherwise, the “minority fake transaction” will be over-written by the self-correcting mechanism of DLT.
DLT is considered to be a highly secure platform for cyber-security that is also practically feasible. Notwithstanding the advantages provided by DLT and asymmetric encryption, both technologies rely on the difficulty of prime number factorization as their main defense. Quantum computers, which have the ability to factor large prime numbers, will therefore present a challenge to security using these technologies.
A number of methods have been proposed that are theoretically capable of making the Brute Force Time exponentially related to the key size when quantum computers are used to do such computational processing. Examples of such methods are code-based encryption, lattice-based encryption, hash-based encryption, systems based on multivariate polynomial equations, and systems based on supersingular isogenies of elliptic curves. Exemplary code-based encryption functions include the McEliece cryptosystem and the Niederreiter cryptosystem which have been mathematically proven to have an exponential relation between key size and the Brute Force Time in the Post-Quantum world.
There are 2 main components of the secret key for the McEliece and Niederreiter schemes, i.e., a Goppa polynomial, G(x), and L, i.e., the set of numerators of the codeword positions, also referred to as the locators or support set. From coding theory it is well-known that it is G(x) and L that uniquely define the Goppa code, i.e., (L,G) code. G(x) and L uniquely determine the parity check and generator matrices and they are also necessary to realize a constructive decoding algorithm of the (L, G) code. In all known schemes based on Goppa codes, the secret is a polynomial G(x) where set L is a set of all elements of the Galois field GF(2m), where 2m=n is an element of a public key.
With respect to the first component of the secret key, the known McEliece and Niederreiter encryption schemes are based on binary irreducible Goppa codes with the following 4 definitions:
Definition #1: Goppa code is called irreducible if G(x) is an irreducible polynomial.
Definition #2: A binary vector a=(a1a2 . . . an) is a codeword of (L, G) code if, and only if, the following equality is satisfied:
where αi∈L, and L={α1,α2, . . . , αn}⊆GF(2m),G(αi)≠0,∀αi∈L.
Definition #3: Goppa code is called separable if the polynomial G(x) does not have multiple roots.
Definition #4: Goppa code is called wild if the polynomial G(x) has the following form: G(x)=g(x)96 where g(x) is a separable polynomial.
With respect to the second component, the second part of the private key of McEliece and Niederreiter schemes is the support set L ⊆GF(2m). In a classical McEliece scheme there are two matrices used: S, a random non-singular k×k matrix, and P, a random n×n permutation matrix. In the McEliece scheme, by using the two matrices and a generator matrix G, obtained from L and G(x), a public key matrix G*=S×G×P is calculated.
The McEliece cryptosystem (MECS) is defined as follows:
Private key: (Decoding algorithm, L, G(x), S, P)
Public key: G*=S×G×P
Encryption: Let m be a k-bit message, and let e be a random n-bit vector with Hamming weight WH(e)≤t. Then c=m×G*⊕ e is a ciphertext.
Decryption: Decryption is given by the following algorithm:
Although a more secure form of encryption, the McEliece and Niederreiter schemes use a large key size, requiring more storage resources. There is a need for a cyber security mechanism that addresses the challenges to cyber-security that quantum computers will present. This mechanism must not only be secure against the computing power of quantum computers but it must also be deployable in connection with classical computing devices, smartphones, Internet-of-Things (IoT) devices, miniature devices like credit card chips, etc. This mechanism must also maintain high efficiency in the encryption/decryption process.
In accordance with one aspect of the present invention, a cryptographic system and cryptographic method is provided in which an input device receives data to be encrypted. The cryptographic system and method also includes a processor for receiving the data to be encrypted and encrypting that data using instructions from a cryptographic engine. In the cryptographic system and method, the instructions when executed encrypt the data using a code-based encryption scheme based on binary irreducible Goppa code in which the support set consists of the rational functions with a degree of the denominator not greater than the degree of the Goppa polynomial.
In accordance with another aspect of the invention, the instructions when executed also use the Goppa codes in a weighted Hamming metric.
In yet another aspect of the invention, the polynomials have degree not greater than r, where r is the maximum degree of the denominator of a rational function over F2
In yet another aspect, a system and method is provided for creating a public key cryptographic platform that has increased security against cyber attacks using quantum computers. In this embodiment there are in general 3 different ways of implementation: 1) Signature-only; 2) Encryption-only; 3) Signature+Encryption. Signature-only implementation is utilized, for example, when authenticity of the message needs to be verifiable but the message can be transmitted and stored without encryption. An example of this is public Blockchain that is storing publicly-accessible data.
Encryption-only implementation is utilized, for example, when messages cannot be altered, corrupted, or replaced. An example is when the media is protected from tampering, but secrecy is required. This implementation is also suitable for cases such as, but not limited to, Tor, I2P, etc. when a sender remains anonymous so that the identity is unknown and therefore signature is not required. Another typical usage is hard drive encryption, folders/files encryption, database encryption, etc.
Signature+Encryption implementation is utilized, for example, when messages are first signed with the sender's private key, then encrypted with the receiver's public key before being transmitted to the receiver and finally decrypted by the receiver using the private key at the receiver. This kind of implementation can be found in most of the modern cryptographic frameworks and protocols such as, but not limited to, SSL, SSH, NPM, PGP/GPG, etc.
In accordance with another aspect of the present invention, a Trusted Platform Module (TPM) is provided for creating a public key cryptographic platform that has increased security against cyber attacks using quantum computers.
In accordance with another aspect of the present invention, an USB secure key is provided for creating a public key cryptographic platform that has increased security against cyber attacks using quantum computers.
In accordance with yet another aspect of the present invention, a Post-Quantum Blockchain (“PQBC”) can be built to create a DLT that is safe in the post-quantum world of computing. This ensures sensitive data like financial transactions, privacy data, etc. can be trusted even in the post-quantum world of computing.
Aspects of the present invention can be applied to virtually any industry to increase security. Application to DLT is only one example of the applications. Optionally, encrypting data blocks in PQBC can further raise security.
There has thus been outlined, rather broadly, certain embodiments of an example of the invention in order that the detailed description thereof herein may be better understood, and in order that the present contribution to the art may be better appreciated. There are, of course, additional embodiments of an example of the invention that will be described below and which will form the subject matter of the claims appended hereto.
In this respect, before explaining at least one embodiment of an example of the invention in detail, it is to be understood that an example of the invention is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The invention is capable of embodiments in addition to those described and of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein, as well as the abstract, are for the purpose of description and should not be regarded as limiting.
As such, those skilled in the art will appreciate that the conception upon which this disclosure is based may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the present invention.
The invention will now be described with reference to the drawing figures in which like reference numerals refer to like parts throughout. In
The encryption key and encrypted data may be received from inside a computing device, such as a personal computer, from one or more devices within a network or from third party devices outside the network. As described in more detail below, it will be readily understood that the public key cryptographic device can be any device capable of performing the processes described herein whether integrated into a single semiconductor package or distributed amongst several semiconductor devices contained within a single computer or server or distributed over multiple devices within one or more networks.
The cryptographic device 100 includes an input/output device 106, which can, for example, be a network communication interface, for receiving the plain data from the input device 104 and receiving the encryption key. The plain data and encryption key are then forwarded to an Input/Output Bridge 108 and a Memory Bridge 110 for storage in system memory 112. In exemplary embodiments the System Memory 112 may contain operating instructions such as, but not limited to, the Operating System 114. In addition to the operating system as well as other operating instructions 114 that are stored in system memory 112, the system memory includes the processing instructions of a cryptographic engine 116. The cryptographic engine 116 provides the operational instructions for the cryptographic functions such as encryption, decryption, digital signature, verification of digital signature, etc.
The cryptographic processing of the encrypted data is performed in the CPU 118 that is linked to system memory 112 via a Memory Bus. The CPU 118 can be implemented as a parallel co-processor, a field programmable gate array (FPGA), microprocessor, or the like, as is well understood.
Where all components of the system are contained within a single device, as depicted in
The embodiment of
In this embodiment, a special representation of the parity check matrix H, and the generator matrix G of the code, a special selection of the error vector, and/or a special selection of the codeword presentation by the additional field(s) inclusion are utilized. In an embodiment a parity check matrix H is generated for an n, k, d binary generalized (L, G) code wherein n, k, and d, are positive integers, n is a code length, k is a number of information symbols and d is a minimal distance n≤Σi=1rI2
In this embodiment, by using the L* support set directly instead of L with matrix S and P, we can obtain the following variant of McEliece scheme:
Private key: (Decoding algorithm, L*, G(x))
Public key: G*
Encryption: Let m be a k-bit message, and let e be a random n-bit vector with Hamming weight WH(e)≤t. Then c=m×G*⊕ e is a ciphertext.
Decryption: Obtaining m by using decoding algorithm (error correcting) with knowledge L* and G.
In the Niederreiter scheme, by using the two matrices and parity check matrix H, obtained from L and G(x), a public key matrix H*=A×H×P is calculated. As with the McEliece scheme, by using the L* support set directly instead of L with matrix A and P, we can obtain the following variant of Niederreiter scheme:
Public key: H*
Encryption: Let m be a message, with Hamming weight WH(e)≤t. Then c=m×H*T is a ciphertext.
Decryption: Obtaining m by using decoding algorithm (error correcting) with knowledge L* and G(x).
This implementation allows for: 1) the expansion of the selection of a support set, thereby expanding the available private keys; 2) use of rational functions of degree greater than one to keep the calculation in a finite field with a comparable code length. For example, for rational functions of degree 2 with coefficients from the field GF(2m), the code length is n=22m−1+2m−1. The practical benefits of using rational functions with different degree are: 1) reducing the amount of CPU cycles needed in the encryption, decryption, and key generation processes; and 2) increasing the security for codes with the same parameters (n, k, d), as in classical Goppa codes.
The generalized (L, G) code of an embodiment of the present invention is characterized by a set L where the proper rational functions of F2
In an embodiment of the invention, a special support set L is used as a second part of the private secret key in the McEliece and Niederreiter method. In this embodiment, we have the following additional definitions:
Definition #5: Support set L is defined as follows:
where f′i(x) is a formal derivative of fi(x) in GF(2m) and fi(x)=xl
Definition #6: Binary vector a=(a1,a2, . . . , an) is a codeword of generalized (L, G) code if and only if the following equality is satisfied:
l=max li and the decoding algorithm corresponding to it is determined. To construct a parity check matrix for such generalized (L, G) code the following presentation for rational functions
by modulo G(x) is used:
The equation for the generalized Goppa code can then be rewritten as:
From this equation a parity check matrix H is obtained:
From this parity check matrix we can obtain a generator matrix G for the generalized (L, G) code and by using matrix S and P to calculate the public key matrix G*=S×G×P.
In another embodiment we can also use the fractions
with different degrees of fi(x) for support set L. By using irreducible polynomials f(x) with degree not greater than r for support set we can obtain a generalized Goppa code with codeword length n≤Σi=1rI2
The following two examples are provided for illustration purposes:
Example 1: In this example m=6 and r=2. Since I2
we obtain n=2048+32=2080. Let d=61, t=30 then we have k≥2080−60·6=1720.
Example 2: For l=2 and fi(x)=(x−βi) (x−βi2
where G(x)=Σi=0tgixi, gi ∈ GF(2m), gt≠0, g0≠0 and
The coefficients at xt−1,xt−2, . . . , x,1 in the sum
A parity check matrix H is defined by:
By way of the foregoing, a special generalization of Goppa codes is constructed with a support set L as a set of rational functions
The special generalization of Goppa codes is neither a Reed Solomon (RS) code nor an alternate code.
For decoding these generalized Goppa codes, the Goppa polynomial G(x) and support set L must be known. A classical decoding algorithm (Euclidean, Berlekamp-Massey, Patterson, etc.) can then be used.
Using a set of position numerators of degree greater than 1, the degree of Galois field extension m for obtaining a support set L is reduced, thereby reducing the complexity of the calculations in the decoding process. The degree m of the field extension is reduced by r times, where r is the degree of the position numerators.
By way of example, a scheme (2060, 1720, t=30) can be constructed close in parameters to the classical McEliece and Niederreiter (2048, 1718, t=30) scheme by using elements from the Galois field GF(26) instead of the field GF(211) used in the original scheme. Therefore in the scheme of this example, all calculations in the decoding procedure can be done in the Galois field GF(26) with only 26 elements instead of the Galois field GF(211) with 211 elements required.
In the embodiment depicted in
In the alternative embodiment of
An application of the foregoing systems is depicted in
Alternative instructions that can be implemented by the device of
For illustration purposes, m determines the Galois field GF(2m) used in the calculations while r and m determine the size of support set L. Since code length n, r, and t determine a minimal distance of the code, therefore these parameters also determine the number of errors that could be corrected by such error correcting code. The private support set L generator 160 chooses or generates n elements (rational functions
to support set L. For the sake of clarity, fi(x) should be an irreducible polynomial of degree r. There are well-known methods to generate such polynomial, which are outside the scope of this invention. The Private Goppa Polynomial G(x) processor 162 chooses and/or generates primitive polynomial degree t from F2
A method of encrypting a message in accordance with an embodiment of the present invention is depicted in
A method of decrypting an encrypted message in accordance with a preferred embodiment of the invention is depicted in
The decoded message 184 is an information vector e of the length n and weight in the weighted Hamming metric less than or equal to t.
A method of obtaining a digital signature for input data, using the cryptographic device 100, is depicted in
The second hash process 194 and the decoder 196 are repeated with an incrementing i value until a successful decoding is reached. The resulting digital signature 120, represented as {s,i}, consists of two elements: 1) a vector s of the length n and weight in the weighted Hamming metric of less than or equal to t; and 2) a parameter i equal to the number of the successful steps.
A method of verifying a digital signature for given data, in the cryptographic device 100, is depicted in
Blockchains are often implemented using a public/private key pair. In some embodiments, the private key may be used to sign transactions or other data, and the public key of that pair may be used to verify the signature (e.g., using elliptic curve cryptography, which is not quantum-safe). The sizes of keys used in blockchains are each typically about 32 bytes (B), which is smaller than the size of a key used in any quantum-safe method.
The output of hashing functions is typically a hash value having a size of 32 B. Some embodiments may perform a hashing function on the public key of a quantum-safe public key cryptographic device to be able to maintain use of a same-sized public key in the data structure or code of the blockchain by instead using that hash value of the public key of the quantum-safe public key cryptographic device.
In these or other embodiments, a look up table (LUT) may be used to look-up a hash value that may be inputted into this table, which may output the corresponding public key; inverse functionality is also contemplated whereby an inputted public key of a quantum-safe public key cryptographic device into the LUT may output a corresponding hash value. The LUT may thus be between the hash, which may be 32 B, and the full public key of the quantum-safe public key cryptographic device, which may be larger than 32 B. For example, the LUT may have two columns, one for the hash values and the other for the full public keys. As such, very little changes may be needed to existing blockchain code to adopt a quantum-safe method.
In a blockchain, the public key is published within the blockchain while the nodes use the private key to sign a transaction or block to be verified by others using the public key. As mentioned, many blockchains use elliptic curve as the cryptographic method. The problem to convert any blockchain to become quantum-safe is that the public key of any quantum-safe algorithm has a size that is greater than 32 B. Therefore, the heart of the code in the blockchain would otherwise have to be modified. The herein-disclosed approach may use a hash value and a LUT to obtain the public key. For example, the public key in the blockchain code may not be the real public key but instead it may be the hash of the public key. A database of public keys and corresponding hash values may be maintained to look-up the real public key. The hash value having a size of 32 B, it may fit well with implementations using a same-sized public key (e.g., the size of an elliptic curve public key).
In some embodiments, a cryptographic system may comprise a processor configured to: generate a public/private key pair for a quantum-safe cryptographic device; perform a hash function on the public key to obtain a hash value; and, responsive to a request or need for the public key to verify a signature of data from a blockchain, obtain a LUT comprising the public key and the hash value. In these or other embodiments, the public key may have a size that is greater than a size of the hash value.
In some embodiments, a cryptographic system may comprise a processor configured to: generate a public/private key pair for a quantum-safe cryptographic device; perform a hash function on the public key to obtain a hash value; and, responsive to a request or need for the public key to encrypt data to be added to a blockchain, obtain a LUT comprising the public key and the hash value.
In some embodiments, an existing blockchain may be converted to a PQBC. For example, a hash value of a public key of a quantum-safe algorithm may be used together with legacy elliptic curve keys such that the blockchain, before the conversion, may be validated against the legacy elliptic curve code. As a result, the system substantially becomes a hybrid one.
The disclosed approach further involves an algorithm for hiding private data in multimedia files (e.g., a set of images or a video) or another computer file (e.g., a message), by using steganography with an error-correction method (e.g., Goppa codes).
Steganography is the practice of concealing a message within computer file(s), another message, or a physical object. In digital steganography, electronic communications may include steganographic coding inside of a transport layer, such as a document file, image file, program, or protocol.
Whereas cryptography is the practice of protecting the contents of a message alone, the herein-disclosed use of steganography may conceal the fact that a secret message is being sent and its contents, and the alteration to include the secret message or other data may be substantially subtle to the extent that an observer is not likely to notice it.
Contemplated herein is use of steganography to hide some private data (e.g., key) in an image (e.g., of JPEG or another format) or another set of data. And a passphrase or a personal identification number (PIN) code may be inserted thereat or otherwise used thereabout to later extract out the private key. For example, the PIN may be a code (e.g., alpha-numeric) or seed, e.g., used in a process for authenticating or securing data. As such, the PIN may dictate how the private data is distributed into the media file, e.g., by adding a suitable “error vector” into the media file for data hiding.
In this or another example, the same or similar Goppa code method disclosed above may be used but in reverse (e.g., to embed the private data into the image or the other set of data). For example, the image may be used in conjunction with the error vector of the herein-disclosed Goppa code technology. In this or another example, the error vector of the Goppa code may be used to insert an error into the image, and the private data may be considered as the secret data (which is disclosed above as being encoded). More particularly, the encoding key may be used to derive the error vector, and disclosed embodiments may use that to determine how to add that “error” into the picture.
As such, rather than using a set of words to retrieve otherwise inaccessible private data, herein-contemplated is an approach that involves inserting a private key into a captured image, other sensed data, or another simple type of object (e.g., which may not be derivable). The resulting image may appear substantially unaltered, and the inserted data may not be retrievable therefrom without the PIN.
In some embodiments, the image, having the private data secretly stored therein, may then be digitally signed as a proof of identify or proof of ownership.
The image having the embedded data may, as a result of the herein-disclosed concealing computer-implemented operations, not need to be stored in substantially secure storage, e.g., being instead downloadable upon a request at a later time. For example, this image may be stored in a more public space (e.g., in the cloud). In this or another example, the one or more steganographic files may be saved at a location, without disclosing the private key hidden inside of it. This approach may be more secure, e.g., when the PIN is preserved secretly and separately from their steganographic containers.
The herein-disclosed approach may involve the concept of “subliminal message,” e.g., by embedding the private data into a normal picture/audio/video file by using a PIN as the seed. For example, the picture/audio/video file may look normal even though the private data may be embedded in it similar to the concept of a subliminal message. In other words, the private data may not be re-derived without the PIN. Since the PIN may be much easier to remember than a 24-word list, it is feasible for the user to simply remember it. Even if the user prefers to write down the PIN for safety and store it in a safety box, someone knowing the PIN may still not be able to derive the private data without the encoded picture/audio/video file. Even losing the paper, it is much more feasible to remember the PIN than a 24-word sequence.
Many types of modern software systems (e.g., blockchains, crypto-wallets, email/file encryption solutions, virtual private networks (VPNs), etc.) rely on public key cryptography. In such systems, information is encrypted and decrypted and/or digitally signed and verified with the help of a public key and private key (or secret key (SK)), i.e., a key pair. The public keys may be distributed openly, but the SKs must be kept secretly (e.g., never being exposed).
In many embodiments of such cryptographic systems, SKs need to be backed up, to provide emergency recovery opportunities.
In some implementations, SKs need to be safely and securely replicated to other systems of the same owner. In these or other implementations, there are unfortunately opportunities for adversaries to intercept the SKs.
A set of words may be used as a seed for generating a private key such that if the key is lost it may be regenerated with said set of words. For example, when someone is creating a crypto wallet, the industry standard is to randomly create a list of English words (e.g. 24 words) as the seed words while using the seed words to derive a private key. The user will write down these 24 words as the secret and store them in a safe place. If anyone knowing these 24 words or the user loses the paper, the wallet problematically will be rendered inoperable.
To prevent any related damage or cyber security attack, a contemplated storage solution of the SK may involve encrypting them, e.g., by using a symmetric algorithm (e.g., AES), with the symmetric keys being derived from the PIN. But even this method may suffer from a number of potential vulnerabilities. For example, the PIN may not be strong enough, and it may be exploited by a vocabulary attack. In another example, even with a strong PIN, ways of deriving the symmetric key from them may contain one or more vulnerabilities that reduce the complexity of brute-force attacks. In another example, with upcoming quantum computing (QC), one may potentially attack via brute-force even a strongest PIN within a reasonable timeframe. There is thus a need in storage solutions for SKs to be backed-up or transferred, to mitigate such risks.
As mentioned, a herein-disclosed approach involves steganography and hiding the SKs in one or more multimedia steganographic files, such as a photographic image, video or audio file. Having the SKs hidden therein may significantly increase the complexity of a brute-force attack due to absence of knowledge of where the bits of the SK reside. In some embodiments, an error-correction system (e.g., Goppa codes) may be used to encode the bit positions of the SK hidden in one or more steganographic files using an encoding key (EK). The SK may only be extracted back using the decoding key (DK). An advantage is that the one or more steganographic files, which may appear as ordinary multimedia file(s), may operate as a secure backup of the SK.
Using more than one steganographic file may further increase the security due to absence of knowledge about which file(s) a collection contains the SK or their fragments.
In some embodiments, the PIN may be used to derive a pair of EK/DK.
Yet another embodiment is that the PIN is used to derive 302 both a pair of EK/DK as well as a symmetric key. The way gives an even higher security whereby the symmetric key may be used to encrypt the SK. The symmetric-encrypted SK may then be hidden 304, 306 in one or more steganographic files using the EK. During the restoration process, the PIN may be used to retrieve both the DK and the symmetric key, e.g., with the DK being used to extract 308 the symmetric-encrypted SK. This may be followed by performing decryption, using the symmetric key, to retrieve 310 the original SK.
In some embodiments, the herein-disclosed approach may recover the encrypted and encoded SK even after processing the multimedia containers that hold them, such as changing their compression rate.
In an example, to conceal 2 megabits, the herein-disclosed approach may need a block of (22m+2m)/2−1 bits for Goppa-encoding. The herein-disclosed approach may use ¼ of a real image file (e.g., a bitmap image in BMP/RGB format) as an effective steganographic container, such as one of the color channels.
Therefore, the information rate of the herein-disclosed system may be about m/(22m+2m). The EK for each block may be a Goppa polynomial of degree 2 from a Galois field GF(22m). And a number of such polynomials may be: (22m−2m)/2.
Therefore, if the herein-disclosed approach uses different Goppa polynomials for each k information blocks, said approach may obtain ((22m−2m)/2)k different values of the EK, since the length of the EK may be about (2m−1)k bits. This may allow a hiding of even potentially large post-quantum cryptography (PQC) SKs within any (e.g., even non-high definition (HD)) quality photographic images.
Although specific embodiments of the invention have been set forth herein, it is not intended that those be limiting. It should be understood that alternate embodiments, including variations and modifications thereto as well as various other features or functions, can be added to the present invention without departing from the scope of the present invention.
This application is a continuation-in-part (CIP) of U.S. patent application Ser. No. 17/689,288 filed Mar. 8, 2022, which is a CIP of U.S. patent application Ser. No. 16/268,098 filed Feb. 5, 2019, now U.S. Pat. No. 11,271,715, which is a National Stage of International Application No. PCT/RU2018/000847, filed Dec. 21, 2018, the entire contents of these applications being incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
Parent | 17689288 | Mar 2022 | US |
Child | 17708426 | US | |
Parent | 16268098 | Feb 2019 | US |
Child | 17689288 | US |