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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=tTOuAWWovkMnvZjXbOc1Wx1nA+VwI5KSmG+wAuWbMU5 n+6xpHG/3B9AWHXxj/+ALk0xNr5MEi7gz6+hH4iK8fMTPIQZZPhGpKrbWXkGYDmd P7FTjJAEOKMSYFTaiNkfO7SMJqavyxNSYFPTurE5s19e6/mdjKJ4gYI3wfQrHpvw = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=MhjFtiWUntb5hqapZg5l9e9HoQY=; b=mkJ07koJRbKFX7mkD OpWfT3vKUpmd0t6eg+IoR/g7YIgXRQbOzJpmNjKYeYAp9cHH+XiQdYmhRxzHbm6R scRJUihftvSfJgF6tA4CiXOtidrnew6XN2b0P2IJgcNq3z5BxrVq2kulbjlRIJ4x 3YtqWhGAXMhyUunvjKrLfjHm+U= 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: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: Ishtar.hs.tlinx.org Message-ID: <56044EBD.8090904@tlinx.org> Date: Thu, 24 Sep 2015 12:27:57 -0700 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: Greg Freemyer , "cygwin AT cygwin DOT com" Subject: Re: cygwin potentially corrupting permissions? References: <560366EE DOT 5020207 AT tlinx DOT org> <56043BA4 DOT 7040405 AT tlinx DOT org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greg Freemyer wrote: > > Totally logical, but not accurate. ) --- What does it say if you do an 'lsacl' on "." (the parent directory). This is a local file system? NTFS? Do you have process hacker? Maybe the writing process has a different integrity label or such. Process hacker lets you see what the integrity labels are on files, but to see what they are on files you'd have to d/l another util. (chml/regil > > - cygwin is not properly maintaining the permissions when it manipulates a file ---- May not be able to ... Windows trumps cygwin. MS-regularly screws w/windows, .. it's like switching to a new init system every month... ok.. maybe not quite that bad... > > Either way, I would really like a solution that doesn't involve a > manual chmod for every file I create via the normal Windows interface > and which I want to work with it in cygwin. === I can understand that -- that's sorta why I haven't upgraded my cygwin lately -- She spent alot of time solving a problem that didn't really appear on my system, so changing the whole security system -- well I already know that cygwin doesn't respect existing standards or sources. (overwrite windows mount points created -- and is shipping a login that zeros your environment -- even when passed switch to not do so -- effectively wipes your windows session -- forcing users to copy sessions from static files to get around the problem. -- 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