mirror of https://github.com/docker/docs.git
d5c080ae9c
Various tests have been calling trustmanager.NewCertificate and open-coding most of cryptoservice.GenerateCertificate. So, add cryptoservice.GenerateTestingCertificate. It differs only by using crypto.Signer instead of data.PrivateKey because the tests have a crypto.Signer more frequently available, and converting from data.PrivateKey to crypto.Signer is easier than the other way. This will make it easier to add policy parameters which the tests don't care about to trustmanager.NewCertificate and cryptoservice.GenerateCertificate in the future. Signed-off-by: Miloslav Trmač <mitr@redhat.com> |
||
|---|---|---|
| .. | ||
| ed25519.go | ||
| ed25519_test.go | ||
| errors.go | ||
| interface.go | ||
| sign.go | ||
| sign_test.go | ||
| verifiers.go | ||
| verifiers_test.go | ||
| verify.go | ||
| verify_test.go | ||