tendermint

291 MiB

Tree: c3384e88e5

Author	SHA1	Message	Date
Dev Ojha	0790223518	Comment about ed25519 private key format on Sign (#2632 ) Closes #2001	6 years ago
Ethan Buchman	feb08fa4f8	ed25519: use golang/x/crypto fork (#2558 ) * ed25519: use golang/x/crypto fork * changelog * gix GenerateFromPassword * fixes from review	6 years ago
Dev Ojha	728d2ed266	crypto: Remove unnecessary prefixes from amino route variable names (#2205 ) * crypto: Remove unnecessary ed25519 and secp256k1 prefixes from amino routes. * (squash this) add changelog * (squash this) multisig amino fixes * (squash this) fix build error	6 years ago
ValarDragon	f903947ff3	crypto: Remove interface from crypto.Signature Signatures are now []byte, which saves on the number of bytes after amino encoding (squash this) address Ismail's comment	6 years ago
Dev Ojha	0bd4fb96f0	crypto: Add benchmarking code for signature schemes (#2061 ) * crypto: Add benchmarking code for signature schemes This does a slight refactor for the key generation code. It now calls a seperate unexported method to allow generation from a reader. I think this will actually reduce time in generation, due to no longer initializing an extra slice. This was needed in order to enable benchmarking. This uses an internal package for the benchmarking code, so that this can be standardized without being exported in the public API. The benchmarking code is derived from agl/ed25519's benchmarking code, and has copied the license over. Closes #1984	7 years ago
Dev Ojha	eb7dea1b0d	crypto/ed25519: Remove privkey.Generate method (#2022 ) The privkey.Generate method here was a custom-made method for deriving a private key from another private key. This function is currently not used anywhere in our codebase, and has not been reviewed enough that it would be secure to use. This removes that method. We should adopt the official ed25519 HD derivation once that has been standardized, in order to fulfill this need. closes #2000	7 years ago
Dev Ojha	c5c1689591	crypto/secp256k1: Add godocs, remove indirection in privkeys (#2017 ) * crypto/secp256k1: Add godocs, remove indirection in privkeys The following was previously done for creating secp256k1 private keys: First obtain privkey bytes. Then create a private key in the underlying library, with scalar exponent equal to privKeyBytes. (The method called was secp256k1.PrivKeyFromBytes, `fb90c334df/btcec/privkey.go (L21))` Then the private key was serialized using the underlying library, which just returns back the bytes that comprised the scalar exponent, but padded to be exactly 32 bytes. `fb90c334df/btcec/privkey.go (L70)` Thus the entire indirection of calling the underlying library can be avoided by just ensuring that we pass in a 32 byte value. A test case has even be written to show this more clearly in review. * crypto/secp256k1: Address PR comments Squash this commit * crypto: Remove note about re-registering amino paths when unnecessary. This commit should be squashed.	7 years ago
ValarDragon	c798702764	crypto: Remove Ed25519 and Secp256k1 suffix on GenPrivKey	7 years ago
Dev Ojha	67762aec73	crypto/ed25519: Update the godocs (#2002 ) This commit updates the godocs for the package, and adds an optimization to the privkey.Pubkey() method. The optimization is that in golang, the private key (due to interface compatibility reasons) has a copy of the public key stored inside of it. Therefore if this copy has already been computed, there is no need to recompute it.	7 years ago
ValarDragon	99e582d79a	crypto: Refactor to move files out of the top level directory Currently the top level directory contains basically all of the code for the crypto package. This PR moves the crypto code into submodules in a similar manner to what `golang/x/crypto` does. This improves code organization. Ref discussion: https://github.com/tendermint/tendermint/pull/1966 Closes #1956	7 years ago

10 Commits (c3384e88e5fee31ecf2d3c62b20204eae965bf02)