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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=HGsuFy0lZcsOHnR6
	Ju9TAniGVqN+lhWqPxwBayA+Qq80s/7rEBZoLPakQg2dWLkV01NYGaj/xbWnsGlR
	uB/OAIqH81PqexLGsVBAe70X9KQkZCbwdkiG0aWe4Z7kkPC7Rho8j+8wGmS9sLAr
	ibxBA+JpmpM8JumatidCzxZnHzY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 29 Aug 2014 23:57:54 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1619566519.20140829235754@yandex.ru>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: (call-process ...) hangs in emacs
In-Reply-To: <5400D64D.1090709@cornell.edu>
References: <87wq9v9j2y.fsf@Rainer.invalid> <53FD0662.5050208@cornell.edu> <20140827084245.GD20700@calimero.vinschen.de> <53FDD4A8.5050401@cornell.edu> <loom.20140827T170804-533@post.gmane.org> <loom.20140828T085927-71@post.gmane.org> <20140828095524.GO20700@calimero.vinschen.de> <20140828131832.GT20700@calimero.vinschen.de> <loom.20140828T172529-396@post.gmane.org> <loom.20140829T115632-276@post.gmane.org> <20140829110938.GD20700@calimero.vinschen.de> <5400C19D.4070408@cornell.edu> <87ha0vhzge.fsf@Rainer.invalid> <5400D64D.1090709@cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Ken Brown!

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

I think, setting ACL that will directly translate to -rwx------ without any
"+" should help.

I'm in the middle of transfer to Win7/64, can't test anything right now.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 29.08.2014, <23:56>

Sorry for my terrible english...


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