cc @FiloSottile @rolandshoemaker

Change https://golang.org/cl/347034 mentions this issue: crypto/x509: support NumericString in DN components

golang.org/x/crypto/cryptobyte, golang.org/x/crypto/cryptobyte/asn1 does not support tag 18 type while standard library encoding/asn1 does.
go1.16 does not have this issue - why go1.17 should use outdated code from golang.org/x/crypto/cryptobyte[/asn1] ?

Same problem here, example: https://play.golang.org/p/-1pDx9dZNpm

join the question
solved the problem like this :
in go-1.17.3/src/vendor/golang.org/x/crypto/cryptobyte/asn1/asn1.go
added NumericString = Tag(18)
in go-1.17.3/src/crypto/x509/parser.go
added
func isNumeric(b byte) bool { return '0' <= b && b <= '9' }
and processing
case cryptobyte_asn1.NumericString: for _, b := range value { if !isNumeric(b) { return "", errors.New("invalid NumrticString") } } return string(value), nil
in
func parseASN1String(tag cryptobyte_asn1.Tag, value []byte) (string, error) { switch tag {

@seankhliao @FiloSottile This is a regression from 1.16 that remains broken even in the latest head. Can the linked CL please be merged, and backported to 1.17?

@seankhliao @FiloSottile @katiehockman @rolandshoemaker @agl

@gopherbot please open a backport issue for 1.17. This is a regression in the parser rewrite that prevents parsing some certificates.

Backport issue(s) opened: #51000 (for 1.17).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.

Change https://golang.org/cl/382857 mentions this issue: [release-branch.go1.17] crypto/x509: support NumericString in DN components