X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 811A33858423
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1681441438;
	bh=x+K6jiH498sZl3sMhrmBoxWNQXVnH1vUtD+Ztzqh2TE=;
	h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:
	 List-Help:List-Subscribe:From:Reply-To:From;
	b=B6sqKKm6+bmP4f9agZ+XGqn7XLvUQwOeXu9yiB4NFpxoNkKD6RoxMx80yF/oCt1gr
	 vjLzsbXc/GI3f5TlTlYSZcg5WeH7XhfClxlbRwzxhLFUtFstOwRVuRa9t8W/n/xZsj
	 knkc0dX1/bySEWaw35Ed2cr9bkXVX8GRK8bQYwRw=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 078DD3858D20
Message-ID: <88697a53-26db-6969-2c18-3d6133d248c1@cs.umass.edu>
Date: Thu, 13 Apr 2023 23:03:40 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.9.1
Content-Language: en-US
To: cygwin <cygwin AT cygwin DOT com>
Subject: Permissions question / issue
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Eliot Moss via Cygwin <cygwin AT cygwin DOT com>
Reply-To: moss AT cs DOT umass DOT edu
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Dear cygwin'ers -

I seem to be caught in a bind with the Cygwin permissions setup.

ssh insists that ~/.ssh/config have permissions no less permissive than rw------- (600).

However, my backup program runs as SYSTEM and needs access.  I tried to
provide that access by adding an ACL g:SYSTEM:r-x, but that appears as
rw-r-x--- and ssh doesn't like it.

I seem to recall that at some point in the past we agreed to ignore the
permissions given to SYSTEM when computing effective permission (e.g., as
output by ls -l).  That would suit the purpose.

Did something change?  or am I misremembering the solution to the conundrum?

Note: I have Administrator privilege on my machine, but that doesn't help,
since the backup tool runs under SYSTEM, a different account.

Best wishes - Eliot Moss

-- 
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