This is the mail archive of the
mailing list for the Cygwin project.
Re: (call-process ...) hangs in emacs
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Fri, 29 Aug 2014 14:08:29 -0400
- Subject: Re: (call-process ...) hangs in emacs
- Authentication-results: sourceware.org; auth=none
- 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>
On 8/29/2014 7:09 AM, Corinna Vinschen wrote:
On Aug 29 09:58, Achim Gratz wrote:
Achim Gratz <Stromeko <at> NexGo.DE> writes:
This fixes the "read-only" problem in Emacs (so that hunch was correct).
Perl still doesn't play, but I think the 5.18 version should get it correct.
Will need to switch a test installation over for that, though.
With that snapshot in place, ssh suddenly recognized that my private key
file was more readable than it liked it to be, so it looks that it's using
the same general strategy of dealing with ACL as Emacs.
...which means, they don't deal with ACLs at all. They only see what's
given in the st_mode permission bits. With this change, the group
permission bits now show that *somebody* has certain permissions on the
file, thus the group permissions indicate a too open access for ssh, if
somebody except you have write access to the file.
Downside: If you use inherited Windows permissions, you'll often have
the case that Administrators and/or SYSTEM have full access to your
files. This in turn shows up as rwx group permissions now. If you
can't change the permissions (company requirements, etc) the ssh key
file permission test will get annoying.
So it's probably a very nice change (thanks a lot for bringing this up!),
but it will probably have some negative side-effects for existing
I'm starting to
like this patch very much... :-)
Despite of what I'm outlining above, me too :)
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple