From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 7 18:37:18 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D285516A4CE for ; Sat, 7 Feb 2004 18:37:18 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B973043D31 for ; Sat, 7 Feb 2004 18:37:18 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i182bIkX000358 for ; Sat, 7 Feb 2004 18:37:18 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <4025A0DD.2010607@acm.org> Date: Sat, 07 Feb 2004 18:37:17 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Odd ACL question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 02:37:18 -0000 In tinkering with libarchive's support for ACLs, I've run across a head-scratcher: Joerg Schilling's "star" archives ACLs as follows: "user::rwx,group::r--,group:mail:rw-:6,mask::rw-,other::r--" Note the "group:mail:rw-:6" entry that contains a fourth field with the uid/gid number. FreeBSD's acl_from_text chokes on this, although Joerg asserts that posix1e permits additional fields. Question: Should acl_from_text be altered to ignore additional fields? What I can't quite figure out is whether or not this uid/gid field is really useful. It seems like it might be useful when moving archives across systems, but I'm not entirely convinced that it's right to restore the uid if the username doesn't exist. Question: Is this a useful extension? If so, then I need to find a straightforward way to implement it. I could maybe add this to our acl-to-text routines, but that sounds dangerous somehow. Alternatively, there might be a way to refactor our acl-to-text routines so I could reuse the bulk of the work there. Any thoughts on the matter are greatly appreciated. Thanks, Tim Kientzle