-
Notifications
You must be signed in to change notification settings - Fork 18
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
Trying to connect with missing certificate_chain crashed python interpreter #87
Comments
Interesting - is this happening in |
Yes, construct, but, really the crash happens initializing the "grpc._channel.Channel" class. Here are the 3 parameters (certificate chain is None).
|
Further testing, if either the private key or the client certificate are None, they both have to be None or you get a crash. |
I'm inclined to say that makes sense, but I don't FULLY understand certificates enough to know situations wherein the client key/cert paired wouldn't be necessary. We can add an exception for that condition - in general I usually have a |
NXOS at first only provided the rootCA.pem and host override name. That also connects successfully for XE. From my limited investigation of TLS, I think that works because the actual root authority is the Cisco device itself. If it was a 3rd party, not so sure that would end in a successful connection. |
Connection code did not find the certificate chain file and assigned python None to Client class which led to this error in grpc/_channel.py.
The text was updated successfully, but these errors were encountered: