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:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=uV num5Yh7JN5GbDGXCCg1bUz0w0wLQ8t4R1liIcAnHN36wEhI/0fYncK1i1mL9PBcr 8RWybnMFYhlEpdsvVuo8a3lu6Y3UpCBDWyAWQ8Dvc62UaeBRrrR/SF9A/LKgtlhf Y19LaEOjm1J0q6qxbXErss9lGX1uVmZirvPEt+hWA= 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:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=THP0j3LT HYlqVS9z3QvGH+QUYxo=; b=r8OirjK5sX1bR9Xq76gnngipeK6+ie0Dvbl12cmi Zs20jymY2K3dH42d6H14QGcajLLOcgzatc7NfHpzPCTLxkWQipLOXoDAAlRizoJZ fEXY/sE4o8ORrSwj5BiNb5YX65blFNFPyOJoQxHwMJtIsVXhHAcnx42dUxlMgGuN SrA= 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=3.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SCAM_SUBJECT,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-qa0-f41.google.com MIME-Version: 1.0 X-Received: by 10.224.57.142 with SMTP id c14mr32460562qah.23.1395098587056; Mon, 17 Mar 2014 16:23:07 -0700 (PDT) In-Reply-To: References: <5307BB89 DOT 80405 AT cse DOT yorku DOT ca> <5307BDDA DOT 4040309 AT cygwin DOT com> <530B6ED1 DOT 2060003 AT cse DOT yorku DOT ca> Date: Mon, 17 Mar 2014 19:23:06 -0400 Message-ID: Subject: Re: Silently configure sshd fails via system account From: Lord Laraby To: Cygwin Mailing List Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Oh and I forgot the most intriguing gotcha. After creating the sshd user for me (I went to service manager and discovered this) the user assigned to the sshd server was actually cyg_server (not sshd)!!!!! After changing all of those things the service started. -- 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