#secret-sharing #shamir-secret-sharing #shares #threshold #scheme


Implementation of threshold Shamir's secret sharing in the Rust programming language

3 unstable releases

Uses old Rust 2015

0.2.2 May 17, 2018
0.2.1 Mar 7, 2018
0.2.0 Mar 7, 2018
0.1.0 Feb 13, 2018
0.0.2 Apr 6, 2016

#1663 in Cryptography

Download history 2/week @ 2024-03-12 1/week @ 2024-03-26 12/week @ 2024-04-02

107 downloads per month
Used in rustysecrets-cli


3.5K SLoC

Rusty Secrets

Build Status Coverage Status Crates.io LICENSE

Rusty Secrets is an implementation of a threshold Shamir's secret sharing scheme.

Documentation (latest)
Documentation (master)

Design goals

The main use for this library is to split a secret of an arbitrary length in n different shares and k-out-of-n shares are required to recover it. The dealer is assumed to be honest (and competent). We further assume that our adversary will only be able to compromise at most k-1 shares. Shares are kept offline.

A typical use case for this library would be splitting an encryption key to a TrueCrypt-like volume.


Structure of the shares

  ^ ^ ^^^^^^^^^^^^^^
  K N        D        

A share is built out of three parts separated with a dash: K-N-D.

  • K specifies the number of shares necessary to recover the secret.
  • N is the identifier of the share and varies between 1 and n where n is the total number of generated shares.
  • The D part is a Base64 encoding of a ShareData protobuf containing information about the share, and if signed, the signature.


There are a few issues with regular Shamir's secret sharing that we wanted to address:

  • a share can be corrupted or incorrectly entered.
  • a malicious share holder can modify the secret that would be recovered by modifying his share.
  • a user has multiple shares from different secret shares and he doesn't know which one belongs to a specific instance.

All of these issues would result in a corrupted secret being outputted and the program, that wouldn't even know that the secret got corrupted, wouldn't be able to give any actionable information.

We addressed this by signing the shares by the dealer and encoding the public key into each share. After the generation of the shares, the dealer erases both the secret and the private signing key used to sign the shares. When recovering the secret, the program verifies that public keys and if some shares do not have the same public key, or a valid signature of that public key, signals the issue to the user with a helpful message.

Signing shares is optional and the usefulness of signing the shares depends on the use case. Since we're using hash-based signatures (using SHA-512 Merkle signing), there is a large overhead from using signatures.

Bug Reporting

Please report bugs either as pull requests or as issues in the issue tracker. RustySecrets has a full disclosure vulnerability policy. Please do NOT attempt to report any security vulnerability in this code privately to anybody.




  • Dealer: Entity that will perform key splitting from a master secret
  • Shares: Part of the split secret distributed


Rusty Secrets was forked off sellibitze's secretshare.


~313K SLoC