# Patent

## Title
Resharing of a split secret

## Abstract

A processor-based method for secret sharing in a computing system is provided. The method includes encrypting shares of a new secret, using a previous secret and distributing unencrypted shares of the new secret and the encrypted shares of the new secret, to members of the computing system. The method includes decrypting at least a subset of the encrypted shares of the new secret, using the previous secret and regenerating the new secret from at least a subset of a combination of the unencrypted shares of the new secret and the decrypted shares of the new secret.

## Background
BACKGROUND
Secret sharing splits a secret into shares (which could be termed parts or pieces of the secret), and was invented by Adi Shamir and George Blakley, independently. The secret can be regenerated, using a sufficient subset (i.e., a specific threshold minimum number of shares or up to and including all) of the shares. Depending on the scheme used for secret sharing, a mathematical operation or algorithm is applied to a sufficient number (specific to the scheme) of the shares, parts or pieces of the secret to recover the secret. Secrets can be used in computing, communication and storage systems for encrypting and decrypting data or the secrets can act as passwords, keys for locks, or features for other security functions. For example, a secret (and each of the shares, parts or pieces of the secret) can be a binary number. In a distributed system, sending shares of a secret to different members of the system protects against theft of or from, or unauthorized access to any one member (or even a few members) of the system, which would at most result in theft of a share or a few shares, but not an entire key or enough shares to regenerate a key. Periodic generation of a new key is desirable from the standpoint of providing additional protection. However, it may not be possible to write a new secret to all of the members of a distributed system, because one or more members might be unavailable at the time the shares are written. If this happens, and the system fails, it is possible that a different set of system members will be available upon reboot of the system, in which case the new secret might not be recoverable, as the required quorum of shares for regenerating the secret might not be available. A distributed system facing such a condition might start again and re-split a secret, sending shares to available system members, whereupon the above situation could recur many times or indefinitely.
It is within this context that the embodiments arise.
SUMMARY
In some embodiments, a processor-based method for secret sharing in a computing system is provided. The method includes encrypting shares of a new secret, using a previous secret and distributing unencrypted shares of the new secret and the encrypted shares of the new secret, to members of the computing system. The method includes decrypting at least a subset of the encrypted shares of the new secret, using the previous secret and regenerating the new secret from at least a subset of a combination of the unencrypted shares of the new secret and the decrypted shares of the new secret.
In some embodiments, a tangible, non-transitory, computer-readable media having instructions thereupon which, when executed by a processor, cause the processor to perform a method. The method includes encrypting, with a previous secret, shares of a new secret and distributing encrypted shares and unencrypted shares of the new secret. The method includes decrypting, with the previous secret, available encrypted shares of the new secret and reproducing the new secret from at least a subset of available unencrypted shares of the new secret and the decrypted shares of the new secret.
In some embodiments, a computing system with a shared secret is provided. The computing system includes a secret generator, configured to generate and regenerate secrets, a share splitter, configured to split a secret into a plurality of shares, an encryption/decryption unit, configured to encrypt and decrypt, and one or more processors, configured to perform actions. The actions include encrypting shares of a second secret, using a first secret and the encryption/decryption unit and sending encrypted shares and unencrypted shares of the second secret to members of the computing system. The actions include decrypting at least a subset of the encrypted shares of the second secret, using the encryption/decryption unit and the first secret and regenerating the second secret, using the secret generator and unencrypted shares and decrypted shares of the second secret.
Other aspects and advantages of the embodiments will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the described embodiments.



BRIEF DESCRIPTION OF THE DRAWINGS
The described embodiments and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings. These drawings in no way limit any changes in form and detail that may be made to the described embodiments by one skilled in the art without departing from the spirit and scope of the described embodiments.
FIG. 1 is a block diagram of a storage device with facilities for sharing and resharing a split secret in accordance with some embodiments.
FIG. 2 is a system diagram with multiple storage devices, generating a secret “A” and shares of the secret in accordance with some embodiments.
FIG. 3 is a system diagram with the storage devices generating a secret “B” and encrypting some of the shares of “B” with “A” in accordance with some embodiments.
FIG. 4 is a system diagram with the storage devices regenerating the secret “A”, decrypting encrypted shares of “B” and regenerating the secret “B” in accordance with some embodiments.
FIG. 5 is a system diagram with a storage device decrypting a key using one secret, and re-encrypting the key with another secret in accordance with some embodiments.
FIG. 6 is a flow diagram of a method for secret sharing, which can be practiced by one or more processors of a computing, communication or storage system in accordance with some embodiments.
FIG. 7 is an illustration showing an exemplary computing device which may implement the embodiments described herein.



