X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; q=dns; s=default; b=yUpgfUE vafSSJKEPZBXw5ralQcs52NYCBmv7h/43tYS4jdvTrhZgH8zUjvMlgVbxAjMK6Ym 6kImAdCV4lTNURLgrUoS2GuYtAM6fhzF1CFwYbAGvOMOtvAwAgwLsiRNbdO3wcIB V+LX6mlweVu0EbfqiL2E03z7Tb9dOdo6XRDc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; s=default; bh=otGN6ZzxIzBED 3wDyZADGlzUf0s=; b=xKj8NcDjmbR1kLpLIlD5oz+u19zZzlRLptMHWkER7qwjU Hei71jxSD84isor3h1LC/tcMZKisXcUi6IAkM3CBGeJBFr3QCx1AbtAjpRlGZ/I3 qc59en/RydLNx+f1iqVGtz1VLm5tgoXapbJY9ZnAHLd8aNseITsQMXLIK+lNsw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=5.0 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-yk0-f176.google.com X-Received: by 10.52.52.136 with SMTP id t8mr84769548vdo.49.1426864952176; Fri, 20 Mar 2015 08:22:32 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <550C3418.9060506@thales-esecurity.com> References: <550C3418 DOT 9060506 AT thales-esecurity DOT com> From: Rexdf Date: Fri, 20 Mar 2015 23:21:52 +0800 Message-ID: Subject: Re: after update to cygwin 1.7.35(0.287/5/3) all file permissions in cygwin are 070 To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes > > You may have misread the original question (and its subject): the POSIX > permissions are 070, not (0)700. These files are accessible to one or more > of the groups the owner is a member of, but not to the owner. > I know clear about 070 and 700 and 0700. It is typos. That is why I ask you to run icacls. > +1 for the ICACLS workaround though. I was bit by this recently when > setting up openssh, which cares about locking down access to keys. I needed > to get rid of those group access bits, but chmod left them unchanged. I > used ICACLS to remove ACEs for 'NT AUTHORITY\SYSTEM', which (based on > experimenting) were affecting the 'group' triplet of the POSIX permissions. > Run mintty.exe as Administrators. You can set permission by chmod setfacl https://cygwin.com/cygwin-ug-net/using-utils.html#setfacl too. If you try to remove some old account(like reinstall a new windows), you can try SubInACL http://www.microsoft.com/en-us/download/details.aspx?id=23510 to deal with SSID (something like S-1-5-21-56246481-4602087933-3644394174-1001) -- 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