From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122603 invoked by alias); 26 Dec 2019 20:24:58 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 122519 invoked by uid 89); 26 Dec 2019 20:24:44 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=exercise, colleagues, officially, HX-Spam-Relays-External:sk:mail-qt X-HELO: mail-qt1-f176.google.com Received: from mail-qt1-f176.google.com (HELO mail-qt1-f176.google.com) (209.85.160.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Dec 2019 20:24:43 +0000 Received: by mail-qt1-f176.google.com with SMTP id j5so23051520qtq.9 for ; Thu, 26 Dec 2019 12:24:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=k/2mKXl5BSh37N/sz1+8hHUaeV+rBO1NNVU+G4PgSW4=; b=UajYr7vUJOVqjBpHexyqx+qyxF4X+/7pjy3bfOvi4niLaSMmSbeMg/yaI1IJHpjr8W N61i/AsL5Qh6498rBSxldMirVH9lBVPJrRwjIR9wOfpQ2J4X2gRVir+NYYB6S26aEYxy SP1PJ2nW5qeMGS8FsJnLyVvj/vbwdENDR95honcCQloIAE1oRbVEj84OdrwgTO+AlpOX P6iLP/NiHzVI4qtPIUZslCOcjQayOj/2Sc9blGM3K0qOp3/ybJs6Dfc2srTgx5v9bnnb VJYPB4LNiOatSzq+yZBFQGVnedUobp1FzBgEzgFGD4juWilfleIO3Iit5SOpPMBKfcfD e22w== Return-Path: Received: from ?IPv6:2604:6000:1405:29b:ec7f:eb14:6faa:cf46? ([2604:6000:1405:29b:ec7f:eb14:6faa:cf46]) by smtp.gmail.com with ESMTPSA id d25sm9693907qtq.11.2019.12.26.12.24.19 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Dec 2019 12:24:19 -0800 (PST) To: cygwin@cygwin.com From: Evan Cooch Subject: installing sshd | Win 10 1909 build Message-ID: <79ab161a-5e1d-e6b2-f46c-275ce7dd719b@gmail.com> Date: Thu, 26 Dec 2019 21:05:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00278.txt.bz2 Greetings -- I (and several colleagues) have been using the Cygwin sshd for many years (Win XP on...). Has worked perfectly. However, with the demise of Win 7, several of us have started the process of 'upgrading' (in some fashion) to Win 10. For people running Cygwin sshd under Win 7, who do an in-place upgrade to Win 10, things seem to be OK -- i.e., Win 10 leaves Cygwin sshd alone. However, I received an email from a colleague who said he had no host of problems trying to install Cygwin sshd on a brand new Win 10 system, 1909 build. It seems that Win 10 has its own sshd, and there is a conflict of some sort between Win 10 (which 'wants' to use its own sshd), and attempts to use Cygwin. Since this exercise (of installing to a brand new Win 10 machine) is something I'll likely be doing myself in the near future, was wondering if there was a canonical set of instructions on how to install Cygqwin, using Cygwin sshd as a service, on a Win 10 1909 platform? I've read a variety of posts on the matter -- spome suggest renaming the Cygwin sshd to something, others talk about registry hacks to not let Win 10 default to its own sshd, and so on. So, is there a 'tried and true, officially sanctioned' way to get Cygin sshd running as a service under the latest build of Windows 10, if you working with a clean, new install of Windows? Thanks much in advance... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple