DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BP0UI513840864
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0FD5B3858D20
To: cygwin AT cygwin DOT com
Subject: access X_OK for administrators has changed in cygwin 3.5.5
Date: Wed, 25 Dec 2024 01:29:47 +0100
Message-ID: <1947635.Bm8zEkEi59@nimes>
Organization: GNU
MIME-Version: 1.0
From: Bruno Haible via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Bruno Haible <bruno AT clisp DOT org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi,

The behaviour of the access(_, X_OK) call has changed for administrator
users in Cygwin 3.5.5. I don't know whether that's intended or not
(haven't seen it mentioned in
<https://sourceware.org/pipermail/cygwin-announce/2024-December/012023.html>).

How to reproduce:
========================== foo.c ===========================
#include <stdio.h>
#include <fcntl.h>
#include <string.h>
#include <grp.h>
#include <unistd.h>
int main ()
{
  close (creat ("file", 0600));
  chmod ("file", 0400);
  printf ("file X_OK ? %d\n", access ("file", X_OK));
}
============================================================
1. In a normal Cygwin console (mintty):
   $ rm -f file
   $ gcc -Wall foo.c
   $ ./a
   => file X_OK ? -1
2. In a Cygwin console that runs "as administrator":
   $ ./a
   => In Cygwin 3.4.6: file X_OK ? -1
      In Cygwin 3.5.5: file X_OK ? 0

Bruno


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple