DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 52SIObTZ350654 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 52SIObTZ350654 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=I7VBs0gW X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 87BB33830602 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1743186276; bh=DyHlVz8PLa5fLPK6gQBSjzYyGRO51RfdZV0nbOIH+Yo=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=I7VBs0gW1DM2vc7+C4MoCVQo4tHVeDglZp3yV7L0BPvkyY3XW8jS9PyjqmPbY20g2 fi4/2eEMrYh3RzVManRyYiE55H+W07rffZlEnR5bJvLN082OcMS2qfnfgPuqaxeRBG aDMx5Q/Uya2N3PeavFd9FVjBpEuuoCNr7xe72TpU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DE9AA3830601 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DE9AA3830601 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743186253; cv=none; b=v+pYrV4N/n+DPKIr6wXoX0xoIk4JDyuLuyef5YAM4TARGWdEUZAeVgXbqvoFnMdFl39/aAZEaPAW6ro1ngZ3MlA6T0cIezQx3coWJmoM2c6Hhg5jPMT0/7h3DvYXiP1C7y1+2xs7m0hY3IR00ue4XynUedEQQLEY2UZyffp34WQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743186253; c=relaxed/simple; bh=bW46cF2iFdvik7bSSv1XGYiPM05vTCchHq7DnQNjM0k=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=nzFbj9uuy4c33ZP+sKQogg5zheScxZyDW4ZGh0Lfyfgi9TnIEHIFlTpdS6E/FGsqn3PNWEYls0JQNrqlBo/6zapCmjwUDoG5FwA/drmGYBUhkxKVa3XPIcT7Q721Nt6VRrdyCaArkv4wC/hEH6n4n1JOIhCoHIXa2qtZA2tFYjo= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DE9AA3830601 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743186251; x=1743791051; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YjJVA1lbgoY3WupmbC38asikoJtzqeDMFXJ1emc+5k4=; b=g3g+JP3CnjOdXUGRo4BNUmAfANdHey5fTmloeqEj4Lh6GvhDkg3KHbZhCTeQjWumhS 04b6KOg43s0fr0sXR8A4BpkjYdKoAoQEG3SkNwi/A9uCFqWuB6Z0o/0ae6cDUeSpPAaT qkHDuQHFKI7Y3cKaKBVxJPYGWGtsbCe5MVJvu3OWp17ftIV6CPLMLTKnZNAyJOAu2fEr h2dEgdxB8ZdO7AhdREjq2kQHYt/h6O2yojjhGzLGHKmS8imGA0L2/Xc9Tq+8n4z9YfBy F7iMBfKVuB4w8hYNqhiCmfCLY/wvCeidgB+g6aG5LadQlPRU8doXJDsfWJrX2tML4VSd hjHg== X-Gm-Message-State: AOJu0YwaiowgoNxaSweoXAE4RAJTeKw8IUoGGVtLBhnoKqPEazWGzLjZ PMoUNfhujTqUXLUkmYSjNKJcXgjG7k2zmyGAqigo7DDXprbSnXdZ9vmKwsCPRq85unwVEi5GD2E oFDg3wEi6buFRHTRMdYOssD6YIfJ/2A== X-Gm-Gg: ASbGncvpt41rFTSl2YkhuNGtUjkHUEgsXWA6tIFuuSSyhXqS+F2LHdPwg+73KXgfRPk d1ozYoZD7Nv3Vp4+CHbSSYUzogMid8/TnOE9n4H9ra7Ps8ccSfbmlcwIcQFRdxCjFAhH1nFBUL+ H1O1Y6j/fxbD5gZKgLT4c0en70H7qd4XGuzg== X-Google-Smtp-Source: AGHT+IEYM5vZ+nnxBSobNgAyetuG8pklk0uslmHHjTY+w0psPzwQTURExB8R5JJj5cu0rUuOCxpIC1QS64Pw0ULn+Ac= X-Received: by 2002:a05:651c:2121:b0:30b:9813:b00c with SMTP id 38308e7fff4ca-30de032936bmr1572251fa.27.1743186250842; Fri, 28 Mar 2025 11:24:10 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 28 Mar 2025 14:23:57 -0400 X-Gm-Features: AQ5f1JoVP60LEiiFw3lHvEEsscx83NTyHspS1XJtgPPIROYOKDrsnhrWAOTK6c8 Message-ID: Subject: sshd times out and disconnects client To: cygwin AT cygwin DOT com X-Content-Filtered-By: Mailman/MimeDel 2.1.30 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Soren via Cygwin Reply-To: Soren Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Hello Cygwinstas, I've got a question about the cygwin ssh daemon running on Windows. I don't know if there is a setting in sshd or in Windows that would alter the behavior I am seeing. That's what I am hoping for. When logging in from a Linux system to my Windows 10 box, there's a timeout (of what duration, I am not precisely sure, maybe after 2 hours?) if I am not doing anything over the ssh connection. The session is disconnected at the server end. I find this a bit annoying. I might want to be doing something else for a couple hours and then come back to the session, only to find it's disconnected. This is in contrast to the reverse case, where I am logging in to one of my Linux boxes from Windows: in that case, the connection stays alive until I deliberately close it. The same with sessions between Linux machines. It's only in the case of incoming connections to sshd on cygwin/windows that I am seeing this. Insights greatly appreciated. Regards, Your fellow loyal Cygwinista, Soren Andersen -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple