X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:content-transfer-encoding :content-type:message-id:date:from:reply-to:to:subject :references:in-reply-to; q=dns; s=default; b=sAPJS8ll4HkK8sYTgGr +yqIqc2FncYmp9LWMhe9jitj6XQjIdtm4ozhS1QVbgc2v+XSPHg+oHgKyRgoA08Y +Hwio/Go3d0Wsrqo19LwmF/VnUGxwlaKZphFPPqGUeXqe6kkLJHuAy1pWR0EfJtW AUH+FTKWf+w85f0CTUreIr0A= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:content-transfer-encoding :content-type:message-id:date:from:reply-to:to:subject :references:in-reply-to; s=default; bh=HytwBr5ISf2HJsNi+vFgXjhIX Co=; b=n0fGyOqehhlthIIKXBt+C3PkLkN0qRJChj1YUFYf189TPR12EjopgvGsf fOor5KH00knMoX9+PYuG/UJOTrnyt/Y7mH7BLpIkI2bviIyuo4olSJCaZVO0Ir2K VjtyJ5oS4EzeReLz4FkPLpuUOlFSIr7mkwy1wzJSmlLgaJC49U= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,URI_HEX autolearn=no version=3.3.2 X-HELO: vms173025pub.verizon.net MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8; format=flowed Message-id: <538CA5E9.9040600@cygwin.com> Date: Mon, 02 Jun 2014 12:27:21 -0400 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 To: cygwin AT cygwin DOT com Subject: Re: Problem logging into ssh References: <96A00236-4DDD-4F39-917D-DC674ECE2642 AT gmail DOT com> <1401562511998-108985 DOT post AT n5 DOT nabble DOT com> In-reply-to: <1401562511998-108985.post@n5.nabble.com> On 05/31/2014 02:55 PM, PolarStorm wrote: > Noah White wrote >> I’ve installed and configured sshd to run as a service under a particular >> account which is an Administrator. I can ssh in fine as that user. >> However, if I try to ssh as any other user I get the following error: >> >> Last login: Wed May 21 18:58:35 2014 from foo.home >> /bin/bash: Operation not permitted >> Connection to tango closed. > > The sshd installation scripts creates two users, one which should not be > used for login, so make sure you sue the right one. Some months ago Actually, neither of the two possible accounts, one for running the service and one for, optionally, privilege separation, should be used by the user as a login. The user should login via ssh using their Windows account login name, after running 'ssh-user-config' as that user. > I posted details about various other issues with sshd setup on W8 > machines. I have no idea if any of these have been fixed and implemented, > but have a close look at the thread: > http://cygwin.1069669.n5.nabble.com/Silently-configure-sshd-fails-via-system-account-td106607.html > > Also, one of the accounts are erroneously set to expire in 42 days. The privilege separation account, sshd, is disabled by design. This keeps anyone from using it as a login, since the account is supposed to be used solely by the service as an added security measure. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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