Skip to content
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

[Bug]: --ssl-insecure does not allow small diffie-hellman keys #20

Open
1 task done
MisterMountain opened this issue Oct 30, 2024 · 1 comment · May be fixed by #21
Open
1 task done

[Bug]: --ssl-insecure does not allow small diffie-hellman keys #20

MisterMountain opened this issue Oct 30, 2024 · 1 comment · May be fixed by #21
Labels

Comments

@MisterMountain
Copy link
Member

Please try to fill out as much of the information below as you can. Thank you!

  • Yes, I've searched similar issues on GitHub and didn't find any.

Which version contains the bug?

4.0.0

Describe the bug

Hello,

as i am testing the monitoring plugin for my environment it looks like i need to use the --ssl-insecure flag, as i have an self-signed certificate in my chain:
root@icinga2:/usr/lib/nagios/plugins# ./check_brevisone.py -H smsgw1.invalid.local UNKNOWN - Could not connect to SMS Gateway <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:992)>
However, when i added the flag it still not lets me do the check due to a small key:
root@icinga2:/usr/lib/nagios/plugins# ./check_brevisone.py -H smsgw1.invalid.local --ssl-insecure UNKNOWN - Could not connect to SMS Gateway <urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:992)>

For my understanding flags like --ssl-insecure should also allow using the plugin in environments with problems like this.

How to recreate the bug?

No response

@MisterMountain MisterMountain added bug needs-triage Needs to be triaged labels Oct 30, 2024
@martialblog martialblog removed the needs-triage Needs to be triaged label Oct 30, 2024
@martialblog
Copy link
Member

We can probably adjust the SSLContext with ctx.set_ciphers to make it even less secure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants