jasonkresch / protect Goto Github PK

Allow verification of each shareholder's contribution

Add local persistence to disk and recovery after crashes without resending previously sent messages

Share recovery initiated by user intervention is not working.

Clean up duplicate code

I used "com.ibm.pross.client.signing.RsaCertificateAuthorityClient" class to generate rsaSharing, store private key share on servers and sign message with "private BigInteger signMessage(final BigInteger toBeSigned)" method to get recoverd signature, but when I verified signature with SigningUtil.verifyDefault, it returned false.

At generation time allow specification of the curve and refresh period for proactive recovery

Not all classes have unit tests, and some unit tests are failing.

Currently named pross.

Should use thread-safe concurrent data structors for collecting responses from the servers.

Consider adding during each epoch change, having each shareholder send a rekey message over the channel to migrate the public key(s) used by a shareholder (signed by the previous private key). -- preventing the next refresh from being compromised.

Build a smaller client jar file separately for CLI tools

Hi Jason,

Just came across this repo; what is the current state of the implementation and can the README be updated to reflect any possible instructions for running things?

Many thanks,
Josh

Hi Jason,

I was following the tutorial and I got stuck when issuing client and server certificates. I could not find the following issue-server-certificates.sh, issue-client-certificates.sh scripts. Could you provide me with some instructions on how to create those by myself?

Thank you.