MIME-Version: 1.0
In-Reply-To: <50C103F6.7020309@gmail.com>
References: <CAMgm8F3N-TnySJUNj0WQc8nvyz+KY7ze=9_aS+oXPB-kC5RK8Q@mail.gmail.com>	<CAMgm8F0G0rQ-to6Uy3pF=u52XBAODdSufE3nmt72gqgN6tyDXA@mail.gmail.com>	<50C103F6.7020309@gmail.com>
Date: Thu, 6 Dec 2012 16:10:48 -0500
Message-ID: <CAMgm8F2FP7qdc8=Sd+12fB5L-wOEZxUC_G=RT7f3eZJk4zikzA@mail.gmail.com>
Subject: Re: Bug in Cygwin Windows 8 group permissions
From: Chaz Littlejohn <chaz@pokeit.co>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 12/6/2012 9:15 PM, Chaz Littlejohn wrote:
>
> a workaround was already available on first link you provided
>
>   chgrp -R Users ~/.ssh
>

I had tried this earlier running the chgrp.exe, but it threw an error
saying unknown group 'Users'. I assume this is because when chgrp.exe
is located outside of the default cygwin directory, it doesn't know
where to find the group file. I also attempted to create a separate
file where i'd dump the contents of my private key into, but that file
seems to also be afflicted by this permissions problem of having 660
with no group set.

> This may just be a problem in terminology but if you're planning to
> only provide a link to Cygwin's site/source, this will not be compliant
> with GPL license.  You have to provide the source for the specific
> binaries you're distributing.  Obviously, the versions may be different
> than whatever is available from the Cygwin site, which is why a simple
> link/pointer is not sufficient.

Yes, this was clarified by the folks on the cygwin-licensing mailing
list and shouldn't be a problem.

Chaz

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