search for: qeporkak

...on. > > A little more information may be logged from the disconnect packet > if it was sent, but there should always be a "Connection closed by ..." > message regardless. I should have shown examples from the system log. SSH-2.0-OpenSSH_9.3: 2024-05-19T15:48:06.591206+02:00 qeporkak sshd 15053 - - Accepted keyboard-interactive/pam for opty from 127.0.0.1 port 41006 ssh2 2024-05-19T15:48:06.601660+02:00 qeporkak elogind-daemon 1111 - - New session 2 of user opty. 2024-05-19T15:48:07.797821+02:00 qeporkak sshd 15058 - - Received disconnect from 127.0.0.1 port 41006:11: disconnec...

On Tue, 21 May 2024, Opty wrote: > Hello, > > can anyone confirm that OpenSSH server doesn't log client disconnect > without SSH_MSG_DISCONNECT? OpenSSH logs the disconnection regardless of whether the client sends SSH_MSG_DISCONNECT or just drops the connection. A little more information may be logged from the disconnect packet if it was sent, but there should always be a

...o INFO. > > > > > > [...] > > > > 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. A bit chatty but works: 2024-06-14T20:01:54.084176+02:00 qeporkak sshd 10012 - - Accepted keyboard-interactive/pam for opty from 127.0.0.1 port 60547 ssh2 2024-06-14T20:01:54.090845+02:00 qeporkak elogind-daemon 1116 - - New session 2 of user opty. 2024-06-14T20:01:55.125617+02:00 qeporkak sshd 10027 - - serverloop.c:process_input():290 (pid=10027): Connection cl...

On Wed, Jun 5, 2024 at 3:14?PM Opty <opty77 at gmail.com> wrote: > On Wed, Jun 5, 2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > > On Sat, 1 Jun 2024, Opty wrote: > > > Indeed I am. > > > > > > What now? > > > > We need to decide whether to promote these log messages to INFO. > > > > > Should PuTTY change its

...gt; > > > > > 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. > > A bit chatty but works: > > 2024-06-14T20:01:54.084176+02:00 qeporkak sshd 10012 - - Accepted > keyboard-interactive/pam for opty from 127.0.0.1 port 60547 ssh2 > 2024-06-14T20:01:54.090845+02:00 qeporkak elogind-daemon 1116 - - New > session 2 of user opty. > 2024-06-14T20:01:55.125617+02:00 qeporkak sshd 10027 - - > serverloop.c:process_input():290 (...

...or just drops the connection. > > > > A little more information may be logged from the disconnect packet > > if it was sent, but there should always be a "Connection closed by ..." > > message regardless. > > Unpatched: > 2024-05-26T13:40:18.419241+02:00 qeporkak sshd 16107 - - Accepted > keyboard-interactive/pam for opty from 127.0.0.1 port 48133 ssh2 > 2024-05-26T13:40:18.428291+02:00 qeporkak elogind-daemon 1114 - - New > session 2 of user opty. > 2024-05-26T13:40:19.309320+02:00 qeporkak elogind-daemon 1114 - - > Removed session 2. >...