Proactive Secret Sharing

Proactive secret sharing is an underlying technique in Proactive Security Protocols.
It is a method to update distributed keys (shares) in a secret sharing scheme periodically such that an attacker has less time to compromise shares and as long as the attacker visits less than a threshold or a quorum group, the system remains secure. This contrasts to a non-proactive scheme where if the threshold number of shares are compromised during the lifetime of the secret, the secret is compromised. The model which takes time constraints into account was originally suggested as an extension of the notion of Byzantine fault tolerance where redundancy of sharing allows robustness into the time domain (periods) and was proposed by Rafail Ostrovsky and Moti Yung in 1991. The method has been used in the areas of cryptographic protocols in secure multi-party computation and in threshold cryptosystems.

Motivation

If the players (holders of the shared secret) store their shares on insecure computer servers, an attacker could crack in and steal/learn the shares. Since it is not often practical to change the secret, the un-compromised (honest) ( Shamir-style) shares should be updated in a way that they generate the same secret, yet the old shares are invalidated. There is also a need to recover shares of previously corrupted servers, and the community of honest server is needed to perform the recovery. This assures the longevity of the secure and recoverable sharing, or secure and correct secure computation protocols.
If one needs to maintain sharing while changing the number of servers or the threshold, then proactive method with share recovery enables this, as was originally shown by Frankel and others. The ability of distributing the secret (codeword) and then recovering the distributed shares as the proactive secret sharing method does, was recognized as much needed in storage systems around 2010, and in reaction, coding theorists renamed the method, further refined it, and formalized is as `regenerating codes' and `locally recoverable codes.'

Mathematics

This follows somewhat the work in.
In order to update the shares, the dealers (i.e., the persons who gives out the shares; and in a distributed system it is all participants one at a time) generates a new random polynomial with constant term zero and calculates for each remaining player a new ordered pair, where the x-coordinates of the old and new pairs are the same. Each player then adds the old and new y-coordinates to each other and keeps the result as the new y-coordinate of the secret.

* The dealer constructs a random polynomial over a field of degree $k - 1$ where $k$ is the threshold
* Each player gets the share $x_^ = f^(i)$ where $i \in \$, $n$ is the number of players, and $x_^$ is the share for player $i$ at time interval $0$
* The secret can be reconstructed via interpolation of $k$ shares
* To update the shares, all parties need to construct a random polynomial of the form $\delta_(z) = \delta_z^ + \delta_z^ + ... + \delta_z^$
* Each player $i$ sends all other players $u_ = \delta_(j)$
* Each player updates their share by $x_^ = x_^ + u_^ + ... + u_^$ where $t$ is the time interval in which the shares are valid

All of the non-updated shares the attacker accumulated become useless. An attacker can only recover the secret if he can find enough other non-updated shares to reach the threshold. This situation should not happen because the players deleted their old shares. Additionally, an attacker cannot recover any information about the original secret from the update process because it only contains random information.

The dealer can change the threshold number while distributing updates, but must always remain vigilant of players keeping expired shares as in. However this is a somewhat limited view since the original methods gives the community of server the ability to be the re-sharing dealer and the regenerator of lost shares.

Example

The following example has 2 shares and a threshold of 2 with 2 players and 1 dealer. Since shares and polynomials are only valid for a certain time period, the time period they are valid is denoted with a superscript.
* All parties agree on a finite field: $Z_$
* The dealer establishes a secret: $s = 6 \in Z_$
* The dealer constructs a random polynomial over $Z_$ of degree 2 - 1 (threshold of 2)
** $f^(x) = 6 + 2 \times x$
** note $f^(0) = s = 6$
* Player 1 gets share $x_^ = f^(1) = 6 + 2 \times 1 = 8$ and player 2 gets share $x_^ = f^(2) = 6 + 2 \times 2 = 10$
* To reconstruct the secret, use $x_^$ and $x_^$
** Since $f^(x)$ is a line, we can use point slope form to interpolate
** $m = (f^(2) - f^(1)) / (2 - 1) = (x_^ - x_^) / (2 - 1) = (10 - 8) / (2 - 1) = 2 / 1 = 2$
** $b = f^(1) - m = x_^ - 2 = 8 - 2 = 6$
** $f^(x) = b + m \times x = 6 + 2 \times x$
** $f^(0) = 6 + 2 \times 0 = 6 = s$
* To update the shares, all parties need to construct random polynomials of degree 1 such that the free coefficient is zero
** Player 1 constructs $\delta_^(z) = \delta_^ \times z^ = 2 \times z^$
** Player 2 constructs $\delta_^(z) = \delta_^ \times z^ = 3 \times z^$
* Each player evaluates their polynomial and shares some information with other players
** Player 1 computes $u_^ = \delta_^(1) = 2$ and $u_^ = \delta_^(2) = 4$ in $Z_$
** Player 1 sends Player 2 $u_^$
** Player 2 computes $u_^ = \delta_^(1) = 3$ and $u_^ = \delta_^(2) = 6$ in $Z_$
** Player 2 sends Player 1 $u_^$
* Each player updates their share by $x_^ = x_^ + u_^ + u_^$
** Player 1 computes $x_^ = x_^ + u_^ + u_^ = 8 + 2 + 3 = 2 \in Z_$
** Player 2 computes $x_^ = x_^ + u_^ + u_^ = 10 + 4 + 6 = 9 \in Z_$
* Confirm updated shares generate same original secret
** Use $x_^$ and $x_^$ to reconstruct the polynomial $f^(x)$
** Since $f^(x)$ is a line, we can use point slope
** $m = (f^(2) - f^(1)) / (2 - 1) = (x_^ - x_) / (2 - 1) = (9 - 2) / (2 - 1) = 7 / 1 = 7$
** $b = f^(1) - m = x_^ - 7 = 2 - 7 = -5 = 6$
** $f^(x) = b + m \times x = 6 + 7 \times x$
** $f^(0) = 6 + 7 \times 0 = 6 = s$

See also

* Key (cryptography)
* Key generation
* Key distribution
* Key management
* Shamir's Secret Sharing

References

{{crypto navbox

Secret sharing