DETAILED DESCRIPTION
A system and related method for resharing of a split secret are herein described. Although shown in embodiments of storage devices in a storage system, the mechanisms and techniques for resharing of a split secret are applicable to computing, communication or storage systems that use a secret for various functions or purposes, and can be used in systems that are distributed, centralized, monolithic, localized, networked, cloud-based, etc. FIGS. 1-5 show storage devices using a secret to encrypt and decrypt, or otherwise lock and unlock, a key that encrypts and decrypts data in the storage system. A new secret is generated and split, and some of the new shares are encrypted, using a previous secret. Unencrypted and encrypted shares are distributed to devices of the system. It should be noted that a share(s) may be referred to as a part(s) of a secret or piece(s) of a secret in some embodiments. To unlock (e.g., decrypt) the locked (or encrypted) key, the system gathers together available unencrypted and encrypted shares, decrypts the encrypted shares using the previous (i.e., old) secret, and uses a sufficient subset of the combination of unencrypted shares and decrypted formerly encrypted shares to regenerate the new secret. Using the new secret, the system unlocks or decrypts the locked or encrypted key, which can then be used for decrypting data in the storage system, or encrypting new data to be stored in the storage system, etc. FIG. 6 presents a method for secret sharing, which is used by the present embodiments and can also be used by other systems for other mechanisms and techniques applying secrets. The mechanism can be applied in an iterative manner, to replace an older secret with a newer secret key, e.g., on a regular or irregular basis, or on demand.
FIG. 1 is a block diagram of a storage device 102 with facilities for sharing and resharing a split secret. In present embodiments, the storage device 102 could be or include a storage node, a storage unit, or a storage drive, and in further embodiments could be a compute only node in a storage cluster or storage system, or other device in another system as the embodiments are not limited to storage systems and may be integrated with any computing device. The various mechanisms shown in FIG. 1 and elsewhere in the application could be implemented in software, hardware, firmware or combinations thereof and included in the storage device 102, with each storage device 102 having each of these mechanisms, or they could be separate from and coupled to the storage device 102, or shared with other storage devices 102, or various combinations thereof. One or more processors 104 could execute software and operate various mechanisms within the storage device 102. The storage device 102 has memory 106, which includes, in some embodiments, a header section 116, a metadata 118 section, and a data storage 120. A secret generator 108 can generate secrets, and regenerate secrets from shares. As noted above, a secret can be split into shares and each share may be referred to as a part of a secret or a piece of a secret in some embodiments. A share splitter 110 splits a secret into shares. Secrets, and shares, could be for example binary, octal, decimal or hexadecimal numbers, alphanumeric strings, or other combinations of bits or symbols. An encryption/decryption unit 112 encrypts and decrypts whatever needs encrypting or decrypting, such as in present embodiments data, a key, or shares of a secret. A communication unit 114 handles communication between storage devices 102 in the storage system, or to other devices in or external to the system, and could include a network port or other wired or wireless communication port. Multiple storage devices 102 are connected, e.g., via a network or bus, to form a storage system, in some embodiments.
FIG. 2 is a system diagram with multiple storage devices 102, generating a secret “A” 210 and shares of the secret. A secret generator 108, which could belong to one of the storage devices 102 or be a shared resource, generates secret “A” 210, for example as a random number from a seed 224 for an initial operation, or in an ongoing operation from a long-ago seed 224 in some embodiments. Each new secret could be independent of previous secrets, or could be based on one or more of them, e.g., as a seed 224, in various embodiments. There are many techniques for generating secrets and shares of secrets, and present embodiments are not dependent on which method or mechanism is used for generating secrets, nor should the following examples be seen as limiting as other known techniques for generating secrets and shares of secrets may be integrated with the embodiments. A key encrypting key container could be used as a secret, as could a key encrypting key plus a version number, or a data encryption key. Shares of a secret could be generated using linear interpolation in some embodiments. In other examples, shares of a secret could be generated using Reed Solomon coding, throwing away original data and keeping only the erasure coding, or shares of a secret can be generated using exclusive or (XOR) operations in some embodiments. The share splitter 110 splits the secret “A” into shares “A0” 212, “A1” 214, “A2” 216, “A3” 218, “A4” 220 and “A5” 222, each of which is sent to a storage device 102. As noted above, each of the shares 212-222 may be referred to as a part of a secret or piece of a secret. The number of shares and naming convention for shares depicted is by way of example only, and should not be considered limiting. Some embodiments of the system distribute more than one share to each storage device 102. When the system is satisfied that the shares of secret “A” 210 are all successfully distributed to storage devices 102, the system can use the secret “A” 210 to encrypt a key 204.
The (unencrypted) key 204 is used to encrypt data 202. For example, a storage device 102 could input the data 202 and the key 204 into an encryption/decryption unit 112, which then outputs data encrypted by the key 206 (i.e., data 202, as encrypted by the key 204). The storage device 102 can then store the encrypted data 206. To lock the key 204, the storage device 102 inputs the key 204 and the secret “A” 210 into the same or another encryption/decryption unit 112, which then outputs the key encrypted by the secret “A” 208 in some embodiments. As a result of these operations, the storage device now stores encrypted data and has a locked or encrypted key, and shares of the secret are distributed to storage devices 102 throughout the system. The other storage devices 102 can perform similar operations with the data those storage devices store. Thus, the system now has encrypted data, one or more locked keys 204 (which could be the same key 204 or differing keys 204 across the system), and a shared secret. Referring back to FIG. 1, each storage device 102 could store an encrypted key (e.g., a key encrypted by secret “A” 208), and one or more shares, in the header section 116 of memory 106, and store encrypted data in the data storage 120 in some embodiments.
FIG. 3 is a system diagram with the storage devices 102 generating a secret “B” 302 and encrypting some of the shares of “B” with “A”. The system is able to decrypt data, and encrypt data, after unlocking or decrypting the key 204 (see FIG. 2). To recover the key 204, a storage device 102 gathers together as many shares of “A” 304 as are available (considering that some other storage devices 102 may be unresponsive, off-line, failed, or otherwise temporarily or permanently unavailable). If all of the shares of “A” 304, or at least a minimum threshold number of the shares of “A” 304 to meet the sufficient subset of shares requirement, are available, the available shares are input into the secret generator 108 which regenerates the secret “A” 210. The storage device 102 inputs the secret “A” 210 and the key encrypted by secret “A” 208 into the same or another encryption/decryption unit 112, which outputs the decrypted key 310 (i.e., the same key 204 that was originally encrypted by the secret “A” 210). The decrypted key 310 is inserted into the same or another encryption/decryption unit 112 along with the data encrypted by key 306 (e.g., the same or other data 202 that was encrypted using the key 204 in FIG. 2), and the encryption/decryption unit 112 outputs decrypted data 308, for use or storage by the storage device 102 or elsewhere within or external to the system. The storage device 102 could also use the decrypted key 310 to encrypt further data, using the process shown in FIG. 2. The system now has a mechanism to unlock or decrypt an encrypted or locked key, and use the now-decrypted or unlocked key to decrypt or encrypt data.
Still referring to FIG. 3, to transition to a new secret, the secret generator 108 generates the secret “B” 302. The share splitter 110 splits the new secret “B” 302 into shares “B0” 312, “B1” 314, “B2” 316, “B3” 318, “B4” 320, and “B5” 322. These new shares are fed into the encryption/decryption unit 112 along with the previous or old secret “A” 210, resulting in encrypted shares “B0” 324 encrypted by “A”, encrypted shares “B1” 326 encrypted by “A”, encrypted shares “B2” 328 encrypted by “A”, encrypted shares “B3” 330 encrypted by “A”, encrypted shares “B4” 332 encrypted by “A”, and encrypted shares “B5” 334 encrypted by “A”. The new shares (from new secret “B” 302) and encrypted new shares are sent to the storage devices 102 in various combinations, which could be specific to system implementations. In some embodiments, each storage device 102 receives at least one unencrypted share based on the new secret “B” 302 and at least one encrypted but different share also based on the new secret “B” 302, e.g., a different share based on secret “B” 302 and encrypted by the old or previous secret “A” 210. In the example shown, one storage device 102 receives the share “B0” 312 and “B1” 314 encrypted by “A” 326, and the other storage devices 102 each receive a corresponding share and differing encrypted share. If any one or two storage devices 102 are unavailable at any given time, sufficient shares and encrypted shares are available to make a sufficient subset of shares for recovery of the secret, as will be shown below with reference to FIG. 4.
It should be appreciated that various combinations of sets and subsets of encrypted and unencrypted shares are possible, and it is not required that the encrypted shares be encrypted from the unencrypted shares. For example, the system could generate a set of shares (e.g., from the share splitter 110), and encrypt some of the shares while leaving others of the shares unencrypted. Alternatively, the system could generate a set of shares, keep a copy of these unencrypted shares, and encrypt the same shares. In some embodiments, a combination of the above could be applied, e.g., with some shares distributed in both encrypted and unencrypted form, and other shares distributed only in encrypted form or only in unencrypted form. The total number of shares and/or the threshold number of shares required for regeneration of a secret could be set as a system dependent or situation dependent number. Two examples are provided below for illustrative purposes.
In a first example, there are seven storage devices 102, a minimum of five shares are needed to reconstruct a secret, and some of the devices are unavailable, as shown in Table 1.









TABLE 1









storage devices















0
1
2
3
4
5
6


















shares of secret “A”
A0
A1
A2
A3
A4
A5
A6


unencrypted shares of
B0
B1
B2
B3
B4


secret “B”


encrypted shares of
A(B4, B5)
A(B5, B6)
A(B0, B6)
A(B0,
A(B1,


secret “B”



B1)
B2)


storage device
yes
yes
yes
yes
yes
no
no


available for writing


secret shares


storage device
yes
yes
yes
no
no
yes
yes


available for reading,


reconstructing secret









The storage devices are numbered from zero through six (see first or top row of table 1). Each of the storage devices has a share of the secret “A” (see second row of table 1). In this example the system has started distributing shares of the secret “B”, but encountered some storage devices that are unavailable (see fifth or second from the bottom row of table 2). The first five shares of the secret “B” are successfully delivered to the first five storage devices (see third row of table 1). The first five storage devices have also received encrypted shares of the secret “B” (see fourth row of table 1). So, the first storage device 102 (numbered “0”) has two encrypted shares of secret “B”, namely the B4 share encrypted by secret “A” and the B5 share encrypted by secret “A” (shown in the table as A(B4, B5)). The next four storage devices 102 each have two more encrypted shares of secret “B”. Distribution of the shares of secret “B”, in unencrypted and encrypted form, is “successful” because all but two devices have received shares, and may be recovered directly by reading shares from each of the five devices 0-4. Secret “A” can be recovered from the five storage devices that are available, by obtaining the A0, A1, A2, A3 and A4 shares of “A” from the available storage devices 102 and regenerating the secret “A”. In some embodiments, if a different set of storage devices is available, as shown in the bottom row of table 2, because the two storage devices that were off-line during the writing of the secret shares become online and two other storage devices go off-line, the secret “A” could be regenerated from the A0, A1, A2, A5, A6 shares. In this example, only the first three unencrypted shares of secret “B”, namely B0, B1 and B2, are available. Then, using the now recovered secret “A”, the system can decrypt two more shares of the secret “B” from the first storage device 102. That is, the system obtains the B4 share encrypted by secret “A” and the B5 share encrypted by secret “A”, and decrypts each of these using the secret “A”. Now, from the five recovered shares of secret “B”, namely B0, B1, B2, B4 and B5, the system regenerates the secret “B”. It should be appreciated that this example shows how a secret can be written and recovered, even though one or more storage devices are off-line during the writing of the secret, and a different one or more storage devices are off-line during the reading and recovery of the secret.
In a second example, there are again seven storage devices, a minimum of five shares are needed to reconstruct a secret, and some of the devices are unavailable during writing or reading, as shown in Table 2.









TABLE 2









storage devices















0
1
2
3
4
5
6


















shares of secret “A”
A0
A1
A2
A3
A4
A5
A6


unencrypted shares of
B0
B1
B2


B5
B6


secret “B”


encrypted shares of secret
A(B7)
A(B8)
A(B9)


A(B12)
A(B13)


“B”


storage device available for
yes
yes
yes
no
no
yes
yes


writing secret shares


storage device available for
yes
yes
yes
yes
yes
no
no


reading, reconstructing


secret









As in the previous example, the storage devices are numbered from zero through six (see first or top row of table 2). Each of the storage devices has a share of the secret “A” (see second row of table 2). The system has begun distributing shares of the secret “B”, but some of the storage devices are unresponsive (see fifth row of table 2). The first three shares of the secret “B” are successfully delivered to the first three storage devices, and the last two shares of the secret “B” are successfully delivered to the last two storage devices (see third row of table 2). The first three and last two storage devices have also each received one encrypted share of the secret “B” (see fourth row of table 2). So, the first storage device (numbered “0”) has one encrypted share of secret “B”, namely the B7 share encrypted by secret “A” (shown in table 2 as A(B7)). The next two storage devices each have one more encrypted share of secret “B”. Distribution of the shares of secret “B”, in unencrypted and encrypted form, is incomplete, since two devices have not received their shares, but the secret “B” is still recoverable even if there were a system crash or other failure, or different storage devices were unavailable for reading. Secret “A” can be recovered if the same five storage devices are available for reading as were available for writing the secret shares, by obtaining the A0, A1, A2, A5 and A6 shares of “A” from the available storage devices (in the sixth or last row of table 2) and regenerating the secret “A”. In some embodiments the system attempts to recover the secret “B”, but storage devices number five and six are unavailable (see sixth or last row of table 2). In this embodiment, the system could still recover the secret “A” as described above regarding table 1. It should be appreciated that the embodiments enable multiple possibilities to recover secret “B”. The system could gather five unencrypted shares of the secret “B”, namely B0, B1, B2, B5 and B6, and regenerate the secret “B” from them, if the same storage devices are available for reading as were available for writing the secret shares. The system could use the recently recovered secret “A” to decrypt one or more of the available encrypted shares of secret “B”, then combine with some of the unencrypted shares of the secret “B” until a sufficient number of shares of secret “B” is obtained to regenerate the secret “B”. This could be accomplished with unencrypted shares B0, B2, B6 and decrypted shares B8 and B9, or unencrypted shares B1 and B5 and decrypted shares B7, B8 and B9, or other combination of sufficient number of shares of secret “B” gathered from available unencrypted and decrypted shares. If storage devices numbered five and six were off-line at the time of reconstructing the secret, as shown in the sixth or bottom row of table 2, the secret “B” could be reconstructed from the unencrypted shares B0, B1, B2 and decrypted shares B7 and B8 or B9, or some other combination of five shares. By using a combination of encrypted and unencrypted shares of a secret, distributed to storage devices in various combinations, the system can recover a secret even in cases where one or more storage devices are unavailable while the encrypted and unencrypted shares are being written to storage devices, and a different one or more storage devices are unavailable while the system reconstructs the secret. Various further scenarios of storage devices being unavailable when secret shares are being written, and the same or differing storage devices being unavailable when secret shares are being read and a secret reconstructed, are readily devised in keeping with the teachings disclosed herein.

