David Benjamin
5ba7f63082
Most implementations, including this one, consider the private key to be the concatenation of the initial 32-byte seed and the public key. However the RFC 8032 formulation considers the "private key" to just be the seed, which, in turn, means the upcoming draft-ietf-curdle-pkix specification for embedding Ed25519 into PKCS#8 only stores the seed. Exporting ed25519.PrivateKey to the seed is easy: key[:32]. Importing the seed to ed25519.PrivateKey is not currently possible because the logic is tied up in ed25519.GenerateKey. Split out ed25519.NewKeyFromSeed for this, as well as an ed25519.PrivateKey.Seed accessor to keep the abstraction consistent. Change-Id: I4068eaf2073009dff3d84224aa145b56b59a5854 Reviewed-on: https://go-review.googlesource.com/115297 Reviewed-by: Filippo Valsorda <filippo@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
Go Cryptography
This repository holds supplementary Go cryptography libraries.
Download/Install
The easiest way to install is to run go get -u golang.org/x/crypto/.... You
can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.
Report Issues / Send Patches
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with "x/crypto:" in the subject line, so it is easy to find.
Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.