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:date:message-id:subject:from:to :content-type; q=dns; s=default; b=eU5k4KT2REMP2Ef14xqTbPWzmB4eT xIPYb/fx8s+0/9AvYgFnPOA51LzuoutgzYb1yxiU+EkiImjb+PU8BsMNHWBcOd7S 0L16Wn6DicBU3o4j1ReEgw+cf2cE3AKrt+5TJQtDQ61iS1cbvrTj94SiB6puIOSk aeqk4X+JKV56so= 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:date:message-id:subject:from:to :content-type; s=default; bh=XCSv2kZ9IoDjymVnhq9ZRCTGlzA=; b=U5Y vN8H1ixVqIs5ZhzqJeAs2Bvo8VgDDluApEWhxPi9IqWiiPxc5wUFwqgJVZNVzAHY T87+Q3O65o1oophlTth/j1eFDw+Tg0Xbliyj2bmerTmNNB5CaPLOAA0sU62J95EA 4qlzEqzvm8u+baFUhlvMxdSI4GdCcigREHp/R2aY= 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=3.6 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-la0-f43.google.com MIME-Version: 1.0 X-Received: by 10.152.42.194 with SMTP id q2mr20485785lal.75.1413160638871; Sun, 12 Oct 2014 17:37:18 -0700 (PDT) Date: Sun, 12 Oct 2014 20:37:18 -0400 Message-ID: Subject: Necessary To Query SACL Information? From: Bryan Berns To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes I noticed when I launch an executable, Cygwin queries SACL information on the executable (which I can see in Process Monitor as a 'QuerySecurityFile' operation). On some of my protected file servers, this generates a failure audit. Looking at the source code, I'm going to guess this might be from the NtQuerySecurityObject call in security.cc which requests SACL information by asking for for ALL_SECURITY_INFORMATION. Does Cygwin really need to query this information? Aside from keeping my audit logs clean, it seems like it might be an opportunity for optimizing the executable launch process if Cygwin doesn't really need this (or some of the other information that ALL_SECURITY_INFORMATION provides). Thoughts? -- 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