public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: TEST RELEASE: Cygwin 1.7.34-002
Date: Fri, 12 Dec 2014 14:35:00 -0000	[thread overview]
Message-ID: <548AFD43.1040306@cornell.edu> (raw)
In-Reply-To: <CAMKht8iYnRuAJ7Eau6LDa_Jszxwo8YwybzwZNHjzWXLMUS8Y-w@mail.gmail.com>

On 12/12/2014 8:49 AM, Michael DePaulo wrote:
> On Sat, Dec 6, 2014 at 2:49 PM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
>> I finally released another TEST version of the next upcoming Cygwin
>> release.  The version number is 1.7.34-002.
>
> I *think* I am experiencing a very bad regression.
>
> These are the Windows permissions on my ~/.ssh/id_rsa file:
> C:\cygwin\home\mike\.ssh>icacls id_rsa
> id_rsa NT AUTHORITY\SYSTEM:(F)
>         DEPAULO\mike:(R,W,D,WDAC,WO)
>
> Under cygwin 1.7.33-2, I am able to use the file fine:
>
> mike@executor ~
> $ uname -a
> CYGWIN_NT-6.3-WOW64 executor 1.7.33-2(0.280/5/3) 2014-11-13 15:45 i686 Cygwin
>
> mike@executor ~
> $ ssh galactica
> Enter passphrase for key '/home/mike/.ssh/id_rsa':
> Last login: Fri Dec 12 08:36:39 2014 from executor.depaulo.org
> mike@galactica:~ :) [1] $ exit
> logout
> Connection to galactica closed.
>
> mike@executor ~
> $ cd .ssh
>
> mike@executor ~/.ssh
> $ ls -latr id_rsa
> -rw------- 1 mike mkpasswd 1743 Dec  7  2013 id_rsa
>
>
> But under 1.7.34-002, I get a permissions error:
>
> mike@executor ~
> $ uname -a
> CYGWIN_NT-6.3-WOW64 executor 1.7.34(0.282/5/3) 2014-12-06 18:03 i686 Cygwin
>
> mike@executor ~
> $ ssh galactica
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> Permissions 0670 for '/home/mike/.ssh/id_rsa' are too open.
> It is recommended that your private key files are NOT accessible by others.
> This private key will be ignored.
> key_load_private_type: bad permissions
> mike@galactica's password:
>
>
> mike@executor ~
> $ cd .ssh
>
> mike@executor ~/.ssh
> $ ls -latr id_rsa
> -rw-rwx---+ 1 mike Domain Users 1743 Dec  7  2013 id_rsa

This isn't a regression.  It's a deliberate change, so that Cygwin now 
takes ACLs into account when calculating permissions.  The simplest fix 
is to use the new feature of setfacl to remove the unwanted permissions. 
  From the release announcement:

> - Add -b/--remove-all option to setfacl to reduce the ACL to only the
>   entries representing POSIX permission bits.

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

  reply	other threads:[~2014-12-12 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20141206194943.GD3810@calimero.vinschen.de>
2014-12-09 22:18 ` Michael DePaulo
2014-12-10 12:35   ` Corinna Vinschen
2014-12-12 13:49 ` Michael DePaulo
2014-12-12 14:35   ` Ken Brown [this message]
2014-12-15 11:35     ` Corinna Vinschen
2014-12-15 17:15       ` Achim Gratz
2014-12-15 17:59         ` Corinna Vinschen
2014-12-15 20:39           ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=548AFD43.1040306@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).