-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crypto/tls: Client Side TLS Authentication fails for certs with long fields #36467
Comments
See also #19933 Where did the OIDs in this cert come from? FWIW, derdump fails on it too:
|
Hi Mike, thanks for responding. The certs and by extension the OIDs are created by a Foreman (RedHat Satellite) server, these are used to distribute things like RPMs/Debs/Containers and are at the core of things like rhn.redhat.com. As far as I understand the reason the OIDs are so long is because they include authorization information in addition to the authentication info (gives the ability to grant access to specific repositories/life-cycles). Perhaps someone more knowledgeable like @ohadlevy or @tbrisker from the @theforeman project could elaborate if needed. |
The files provided in the bug report are not DER encoded. They are PEM encoded. If you run To convert them to DER, you'll need to strip the |
/cc @agl @FiloSottile |
Change https://golang.org/cl/248259 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
package main
import (
"crypto/tls"
"fmt"
)
func main() {
cert, err := tls.LoadX509KeyPair("./helm-test-crt", "./helm-test.key")
fmt.Println(cert, err)
}
Test certs:
https://gist.github.com/antevens/a05409165d33bd771e39bc219fe2c6bb/archive/e56cf114dee64a6b367abf08ab1c34a405a62f88.zip
helm/helm#7343
What did you expect to see?
Client side TLS authentication succeed.
What did you see instead?
asn1: structure error: base 128 integer too large
The text was updated successfully, but these errors were encountered: