Darren Tucker
2023-Jun-05 06:59 UTC
[feature suggestion] sshd should log the listening port number while logging errors/warnings
On Mon, 5 Jun 2023 at 16:29, Yuri <yuri at rawbw.com> wrote:> ssh_kex_exchange_identification: banner line contains invalid characters[...]> It would be easier to figure out where offending connections come from.The subsequent log line from sshpkt_fatal contains the source address and port of that connection: $ sudo `pwd`/sshd -ddd -p 2022 [...] kex_exchange_identification: banner line contains invalid characters banner exchange: Connection from 127.0.0.1 port 52410: invalid format -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
Yuri
2023-Jun-05 07:06 UTC
[feature suggestion] sshd should log the listening port number while logging errors/warnings
On 6/4/23 23:59, Darren Tucker wrote:> The subsequent log line from sshpkt_fatal contains the source address > and port of that connection: > > $ sudo `pwd`/sshd -ddd -p 2022 > [...] > kex_exchange_identification: banner line contains invalid characters > banner exchange: Connection from 127.0.0.1 port 52410: invalid formatI am using sshd on FreeBSD 13.2 and it only logs the first line. Does the second line require some special setting values to be printed? Yuri