similar to: OpenSSH server doesn't log client disconnect without SSH_MSG_DISCONNECT

On Sun, 26 May 2024, Opty wrote: > On Wed, May 22, 2024 at 6:29?AM Damien Miller <djm at mindrot.org> wrote: > > 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

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

On Wed, May 22, 2024 at 6:29?AM Damien Miller <djm at mindrot.org> wrote: > 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 "Connection closed by ..." > message regardless. I

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

On Tue, Jun 11, 2024 at 1:24?PM Opty <opty77 at gmail.com> wrote: > 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: > > > We need to decide whether to promote these log messages to INFO. > > > > > > [...] > > > > I will wait for the final

On Fri, 14 Jun 2024, Opty wrote: > On Tue, Jun 11, 2024 at 1:24?PM Opty <opty77 at gmail.com> wrote: > > 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: > > > > We need to decide whether to promote these log messages to INFO. > > > > > >

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 'perfectly OK to unceremoniously > > slam the connection shut when you're done' attitude? > >

On Thu, May 30, 2024 at 3:03?AM Damien Miller <djm at mindrot.org> wrote: > On Wed, 29 May 2024, Opty wrote: > > On Mon, May 27, 2024 at 4:18?AM Damien Miller <djm at mindrot.org> wrote: > > > Yeah, you're adding a new thing that will be logged. IMO you should > > > try to figure out why the "Connection closed" message that is present > >

On Thu, May 30, 2024 at 6:02?PM Opty <opty77 at gmail.com> wrote: > On Thu, May 30, 2024 at 3:03?AM Damien Miller <djm at mindrot.org> wrote: > > On Wed, 29 May 2024, Opty wrote: > > > On Mon, May 27, 2024 at 4:18?AM Damien Miller <djm at mindrot.org> wrote: > > > > Yeah, you're adding a new thing that will be logged. IMO you should > >

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 > ---

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 'perfectly OK to unceremoniously > slam the connection shut when you're done' attitude? I don't think they need to. I think it's fair that we log connections that are terminated regardsless of how graceful

On Wed, 29 May 2024, Opty wrote: > On Mon, May 27, 2024 at 4:18?AM Damien Miller <djm at mindrot.org> wrote: > > Yeah, you're adding a new thing that will be logged. IMO you should > > try to figure out why the "Connection closed" message that is present > > in the debug log you sent is not making to to your syslog. > > If I change LogLevel in

On Fri, 31 May 2024, Opty wrote: > > 9.3p2, 64-bit Slackware 15.0 package which uses two patches but they > > look LogLevel-safe to me, you can check at > > http://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/source/openssh/ > > 9.7p1 built from source without TCP wrappers and still no 'Connection > closed' at 'LogLevel INFO'. You might be

On Mon, May 27, 2024 at 4:18?AM Damien Miller <djm at mindrot.org> wrote: > Yeah, you're adding a new thing that will be logged. IMO you should > try to figure out why the "Connection closed" message that is present > in the debug log you sent is not making to to your syslog. If I change LogLevel in /etc/ssh/sshd_config from default INFO to VERBOSE then I see

Hi. >From my understanding the MaxStartups option can be set to limit the number of concurrent sessions the OpenSSH server opens. My concern is how OpenSSH handles the case where this number is reached. >From the code it looks like it simply closes the socket: sshd.c:1440 if (drop_connection(startups) == 1) { debug("drop connection #%d", startups); close(newsock);

To whomsoever it may concern, I use putty-0.51 as ssh client on windows and openssh-2.9p2 implementation on RedHat 7.0 Linux as ssh server. For the client to exit, I expected ssh client to send SSH_CMSG_EOF to the server and the server respond with SSH_CMSG_EXITSTATUS and finally close the connection when the client sends SSH_CMSG_EXIT_CONFIRMATION. This will effectively end the server_loop in

Hi Jan, > I've been looking into how to make llvm bitcode files smaller. There is one > simple change that appears to shrink linked bitcode files by about 15%. See > this spreadsheet for some rough data: > > https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E the improvement is wonderful! ... > In any case, the patch is attached if

On Tue, Jul 19, 2011 at 10:12:47AM +0100, Jay Foad wrote: > On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote: > > Looks like that break came > > from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 > > Judging by this ArrayRef ctor you should be able to simplify those calls by > > changing the last two arguments from

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

I have a new dell t105(opty 1210's with 4 gigs of ram..sata hdd's and sata dvd-rom). I can bot to the Cent 5 64 bit dvd fine but once it asks where the install image is i tell it cd-rom..then it rejects the dvd spits it out and tells me it's not there. the same happens on 32 bit. I have downloaded centos5 twice now, md5 verified..and even burned at 1x(that took forever). Any