Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
encoding/asn1: tags don't match parsing certificate #18634
Maybe related to #18584 but not fixed by 1.8rc1.
What version of Go are you using (
Not a regression from Go 1.7, so this isn't a Go 1.8 candidate at this stage. Targetting Go 1.9.
@agl: Can you explain this a bit more?
This is the way the EC key was generated:
what do you mean by "The certificate is trying to use arbitrary curves rather than specifying one."
A long time ago it was unclear which elliptic curves would end up being a good idea so formats were designed to support arbitrary curves: i.e. the public key can contain the specification for any curve over prime or binary fields and, in theory, every public key could work on its own, unique curve.
That was bonkers and now software only operates on a few, known-good curves (i.e. P-256, P-384 etc). Thus public keys now just contain an OID identifying the curve.
Your certificate contains the full set of parameters however. It's probably the parameters for a standard curve, but we don't go trying to match arbitrary curves to ones that we know.
One option is to generate the key and certificate using Go.
If you need to use the OpenSSL command-line tools then you can add