Command line interface for Publicly Verifiable Secret Sharing
Sunday 03 December 2017
ShareSafe is available and
ready to use. It allows users to leverage Publicly Verifiable Secret Sharing
It is a library (first at all) that provides simple interfaces to make use of PVSS to encrypt/decrypt data.
A command line interface (CLI) is provided with the package and it is what we will be talking about here.
Quickly, PVSS is a protocol to allow users to create (and verify) a secret made
n participants. These
n participants only shares their
n public keys
to create a secret. They have decided that
m participants (0 <
are needed to retrieve the Secret.
Very simple :
n participants only share their public keys. All or a subset are
needed to recover the secret.
The generated/retrieved secret can be used for multiple purpose. One of them,
the one used in
sharesafe, is for symmetric encryption.
i.e. if one want to send private data, it only needs the public key of the recipient. So now you can say that there is already asymmetric encryption for that and you would be right. PVSS here is interesting because you can add yourself in the scheme. The sender can set itself as a participant of share and can retrieve the same secret.
This is interesting because it provides us with a way to verify who participated to a given secret/share.
You can checkout the use case described in the README.md of
# generate to the standard output sharesafe key new # generate in a file sharesafe key new -o <generated-key-pair>
by default we are not setting a password for the secret. If you want to set a
--password. By default the password is the empty string.
To export the public key:
# by default `sharesafe` will read the keypair from the standard input # and will write the exported public key to the standard output. sharesafe key export-public -i <generated-key-pair> -o <exported-public-key>
This command will create the shares for every participants, the commitments and the encryption key.
shareswill be needed to recover the secret later on. Only the secret key associated to the share can unlock the share;
thresholdof unlocked shares to recover the secret;
commitmentscan be used to check the shares;
encryption-keyis the key generated from the secret;
This command will create a locked
share for every given
name will be the input file name with the suffix replaced to
sharesafe pvss new --participant public-key1 \ --participant public-key2 \ --threshold=1 \ --commitments commitments \ -o encryption-key
Once you have generated the shares, you can simply share them Publicly (or not). Only the private key associated to the public key used to generate the share can unlock the share.
sharesafe pvss verify -s <locked-share> -c commitments
sharesafe pvss open-share -s <share-file> -k <private-key> -o <opened-share>
sharesafe pvss recover -s $(cat <opened-share>) \ -o encryption-key.recovered
encryption-key is generated using Diffie-Hellman derivation from the
PVSS secret. The encryption algorithm provided is
It provides a default authentication of the ciphered content.
cat input-file | \ sharesafe cipher encrypt -k $(cat encryption-key) > input-file.encrypted
cat input-file.encrypted | \ sharesafe cipher decrypt -k $(cat encryption-key) > input-file