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:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=y673VSPU0IjlgSITprPK4BFzVkjy876Pl3hK8ZWNkRySbT
	bJFBTCLKPkSGYR7itssu/fVM/o5d4zOqb6p1CphZVGyq1XZeefOwI2vk0Pd5vrRQ
	6AZVzJxfbWJAN9bosz+cdsTzKKYaqVObwI73/pN6ToN6UsOlmp60oyAA1nBLY=
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:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=temIk6EOC9lUHukI+aMq/wSlEVU=; b=AAus/he7MwVfnv9vCB7Q
	BpetM7mODRc3P2/PJOcFMCqjvrF3H66tZH2FbTYfiPDNxW2h/g3fQF7wfozhHkB7
	J/8w1v71vH3NlaULeuX5x9zjDGW/CwD4Noxq9KQ8ueZRVE5p3LGJug5jeqlgJWXA
	iOYVfw2AWv5bPTYpKyUqWWs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-3.6 required=5.0 tests=AWL,BAYES_50,SPF_NEUTRAL,URI_HEX autolearn=no version=3.3.2
X-HELO: sam.nabble.com
Date: Sat, 31 May 2014 11:55:11 -0700 (PDT)
From: PolarStorm <developer AT clinicsearch DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <1401562511998-108985.post@n5.nabble.com>
In-Reply-To: <96A00236-4DDD-4F39-917D-DC674ECE2642@gmail.com>
References: <96A00236-4DDD-4F39-917D-DC674ECE2642 AT gmail DOT com>
Subject: Re: Problem logging into ssh
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s4VItOX4025325

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






--
View this message in context: http://cygwin.1069669.n5.nabble.com/Problem-logging-into-ssh-tp108818p108985.html
Sent from the Cygwin list mailing list archive at Nabble.com.

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