FIG. 4 is a system diagram with the storage devices 102 regenerating the secret “A” 210, decrypting encrypted shares of “B” and regenerating the secret “B” 302. Keeping in mind that one or more of the storage devices 102 may be unavailable or unresponsive at any given time, the system gathers together shares of the secret “A” 210, for example by having storage devices 102 communicate with each other. The system also gathers together encrypted and unencrypted shares of the secret “B” 302. If the system is able to gather together a sufficient subset of shares of “A” 402, i.e., anywhere from at least the threshold number of shares of secret “A” 210 needed to regenerate the secret “A” 210 up to and including all of the shares of “A”, these shares are inserted into the secret generator 108, which regenerates the secret “A” 210. If not enough shares are available, the system can wait for a period of time and retry gathering a sufficient number of shares in some embodiments. Once the secret “A” 210 is regenerated, the secret “A” 210 and the available “A” encrypted shares of “B” 404 (i.e., shares of the secret “B” 302 as encrypted by the secret “A” 210 in FIG. 3) are input into the same or a differing encryption/decryption unit 112, which produces decrypted shares of “B” 408. If the combination of the gathered unencrypted shares of “B” 406 and the now decrypted shares of “B” 408 forms a sufficient subset of shares of “B” 410 (i.e., anywhere from at least the threshold number of shares of secret “B” 302 needed to regenerate the secret “B” 302 up to and including all of the shares of “B”), a sufficient number of these shares are input into the same or a differing secret generator 108, which outputs the regenerated secret “B” 302. If not enough shares are available, the system can wait for a period of time and retry gathering a sufficient number of shares in some embodiments.
FIG. 5 is a system diagram with a storage device 102 decrypting a key using one secret, and re-encrypting the key with another secret. In some embodiments, the system determines that all storage devices 102 have received their respective (unencrypted and/or encrypted) shares of the new secret, before proceeding with re-encrypting a key 204 with a new secret. This can be accomplished using polling, acknowledgment or other communication among storage devices 102 or other members of a system. To re-encrypt the key 204, e.g., the key 204 which was used to encrypt data 202 and which was encrypted with the secret “A” in FIG. 2, the storage device 102 obtains the key encrypted by secret “A” 208. The secret “A” 210 and the key encrypted by secret “A” 208 are input into the same or a differing encryption/decryption unit 112, which outputs the decrypted key 310 (i.e., the same number, or combination of bits or symbols as the original key 204). The decrypted key 310 and the secret “B” 302 are input into the same or another encryption/decryption unit 112, which outputs the key encrypted by “B” 502. This procedure can be used iteratively, to reencrypt a key with new secrets on an ongoing basis. Once new shares are stored and verified stored, previous versions (of shares and/or encrypted keys) can be destroyed, making share rotation possible and adding security.
With reference back to FIGS. 1-5, it is readily appreciated that present embodiments of storage devices 102 in a storage system, or other computing, communication or storage systems, could apply the above mechanisms and techniques iteratively. For example, after distributing shares of secret “B” 302 in both encrypted and unencrypted form, verifying that storage devices 102 have received respective shares, and re-encrypting the key 204 with the secret “B” 302, the system can repeat these processes for a new secret “C”, using the secret “B” as the previous or old secret. This process then repeats for the next new secret “D”, using the secret “C” as the previous or old secret, and so on. Systems that use a secret for other mechanisms or purposes may omit or modify the data encrypting and/or key encrypting processes according to designs or circumstances in some embodiments. In some versions, off-site storage is used for some of the encrypted and/or unencrypted shares. In some embodiments, the system can use new shares to regenerate further new shares for members of the system that are missing shares (whether encrypted or unencrypted), and update those members. It should be appreciated that the mechanism discussed above is faster and more reliable than updating all of the members of the system, and prevents an attack under which an attacker always keeps multiple members out of a system to prevent resharing. In a further embodiment, a master key can unlock a system with fewer members than might otherwise be required. Some of the shares can be encrypted with a key, but the key is then stored in or external to the system. By itself, the stored key cannot unlock a system member, however, the key can unlock the shares encrypted with that key. The mechanisms and techniques described herein improve reliability, security and responsiveness of a secure system, and provide a way to reliably advance to a new secret in the face of varying availability of various devices in the system while maintaining security against theft or unauthorized access of portions of the system.
FIG. 6 is a flow diagram of a method for secret sharing, which can be practiced by one or more processors of a computing, communication or storage system. The method can be practiced on or by embodiments of the storage device as described above or any other computing device. In an action 602, shares are generated from a new secret. A subset of the shares is encrypted, using a previous secret, in an action 604. Unencrypted and encrypted shares are distributed, in an action 606. The shares that are encrypted could be the same as, or different from, some or all of the unencrypted shares, in various embodiments of the method.
To later recover the new secret, the previous secret is regenerated in an action 608. The previous secret is regenerated from a sufficient subset of shares of the previous secret. This would be a threshold number of shares of the previous secret, or all of the shares of the previous secret, or any number of shares in between these two numbers of shares. The encrypted shares of the new secret are decrypted, using the previous secret, in an action 610. In an action 612, the new secret is regenerated, from a sufficient subset of shares. This would be a threshold number of shares of the new secret, or all of the shares of the new secret, or any number of shares in between these two numbers of shares, from the combination of the gathered available unencrypted shares and the decrypted shares from the gathered available encrypted shares.
It should be appreciated that the methods described herein may be performed with a digital processing system, such as a conventional, general-purpose computer system. Special purpose computers, which are designed or programmed to perform only one function may be used in the alternative. FIG. 7 is an illustration showing an exemplary computing device which may implement the embodiments described herein. The computing device of FIG. 7 may be used to perform embodiments of the functionality for resharing of a split secret in accordance with some embodiments. The computing device includes a central processing unit (CPU) 701, which is coupled through a bus 705 to a memory 703, and mass storage device 707. Mass storage device 707 represents a persistent data storage device such as a floppy disc drive or a fixed disc drive, which may be local or remote in some embodiments. The mass storage device 707 could implement a backup storage, in some embodiments. Memory 703 may include read only memory, random access memory, etc. Applications resident on the computing device may be stored on or accessed via a computer readable medium such as memory 703 or mass storage device 707 in some embodiments. Applications may also be in the form of modulated electronic signals modulated accessed via a network modem or other network interface of the computing device. It should be appreciated that CPU 701 may be embodied in a general-purpose processor, a special purpose processor, or a specially programmed logic device in some embodiments.
Display 711 is in communication with CPU 701, memory 703, and mass storage device 707, through bus 705. Display 711 is configured to display any visualization tools or reports associated with the system described herein. Input/output device 709 is coupled to bus 705 in order to communicate information in command selections to CPU 701. It should be appreciated that data to and from external devices may be communicated through the input/output device 709. CPU 701 can be defined to execute the functionality described herein to enable the functionality described with reference to FIGS. 1-6. The code embodying this functionality may be stored within memory 703 or mass storage device 707 for execution by a processor such as CPU 701 in some embodiments. The operating system on the computing device may be MS DOSTM, MS-WINDOWSTM, OS/2TM, UNIXTM, LINUXTM, or other known operating systems. It should be appreciated that the embodiments described herein may also be integrated with a virtualized computing system implemented with physical computing resources.
Detailed illustrative embodiments are disclosed herein. However, specific functional details disclosed herein are merely representative for purposes of describing embodiments. Embodiments may, however, be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein.
It should be understood that although the terms first, second, etc. may be used herein to describe various steps or calculations, these steps or calculations should not be limited by these terms. These terms are only used to distinguish one step or calculation from another. For example, a first calculation could be termed a second calculation, and, similarly, a second step could be termed a first step, without departing from the scope of this disclosure. As used herein, the term “and/or” and the “/” symbol includes any and all combinations of one or more of the associated listed items.
As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “includes”, and/or “including”, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Therefore, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.
It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
With the above embodiments in mind, it should be understood that the embodiments might employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing. Any of the operations described herein that form part of the embodiments are useful machine operations. The embodiments also relate to a device or an apparatus for performing these operations. The apparatus can be specially constructed for the required purpose, or the apparatus can be a general-purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general-purpose machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
A module, an application, a layer, an agent or other method-operable entity could be implemented as hardware, firmware, or a processor executing software, or combinations thereof. It should be appreciated that, where a software-based embodiment is disclosed herein, the software can be embodied in a physical machine such as a controller. For example, a controller could include a first module and a second module. A controller could be configured to perform various actions, e.g., of a method, an application, a layer or an agent.
The embodiments can also be embodied as computer readable code on a tangible non-transitory computer readable medium. The computer readable medium is any data storage device that can store data, which can be thereafter read by a computer system. Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer system so that the computer readable code is stored and executed in a distributed fashion. Embodiments described herein may be practiced with various computer system configurations including hand-held devices, tablets, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The embodiments can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
Although the method operations were described in a specific order, it should be understood that other operations may be performed in between described operations, described operations may be adjusted so that they occur at slightly different times or the described operations may be distributed in a system which allows the occurrence of the processing operations at various intervals associated with the processing.
In various embodiments, one or more portions of the methods and mechanisms described herein may form part of a cloud-computing environment. In such embodiments, resources may be provided over the Internet as services according to one or more various models. Such models may include Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). In IaaS, computer infrastructure is delivered as a service. In such a case, the computing equipment is generally owned and operated by the service provider. In the PaaS model, software tools and underlying equipment used by developers to develop software solutions may be provided as a service and hosted by the service provider. SaaS typically includes a service provider licensing software as a service on demand. The service provider may host the software, or may deploy the software to a customer for a given period of time. Numerous combinations of the above models are possible and are contemplated.
Various units, circuits, or other components may be described or claimed as “configured to” perform a task or tasks. In such contexts, the phrase “configured to” is used to connote structure by indicating that the units/circuits/components include structure (e.g., circuitry) that performs the task or tasks during operation. As such, the unit/circuit/component can be said to be configured to perform the task even when the specified unit/circuit/component is not currently operational (e.g., is not on). The units/circuits/components used with the “configured to” language include hardware—for example, circuits, memory storing program instructions executable to implement the operation, etc. Reciting that a unit/circuit/component is “configured to” perform one or more tasks is expressly intended not to invoke 35 U.S.C. 112, sixth paragraph, for that unit/circuit/component. Additionally, “configured to” can include generic structure (e.g., generic circuitry) that is manipulated by software and/or firmware (e.g., an FPGA or a general-purpose processor executing software) to operate in manner that is capable of performing the task(s) at issue. “Configured to” may also include adapting a manufacturing process (e.g., a semiconductor fabrication facility) to fabricate devices (e.g., integrated circuits) that are adapted to implement or perform one or more tasks.
The foregoing description, for the purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the embodiments and its practical applications, to thereby enable others skilled in the art to best utilize the embodiments and various modifications as may be suited to the particular use contemplated. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

## Claims

1. A processor-based method for secret sharing in a computing system, comprising:
encrypting, by an encryption/decryption unit, shares of a new secret, using a previous secret;
distributing unencrypted shares of the new secret and the encrypted shares of the new secret, to members of the computing system;
decrypting, by the encryption/decryption unit, at least a subset of the encrypted shares of the new secret, using the previous secret; and
regenerating the new secret from at least a subset of a combination of the unencrypted shares of the new secret and the decrypted shares of the new secret, wherein each member of the computing system receives an unencrypted share of the new secret and an encrypted, differing share of the new secret.

2. The method of claim 1, further comprising:
regenerating the previous secret from shares of the previous secret.

3. The method of claim 1, further comprising:
determining whether all members of the computing system have received the distributed shares of the new secret; and
encrypting a key, using the new secret, in response to determining that all of the members of the computing system have received the distributed shares of the new secret.

4. The method of claim 1, further comprising:
encrypting data, using a data encryption key; and
decrypting the data encryption key, using the new secret.

5. The method of claim 1, further comprising:
regenerating at least one share of the new secret from the new secret; and
distributing the at least one regenerated share of the new secret to at least one member of the computing system that does not have a share of the new secret.

6. The method of claim 1, further comprising:
determining whether all of the members of the computing system have received shares of the new secret; and
deleting the previous secret, responsive to a positive result of the determining.

7. The method of claim 1, further comprising:
iterating the encrypting, distributing, decrypting and regenerating for a plurality of further new secrets.

8. A tangible, non-transitory, computer-readable media having instructions thereupon which, when executed by a processor, cause the processor to perform a method comprising:
encrypting, with a previous secret, shares of a new secret;
distributing encrypted shares and unencrypted shares of the new secret;
decrypting, with the previous secret, available encrypted shares of the new secret; and
reproducing the new secret from at least a subset of available unencrypted shares of the new secret and the decrypted shares of the new secret, wherein each member of the computing system receives an unencrypted share of the new secret and an encrypted, differing share of the new secret.

9. The computer-readable media of claim 8, wherein the method further comprises:
reproducing the previous secret from previously generated shares of the previous secret.

10. The computer-readable media of claim 8, wherein the method further comprises:
repeating the encrypting, distributing, decrypting and reproducing in an iterative manner for further new secrets.

11. The computer-readable media of claim 8, wherein the method further comprises:
encrypting and decrypting data, with a data encryption key; and
encrypting and decrypting the data encryption key, with the new secret.

12. The computer-readable media of claim 8, wherein the method further comprises:
determining that all members of a system have received the shares of the new secret; and
deleting the previous secret, responsive to the determining.

13. The computer-readable media of claim 8, wherein the method further comprises:
determining whether members of a system have received the encrypted and unencrypted shares of the new secret; and
encrypting a key with the new secret, responsive to the determining.

