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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=hLykGYESbobp2/VvcXyhPnNgehA6/CceYphb2Wt9EFU
	Z7cpfl3d9KEnRBeuBp0aDyeCuV+9MxR6etadxnIUYhmQDAxY45czVVGQMyLG3omq
	7mypi3yNH91kCKmZO3gBFCL5I4Pgb7TR8uuLbXLPlDvwDVCMGY3WnieoBD3hpvqw
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=1aHzjz4y0xDJHT0doF4EtEEWrqg=; b=ZIUk4kJqdkmjHCbLc
	5VDVTA21yLj7+UHJhTgLn0MS41f7DW1GjkxT5oQPkedj++HIj5DJRlpjY+I9Byro
	XFCXxnp6u/qYaeJgChXy8BjDj09OS5ojHKppo7QccLteX64UALP7C303o8oC4BFT
	ETVEaqhNATpB94xrgxUgvcm6sY=
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=-1.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock03.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <5400D64D.1090709@cornell.edu>
Date: Fri, 29 Aug 2014 15:36:45 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: (call-process ...) hangs in emacs
References: <87wq9v9j2y DOT fsf AT Rainer DOT invalid> <53FD0662 DOT 5050208 AT cornell DOT edu>	<20140827084245 DOT GD20700 AT calimero DOT vinschen DOT de>	<53FDD4A8 DOT 5050401 AT cornell DOT edu>	<loom DOT 20140827T170804-533 AT post DOT gmane DOT org>	<loom DOT 20140828T085927-71 AT post DOT gmane DOT org>	<20140828095524 DOT GO20700 AT calimero DOT vinschen DOT de>	<20140828131832 DOT GT20700 AT calimero DOT vinschen DOT de>	<loom DOT 20140828T172529-396 AT post DOT gmane DOT org>	<loom DOT 20140829T115632-276 AT post DOT gmane DOT org>	<20140829110938 DOT GD20700 AT calimero DOT vinschen DOT de>	<5400C19D DOT 4070408 AT cornell DOT edu> <87ha0vhzge DOT fsf AT Rainer DOT invalid>
In-Reply-To: <87ha0vhzge.fsf@Rainer.invalid>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 8/29/2014 3:23 PM, Achim Gratz wrote:
> Ken Brown writes:
>> With the latest snapshot I can't start the sshd service.  The
>> Application Log just says, "`sshd' service stopped, exit
>> status:255". The problem doesn't occur with the 2014-08-27 snapshot.
>> I guess this has something to do with the new permissions on various
>> files, but I'm not sure which ones.
>
> Off the top of my head for the standard installation:
>
> /etc/ssh*
> /var/empty
> /var/log/sshd
>
> When you try to debug the sshd, IIR these are the files that must be
> chown'ed to the admin user that runs sshd from the terminal.  Running in
> debug mode (either from the terminal or via sshd_config) should produce
> messages which file or directory sshd is choking on.

I just checked /var/log/sshd.log.  (I hadn't thought to do that before.) 
  The last message in it is, "/var/empty must be owned by root and not 
group or world-writable."  So the problem seems to be that /var/empty 
appears to sshd to be group writable under the latest snapshot.  This is 
the "downside" that Corinna mentioned.  What needs to be done to 
/var/empty to fix this?

Ken


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