X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=S9vgpoqk5RuUtJFXU9JP1xSPA8Kd3EmqOCDLq7R5DrI=; b=V0GhKhXXWRx4HCecMZeAaNekN443aIX5QvcYeAlO1cp+1zm14GHV+uJWWmI/LTiQ/+ O/mFlVhMH9exM73iLF4uUE16rZpVtiZym3fy8URvJVoRT0UTg49INXDV4oS2PUBC5AwI Oa7Ikjh1RqffamcLbHKgRtrr4J6iduuahRP4TebsbFcgcWmkHKVYU1y/8BWhP5Lj4yV0 9nPuZo8N4PyiuxN9LpMabKIz0zOdfzVzmYGoitxiOu+INKUjyF2skMBe66Srw6bTSvyW vUbC9uAuEdTgD1roZYT+6zC/NKnbVFXpwsNdiKtZEVJbgOl7IY/xdMGaB0OSp3ZmE2ni QG9Q== MIME-Version: 1.0 In-Reply-To: <50C103F6.7020309@gmail.com> References: <50C103F6 DOT 7020309 AT gmail DOT com> Date: Thu, 6 Dec 2012 16:10:48 -0500 Message-ID: Subject: Re: Bug in Cygwin Windows 8 group permissions From: Chaz Littlejohn To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkKv/yiqoI/c/T+icP2UZZUZmKmrFXIT7Zo+S2tR7o3Kgt54WnuNs8S15XE0d2WnbDXjMTu X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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