14. The computer-readable media of claim 8, wherein the distributing includes sending at least one share of the new secret to off-site storage.

15. The computer-readable media of claim 8, wherein the method further comprises:
verifying that all of the shares of the new secret are stored; and
deleting shares of the previous secret, responsive to the verifying.

16. A computing system with a shared secret, comprising:
a secret generator, configured to generate and regenerate secrets;
a share splitter, configured to split a secret into a plurality of shares;
an encryption/decryption unit, configured to encrypt and decrypt; and
one or more processors, configured to perform actions comprising:
encrypting shares of a second secret, using a first secret and the encryption/decryption unit;
sending encrypted shares and unencrypted shares of the second secret to members of the computing system;
decrypting at least a subset of the encrypted shares of the second secret, using the encryption/decryption unit and the first secret; and
regenerating the second secret, using the secret generator and unencrypted shares and decrypted shares of the second secret,

wherein each member of the computing system receives an unencrypted share of the second secret and an encrypted, differing share of the second secret.

17. The computing system of claim 16, further comprising:
a memory having a header section configured to store keys and shares of secrets; and
the memory further having a data storage configured for storage of encrypted data, distinct from the header section.

18. The computing system of claim 16, wherein the actions further comprise:
regenerating the first secret from shares of the first secret, using the secret generator, so that the first secret can be used for encrypting the shares of the second secret.

19. The computing system of claim 16, wherein the actions further comprise:
regenerating at least one share of the second secret; and
updating at least one member of the computing system that is missing the at least one share of the second secret.