-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Enable HostKeyTest to extract ECDSA and DSA keys #286
Enable HostKeyTest to extract ECDSA and DSA keys #286
Conversation
Their certificate-embedded counterparts are enabled as well. As with RSA, it *is* possible for DSA keys to be of variable length (not just 1024 bits), so I've added `{'variable_key_len': True}` to the relevant `HOST_KEY_TYPES` entries, although this key-value pair is otherwise unused.
The way that ssh-audit/src/ssh_audit/hostkeytest.py Lines 118 to 129 in 574a53d
A more universal and future-proof way to handle this would be to simply test for every key type that the server claims to support ( ssh-audit/src/ssh_audit/hostkeytest.py Lines 180 to 183 in 574a53d
@jtesta would you be receptive to such a change? |
…ean up Docker tests from merge of #286.
The DSA algorithm can indeed use variable moduli, though the DSS standard is defined at exactly 1024 bits only. So using, say, a 3072-bit modulus would be possible, but wouldn't be considered DSS anymore. That said, I've seen a non-standard algorithm out in the wild called
Sure. Thanks for this PR! |
Btw, aren't DSA keys currently discouraged? |
@perkelix wrote:
Yes, indeed. Which is exactly why a tool for finding and cataloging them should be able to extract them. |
Their certificate-embedded counterparts are enabled as well.
As with RSA, it is possible for DSA keys to be of variable length (not just 1024 bits), so I've added
{'variable_key_len': True}
to the relevantHOST_KEY_TYPES
entries, although this key-value pair is otherwise unused.