search for: ssh2_msg_disconnect

...e' attitude? I don't think they need to. I think it's fair that we log connections that are terminated regardsless of how graceful the termination was. E.g. why shouldn't we log connections that drop because the peer process got SIGINT or the TCP connection dropped before sending a SSH2_MSG_DISCONNECT? -d

...don't think they need to. I think it's fair that we log connections > that are terminated regardsless of how graceful the termination was. > E.g. why shouldn't we log connections that drop because the peer > process got SIGINT or the TCP connection dropped before sending a > SSH2_MSG_DISCONNECT? I will wait for the final verdict then. Thanks for letting me know. Regards, Opty

...signee: unassigned-bugs at mindrot.org Reporter: imorgan at nas.nasa.gov Created attachment 2204 --> https://bugzilla.mindrot.org/attachment.cgi?id=2204&action=edit Use error() to report "Received disconnect" messages to the user In packet.c, logit() is used to report SSH2_MSG_DISCONNECT and SSH_MSG_DISCONNECT messages to the user. This means that if the user has LogLevel set to "error," such messages will be suppressed. Since the circumstances which trigger packet_disconnect() to be called are really error conditions, it seems more appropriate to use error(). One scenar...

On Sat, Jun 1, 2024 at 5:23?AM Damien Miller <djm at mindrot.org> wrote: > On Fri, 31 May 2024, Opty wrote: > > 9.7p1 built from source without TCP wrappers and still no 'Connection > > closed' at 'LogLevel INFO'. > > You might be hitting this exit path: > > diff --git a/serverloop.c b/serverloop.c > index 4eabfced6..bf45f77a2 100644 > ---

...need to. I think it's fair that we log connections > > that are terminated regardsless of how graceful the termination was. > > E.g. why shouldn't we log connections that drop because the peer > > process got SIGINT or the TCP connection dropped before sending a > > SSH2_MSG_DISCONNECT? > > I will wait for the final verdict then. Thanks for letting me know. I will also try 'LogVerbose serverloop.c:process_input():*' soon which might do here. Regards, Opty

I am testing with a 5.4p1 client and have noticed, on the server side, that sometimes an SSH_MSG_DISCONNECT message is received with the following 28-byte long payload: 0x00 0x00 0x00 0x0b Reason: SSH_DISCONNECT_BY_APPLICATION 0x00 0x00 0x00 0x14 Description string length: 20 bytes 0x64 0x69 0x73 0x63 0x6f 0x6e 0x6e 0x65