`[exception] did not receive banner.` exception
See original GitHub issueFor an sshd
configuration, it is valid to have the Banner
option in /etc/ssh/sshd_config
set to none
.
However, ssh-audit
then always throws a [exception] did not receive banner.
.
It would be nice if ssh-audit
could optionally skip checking for a banner.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Paramiko : Error reading SSH protocol banner - Stack Overflow
Recently, I made a code that connect to work station with different usernames (thanks to a private key) based on paramiko. I never...
Read more >Inbound Rule exception not working properly
I have a rule to add an annoying banner for all external emails. All of the exceptions work except for the one to...
Read more >SSL banner_timeouts - NETCONF - ConfD User Community
Exception: Error reading SSH protocol banner Traceback (most recent call ... I suspect that ConfD is not the one closing the connection.
Read more >Error reading SSH protocol banner - Google Groups
Underlying exception: ... You're not specifying a port anywhere are you? ... You received this message because you are subscribed to the Google...
Read more >Workflow Notifications Not Received Failing With Unhandled ...
My Oracle Support Banner. Workflow Notifications Not Received Failing With Unhandled Exception in the Oracle Applications Framework layer (Doc ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Option could be added, just have to think about the naming and design, e.g., will that include two options (connection and read timeout) or a single one; how to specify them intuitively, etc. I was thinking something along the lines of
-t 3:5
. What do You think?Good idea.
Note that having one option with a list of parameters can be hard parsing and harder to remember the order of the parameters, so it might be easier to support this:
[--connection-timeout|-ct] <integer>
[--read-timeout|-rt] <integer>