7 Commits

Author	SHA1	Message	Date
Jason Rhinelander	cd8f26deff	Use hash instead of random for signing hash data ... This makes PrivateKey store both the key followed by the hash. For PrivateKeys based on SecretKeys this just means the second half of the SHA-512 of the seed, and makes a PrivateKey constructed from a SecretKey give an identical signature to signing directly with sodium. For derived keys we use a ShortHash of the root key's signing hash concatenated with the publicly known hash value, so that our derived key signing hash will be different from the root signing hash and also different for different derivation parameters. This also changed one of the asserts in crypto_noop, but upon closer inspection the copying of the secret key into the signature seems really wrong, so just changed them to fill with 0s.	2020-01-31 16:47:25 -04:00
Thomas Winget	a487982c49	initial implementation of blinded sign -- not working yet	2020-01-31 12:05:20 -04:00
Jeff Becker	098915bb8e	add check for identity key validity	2019-11-26 20:40:55 -05:00
Michael	16cdfbd5f0	clang-tidy modernize pass	2019-08-12 16:52:58 +01:00
Jeff Becker	0808060a61	fix previous commit	2019-05-31 06:59:47 -04:00
Jeff Becker	a51f4c8328	make debian stable happy	2019-05-29 08:41:00 -04:00
Michael	8323725509	Initial No-Op Crypto implementation	2019-05-29 09:46:34 +01:00