-
Notifications
You must be signed in to change notification settings - Fork 167
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
Config
ignores insecure-skip-tls-verify
field
#555
Labels
Comments
This was referenced Mar 23, 2022
Merged
cben
added a commit
to cben/kubeclient
that referenced
this issue
Mar 23, 2022
Tiny followup to ManageIQ#556. Sorry for noise, had these locally but forgot to push before merging. If I start backporting, CHANGELOG.md on master branch might not always be updated with all backports (it SHOULD, but it will require separate merges to master). So I prefer pointing to the vulnerability issue as the "source of truth". Also, security impact will be better discussed on the issue.
Closing, this has been fixed both in 4.9.3 and on master branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tightly related to #554, also broken ever since
Kubeclient::Config
was added (I'm fixing them together):insecure-skip-tls-verify
field in kubeconfig was never honored.The distinction is that #554 is about the default being dangerous, and this ticket is about inability to override the default (either way) by
insecure-skip-tls-verify
.The text was updated successfully, but these errors were encountered: