From Calum.Mackay@sun.com Fri May 18 14:48:25 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4ILmO0d005585
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 18 May 2007 14:48:24 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4ILl7jv007526
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 18 May 2007 22:47:14 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JI900H01B6OMW00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Fri, 18 May 2007 14:47:12 -0700 (PDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JI900CPLB6NVB10@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri,
 18 May 2007 14:47:12 -0700 (PDT)
Received: from d1-emea-09.sun.com ([192.18.2.119])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4ILlAnh014848	for
 <psarc-ext@sun.com>; Fri, 18 May 2007 21:47:10 +0000 (GMT)
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JI900801B3RK200@d1-emea-09.sun.com>
 (original mail from Calum.Mackay@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri,
 18 May 2007 22:47:10 +0100 (BST)
Received: from [192.168.254.1] ([62.24.230.83])
 by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0JI90013HB6KS8B0@d1-emea-09.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri,
 18 May 2007 22:47:10 +0100 (BST)
Date: Fri, 18 May 2007 22:47:07 +0100
From: Calum Mackay <Calum.Mackay@sun.com>
Subject: 2007/281 NFS share properties for Montana compatibility
Sender: Calum.Mackay@sun.com
To: psarc-ext@sun.com
Cc: Doug McCallum <Doug.McCallum@sun.com>
Message-id: <464E1EDB.9050307@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
User-Agent: Thunderbird 3.0a1 (X11/20070504)
Status: RO
Content-Length: 6292

I'm sponsoring the following fast-track for Doug McCallum.

The timer is set to Wednesday 30th May.

The case seeks Minor binding.

The interface stability for the new properties is Committed.

I have placed example new man pages for sharemgr(1M) and share_nfs(1M), 
with change bars, in the case's materials directory.

When replying, please be sure to Cc: psarc-ext@sun.com

cheers,
calum.


1. Introduction
    1.1. Project/Component Working Name:

	New NFS share properties for compatibility with Montana
	functionality

    1.2. Name of Document Author/Supplier:

	Doug McCallum

    1.3. Date of This Document:

	05/02/2007

    1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:

	       Solaris

	1.4.2. The ARC(s) you expect to review your project:

	       PSARC

	1.4.3. The Director/VP who is "Sponsoring" this project:

		Fred Zlotnick

	1.4.4. The name of your business unit:

		Software

    1.5. Email Aliases:
     	1.5.1. Responsible Manager:	Don Traub
     	1.5.2. Responsible Engineer:	Doug McCallum
     	1.5.3. Marketing Manager:	Margaret Hamburger
	1.5.4. Interest List:		nfs-eng@sun.com, snas-tech-team@sun.com

2. Project Summary
    2.1. Project Description:

	Add several new properties to NFS shares that provide
	compatibility with the existing NAS server (Montana).

    2.2. Risks and Assumptions:

	Low risk. The changes are incremental, only add new
	functionality and don't modify any existing functionality.

3. Business Summary
    3.1. Problem Area:

	The problem is to provide equivalent functionality to our
	existing NAS product. The existing NFS implementation is
	missing several share properties that our current customer
	base uses. This corresponds to RFE 6475452. These properties
	are only implemented on the NFS server.

	There are three types of properties to be added:

	none		The none property takes an access list the
			same way that the rw/ro properties do. It
			provides a mechanism to exclude clients from
			any access to the server. This property is
			declared within a security flavor just as
			rw/ro are.

			Example: "none=host1:host2" would prevent any
			access by host1 or host2.

	uid0		Is similar to the "anon" property except that
			it changes the UID associated with a root
			client that is allowed root access via the
			"root=access-list" property.
			
			Example: "root=host1:host2,uid0=321" would set
			the UID of the root user on host1 or host2 to
			321 instead of 0.

	<charset>	This is a set of properties that specify a
			supported character set and an access-list. If
			a client appears in one of the <charset>
			properies access-list, a conversion between
			the client's character set and UTF-8 will be
			performed in order to ensure that the server
			file system only sees UTF-8 file names.

			Example: "euc-kr=host1:host2" specifies that
			host1 and host2 use the euc-kr character set
			and that path and file name components must be
			converted between euc-kr and UTF-8.

			An initial set of translations will be
			available with possible future additions being
			delivered through the facilities provided via
			PSARC/2007/173.

    3.2. Market/Requester:

	NAS server team

    3.3. Business Justification:

	Needed to maintain compatibility with our existing product
	line when it migrates to a Solaris base.

    3.4. Competitive Analysis:

	Current Procom based product uses this functionality.

    3.5. Opportunity Window/Exposure:

	Needs to be available in first release of the Solaris based
	NAS server.

    3.6. How will you know when you are done?:

	When the properties are implemented and tested. This is not a
	large effort.


4. Technical Description:
     4.1. Details:

	 The properties need to be added to the sharemgr NFS plugin to
	 enable the correct property parsing and fill-in of the export
	 structures.

	 Mountd needs to be taught about the "none" and charset
	 properties in order to search the access-list associated with
	 it.

	 The kernel nfs modules need to know that the uid0 value needs
	 to be used appropriately.

	 An upcall to mountd to check the access list needs to be done
	 at client session establishment.

	 The kernel nfs modules will need to know that a client
	 session needs a character conversion and convert the paths
	 and file name components appropriately. This includes all
	 lookup cases and dirent calls, among others.


     4.2. Bug/RFE Number(s):

	 6475452 Need Solaris support for Montana approve file functionality in NFS

     4.3. In Scope:


     4.4. Out of Scope:


     4.5. Interfaces:

	 New options on exported NFS shares. These will be committed
	 interfaces.

     4.6. Doc Impact:

	 Man pages and the adminstration guide will need to be updated
	 to reflect the new functionality.  In particular,
	 sharemgr(1m) and share_nfs(1m) need updating.

     4.7. Admin/Config Impact:
	// How will this change impact the administration of the product?
	// Identify changes to GUIs, CLI, agents, plugins...

     4.8. HA Impact:

	 N/A

     4.9. I18N/L10N Impact:

	N/A

     4.10. Packaging & Delivery:

	  No new packages and no install time dependencies.

     4.11. Security Impact:

	  Doesn't affect existing security interfaces. Provides a way
	  to limit root clients or to exclude some clients from
	  accessing NFS.

     4.12. Dependencies:

	  N/A

5. Reference Documents:
	  6475452 Need Solaris support for Montana approve file functionality 
in NFS
	

6. Resources and Schedule:
    6.1. Projected Availability:

	Q2 - 2007

    6.2. Cost of Effort:

	Couple of weeks
	

    6.3. Cost of Capital Resources:

	Using existing equipment

    6.4. Product Approval Committee requested information:
    	6.4.1. Consolidation or Component Name:
	       ON

	6.4.3. Type of CPT Review and Approval expected:
	       RFE

         6.4.4. Project Boundary Conditions:
	       N/A

	6.4.5. Is this a necessary project for OEM agreements:
	       N/A

	6.4.6. Notes:
	6.4.7. Target RTI Date/Release:
	       onnv_67

	6.4.8. Target Code Design Review Date:
	6.4.9. Update approval addition:
	       N/A

    6.5. ARC review type:
	       FastTrack

7. Prototype Availability:
    7.1. Prototype Availability:

	before end of May

    7.2. Prototype Cost:



From Darren.Moffat@Sun.COM Mon May 21 01:35:49 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4L8Zmog025373
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 21 May 2007 01:35:48 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4L8YZAu009321
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Mon, 21 May 2007 09:34:36 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JID00I07UHLWC00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Mon, 21 May 2007 02:34:33 -0600 (MDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.5])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JID00EMNUHKUD20@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon,
 21 May 2007 02:34:33 -0600 (MDT)
Received: from d1-emea-09.sun.com (d1-emea-09.sun.com [192.18.2.119])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4L8YVRK010295	for
 <psarc-ext@sun.com>; Mon, 21 May 2007 08:34:31 +0000 (GMT)
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JID00N01TY50Q00@d1-emea-09.sun.com>
 (original mail from Darren.Moffat@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon,
 21 May 2007 09:34:31 +0100 (BST)
Received: from [129.156.173.21] by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JID00ECXUGXGS10@d1-emea-09.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Mon, 21 May 2007 09:34:28 +0100 (BST)
Date: Mon, 21 May 2007 09:34:09 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <464E1EDB.9050307@sun.com>
Sender: Darren.Moffat@Sun.COM
To: Calum Mackay <Calum.Mackay@Sun.COM>
Cc: psarc-ext@Sun.COM, Doug McCallum <Doug.McCallum@Sun.COM>
Message-id: <46515981.2000000@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <464E1EDB.9050307@sun.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070424)
Status: RO
Content-Length: 1075

Calum Mackay wrote:


>     uid0        Is similar to the "anon" property except that
>             it changes the UID associated with a root
>             client that is allowed root access via the
>             "root=access-list" property.
>            
>             Example: "root=host1:host2,uid0=321" would set
>             the UID of the root user on host1 or host2 to
>             321 instead of 0.

I assume that if uid0= is used and root= is not used before it then 
there is no effect ?  I'm basing this assumption on the fact that by 
default uid of 0 is mapped to the anon user.

Is there any flexibility in the choice of name ?  I personally find this 
name very confusing since we already have a root= property.  My 
suggestion would be map_uid0=.  Is this really only needed for mapping 
of uid 0 to some other uid, why not have a generic system ?

How does this interact with nfsmapid and (if we have it yet) the ability 
to write plugins for doing mappings ?

I think the answer is that this happens after name to id mapping right ?


-- 
Darren J Moffat

From Doug.McCallum@sun.com Mon May 21 06:02:47 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4LD2kuA029332
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 21 May 2007 06:02:47 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4LD1NKl015963
	for <@sunmail3mpk.sfbay.sun.com:psarc-ext@sun.com>; Mon, 21 May 2007 14:01:34 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JIE0010D6UL2H00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Mon, 21 May 2007 06:01:33 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JIE00DHN6ULLUD0@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon,
 21 May 2007 06:01:33 -0700 (PDT)
Received: from fe-amer-01.sun.com ([192.18.108.175])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4LD1XbN020370	for
 <psarc-ext@sun.com>; Mon, 21 May 2007 13:01:33 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JIE00M0164ASA00@mail-amer.sun.com>
 (original mail from Doug.McCallum@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon,
 21 May 2007 07:01:33 -0600 (MDT)
Received: from [129.150.49.21] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JIE00IGA6U3T782@mail-amer.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Mon, 21 May 2007 07:01:16 -0600 (MDT)
Date: Mon, 21 May 2007 07:01:17 -0600
From: Doug McCallum <Doug.McCallum@sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <46515981.2000000@Sun.COM>
Sender: Doug.McCallum@sun.com
To: Darren J Moffat <Darren.Moffat@sun.com>
Cc: Calum Mackay <Calum.Mackay@sun.com>, psarc-ext@sun.com
Message-id: <4651981D.40601@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <464E1EDB.9050307@sun.com> <46515981.2000000@Sun.COM>
User-Agent: Thunderbird 1.5.0.5 (X11/20060828)
Status: RO
Content-Length: 1442

Darren J Moffat wrote:
> Calum Mackay wrote:
>
>
>>     uid0        Is similar to the "anon" property except that
>>             it changes the UID associated with a root
>>             client that is allowed root access via the
>>             "root=access-list" property.
>>                        Example: "root=host1:host2,uid0=321" would set
>>             the UID of the root user on host1 or host2 to
>>             321 instead of 0.
>
> I assume that if uid0= is used and root= is not used before it then 
> there is no effect ?  I'm basing this assumption on the fact that by 
> default uid of 0 is mapped to the anon user.
That is correct. If root isn't used, the normal root processing is in 
effect. uid0 is to change the uid for authorized root users.
>
> Is there any flexibility in the choice of name ?  I personally find 
> this name very confusing since we already have a root= property.  My 
> suggestion would be map_uid0=.  Is this really only needed for mapping 
> of uid 0 to some other uid, why not have a generic system ?
I'm not tied to the name. uid0 is what the Montana product uses. It 
could be something else without a problem.

>
> How does this interact with nfsmapid and (if we have it yet) the 
> ability to write plugins for doing mappings ?
>
> I think the answer is that this happens after name to id mapping right ?
Yes.  The uid0 mapping is done late in the processing and id mapping is 
already done.



From gww@eng.sun.com Wed May 23 09:27:59 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NGRwWM002734
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 23 May 2007 09:27:58 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4NGQWN4019936
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 00:26:44 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII0000B5OIZU00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 09:26:42 -0700 (PDT)
Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00JM65OHEND0@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 09:26:41 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2)
 with ESMTP id l4NGQcC6000725; Wed, 23 May 2007 09:26:38 -0700 (PDT)
Received: from marduk.eng.sun.com (localhost [127.0.0.1])
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l4NGSgxZ016860; Wed,
 23 May 2007 09:28:42 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l4NGSgUU016859; Wed,
 23 May 2007 09:28:42 -0700 (PDT)
Date: Wed, 23 May 2007 09:28:42 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
To: Darren.Moffat@sun.com, Doug.McCallum@sun.com
Cc: Calum.Mackay@sun.com, psarc-ext@sun.com
Message-id: <200705231628.l4NGSgUU016859@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
Status: RO
Content-Length: 1062

> Darren J Moffat wrote:
> > Calum Mackay wrote:
> >
> >
> >>     uid0        Is similar to the "anon" property except that
> >>             it changes the UID associated with a root
> >>             client that is allowed root access via the
> >>             "root=access-list" property.
> >>                        Example: "root=host1:host2,uid0=321" would set
> >>             the UID of the root user on host1 or host2 to
> >>             321 instead of 0.
> >
> > I assume that if uid0= is used and root= is not used before it then 
> > there is no effect ?  I'm basing this assumption on the fact that by 
> > default uid of 0 is mapped to the anon user.

	I too am not excited about the keyword "uid0", not "map_uid0",
	since privileges are now the general security mechanism,
	I'd prefer not to suggest "0" is special.  How about
	"root=<list>,maped_uid=<uid_t>"?
	I know it's nit picking and not architectural except for the
	implication of 0 == all privs, when it's really suid 0 force
	all privs and everything else is inheritance from cred.

Gary..

From Doug.McCallum@sun.com Wed May 23 09:40:54 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NGer32003150
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 09:40:54 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4NGdW3Y016643
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 23 May 2007 17:39:40 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII0020D6A33F00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 09:39:39 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII000FB6A2VI20@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 09:39:38 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.108.184])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NGdc3w011044	for
 <psarc-ext@sun.com>; Wed, 23 May 2007 16:39:38 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII0050165C7S00@mail-amer.sun.com>
 (original mail from Doug.McCallum@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 10:39:38 -0600 (MDT)
Received: from [198.18.100.238] ([12.10.172.132])
 by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0JII00KWL6A1SFM0@mail-amer.sun.com>; Wed,
 23 May 2007 10:39:38 -0600 (MDT)
Date: Wed, 23 May 2007 10:39:40 -0600
From: Doug McCallum <Doug.McCallum@sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <200705231628.l4NGSgUU016859@marduk.eng.sun.com>
Sender: Doug.McCallum@sun.com
To: Gary Winiger <gww@eng.sun.com>
Cc: Darren.Moffat@sun.com, Calum.Mackay@sun.com, psarc-ext@sun.com
Message-id: <46546E4C.5010309@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <200705231628.l4NGSgUU016859@marduk.eng.sun.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060828)
Status: RO
Content-Length: 719

