-
-
Notifications
You must be signed in to change notification settings - Fork 593
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
New plugin to check for ignoring host keys #374
Conversation
:Example: | ||
|
||
|
||
.. versionadded:: 1.5.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume the next release is 1.5.1
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep 1.5.1 seems reasonable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also need a new file in doc/source/plugins/b507_ssh_no_host_key_verification.rst
:Example: | ||
|
||
|
||
.. versionadded:: 1.5.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep 1.5.1 seems reasonable.
This new plugin adds a check that detects whether some code using paramiko is ignoring the host key verification. Ignoring a host key is the equivalent of ignoring a certificate as part of the TLS protocol. Original author: Eric Brown <browne@vmware.com> Fixes Issue: #357
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This new plugin adds a check that detects whether some code using
paramiko is ignoring the host key verification. Ignoring a host
key is the equivalent of ignoring a certificate as part of the
TLS protocol.
Original author: Eric Brown browne@vmware.com
Fixes Issue: #357