Gary Winiger wrote:
>
> 	I too am not excited about the keyword "uid0", not "map_uid0",
> 	since privileges are now the general security mechanism,
> 	I'd prefer not to suggest "0" is special.  How about
> 	"root=<list>,maped_uid=<uid_t>"?
> 	I know it's nit picking and not architectural except for the
> 	implication of 0 == all privs, when it's really suid 0 force
> 	all privs and everything else is inheritance from cred.
>   
Something like "mapped_uid" instead of uid0 sounds fine to me. It would 
then be documented to be
associated with the root=<list> property and becomes the uid that the 
"root" user is mapped to
rather than what uid == 0 is mapped to.  I can go with whatever guidance 
is provided.

Doug

From Gordon.Ross@Sun.COM Wed May 23 09:57:12 2007
Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NGvB4G004772
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 23 May 2007 09:57:11 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l4NGtnj2000032
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Thu, 24 May 2007 00:55:57 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII0030D718JW00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 09:55:56 -0700 (PDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII000AT717VI60@nwk-avmta-1.sfbay.Sun.COM> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 09:55:55 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.108.184])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NGtscV023729	for
 <psarc-ext@sun.com>; Wed, 23 May 2007 16:55:54 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII002016YMUN00@mail-amer.sun.com>
 (original mail from Gordon.Ross@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 10:55:54 -0600 (MDT)
Received: from [192.9.61.211] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JII00KNU714SESR@mail-amer.sun.com>; Wed,
 23 May 2007 10:55:54 -0600 (MDT)
Date: Wed, 23 May 2007 12:55:51 -0400
From: Gordon Ross <Gordon.Ross@Sun.COM>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <46546E4C.5010309@Sun.COM>
Sender: Gordon.Ross@Sun.COM
To: Doug McCallum <Doug.McCallum@Sun.COM>
Cc: Gary Winiger <gww@eng.sun.com>, Darren.Moffat@Sun.COM,
        Calum.Mackay@Sun.COM, psarc-ext@Sun.COM
Message-id: <46547217.1050008@Sun.COM>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <200705231628.l4NGSgUU016859@marduk.eng.sun.com>
 <46546E4C.5010309@Sun.COM>
User-Agent: Thunderbird 1.5.0.8 (X11/20061204)
Status: RO
Content-Length: 1021

I know, committees can argue endlessly about names and colors,
so with some hesitation I'll suggest that it seems more obvious
with "root" in the name.  Then the options might look like:
    root=host-list, root_mapping=65534
  
Doug McCallum wrote:
> Gary Winiger wrote:
>>
>>     I too am not excited about the keyword "uid0", not "map_uid0",
>>     since privileges are now the general security mechanism,
>>     I'd prefer not to suggest "0" is special.  How about
>>     "root=<list>,maped_uid=<uid_t>"?
>>     I know it's nit picking and not architectural except for the
>>     implication of 0 == all privs, when it's really suid 0 force
>>     all privs and everything else is inheritance from cred.
>>   
> Something like "mapped_uid" instead of uid0 sounds fine to me. It 
> would then be documented to be
> associated with the root=<list> property and becomes the uid that the 
> "root" user is mapped to
> rather than what uid == 0 is mapped to.  I can go with whatever 
> guidance is provided.
>
> Doug
>




From Calum.Mackay@sun.com Wed May 23 10:34:46 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NHYjuA008519
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 10:34:45 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4NHXTE0006491
	for <@newsunmail1brm.central.sun.com:psarc-ext@sun.com>; Wed, 23 May 2007 18:33:32 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00H1Z8RWPC00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Wed, 23 May 2007 11:33:32 -0600 (MDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.5])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII0059U8RV0R60@brm-avmta-1.central.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 11:33:31 -0600 (MDT)
Received: from d1-emea-09.sun.com (d1-emea-09.sun.com [192.18.2.119])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NHXUcE004644	for
 <psarc-ext@sun.com>; Wed, 23 May 2007 17:33:30 +0000 (GMT)
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII00C018MJUE00@d1-emea-09.sun.com>
 (original mail from Calum.Mackay@Sun.COM)
 for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 18:33:30 +0100 (BST)
Received: from [192.168.254.1] ([62.24.230.83])
 by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0JII00H708RTWX3D@d1-emea-09.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed,
 23 May 2007 18:33:30 +0100 (BST)
Date: Wed, 23 May 2007 18:33:28 +0100
From: Calum Mackay <Calum.Mackay@sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <464E1EDB.9050307@sun.com>
Sender: Calum.Mackay@sun.com
To: Calum Mackay <Calum.Mackay@sun.com>
Cc: PSARC-EXT@sun.com, Doug McCallum <Doug.McCallum@sun.com>
Message-id: <46547AE8.7090002@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <464E1EDB.9050307@sun.com>
User-Agent: Thunderbird 3.0a1 (X11/20070504)
Status: RO
Content-Length: 220

This fast-track was approved at today's PSARC meeting, subject to a 
final agreement on the name of the root uid mapping option.

When that agreement is reached, I will update the case with the final spec.

cheers,
c.



From Darren.Moffat@sun.com Wed May 23 11:50:47 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NIolpY010678
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 11:50:47 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4NInGcu003614
	for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@sun.com>; Wed, 23 May 2007 19:49:33 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00L09CAK0M00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com
 (ORCPT PSARC-EXT@sun.com); Wed, 23 May 2007 11:49:32 -0700 (PDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00DBECAI9ZB0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed,
 23 May 2007 11:49:31 -0700 (PDT)
Received: from d1-emea-09.sun.com ([192.18.2.119])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NInUjX025332	for
 <PSARC-EXT@sun.com>; Wed, 23 May 2007 18:49:30 +0000 (GMT)
Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII00801C8I5W00@d1-emea-09.sun.com>
 (original mail from Darren.Moffat@Sun.COM)
 for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed,
 23 May 2007 19:49:30 +0100 (BST)
Received: from [129.156.173.21] by d1-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JII00KAOCAHLB10@d1-emea-09.sun.com>; Wed,
 23 May 2007 19:49:30 +0100 (BST)
Date: Wed, 23 May 2007 19:49:29 +0100
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <46547217.1050008@Sun.COM>
Sender: Darren.Moffat@sun.com
To: Gordon Ross <Gordon.Ross@sun.com>
Cc: Doug McCallum <Doug.McCallum@sun.com>, PSARC-EXT@sun.com,
        Calum.Mackay@sun.com, Gary Winiger <gww@eng.sun.com>
Message-id: <46548CB9.5040803@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <200705231628.l4NGSgUU016859@marduk.eng.sun.com>
 <46546E4C.5010309@Sun.COM> <46547217.1050008@Sun.COM>
User-Agent: Thunderbird 2.0.0.0 (X11/20070424)
Status: RO
Content-Length: 547

Gordon Ross wrote:
> I know, committees can argue endlessly about names and colors,
> so with some hesitation I'll suggest that it seems more obvious
> with "root" in the name.  Then the options might look like:
>    root=host-list, root_mapping=65534

but as I understand this it is not about mapping the root username but 
the actual uid of 0.  This happens after the name to id mapping that 
that is already done.

However given that this only actually makes sense with the root= option 
I'd be happy with your suggestion.

-- 
Darren J Moffat

From gww@eng.sun.com Wed May 23 13:02:04 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NK23hd012567
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 13:02:04 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4NK0KSB024995
	for <@sunmail2sca.sfbay.sun.com:PSARC-EXT@sun.com>; Wed, 23 May 2007 21:00:50 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00K0JFLDB500@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@sun.com
 (ORCPT PSARC-EXT@sun.com); Wed, 23 May 2007 13:00:49 -0700 (PDT)
Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII00IANFLB4W20@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed,
 23 May 2007 13:00:47 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2)
 with ESMTP id l4NK0i86000974; Wed, 23 May 2007 13:00:44 -0700 (PDT)
Received: from marduk.eng.sun.com (localhost [127.0.0.1])
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l4NK2mb2017339; Wed,
 23 May 2007 13:02:48 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l4NK2m6c017338; Wed,
 23 May 2007 13:02:48 -0700 (PDT)
Date: Wed, 23 May 2007 13:02:48 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
To: Gordon.Ross@sun.com, Darren.Moffat@sun.com
Cc: Doug.McCallum@sun.com, psarc-ext@sun.com, Calum.Mackay@sun.com,
        gww@eng.sun.com
Message-id: <200705232002.l4NK2m6c017338@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-Sun-Charset: US-ASCII
X-PMX-Version: 5.2.0.264296
Status: RO
Content-Length: 715

> Gordon Ross wrote:
> > I know, committees can argue endlessly about names and colors,
> > so with some hesitation I'll suggest that it seems more obvious
> > with "root" in the name.  Then the options might look like:
> >    root=host-list, root_mapping=65534
> 
> but as I understand this it is not about mapping the root username but 
> the actual uid of 0.  This happens after the name to id mapping that 
> that is already done.
> 
> However given that this only actually makes sense with the root= option 
> I'd be happy with your suggestion.

	This is acceptable to me as well.  Project team please update
	the spec and case owner please post the final spec and close
	the case as approved.

Thankx,
Gary..

From Calum.Mackay@sun.com Wed May 23 15:32:44 2007
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4NMWha1015130
	for <psarc-ext@sac.sfbay.sun.com>; Wed, 23 May 2007 15:32:43 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4NMVOPo011525
	for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@sun.com>; Wed, 23 May 2007 23:31:29 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JII00805MKHMU00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com
 (ORCPT PSARC-EXT@sun.com); Wed, 23 May 2007 15:31:29 -0700 (PDT)
Received: from gmp-ea-fw-1.sun.com ([129.156.42.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JII002NXMKF5LD0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed,
 23 May 2007 15:31:28 -0700 (PDT)
Received: from d1-emea-10.sun.com ([192.18.2.120])
	by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4NMVRbN002349	for
 <PSARC-EXT@sun.com>; Wed, 23 May 2007 22:31:27 +0000 (GMT)
Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JII00101MEXW200@d1-emea-10.sun.com>
 (original mail from Calum.Mackay@Sun.COM)
 for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed,
 23 May 2007 23:31:27 +0100 (BST)
Received: from [192.168.254.1] ([62.24.230.83])
 by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0JII00177MKEEV49@d1-emea-10.sun.com>; Wed,
 23 May 2007 23:31:27 +0100 (BST)
Date: Wed, 23 May 2007 23:31:25 +0100
From: Calum Mackay <Calum.Mackay@sun.com>
Subject: Re: 2007/281 NFS share properties for Montana compatibility
In-reply-to: <200705232002.l4NK2m6c017338@marduk.eng.sun.com>
Sender: Calum.Mackay@sun.com
To: Gary Winiger <gww@eng.sun.com>
Cc: Gordon.Ross@sun.com, Darren.Moffat@sun.com, Doug.McCallum@sun.com,
        psarc-ext@sun.com
Message-id: <4654C0BD.8000508@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.2.0.264296
References: <200705232002.l4NK2m6c017338@marduk.eng.sun.com>
User-Agent: Thunderbird 3.0a1 (X11/20070504)
Status: RO
Content-Length: 213

The submitter agrees with using the "root_mapping=" property.

I have placed a final spec in spec.txt, and updated the man page in the 
materials directory.

The case is now marked "closed approved".

cheers,
c.


