From <IMAP4.psuedo.sims> Fri Apr 18 14:14:28 2008
Date: Fri, 18 Apr 2008 14:14:28 -0700 (PDT)
From: Postmaster
Subject: Message from mail server       
Content-Length: 94
Mime-Version: 1.0
Status: RO
X-IMAP: 1208553268 30

Delete.
This is a system message.                                













--END+PSEUDO--

From tim.haley@sun.com Tue Apr 15 10:01:44 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FH1ii3024089
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 10:01:44 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FH1hu9025284;
	Tue, 15 Apr 2008 10:01:44 -0700 (PDT)
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 <0JZD00M1LLYVRH00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 10:01:43 -0700 (PDT)
Received: from spidey.central.sun.com ([172.20.25.27])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD00M3ILYUPS00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 10:01:42 -0700 (PDT)
Received: from spidey.central.sun.com (localhost [127.0.0.1])
	by spidey.central.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m3FH1gfS005625;
 Tue, 15 Apr 2008 11:01:42 -0600 (MDT)
Received: (from timh@localhost)	by spidey.central.sun.com
 (8.14.2+Sun/8.14.2/Submit) id m3FH1gVn005623; Tue,
 15 Apr 2008 11:01:42 -0600 (MDT)
Date: Tue, 15 Apr 2008 11:01:42 -0600 (MDT)
From: Tim Haley - Sun Microsystem <tim.haley@sun.com>
Subject: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: PSARC-ext@sun.com
Cc: cifs-eng@sun.com
Message-id: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Content-Length: 10916
Status: RO
X-Status: $$$$
X-UID: 0000000001

I am sponsoring the following fast-track for Keyur Desai.  The
requested binding is micro, timeout 4/22/2008.

Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Introduce nbtd, NetBIOS service daemon
    1.2. Name of Document Author/Supplier:
	 Author:  Keyur Desai
    1.3  Date of This Document:
	15 April, 2008

4. Technical Description:

OVERVIEW

	This proposal is to decouple the NetBIOS name, datagram and 
        browser client services from the SMB daemon and start them in a 
        separate daemon process called nbtd. This is an existing smbd  
        component and is simply being split out as a separate daemon in 
        order to provide the same functionality, currently available 
        within the CIFS service, to other Solaris services, such as 
        idmapd (Winchester) and smbfs (CIFS client).


PROPOSED SOLUTION

	A new NetBIOS name, datagram and browser client service daemon 
        (aka nbtd) along with a shared library named libnbt.so would be 
        added to Solaris.

	The nbtd daemon provides NetBIOS-over-TCP (NBT) name, datagram 
        and CIFS/E browser services including NetBIOS host announcement,
        name caching and domain controller location.  If a WINS server 
        has been configured, the local system will be registered with 
        the WINS server. Only processes with {PRIV_SYS_SMB} can run this
        daemon.

	The nbtd daemon, is managed as an SMF service with an FMRI of
	svc:/network/nbt:default.

	A shared library, libnbt.so, provides an API to the nbtd name
	service.

	The browser client does not request a list of backup browsers or
        a server list from the local master browser and does not request
        or participate in browser elections.


    4.2. Bug/RFE Number(s):

	6687726: NetBIOS service daemon
        
    4.5. Interfaces:

	The following interfaces, mentioned in CIFS design document 
        (PSARC/2006/715), are moved from SMB daemon (smbd) to NetBIOS 
        services daemon (nbtd).
		
	    - NetBIOS Browser: CIFS/E Browser Protocol [4]
	    - NetBIOS message headers: RFC 1001 [1] and RFC 1002 [2]

	Exported Interfaces
	--------------------
	    - libnbt.so

	Consumed Interfaces
	-------------------
 	    - libsmb.so
 	    - libaavl.so
 	    - libnsl.so
 	    - libsocket.so

    
    4.6. Doc Impact:

	1). Changes to smb(4) manpage
--------------------------------------------------------------------------
95,111d94
< 
<      netbios_scope
< 
<          Specifies the NetBIOS scope identifier, which identifies
<          logical  NetBIOS  networks that are on the same physical
<          network. When you specify a  NetBIOS  scope  identifier,
<          the  server  is only able to communicate with other sys-
<          tems that have the same scope defined. The  value  is  a
<          text string that represents a domain name and is limited
<          to 16 characters. By default, no value is set.
< 
<          Most environments do not require the use of the  NetBIOS
<          scope feature. If you must use this feature, ensure that
<          you track the scope identifier assigned to each node.
< 
< 
< 
133,142d115
<      pdc
< 
<          Specifies the preferred IP address for the  domain  con-
<          troller.  This property is sometimes used when there are
<          multiple domain controllers to  indicate  which  one  is
<          preferred.  If the specified domain controller responds,
<          it is chosen even if the other  domain  controllers  are
<          also available.  By default, no value is set.
< 
< 
160,178d132
<      wins_exclude
< 
<          Specifies a comma-separated list of  IP  addresses  that
<          are  to  be  excluded from WINS registration when a WINS
<          server is configured. By default, no value is set.
< 
< 
<      wins_server_1
< 
<          Specifies the IP address of the primary WINS server.  By
<          default, no value is set.
< 
< 
<      wins_server_2
< 
<          Specifies the IP address of the secondary  WINS  server.
<          By default, no value is set.
< 
< 
--------------------------------------------------------------------------

	2). Changes to smbd(1M) manpage
--------------------------------------------------------------------------
71c71
<      nbtd(1M), nbt(4), attributes(5), smf(5)
---
>      attributes(5), smf(5)
--------------------------------------------------------------------------

	3). New nbtd manpage
--------------------------------------------------------------------------
NAME
	nbtd  -  NetBIOS services daemon.

SYNOPSIS
	/usr/lib/smbsrv/nbtd
	
DESCRIPTION

	The nbtd daemon provides NetBIOS-over-TCP (NBT) name, datagram  
        & CIFS/E browser services including NetBIOS host announcement, 
	name caching and domain controller location.  If a WINS server 
	has been configured, the local system will be registered with 
	the WINS server. Only processes with {PRIV_SYS_SMB} can run this
	daemon.

	When nbtd daemon is started, the  following  services  are
	enabled:

         o    The NetBIOS name service is  started  on  UDP  port
              137.

         o    The NetBIOS datagram service is started on UDP port
              138.

	Only one instance of nbtd may be running at a time.

EXIT STATUS

	The following exit values are returned:

	0      Daemon exited cleanly.

	95     Daemon exited with a fatal error.

	96     Daemon exited with a configuration error.

ATTRIBUTES

	See the attributes(5) man page for descriptions of the  fol-
	lowing attributes:

	 ___________________________________________________________
	|       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
	|_____________________________|_____________________________|
	| Availability                | SUNWsmbsu                   |
	|_____________________________|_____________________________|
	| Interface Stability         | Uncommitted                 |
	|_____________________________|_____________________________|


SEE ALSO

	smbd(1M), smbadm(1M), svcs(1),  sharectl(1M),  sharemgr(1M),
	svcadm(1M), smb(4), nbt(4), smbautohome(4), system(4), smf(5),
	attributes(5)

NOTES
	Use the svcadm command to perform administrative actions  on
	the nbtd service, such as enabling, disabling, or restarting
	the service. Use the  svcs  command  to  query  the  service
	status.

	The nbtd service is managed by the service management facil-
	ity under the service identifier svc:/network/nbt:default.

	The nbtd service does not participate in Browser elections.
--------------------------------------------------------------------------

	4). New nbt manpage

	  The following SMF properties will be now part of nbtd manifest
	  and will be set via sharectl command by authorized users.

		    - scope
		    - enable
		    - exclude
		    - pdc
		    - primary_wins
		    - secondary_wins	
--------------------------------------------------------------------------
NAME
	nbt - configuration properties for Solaris NetBIOS service

DESCRIPTION
	Behavior of the Solaris NetBIOS service daemon(nbtd) is defined
	by property values that are stored in the Service Management 
	facility, smf(5).

	An authorized user can use the sharectl(1M) command  to  set
	global values for these properties in SMF.

	The following list describes the properties:

	scope

	    Specifies the NetBIOS scope, which is a character string,
	    in the form of a DNS domain name, that defines the group
	    of computers across which a registered NetBIOS name is
	    known.  NetBIOS scopes can be used to partition the
	    computer names a NetBIOS Browser displays when browsing
	    a network.  By default, no value is set. 


	pdc

	    Specifies the preferred IP address for the  domain  con-
	    troller.  When there are multiple domain controllers, the 
	    pdc property can be used to indicate a domain controller 
	    preference. If the specified domain controller responds,
	    it is chosen even if the other  domain  controllers  are
	    also available.  By default, no value is set.


	exclude

	    Specifies a comma-separated list of  IP  addresses  that
	    are  to  be  excluded from WINS registration when a WINS
	    server is configured. By default, no value is set.


	primary_wins

	    Specifies the IP address of the primary WINS server.  By
	    default, no value is set.


	secondary_wins

	    Specifies the IP address of the secondary  WINS  server.
	    By default, no value is set.


	enable
	
	    The enable property allows NetBIOS services to be enabled or
	    disabled.  

	    When NetBIOS services are enabled: 

	     - nbtd(1M) will generate host announcements and listen for
	       NetBIOS messages on ports 137 and 138.

	     - smbd(1M) will accept SMB-over-NetBIOS (port 139) and
	       SMB-over-TCP (port 445) connections.

	     - The smbd(1M) redirector will attempt to make connections
	       using SMB-over-TCP (port 445) and, if that fails, retry
	       using SMB-over-NetBIOS (port 139). 

	    When NetBIOS services are disabled:

	     - nbtd(1M) will not generate host announcements and will
               not listen on ports 137 or 138.

             - smbd(1M) will only accept SMB-over-TCP (port 445)
               connections.

             - The smbd(1M) redirector will only make connections
               using SMB-over-TCP (port 445).

            By default, the enable property is set to 'true' and NetBIOS
	    services are enabled. 


ATTRIBUTES
	See the attributes(5) man page for descriptions of the  fol-
	lowing attributes:

	 ___________________________________________________________
	|       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
	|_____________________________|_____________________________|
	| Availability                | SUNWsmbsu                   |
	|_____________________________|____________________________ |
	| Interface Stability         | Uncommitted                 |
	|_____________________________|_____________________________|


SEE ALSO
	sharectl(1M),  smbadm(1M),  smbd(1M),  nbtd(1M), smbstat(1M),
	attributes(5), smf(5), smb(4)
--------------------------------------------------------------------------

        
    4.10. Packaging & Delivery:

	- SUNWsmbsr and SUNWsmbsu.

5. Reference Documents:

	[1] RFC 1001 : NetBIOS over TCP/UDP Concepts.
  		Protocol Standard For a NetBIOS Service on a 
		TCP/UDP Transport: Concepts and Methods.

	[2] RFC 1002 : NetBIOS over TCP/UDP Specification.
		Protocol Standard For a NetBIOS Service on a
		TCP/UDP Transport: Detailed Specifications.

	[3] PSARC/2006/715

	[4] CIFS/E Browser Protocol: Paul Leach and Dilip Naik

6. Resources and Schedule:
   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name: ON

   6.5. ARC review type:  FastTrack

   6.6. ARC Exposure:	open

From carlsonj@phorcys.east.sun.com Tue Apr 15 10:19:13 2008
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 m3FHJCEs025366
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 10:19:13 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FHJA9P011663;
	Wed, 16 Apr 2008 01:19:11 +0800 (SGT)
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 <0JZD00L07MRXX700@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 11:19:09 -0600 (MDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD0094BMRR5IC0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 11:19:03 -0600 (MDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m3FHJ3VA029813; Tue,
 15 Apr 2008 13:19:03 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m3FHJ3Kd029810; Tue,
 15 Apr 2008 13:19:03 -0400 (EDT)
Date: Tue, 15 Apr 2008 13:19:03 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
To: Tim Haley - Sun Microsystem <tim.haley@sun.com>
Cc: psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <18436.58247.480216.52598@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
Content-Length: 1832
Status: RO
X-Status: $$$$
X-UID: 0000000002

Tim Haley - Sun Microsystem writes:
> I am sponsoring the following fast-track for Keyur Desai.  The
> requested binding is micro, timeout 4/22/2008.

Is "patch/micro" intended?

If so, then what happens when someone with one of the existing systems
gets this new implementation?  What does patch installation do?

> 	Exported Interfaces
> 	--------------------
> 	    - libnbt.so

Exported how?  What stability do these interfaces have?  Does anything
use them?  (Are they present on any other systems?)

If these are intended to be something other than "Project Private,"
could we have a list of the interfaces in the library?

> SYNOPSIS
> 	/usr/lib/smbsrv/nbtd

Are users or scripts supposed to interact directly with the binary?
If not, then why document it?

I suspect that this should actually be a Project Private detail, and
that the SMF FMRI is the documented administrative interface.

> EXIT STATUS
> 
> 	The following exit values are returned:

Similarly, I don't think these should be public interfaces, unless
there's some clear need for some other part of the system to invoke
the daemon directly.  If there is such a need, then that's an
important bit of architecture to discuss.  (And, if so, this might not
be a fast-track anymore.)

> 	Use the svcadm command to perform administrative actions  on
> 	the nbtd service, such as enabling, disabling, or restarting
> 	the service. Use the  svcs  command  to  query  the  service
> 	status.

Who enables this?  Is the administrator expected to know when to do
this, or does it get enabled automatically when needed (when sharectl
demands it)?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Timothy.Haley@sun.com Tue Apr 15 11:08:45 2008
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 m3FI8iR6027627
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 11:08:44 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FI8cqK029553;
	Wed, 16 Apr 2008 02:08:43 +0800 (SGT)
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 <0JZD0012ZP2IH400@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 12:08:42 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD009EEP2G61F0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 12:08:40 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3FI8ed9000944; Tue,
 15 Apr 2008 18:08:40 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00601OTFYK00@mail-amer.sun.com>
 (original mail from Timothy.Haley@Sun.COM); Tue,
 15 Apr 2008 12:08:40 -0600 (MDT)
Received: from [172.20.25.27] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZD00ABDP27UDC0@mail-amer.sun.com>; Tue,
 15 Apr 2008 12:08:31 -0600 (MDT)
Date: Tue, 15 Apr 2008 12:08:31 -0600
From: Tim Haley <Timothy.Haley@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <18436.58247.480216.52598@gargle.gargle.HOWL>
Sender: Timothy.Haley@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: psarc-ext@sun.com, cifs-eng@sun.com, Keyur Desai <Keyur.Desai@sun.com>
Message-id: <4804EF1F.2010400@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.12 (X11/20080325)
Content-Length: 2318
Status: RO
X-Status: $$$$
X-UID: 0000000003

James Carlson wrote:
> Tim Haley - Sun Microsystem writes:
>> I am sponsoring the following fast-track for Keyur Desai.  The
>> requested binding is micro, timeout 4/22/2008.
> 
> Is "patch/micro" intended?
> 
Argh, no, there is no intent to backport these, that should have been minor.
I probably owe someone a Bier(1) for getting this wrong one too many times.

> If so, then what happens when someone with one of the existing systems
> gets this new implementation?  What does patch installation do?
> 
>> 	Exported Interfaces
>> 	--------------------
>> 	    - libnbt.so
> 
> Exported how?  What stability do these interfaces have?  Does anything
> use them?  (Are they present on any other systems?)
> 
> If these are intended to be something other than "Project Private,"
> could we have a list of the interfaces in the library?
> 

These are indeed project private, as were the smbd and libsmb interfaces from 
PSARC/2006/715.  Since we did not enumerate in depth the interfaces in that 
case, we chose to do the same here.  We will note that they are project 
private in the materials, however.

>> SYNOPSIS
>> 	/usr/lib/smbsrv/nbtd
> 
> Are users or scripts supposed to interact directly with the binary?
> If not, then why document it?
> 
I'll let Keyur confirm, but I don't believe so.  It was included for 
completeness more than anything.

> I suspect that this should actually be a Project Private detail, and
> that the SMF FMRI is the documented administrative interface.
> 
>> EXIT STATUS
>>
>> 	The following exit values are returned:
> 
> Similarly, I don't think these should be public interfaces, unless
> there's some clear need for some other part of the system to invoke
> the daemon directly.  If there is such a need, then that's an
> important bit of architecture to discuss.  (And, if so, this might not
> be a fast-track anymore.)
> 
Again, I'll ask Keyur to respond on details here.

>> 	Use the svcadm command to perform administrative actions  on
>> 	the nbtd service, such as enabling, disabling, or restarting
>> 	the service. Use the  svcs  command  to  query  the  service
>> 	status.
> 
> Who enables this?  Is the administrator expected to know when to do
> this, or does it get enabled automatically when needed (when sharectl
> demands it)?
> 
and again here. :-)

thanks,
-tim

From Darren.Moffat@Sun.COM Tue Apr 15 13:59:34 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FKxXgV009583
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 13:59:33 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FKxWk9030864;
	Tue, 15 Apr 2008 14:59:33 -0600 (MDT)
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 <0JZD00C0JWZ9WK00@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 14:59:33 -0600 (MDT)
Received: from gmp-eb-inf-2.sun.com ([192.18.6.24])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD0027IWZ6AL80@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 14:59:31 -0600 (MDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10])
	by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FKxUNf012976; Tue,
 15 Apr 2008 20:59:30 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00I01WTD3C00@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM); Tue,
 15 Apr 2008 21:59:30 +0100 (BST)
Received: from [10.0.242.191] ([192.18.41.196])
 by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28
 2007)) with ESMTPSA id <0JZD00M1MWZ3PX20@fe-emea-10.sun.com>; Tue,
 15 Apr 2008 21:59:30 +0100 (BST)
Date: Tue, 15 Apr 2008 22:59:27 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
Sender: Darren.Moffat@Sun.COM
To: Tim Haley - Sun Microsystem <tim.haley@Sun.COM>
Cc: psarc-ext@Sun.COM, cifs-eng@Sun.COM
Message-id: <4805253F.5090506@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
Content-Length: 80
Status: RO
X-Status: $$$$
X-UID: 0000000004

What uid/gid and full list of privileges does nbtd run as ?

--
Darren J Moffat

From Keyur.Desai@Sun.COM Tue Apr 15 14:11:55 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FLBtKD011032
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 14:11:55 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FLBtk4003757;
	Tue, 15 Apr 2008 14:11:55 -0700 (PDT)
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 <0JZD0000HXJUER00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 14:11:54 -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 <0JZD00HFZXJGFEB0@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 14:11:40 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3FLBdBp018229; Tue,
 15 Apr 2008 21:11:40 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00501UEXV100@mail-amer.sun.com>
 (original mail from Keyur.Desai@Sun.COM); Tue, 15 Apr 2008 15:11:39 -0600 (MDT)
Received: from [129.147.51.20] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZD00KV4XIUUW40@mail-amer.sun.com>; Tue,
 15 Apr 2008 15:11:24 -0600 (MDT)
Date: Tue, 15 Apr 2008 15:06:01 -0600
From: Keyur Desai <Keyur.Desai@Sun.COM>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <4805253F.5090506@Sun.COM>
Sender: Keyur.Desai@Sun.COM
To: Darren J Moffat <Darren.Moffat@Sun.COM>
Cc: Tim Haley - Sun Microsystem <tim.haley@Sun.COM>, psarc-ext@Sun.COM,
        cifs-eng@Sun.COM
Message-id: <480518B9.8030003@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <4805253F.5090506@Sun.COM>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Content-Length: 147
Status: RO
X-Status: $$$$
X-UID: 0000000005

Darren J Moffat wrote:
> What uid/gid and full list of privileges does nbtd run as ?

root/sys

privileges=basic,sys_smb

> -- 
> Darren J Moffat


From Darren.Moffat@Sun.COM Tue Apr 15 14:48:35 2008
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 m3FLmYvf012686
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 14:48:35 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FLmRTZ021443;
	Wed, 16 Apr 2008 05:48:33 +0800 (SGT)
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 <0JZD00A01Z8VGI00@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 14:48:31 -0700 (PDT)
Received: from gmp-eb-inf-1.sun.com ([192.18.6.21])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD006FXZ8UEO80@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 14:48:31 -0700 (PDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FLmTtj021797; Tue,
 15 Apr 2008 21:48:30 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00L01Z15K500@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM); Tue,
 15 Apr 2008 22:48:29 +0100 (BST)
Received: from [129.146.30.42] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZD00M42Z8RPX20@fe-emea-10.sun.com>; Tue,
 15 Apr 2008 22:48:29 +0100 (BST)
Date: Tue, 15 Apr 2008 23:48:26 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <480518B9.8030003@Sun.COM>
Sender: Darren.Moffat@Sun.COM
To: Keyur Desai <Keyur.Desai@Sun.COM>
Cc: Tim Haley - Sun Microsystem <tim.haley@Sun.COM>, psarc-ext@Sun.COM,
        cifs-eng@Sun.COM
Message-id: <480530BA.3080707@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <4805253F.5090506@Sun.COM> <480518B9.8030003@Sun.COM>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
Content-Length: 255
Status: RO
X-Status: $$$$
X-UID: 0000000006

Keyur Desai wrote:
> Darren J Moffat wrote:
>> What uid/gid and full list of privileges does nbtd run as ?
> 
> root/sys
> 
> privileges=basic,sys_smb

Why does it need uid root and gid sys ?

Why can't it run as uid and gid daemon ?

-- 
Darren J Moffat

From Keyur.Desai@sun.com Tue Apr 15 14:50:45 2008
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 m3FLojXR012721
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 14:50:45 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3FLofQH002983;
	Tue, 15 Apr 2008 22:50:44 +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 <0JZD00401ZCKNS00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 14:50:44 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD004IBZCJ9K10@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 14:50:43 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3FLohtD025978; Tue,
 15 Apr 2008 21:50:43 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00B01XFWFU00@mail-amer.sun.com>
 (original mail from Keyur.Desai@Sun.COM); Tue, 15 Apr 2008 15:50:43 -0600 (MDT)
Received: from [129.147.51.20] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZD00LTAZCHRE20@mail-amer.sun.com>; Tue,
 15 Apr 2008 15:50:41 -0600 (MDT)
Date: Tue, 15 Apr 2008 15:45:23 -0600
From: Keyur Desai <Keyur.Desai@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <4804EF1F.2010400@sun.com>
Sender: Keyur.Desai@sun.com
To: James.D.Carlson@sun.com
Cc: psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <480521F3.10101@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Content-Length: 1993
Status: RO
X-Status: $$$$
X-UID: 0000000007

Answers embedded.

>>> SYNOPSIS
>>>     /usr/lib/smbsrv/nbtd
>>
>>
>> Are users or scripts supposed to interact directly with the binary?
>> If not, then why document it?
>>
> I'll let Keyur confirm, but I don't believe so.  It was included for 
> completeness more than anything.

That is correct. The nbtd(1M) and the nbt(4) man pages were included for
completeness purposes.


>> I suspect that this should actually be a Project Private detail, and
>> that the SMF FMRI is the documented administrative interface.
>>
>>> EXIT STATUS
>>>
>>>     The following exit values are returned:
>>
>>
>> Similarly, I don't think these should be public interfaces, unless
>> there's some clear need for some other part of the system to invoke
>> the daemon directly.  If there is such a need, then that's an
>> important bit of architecture to discuss.  (And, if so, this might not
>> be a fast-track anymore.)
>>
> Again, I'll ask Keyur to respond on details here.


Same answers as above. These are not public interfaces. The nbtd(1M) and
the nbt(4) man pages were included for completeness purposes.


>>>     Use the svcadm command to perform administrative actions  on
>>>     the nbtd service, such as enabling, disabling, or restarting
>>>     the service. Use the  svcs  command  to  query  the  service
>>>     status.
>>
>>
>> Who enables this?  Is the administrator expected to know when to do
>> this, or does it get enabled automatically when needed (when sharectl
>> demands it)?
>>

nbtd daemon is disabled by default. Most administrators know if they
need to enable/disable NetBIOS protocol in their network.

Some scenarios to enable NetBIOS include, having a system in a network,
which has NT 4.0 (and/or previous) OS installed, or systems
not upgraded to ADS.

Some administrators choose to disable NetBIOS from their network,
in order to reduce network traffic caused by periodic host announcements.

Enabling/disabling of this daemon is at the discretion of the administrator.




From gww@eng.sun.com Tue Apr 15 14:57:18 2008
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 m3FLvHkH013174
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 14:57:18 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FLvEml024708;
	Wed, 16 Apr 2008 05:57:17 +0800 (SGT)
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 <0JZD00H03ZNG6C00@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 15:57:16 -0600 (MDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD0026IZNFAIC0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 15:57:16 -0600 (MDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3FLvE4t016993; Tue, 15 Apr 2008 14:57:14 -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 m3FLun0k011795; Tue,
 15 Apr 2008 14:56:49 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3FLunNi011794; Tue,
 15 Apr 2008 14:56:49 -0700 (PDT)
Date: Tue, 15 Apr 2008 14:56:49 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: Keyur.Desai@sun.com, Darren.Moffat@sun.com
Cc: tim.haley@sun.com, psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-Sun-Charset: US-ASCII
X-PMX-Version: 5.4.1.325704
Content-Length: 78
Status: RO
X-Status: $$$$
X-UID: 0000000008

> Why can't it run as uid and gid daemon ?

	Or better yet, noaccess?

Gary..

From Darren.Moffat@Sun.COM Tue Apr 15 15:01:53 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FM1rv6013351
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 15:01:53 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FM1qWS002192;
	Tue, 15 Apr 2008 15:01:53 -0700 (PDT)
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 <0JZD00A0FZV4WR00@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 15:01:52 -0700 (PDT)
Received: from gmp-eb-inf-2.sun.com ([192.18.6.24])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZD006B8ZV1EF80@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 15:01:50 -0700 (PDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12])
	by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FM1ntF014391; Tue,
 15 Apr 2008 22:01:49 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00501ZOD0500@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM); Tue,
 15 Apr 2008 23:01:49 +0100 (BST)
Received: from [129.146.30.42] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZD00M4RZUDPX20@fe-emea-10.sun.com>; Tue,
 15 Apr 2008 23:01:27 +0100 (BST)
Date: Wed, 16 Apr 2008 00:01:25 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
Sender: Darren.Moffat@Sun.COM
To: Gary Winiger <gww@eng.sun.com>
Cc: Keyur.Desai@Sun.COM, tim.haley@Sun.COM, psarc-ext@Sun.COM,
        cifs-eng@Sun.COM
Message-id: <480533C5.9010904@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
Content-Length: 411
Status: RO
X-Status: $$$$
X-UID: 0000000009

Gary Winiger wrote:
>> Why can't it run as uid and gid daemon ?
> 
> 	Or better yet, noaccess?

No not better at all IMO, as user accounts one is no better than the 
other. However is more current use of daemon than noaccess (kcfd, 
rpcbind, nfsd, statd, lockd, for starters) in Solaris services. Also 
daemons running as daemon looks reasonable,  "noaccess" looks strange 
(to me anyway).

-- 
Darren J Moffat

From Nicolas.Williams@sun.com Tue Apr 15 15:10:06 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FMA67o014002
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 15:10:06 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FMA4cC017937;
	Tue, 15 Apr 2008 15:10:04 -0700 (PDT)
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 <0JZE0060308RMR00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:10:03 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE005OS08PNN10@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:10:02 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m3FMA1fY013160;
 Tue, 15 Apr 2008 17:10:01 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m3FMA1TL013159; Tue,
 15 Apr 2008 17:10:01 -0500 (CDT)
Date: Tue, 15 Apr 2008 17:10:01 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <480521F3.10101@Sun.COM>
To: Keyur Desai <Keyur.Desai@sun.com>
Cc: James.D.Carlson@sun.com, psarc-ext@sun.com, cifs-eng@sun.com
Mail-followup-to: Keyur Desai <Keyur.Desai@sun.com>, James.D.Carlson@sun.com,
 psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <20080415221001.GO8027@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Content-Length: 1002
Status: RO
X-Status: $$$$
X-UID: 0000000010

On Tue, Apr 15, 2008 at 03:45:23PM -0600, Keyur Desai wrote:
> >>Who enables this?  Is the administrator expected to know when to do
> >>this, or does it get enabled automatically when needed (when sharectl
> >>demands it)?
> >>
> 
> nbtd daemon is disabled by default. Most administrators know if they
> need to enable/disable NetBIOS protocol in their network.
> 
> Some scenarios to enable NetBIOS include, having a system in a network,
> which has NT 4.0 (and/or previous) OS installed, or systems
> not upgraded to ADS.

This can't be right.  You must mean providing services to such systems
requires that this service be enabled, right?

> Some administrators choose to disable NetBIOS from their network,
> in order to reduce network traffic caused by periodic host announcements.

And also because NetBIOS has a reputation for security bugs.

> Enabling/disabling of this daemon is at the discretion of the administrator.

It's not needed by either the SMB server nor the SMB client?

Nico
-- 

From gdamore@sun.com Tue Apr 15 15:20:46 2008
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 m3FMKj2l014648
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 15:20:45 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FMKOtS003067;
	Wed, 16 Apr 2008 06:20:44 +0800 (SGT)
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 <0JZE00J0D0QI0T00@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:20:42 -0600 (MDT)
Received: from sca-es-mail-1.sun.com ([192.18.43.132])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE002L60QFASC0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:20:40 -0600 (MDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FMKdX0013450;
 Tue, 15 Apr 2008 15:20:39 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZD00L01YKTZE00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com)
 ; Tue, 15 Apr 2008 15:20:39 -0700 (PDT)
Received: from [192.168.251.106] ([76.174.83.55])
 by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0JZE004YE0Q4WDB0@fe-sfbay-09.sun.com>; Tue,
 15 Apr 2008 15:20:29 -0700 (PDT)
Date: Tue, 15 Apr 2008 15:16:09 -0700
From: "Garrett D'Amore" <gdamore@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <480533C5.9010904@Sun.COM>
Sender: Garrett.Damore@sun.com
To: Darren J Moffat <Darren.Moffat@sun.com>
Cc: Gary Winiger <gww@eng.sun.com>, Keyur.Desai@sun.com, tim.haley@sun.com,
        psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <48052929.3080209@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
 <480533C5.9010904@Sun.COM>
User-Agent: Thunderbird 2.0.0.6 (X11/20071023)
Content-Length: 1642
Status: RO
X-Status: $$$$
X-UID: 0000000011

Darren J Moffat wrote:
> Gary Winiger wrote:
>>> Why can't it run as uid and gid daemon ?
>>
>>     Or better yet, noaccess?
>
> No not better at all IMO, as user accounts one is no better than the 
> other. However is more current use of daemon than noaccess (kcfd, 
> rpcbind, nfsd, statd, lockd, for starters) in Solaris services. Also 
> daemons running as daemon looks reasonable,  "noaccess" looks strange 
> (to me anyway).
>
Comparing noaccess and daemon, I agree that there is little difference 
between the two.  (ISTR however that NFS had some special handling 
around noaccess, or maybe that is nobody.  I never did anything that 
relied on the special semantics, in any case.)

HOWEVER, one could reasonably argue *separate* UID/GIDs could be used to 
provide better security isolation.  I.e., it makes sense that if someone 
finds a hack for nbtd, that we might not want that to create an exposure 
for kcfd, or nfsd, etc.  (E.g. imagine that you can now attach a 
debugger to nfsd because you hacked nbt...)

It would be really nice if we had a better way to allocate special 
purpose UIDs for these sorts of things, without worrying about 
collisions with site use of UIDs or collisions with other OS' use of 
UIDs (for shared NIS maps, for example.)  Almost like a completely 
different number space for system use only, that was guaranteed not to 
collide with any other UIDs.  Gary, do you have any thoughts here?  (I 
realize that such a project is far outside of the scope of this project, 
although the notion of possibly selected a different low numbered UID 
for nbt seems not entirely out of scope.)

    -- Garrett


From amw@sun.com Tue Apr 15 15:26:47 2008
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 m3FMQkbs014815
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 15:26:47 -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 m3FMQb2U005829;
	Wed, 16 Apr 2008 06:26:45 +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 <0JZE0080310IAZ00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:26:42 -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 <0JZE005Z610HNM20@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:26:42 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3FMQfUo015837; Tue,
 15 Apr 2008 22:26:41 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE008010FXXJ00@mail-amer.sun.com> (original mail from amw@sun.com); Tue,
 15 Apr 2008 16:26:41 -0600 (MDT)
Received: from [10.1.98.35] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE00M1610CLL60@mail-amer.sun.com>; Tue,
 15 Apr 2008 16:26:37 -0600 (MDT)
Date: Tue, 15 Apr 2008 15:25:38 -0700
From: Alan M Wright <amw@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <20080415221001.GO8027@Sun.COM>
Sender: Alan.M.Wright@sun.com
To: Keyur Desai <Keyur.Desai@sun.com>, James.D.Carlson@sun.com,
        psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <48052B62.5090105@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <20080415221001.GO8027@Sun.COM>
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)
Content-Length: 1310
Status: RO
X-Status: $$$$
X-UID: 0000000012

Nicolas Williams wrote:
> On Tue, Apr 15, 2008 at 03:45:23PM -0600, Keyur Desai wrote:
>>>> Who enables this?  Is the administrator expected to know when to do
>>>> this, or does it get enabled automatically when needed (when sharectl
>>>> demands it)?
>>>>
>> nbtd daemon is disabled by default. Most administrators know if they
>> need to enable/disable NetBIOS protocol in their network.
>>
>> Some scenarios to enable NetBIOS include, having a system in a network,
>> which has NT 4.0 (and/or previous) OS installed, or systems
>> not upgraded to ADS.
> 
> This can't be right.  You must mean providing services to such systems
> requires that this service be enabled, right?

Yes.

>> Some administrators choose to disable NetBIOS from their network,
>> in order to reduce network traffic caused by periodic host announcements.
> 
> And also because NetBIOS has a reputation for security bugs.

Yes.

>> Enabling/disabling of this daemon is at the discretion of the administrator.
> 
> It's not needed by either the SMB server nor the SMB client?

Other services (such as the SMB server or client) can specify nbtd
as a dependency but I think that's outside the scope of this fasttrack.
 From the nbtd perspective, it is only started on demand, which may
be as a result of an 'svcadm enable -r ...'

Alan

From Nicolas.Williams@sun.com Tue Apr 15 15:33:51 2008
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 m3FMXosY015016
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 15:33:50 -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 m3FMXbhS008475;
	Wed, 16 Apr 2008 06:33:43 +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 <0JZE009011C77700@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:33:43 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE0041V1C69K90@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:33:42 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m3FMXgsl013234;
 Tue, 15 Apr 2008 17:33:42 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m3FMXgsG013233; Tue,
 15 Apr 2008 17:33:42 -0500 (CDT)
Date: Tue, 15 Apr 2008 17:33:42 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <48052929.3080209@sun.com>
To: "Garrett D'Amore" <gdamore@sun.com>
Cc: Darren J Moffat <Darren.Moffat@sun.com>, Gary Winiger <gww@eng.sun.com>,
        Keyur.Desai@sun.com, tim.haley@sun.com, PSARC-ext@sun.com,
        cifs-eng@sun.com
Mail-followup-to: Garrett D'Amore <gdamore@sun.com>,
 Darren J Moffat <Darren.Moffat@sun.com>, Gary Winiger <gww@eng.sun.com>,
 Keyur.Desai@sun.com, tim.haley@sun.com, PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <20080415223341.GS8027@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
 <480533C5.9010904@Sun.COM> <48052929.3080209@sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Content-Length: 1780
Status: RO
X-Status: $$$$
X-UID: 0000000013

On Tue, Apr 15, 2008 at 03:16:09PM -0700, Garrett D'Amore wrote:
> Comparing noaccess and daemon, I agree that there is little difference 
> between the two.  (ISTR however that NFS had some special handling 
> around noaccess, or maybe that is nobody.  I never did anything that 
> relied on the special semantics, in any case.)

You're thinking of nobody.  (heh)

> HOWEVER, one could reasonably argue *separate* UID/GIDs could be used to 
> provide better security isolation.  I.e., it makes sense that if someone 

I agree.

> finds a hack for nbtd, that we might not want that to create an exposure 
> for kcfd, or nfsd, etc.  (E.g. imagine that you can now attach a 
> debugger to nfsd because you hacked nbt...)
> 
> It would be really nice if we had a better way to allocate special 
> purpose UIDs for these sorts of things, without worrying about 
> [...]

We almost do!  Now that we have an ephemeral ID concept we could have
idmapd provide an ephemeral ID allocation service for this purpose.

Another possibility is that the kernel allocates a range of ephemeral
IDs for this purpose before idmapd starts.  Since there will be few of
these we might as well have the kernel provide the allocation and name
service.

The only thing is: we still need a user/group namespace for such IDs
that won't conflict with customers.  But then, that's never stopped us
from allocating new ones in /etc/passwd and /etc/group, so it's not
necessarily a serious concern.

Still: not this case.  Or does the ARC think now's the time to put its
foot down on this issue?

Keep in mind that adding such a service to idmapd is not something we
can turn around in a week, say.  A kernel- based service could possibly
be added more quickly, and IMO would be a better architecture.

Nico
-- 

From Nicolas.Williams@sun.com Tue Apr 15 15:35:09 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FMZ9D4015032
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 15:35:09 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FMZ7lZ057890;
	Tue, 15 Apr 2008 16:35:08 -0600 (MDT)
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 <0JZE00K1H1EI2400@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:35:06 -0600 (MDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE002FV1EIAIE0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:35:06 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m3FMZ6bG013241;
 Tue, 15 Apr 2008 17:35:06 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m3FMZ6hk013240; Tue,
 15 Apr 2008 17:35:06 -0500 (CDT)
Date: Tue, 15 Apr 2008 17:35:06 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <48052B62.5090105@sun.com>
To: Alan M Wright <amw@sun.com>
Cc: Keyur Desai <Keyur.Desai@sun.com>, James.D.Carlson@sun.com,
        psarc-ext@sun.com, cifs-eng@sun.com
Mail-followup-to: Alan M Wright <amw@sun.com>,
 Keyur Desai <Keyur.Desai@sun.com>, James.D.Carlson@sun.com, psarc-ext@sun.com,
 cifs-eng@sun.com
Message-id: <20080415223506.GT8027@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <20080415221001.GO8027@Sun.COM>
 <48052B62.5090105@sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Content-Length: 607
Status: RO
X-Status: $$$$
X-UID: 0000000014

On Tue, Apr 15, 2008 at 03:25:38PM -0700, Alan M Wright wrote:
> >It's not needed by either the SMB server nor the SMB client?
> 
> Other services (such as the SMB server or client) can specify nbtd
> as a dependency but I think that's outside the scope of this fasttrack.
> From the nbtd perspective, it is only started on demand, which may
> be as a result of an 'svcadm enable -r ...'

Right, but I think the real question is: does this change how users are
expected to enable the SMB service?  And since the SMB service can be
enabled indirectly via sharectl, IIRC, shouldn't sharectl learn to do
this?

From Darren.Moffat@sun.com Tue Apr 15 15:38:09 2008
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 m3FMc9k8015073
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 15:38:09 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3FMc5CQ021054;
	Tue, 15 Apr 2008 23:38:08 +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 <0JZE00K071JJ8P00@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:38:07 -0600 (MDT)
Received: from gmp-eb-inf-1.sun.com ([192.18.6.21])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE002LH1JIAIE0@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 16:38:06 -0600 (MDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FMc56N023105; Tue,
 15 Apr 2008 22:38:05 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE00L0119S9900@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM); Tue,
 15 Apr 2008 23:38:05 +0100 (BST)
Received: from [129.146.30.42] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE00M691J4PX20@fe-emea-10.sun.com>; Tue,
 15 Apr 2008 23:37:55 +0100 (BST)
Date: Wed, 16 Apr 2008 00:37:51 +0100
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <48052929.3080209@sun.com>
Sender: Darren.Moffat@sun.com
To: "Garrett D'Amore" <gdamore@sun.com>
Cc: Gary Winiger <gww@eng.sun.com>, Keyur.Desai@sun.com, tim.haley@sun.com,
        psarc-ext@sun.com, cifs-eng@sun.com
Message-id: <48053C4F.2030302@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
 <480533C5.9010904@Sun.COM> <48052929.3080209@sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
Content-Length: 2314
Status: RO
X-Status: $$$$
X-UID: 0000000015

Garrett D'Amore wrote:
> Darren J Moffat wrote:
>> Gary Winiger wrote:
>>>> Why can't it run as uid and gid daemon ?
>>>
>>>     Or better yet, noaccess?
>>
>> No not better at all IMO, as user accounts one is no better than the 
>> other. However is more current use of daemon than noaccess (kcfd, 
>> rpcbind, nfsd, statd, lockd, for starters) in Solaris services. Also 
>> daemons running as daemon looks reasonable,  "noaccess" looks strange 
>> (to me anyway).
>>
> Comparing noaccess and daemon, I agree that there is little difference 
> between the two.  (ISTR however that NFS had some special handling 
> around noaccess, or maybe that is nobody.  I never did anything that 
> relied on the special semantics, in any case.)

It is the nobody account that is special to NFS:

nobody:x:60001:60001:NFS Anonymous Access User:/:
noaccess:x:60002:60002:No Access User:/:
nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/:


> HOWEVER, one could reasonably argue *separate* UID/GIDs could be used to 
> provide better security isolation.  I.e., it makes sense that if someone 
> finds a hack for nbtd, that we might not want that to create an exposure 
> for kcfd, or nfsd, etc.  (E.g. imagine that you can now attach a 
> debugger to nfsd because you hacked nbt...)

That is fine but we only have a limited number (gid and uid 0 through 
100) the upside is we have only allocated 19 of those so far.

> It would be really nice if we had a better way to allocate special 
> purpose UIDs for these sorts of things, without worrying about 

Exactly what is wrong with the process we use just now ?

The range 0 through 100 is reserved and PSARC deals with the allocation 
with the repository being the source of the /etc/passwd and /etc/group 
files in the current ON gate.

Because we only have a limited number we have been taking the stance 
that unless the service needs to own files that it needs to modify then 
it should not need a uid of its own.

In addition to running as daemon it is also recommended to remove the 
basic privileges proc_info and proc_session which gives a lot of the 
benefits of running as a different uid for each process.

This has all been covered in previous cases that dealt with uid allocation.

Maybe I should write it up in a best practice.


-- 
Darren J Moffat


From scott.rotondo@sun.com Tue Apr 15 15:43:03 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FMh30K015107
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 15:43:03 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FMh1Xk060338;
	Tue, 15 Apr 2008 16:43:01 -0600 (MDT)
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 <0JZE00A011RP6H00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:43:01 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE005401RONM50@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:43:00 -0700 (PDT)
Received: from [129.146.108.62] (vinifera.SFBay.Sun.COM [129.146.108.62])
	by jurassic-x4600.sfbay.sun.com (8.14.2+Sun/8.14.2)
 with ESMTP id m3FMh0hK641629; Tue, 15 Apr 2008 15:43:00 -0700 (PDT)
Date: Tue, 15 Apr 2008 15:43:00 -0700
From: Scott Rotondo <scott.rotondo@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <48052929.3080209@sun.com>
To: "Garrett D'Amore" <gdamore@sun.com>
Cc: Darren J Moffat <Darren.Moffat@sun.com>, Gary Winiger <gww@eng.sun.com>,
        Keyur.Desai@sun.com, tim.haley@sun.com, psarc-ext@sun.com,
        cifs-eng@sun.com
Message-id: <48052F74.6010602@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804152156.m3FLunNi011794@marduk.eng.sun.com>
 <480533C5.9010904@Sun.COM> <48052929.3080209@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071119)
Content-Length: 1293
Status: RO
X-Status: $$$$
X-UID: 0000000016

Garrett D'Amore wrote:
> Darren J Moffat wrote:
>> Gary Winiger wrote:
>>>> Why can't it run as uid and gid daemon ?
>>>
>>>     Or better yet, noaccess?
>>
>> No not better at all IMO, as user accounts one is no better than the 
>> other. However is more current use of daemon than noaccess (kcfd, 
>> rpcbind, nfsd, statd, lockd, for starters) in Solaris services. Also 
>> daemons running as daemon looks reasonable,  "noaccess" looks strange 
>> (to me anyway).
>>
> Comparing noaccess and daemon, I agree that there is little difference 
> between the two.  (ISTR however that NFS had some special handling 
> around noaccess, or maybe that is nobody.  I never did anything that 
> relied on the special semantics, in any case.)

If you're going to run a daemon with a non-root uid, and you're not 
going to create a new uid, you should use daemon. That's exactly the 
reason this user account exists.

The nobody account is, indeed, the uid to which NFS maps remote access 
by uid 0. No process should run with that uid.

Similarly, noaccess is not appropriate as a process uid unless you are 
certain that the process will not create files. Nothing in the file 
system should be owned by user noaccess. On the other hand, there are 
some files and directories owned by daemon.

	Scott


From gww@eng.sun.com Tue Apr 15 15:46:08 2008
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 m3FMk79C015267
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 15:46:07 -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 m3FMk22v013224;
	Wed, 16 Apr 2008 06:46:04 +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 <0JZE00A0D1WRJW00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:46:03 -0700 (PDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE004RY1WP9KA0@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 15:46:02 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3FMk0hp046391; Tue, 15 Apr 2008 15:46:00 -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 m3FMjZdW011967; Tue,
 15 Apr 2008 15:45:35 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3FMjZD8011966; Tue,
 15 Apr 2008 15:45:35 -0700 (PDT)
Date: Tue, 15 Apr 2008 15:45:35 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: Darren.Moffat@sun.com, gdamore@sun.com
Cc: gww@eng.sun.com, Keyur.Desai@sun.com, tim.haley@sun.com, psarc-ext@sun.com,
        cifs-eng@sun.com
Message-id: <200804152245.m3FMjZD8011966@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-Sun-Charset: US-ASCII
X-PMX-Version: 5.4.1.325704
Content-Length: 2058
Status: RO
X-Status: $$$$
X-UID: 0000000017

> Comparing noaccess and daemon, I agree that there is little difference 
> between the two.  (ISTR however that NFS had some special handling 
> around noaccess, or maybe that is nobody.  I never did anything that 
> relied on the special semantics, in any case.)

	NFS special cases nobody (and nobody4).  I don't recall the
	rules around user daemon.  The rules around user noaccess is
	that there are to be no objects owned by the "noaccess" user
	or group.  "daemon" being an historic user/group might have
	objects owned by it.  In fact user "bin" and "adm" are in group
	"daemon".  AND worse, user "daemon" is in group "root".  User's
	"daemon", "bin", "adm" all allow for cron jobs run as them thus
	making them more dangerous accounts than "noaccess" which has no
	such provisions.

Gary..
> HOWEVER, one could reasonably argue *separate* UID/GIDs could be used to 
> provide better security isolation.  I.e., it makes sense that if someone 
> finds a hack for nbtd, that we might not want that to create an exposure 
> for kcfd, or nfsd, etc.  (E.g. imagine that you can now attach a 
> debugger to nfsd because you hacked nbt...)

	See above.  An exploit of a service running as daemon could
	create cron jobs that would run with group root.

> It would be really nice if we had a better way to allocate special 
> purpose UIDs for these sorts of things, without worrying about 
> collisions with site use of UIDs or collisions with other OS' use of 
> UIDs (for shared NIS maps, for example.)  Almost like a completely 
> different number space for system use only, that was guaranteed not to 
> collide with any other UIDs.  Gary, do you have any thoughts here?  (I 
> realize that such a project is far outside of the scope of this project, 
> although the notion of possibly selected a different low numbered UID 
> for nbt seems not entirely out of scope.)

	Yes that's out of this cases scope.  See the OpenSolaris
	Fine Grained Access Policy (FGAP) project for binding a
	process/user to a set of objects it can view and or modify.

Gary..

From amw@sun.com Tue Apr 15 15:58:05 2008
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 m3FMw4pc015951
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 15:58:04 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3FMvtfh017625;
	Wed, 16 Apr 2008 06:58:02 +0800 (SGT)
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 <0JZE00D072GM7300@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 15:57:58 -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 <0JZE006VL2GMEKB0@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 15:57:58 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3FMvwMV012247; Tue,
 15 Apr 2008 22:57:58 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE0010127X7V00@mail-amer.sun.com> (original mail from amw@sun.com); Tue,
 15 Apr 2008 16:57:58 -0600 (MDT)
Received: from [10.1.98.35] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE009SN2GJST60@mail-amer.sun.com>; Tue,
 15 Apr 2008 16:57:55 -0600 (MDT)
Date: Tue, 15 Apr 2008 15:56:57 -0700
From: Alan M Wright <amw@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <20080415223506.GT8027@Sun.COM>
Sender: Alan.M.Wright@sun.com
To: Keyur Desai <Keyur.Desai@sun.com>, James.D.Carlson@sun.com,
        PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <480532B9.4080904@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <20080415221001.GO8027@Sun.COM>
 <48052B62.5090105@sun.com> <20080415223506.GT8027@Sun.COM>
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)
Content-Length: 855
Status: RO
X-Status: $$$$
X-UID: 0000000018

Nicolas Williams wrote:
> On Tue, Apr 15, 2008 at 03:25:38PM -0700, Alan M Wright wrote:
>>> It's not needed by either the SMB server nor the SMB client?
>> Other services (such as the SMB server or client) can specify nbtd
>> as a dependency but I think that's outside the scope of this fasttrack.
>> From the nbtd perspective, it is only started on demand, which may
>> be as a result of an 'svcadm enable -r ...'
> 
> Right, but I think the real question is: does this change how users are
> expected to enable the SMB service?  And since the SMB service can be
> enabled indirectly via sharectl, IIRC, shouldn't sharectl learn to do
> this?

It shouldn't change how the SMB service is started.  We currently advise
users to use '-r' to ensure that idmapd is started, which can also start
nbtd.  I don't smbd (smb/server) is started by sharectl.

Alan

From Darren.Moffat@sun.com Tue Apr 15 16:01:03 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FN13lu016060
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 16:01:03 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FN12bq016897;
	Tue, 15 Apr 2008 16:01:02 -0700 (PDT)
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 <0JZE00D072LQBL00@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 16:01:02 -0700 (PDT)
Received: from gmp-eb-inf-2.sun.com ([192.18.6.24])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE006HX2LNEOC0@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 16:01:00 -0700 (PDT)
Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11])
	by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3FN0xlD015461; Tue,
 15 Apr 2008 23:00:59 +0000 (GMT)
Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE00F012CAEW00@fe-emea-09.sun.com>
 (original mail from Darren.Moffat@Sun.COM); Wed,
 16 Apr 2008 00:00:59 +0100 (BST)
Received: from [129.146.30.42] by fe-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE00J452KYXX20@fe-emea-09.sun.com>; Wed,
 16 Apr 2008 00:00:36 +0100 (BST)
Date: Wed, 16 Apr 2008 01:00:33 +0100
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804152245.m3FMjZD8011966@marduk.eng.sun.com>
Sender: Darren.Moffat@sun.com
To: Gary Winiger <gww@eng.sun.com>
Cc: gdamore@sun.com, Keyur.Desai@sun.com, tim.haley@sun.com, PSARC-ext@sun.com,
        cifs-eng@sun.com
Message-id: <480541A1.4040301@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804152245.m3FMjZD8011966@marduk.eng.sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
Content-Length: 1134
Status: RO
X-Status: $$$$
X-UID: 0000000019

Gary Winiger wrote:
>> Comparing noaccess and daemon, I agree that there is little difference 
>> between the two.  (ISTR however that NFS had some special handling 
>> around noaccess, or maybe that is nobody.  I never did anything that 
>> relied on the special semantics, in any case.)
> 
> 	NFS special cases nobody (and nobody4).  I don't recall the
> 	rules around user daemon.  The rules around user noaccess is
> 	that there are to be no objects owned by the "noaccess" user
> 	or group.  "daemon" being an historic user/group might have
> 	objects owned by it.  In fact user "bin" and "adm" are in group
> 	"daemon".  

No they aren't, daemon is in group bin and adm not the other way around.

The daemon group has only the root user it in in the default /etc/group 
file.

>		AND worse, user "daemon" is in group "root". 

No it isn't. daemon uid primary group is 1 (other).  The group root has 
no members and until recently root wasn't even in the root group.

I think you need to have a look at the default /etc/passwd and 
/etc/group files, you have it all back to front (or is that front to back).

-- 
Darren J Moffat

From gww@eng.sun.com Tue Apr 15 16:13:56 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3FNDuCq016223
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 16:13:56 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3FNDsLr020443;
	Tue, 15 Apr 2008 16:13:56 -0700 (PDT)
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 <0JZE00D0J377RJ00@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 16:13:55 -0700 (PDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE006PG375EDC0@nwk-avmta-2.sfbay.sun.com>; Tue,
 15 Apr 2008 16:13:53 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3FNDppQ062354; Tue, 15 Apr 2008 16:13:51 -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 m3FNDQa9012069; Tue,
 15 Apr 2008 16:13:26 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3FNDQxK012068; Tue,
 15 Apr 2008 16:13:26 -0700 (PDT)
Date: Tue, 15 Apr 2008 16:13:26 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: gww@eng.sun.com, Darren.Moffat@sun.com
Cc: gdamore@sun.com, Keyur.Desai@sun.com, tim.haley@sun.com, PSARC-ext@sun.com,
        cifs-eng@sun.com
Message-id: <200804152313.m3FNDQxK012068@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-Sun-Charset: US-ASCII
X-PMX-Version: 5.4.1.325704
Content-Length: 393
Status: RO
X-Status: $$$$
X-UID: 0000000020

> >		AND worse, user "daemon" is in group "root". 
> 
> No it isn't. daemon uid primary group is 1 (other).  The group root has 
> no members and until recently root wasn't even in the root group.

	Right, my bad, I read /etc/group backwards.
tundra.eng-gww[102]: groups daemon
other bin adm bprice
tundra.eng-gww[103]: groups root
root other bin sys adm uucp mail tty lp nuucp daemon

Gary..

From gww@eng.sun.com Tue Apr 15 17:28:41 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3G0SfnG019047
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 17:28:41 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3G0Scv1021500;
	Tue, 15 Apr 2008 18:28:40 -0600 (MDT)
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 <0JZE00L1T6NRI400@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 17:28:39 -0700 (PDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE005ZU6NQNRE0@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 17:28:38 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3G0Sbae031663; Tue, 15 Apr 2008 17:28:37 -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 m3G0S8u3012382; Tue,
 15 Apr 2008 17:28:08 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3G0S89N012381; Tue,
 15 Apr 2008 17:28:08 -0700 (PDT)
Date: Tue, 15 Apr 2008 17:28:08 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: Darren.Moffat@sun.com, gdamore@sun.com
Cc: Keyur.Desai@sun.com, cifs-eng@sun.com, gww@eng.sun.com, psarc-ext@sun.com,
        tim.haley@sun.com
Message-id: <200804160028.m3G0S89N012381@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Content-Length: 1403
Status: RO
X-Status: $$$$
X-UID: 0000000021

> In addition to running as daemon it is also recommended to remove the 
> basic privileges proc_info and proc_session which gives a lot of the 
> benefits of running as a different uid for each process.
> 
> This has all been covered in previous cases that dealt with uid allocation.
> 
> Maybe I should write it up in a best practice.

	I don't want to stray too far off course with this.  I will note
	we could ask Joe about noaccess, and let's continue the archeology
	off line:

	shadow:
	1.4
	17 lines
	No id keywords (cm7)
	noaccess:NP:6445::::::

	D 1.4 90/04/24 01:09:41 jek3 13 11      00003/00001/00014
	MRs:
	COMMENTS:
	k18.2 Merge; matches passwd; retains lp uid
	jek3 Fri Apr 20 19:41:02 1990

	passwd:
	1.4
	17 lines
	No id keywords (cm7)
	noaccess:x:60002:60002:uid no access:/:

	D 1.4 90/04/24 01:09:45 jek3 13 11      00003/00001/00014
	MRs:
	COMMENTS:
	k18.2 merge - retained lp uid and nuucp as 9 - k18.2 adds nobody
	and noaccess
	jek3 Fri Apr 20 19:38:42 1990

	shadow:
	1.11
	noaccess:*LK*:6445::::::
	14 lines
	No id keywords (cm7)
	D 1.11 03/10/10 14:15:45 darrenm 21 20  00004/00003/00010
	MRs:
	COMMENTS:
	PSARC/2003/592 Clarification of nobody account usage
	4862399 nobody account in /etc/passwd should have an account description
	PSARC/2003/405 Sun ONE WebServer reserved uid/gid
	4926183 webservd uid 80 gid 80 should be in the default
	passwd/shadow/group file

Gary..

From gww@eng.sun.com Tue Apr 15 17:32:53 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3G0WrjB019104
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 17:32:53 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3G0WqkQ022750;
	Tue, 15 Apr 2008 18:32:52 -0600 (MDT)
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 <0JZE003136URSA00@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 18:32:51 -0600 (MDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE000416UO9J40@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 18:32:48 -0600 (MDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3G0WmRC034262; Tue, 15 Apr 2008 17:32:48 -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 m3G0WNJN012398; Tue,
 15 Apr 2008 17:32:23 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3G0WMRx012397; Tue,
 15 Apr 2008 17:32:22 -0700 (PDT)
Date: Tue, 15 Apr 2008 17:32:22 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: psarc-ext@sun.com, tim.haley@sun.com
Cc: cifs-eng@sun.com
Message-id: <200804160032.m3G0WMRx012397@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Content-Length: 1079
Status: RO
X-Status: $$$$
X-UID: 0000000022

> NOTES
> 	Use the svcadm command to perform administrative actions  on
> 	the nbtd service, such as enabling, disabling, or restarting
> 	the service. Use the  svcs  command  to  query  the  service
> 	status.
> 
> 	The nbtd service is managed by the service management facil-
> 	ity under the service identifier svc:/network/nbt:default.
> 
> 	The nbtd service does not participate in Browser elections.
> --------------------------------------------------------------------------
> 
> 	4). New nbt manpage
> 
> 	  The following SMF properties will be now part of nbtd manifest
> 	  and will be set via sharectl command by authorized users.
> 
> 		    - scope
> 		    - enable
> 		    - exclude
> 		    - pdc
> 		    - primary_wins
> 		    - secondary_wins	
> --------------------------------------------------------------------------

	How does this project meet the SMF policy:
	http://opensolaris.org/os/community/arc/policies/SMF-policy/
	particularly with respect to action and value authorizations,
	Rights Profiles, and as we've been discussing method contexts?

Gary..

From carlsonj@phorcys.east.sun.com Tue Apr 15 18:14:54 2008
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 m3G1ErYf019732
	for <psarc-ext@sac.sfbay.Sun.COM>; Tue, 15 Apr 2008 18:14:54 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3G1Ekqm003005;
	Wed, 16 Apr 2008 09:14:51 +0800 (SGT)
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 <0JZE006018SPY700@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 19:14:49 -0600 (MDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE000LO8SO9L50@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 19:14:48 -0600 (MDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m3G1Em01001361; Tue,
 15 Apr 2008 21:14:48 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m3G1ElxE001358; Tue,
 15 Apr 2008 21:14:47 -0400 (EDT)
Date: Tue, 15 Apr 2008 21:14:47 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <480521F3.10101@Sun.COM>
To: Keyur Desai <Keyur.Desai@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <18437.21255.975792.334343@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM>
Content-Length: 1945
Status: RO
X-Status: $$$$
X-UID: 0000000023

Keyur Desai writes:
> >> Are users or scripts supposed to interact directly with the binary?
> >> If not, then why document it?
> >>
> > I'll let Keyur confirm, but I don't believe so.  It was included for 
> > completeness more than anything.
> 
> That is correct. The nbtd(1M) and the nbt(4) man pages were included for
> completeness purposes.

OK.  Then what are users told?

> >> Who enables this?  Is the administrator expected to know when to do
> >> this, or does it get enabled automatically when needed (when sharectl
> >> demands it)?
> >>
> 
> nbtd daemon is disabled by default. Most administrators know if they
> need to enable/disable NetBIOS protocol in their network.

You said above that the man pages shown here won't be delivered.

So how do users know that "nbtd" is NetBIOS, and how do they know when
they need to enable the service?

> Some scenarios to enable NetBIOS include, having a system in a network,
> which has NT 4.0 (and/or previous) OS installed, or systems
> not upgraded to ADS.

Sure ... but that translates into knowing "I need NetBIOS," not into
"I need to issue 'svcadm enable nbtd' in order to finish
configuration."

How do users figure that part out?

> Some administrators choose to disable NetBIOS from their network,
> in order to reduce network traffic caused by periodic host announcements.

No doubt.  NetBIOS is chatty.

> Enabling/disabling of this daemon is at the discretion of the administrator.

I'm asking about what documentation might be provided that tells them
that they need to do this or (alternatively) how the service can be
managed automatically based on the system configuration.

If you can do the latter, then there might not be a need for the
former.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Keyur.Desai@sun.com Tue Apr 15 21:47:13 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3G4lDXJ024201
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 21:47:13 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3G4lBBV012094;
	Tue, 15 Apr 2008 21:47:13 -0700 (PDT)
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 <0JZE0011HIMON100@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 22:47:12 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZE000I9IMN4C10@brm-avmta-1.central.sun.com>; Tue,
 15 Apr 2008 22:47:11 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3G4lBSu018294; Wed,
 16 Apr 2008 04:47:11 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE00901I95UD00@mail-amer.sun.com>
 (original mail from Keyur.Desai@Sun.COM); Tue, 15 Apr 2008 22:47:11 -0600 (MDT)
Received: from [129.147.51.20] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE00FS7IM9YH30@mail-amer.sun.com>; Tue,
 15 Apr 2008 22:46:58 -0600 (MDT)
Date: Tue, 15 Apr 2008 22:41:38 -0600
From: Keyur Desai <Keyur.Desai@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804160032.m3G0WMRx012397@marduk.eng.sun.com>
Sender: Keyur.Desai@sun.com
To: Gary Winiger <gww@eng.sun.com>
Cc: PSARC-ext@sun.com, tim.haley@sun.com, cifs-eng@sun.com
Message-id: <48058382.1060405@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200804160032.m3G0WMRx012397@marduk.eng.sun.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Content-Length: 1732
Status: RO
X-Status: $$$$
X-UID: 0000000024

Gary Winiger wrote:
>>NOTES
>>	Use the svcadm command to perform administrative actions  on
>>	the nbtd service, such as enabling, disabling, or restarting
>>	the service. Use the  svcs  command  to  query  the  service
>>	status.
>>
>>	The nbtd service is managed by the service management facil-
>>	ity under the service identifier svc:/network/nbt:default.
>>
>>	The nbtd service does not participate in Browser elections.
>>--------------------------------------------------------------------------
>>
>>	4). New nbt manpage
>>
>>	  The following SMF properties will be now part of nbtd manifest
>>	  and will be set via sharectl command by authorized users.
>>
>>		    - scope
>>		    - enable
>>		    - exclude
>>		    - pdc
>>		    - primary_wins
>>		    - secondary_wins	
>>--------------------------------------------------------------------------
> 
> 
> 	How does this project meet the SMF policy:
> 	http://opensolaris.org/os/community/arc/policies/SMF-policy/
> 	particularly with respect to action and value authorizations,
> 	Rights Profiles, and as we've been discussing method contexts?
> 

The following authorizations and profiles will be used.

1).
   - solaris.smf.manage.smb

The existing solaris.smf.manage.smb authorization, will be used to cover 
activities that change the state of the service, such as starting, 
stopping or refreshing of the nbtd(1M) daemon.

2).
   - solaris.smf.value.smb

The existing solaris.smf.value.smb authorization, will be used to allow 
the users to change the nbtd daemon configuration property values.

3).
The existing SMB Management right profile will be used.

SMB Management:::Manage SMB service:
auths=solaris.smf.manage.smb,solaris.smf.value.smb:help=RtSMBMngmnt.html

From Keyur.Desai@sun.com Tue Apr 15 22:14:04 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3G5E3xl024819
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 15 Apr 2008 22:14:04 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3G5E1wJ017207;
	Tue, 15 Apr 2008 22:14:03 -0700 (PDT)
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 <0JZE0090BJVE1800@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 22:14:02 -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 <0JZE009TLJVECC90@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 15 Apr 2008 22:14:02 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3G5E2UB024444; Wed,
 16 Apr 2008 05:14:02 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZE00301JVC1B00@mail-amer.sun.com>
 (original mail from Keyur.Desai@Sun.COM); Tue, 15 Apr 2008 23:14:02 -0600 (MDT)
Received: from [129.147.51.20] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZE00IFQJVD4K70@mail-amer.sun.com>; Tue,
 15 Apr 2008 23:14:02 -0600 (MDT)
Date: Tue, 15 Apr 2008 23:08:41 -0600
From: Keyur Desai <Keyur.Desai@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <18437.21255.975792.334343@gargle.gargle.HOWL>
Sender: Keyur.Desai@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <480589D9.8040502@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Content-Length: 2638
Status: RO
X-Status: $$$$
X-UID: 0000000025

Hi James,

Answers embedded.

>>>>Are users or scripts supposed to interact directly with the binary?
>>>>If not, then why document it?
>>>>
>>>
>>>I'll let Keyur confirm, but I don't believe so.  It was included for 
>>>completeness more than anything.
>>
>>That is correct. The nbtd(1M) and the nbt(4) man pages were included for
>>completeness purposes.
> 
> 
> OK.  Then what are users told?

We will be delivering both nbtd(1M) and nbt(4) man pages and that end 
users will have access to them. (I might have caused some confusion by 
stating that man pages were included for completeness purposes)

>>>>Who enables this?  Is the administrator expected to know when to do
>>>>this, or does it get enabled automatically when needed (when sharectl
>>>>demands it)?
>>>>
>>
>>nbtd daemon is disabled by default. Most administrators know if they
>>need to enable/disable NetBIOS protocol in their network.
> 
> 
> You said above that the man pages shown here won't be delivered.
> 
> So how do users know that "nbtd" is NetBIOS, and how do they know when
> they need to enable the service?

In addition to the man pages being delivered, the Windows 
Interoperability documentation (Getting Started Guide, Admin Guide and 
Troubleshooting Guide) will be updated to cover these changes.

>>Some scenarios to enable NetBIOS include, having a system in a network,
>>which has NT 4.0 (and/or previous) OS installed, or systems
>>not upgraded to ADS.
> 
> 
> Sure ... but that translates into knowing "I need NetBIOS," not into
> "I need to issue 'svcadm enable nbtd' in order to finish
> configuration."
> 
> How do users figure that part out?
> 
> 
>>Some administrators choose to disable NetBIOS from their network,
>>in order to reduce network traffic caused by periodic host announcements.
> 
> 
> No doubt.  NetBIOS is chatty.
> 
> 
>>Enabling/disabling of this daemon is at the discretion of the administrator.
> 
> 
> I'm asking about what documentation might be provided that tells them
> that they need to do this or (alternatively) how the service can be
> managed automatically based on the system configuration.

We will be delivering the following documentation,

    - nbtd(1M) and nbt(4) man pages.
    - Windows Interoperability documentation (Getting Started Guide,
      Admin Guide and Troubleshooting Guide) will be updated to cover
      these changes.

Just to restate, this work is just a repartitioning of existing SMB 
server functionality to make it accessible to other Solaris services 
(like SMB client) and make it independently configurable, i.e. so that 
NBT configuration is distinguishable SMB configuration.

From carlsonj@phorcys.east.sun.com Thu Apr 17 08:27:31 2008
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 m3HFRVE1025802
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 17 Apr 2008 08:27:31 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3HFRQMS019367;
	Thu, 17 Apr 2008 16:27:28 +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 <0JZH00A056XRAI00@brm-avmta-1.central.sun.com>; Thu,
 17 Apr 2008 09:27:27 -0600 (MDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZH00KGO6XRRHE0@brm-avmta-1.central.sun.com>; Thu,
 17 Apr 2008 09:27:27 -0600 (MDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m3HFRQuR012562; Thu,
 17 Apr 2008 11:27:26 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m3HFRQ40012559; Thu,
 17 Apr 2008 11:27:26 -0400 (EDT)
Date: Thu, 17 Apr 2008 11:27:26 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <480589D9.8040502@Sun.COM>
To: Keyur Desai <Keyur.Desai@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <18439.27742.346433.684438@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
 <480589D9.8040502@Sun.COM>
Content-Length: 1362
Status: RO
X-Status: $$$$
X-UID: 0000000026

Keyur Desai writes:
> > OK.  Then what are users told?
> 
> We will be delivering both nbtd(1M) and nbt(4) man pages and that end 
> users will have access to them. (I might have caused some confusion by 
> stating that man pages were included for completeness purposes)

I see ...

In that case, I'd recommend paring down the information (particularly
about the exit codes) so that it's clear that the intended
administrative interface is SMF.

The goal I'm aiming at here isn't that private interfaces are
necessarily "secret," but rather that we don't document and advertise
them in a way that could lead users into depending on them.

> In addition to the man pages being delivered, the Windows 
> Interoperability documentation (Getting Started Guide, Admin Guide and 
> Troubleshooting Guide) will be updated to cover these changes.

Does smb(4) or some other existing man page need a pointer to the nbtd
page?

(Not that I care much, but "nbtd" is a pretty obscure name for the
service.  "nbt" would be better, and just plain "netbios" would
probably be even better still ... though I realize it doesn't provide
_all_ of NetBIOS.)

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From jek3@sun.com Thu Apr 17 13:15:27 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3HKFQxj007042
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 17 Apr 2008 13:15:26 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3HKFN74022138;
	Thu, 17 Apr 2008 13:15:24 -0700 (PDT)
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 <0JZH00A0RK9OIM00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 13:15:24 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZH0080AK9L3DB0@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 13:15:21 -0700 (PDT)
Received: from [129.150.13.200]
 (vpn-129-150-13-200.SFBay.Sun.COM [129.150.13.200])
	by jurassic-x4600.sfbay.sun.com (8.14.2+Sun/8.14.2)
 with ESMTP id m3HKFKwA972603; Thu, 17 Apr 2008 13:15:20 -0700 (PDT)
Date: Thu, 17 Apr 2008 10:15:50 -1000
From: Joseph Kowalski <jek3@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804160028.m3G0S89N012381@marduk.eng.sun.com>
To: Gary Winiger <gww@eng.sun.com>
Cc: Darren.Moffat@sun.com, gdamore@sun.com, Keyur.Desai@sun.com,
        cifs-eng@sun.com, psarc-ext@sun.com, tim.haley@sun.com
Message-id: <4807AFF6.5060401@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804160028.m3G0S89N012381@marduk.eng.sun.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20080225)
Content-Length: 1737
Status: RO
X-Status: $$$$
X-UID: 0000000027

Gary Winiger wrote:
>> In addition to running as daemon it is also recommended to remove the 
>> basic privileges proc_info and proc_session which gives a lot of the 
>> benefits of running as a different uid for each process.
>>
>> This has all been covered in previous cases that dealt with uid allocation.
>>
>> Maybe I should write it up in a best practice.
>>     
>
> 	I don't want to stray too far off course with this.  I will note
> 	we could ask Joe about noaccess, and let's continue the archeology
> 	off line:
>   
You're kidding...  :-)

It came from New Jersey.  I think it came from us via NFS (as 
suggested), but there is nothing
in this set of deltas to indicate that.

Yea, a "best practice" would be good.

- jek3
> 	shadow:
> 	1.4
> 	17 lines
> 	No id keywords (cm7)
> 	noaccess:NP:6445::::::
>
> 	D 1.4 90/04/24 01:09:41 jek3 13 11      00003/00001/00014
> 	MRs:
> 	COMMENTS:
> 	k18.2 Merge; matches passwd; retains lp uid
> 	jek3 Fri Apr 20 19:41:02 1990
>
> 	passwd:
> 	1.4
> 	17 lines
> 	No id keywords (cm7)
> 	noaccess:x:60002:60002:uid no access:/:
>
> 	D 1.4 90/04/24 01:09:45 jek3 13 11      00003/00001/00014
> 	MRs:
> 	COMMENTS:
> 	k18.2 merge - retained lp uid and nuucp as 9 - k18.2 adds nobody
> 	and noaccess
> 	jek3 Fri Apr 20 19:38:42 1990
>
> 	shadow:
> 	1.11
> 	noaccess:*LK*:6445::::::
> 	14 lines
> 	No id keywords (cm7)
> 	D 1.11 03/10/10 14:15:45 darrenm 21 20  00004/00003/00010
> 	MRs:
> 	COMMENTS:
> 	PSARC/2003/592 Clarification of nobody account usage
> 	4862399 nobody account in /etc/passwd should have an account description
> 	PSARC/2003/405 Sun ONE WebServer reserved uid/gid
> 	4926183 webservd uid 80 gid 80 should be in the default
> 	passwd/shadow/group file
>
> Gary..
>
>   


From Keyur.Desai@sun.com Thu Apr 17 14:12:16 2008
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 m3HLCFGV009476
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 17 Apr 2008 14:12:16 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3HLC33X017674;
	Thu, 17 Apr 2008 22:12: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 <0JZH00G0FMWBLS00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 14:12:11 -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 <0JZH00FS7MWAAX00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 14:12:10 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3HLCAng015414; Thu,
 17 Apr 2008 21:12:10 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZH00G01MD4X600@mail-amer.sun.com>
 (original mail from Keyur.Desai@Sun.COM); Thu, 17 Apr 2008 15:12:10 -0600 (MDT)
Received: from [129.147.51.20] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZH002P7MW4MO20@mail-amer.sun.com>; Thu,
 17 Apr 2008 15:12:04 -0600 (MDT)
Date: Thu, 17 Apr 2008 15:06:43 -0600
From: Keyur Desai <Keyur.Desai@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <18439.27742.346433.684438@gargle.gargle.HOWL>
Sender: Keyur.Desai@sun.com
To: James Carlson <James.D.Carlson@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <4807BBE3.7020801@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
 <480589D9.8040502@Sun.COM> <18439.27742.346433.684438@gargle.gargle.HOWL>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Content-Length: 1329
Status: RO
X-Status: $$$$
X-UID: 0000000028

Hi James,

> 
> I see ...
> 
> In that case, I'd recommend paring down the information (particularly
> about the exit codes) so that it's clear that the intended
> administrative interface is SMF.

The exit codes in nbtd(1M) are the same as those in smbd(1M), which was 
recommended when smbd(1M) was reviewed during the CIFS server case. 
(PSARC/2006/715)

>>In addition to the man pages being delivered, the Windows 
>>Interoperability documentation (Getting Started Guide, Admin Guide and 
>>Troubleshooting Guide) will be updated to cover these changes.
> 
> 
> Does smb(4) or some other existing man page need a pointer to the nbtd
> page?

We will raise CRs against smbd(1M) and smb(4) manpage, to include 
references to nbtd(1M) and nmb(4) manpage.

The diffs in the smbd(1M) manpage, listed in the fasttrack, calls out 
for addition of nbtd(1M) and nmb(4) in the SEE ALSO section.

> (Not that I care much, but "nbtd" is a pretty obscure name for the
> service.  "nbt" would be better, and just plain "netbios" would
> probably be even better still ... though I realize it doesn't provide
> _all_ of NetBIOS.)
> 

The service is named as "nbt" i.e. SMF service with an FMRI of
"svc:/network/nbt:default". (No preference here. We could call the
service "netbios")

The daemon is named as "nbtd".

Thanks for the comments.

From Gordon.Ross@sun.com Thu Apr 17 14:20:25 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3HLKPwH009603
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 17 Apr 2008 14:20:25 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3HLKMRM005188;
	Thu, 17 Apr 2008 15:20:25 -0600 (MDT)
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 <0JZH00B0JNA0NN00@brm-avmta-1.central.sun.com>; Thu,
 17 Apr 2008 15:20:24 -0600 (MDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZH008QSN9YRD30@brm-avmta-1.central.sun.com>; Thu,
 17 Apr 2008 15:20:22 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3HLKMwJ015086; Thu,
 17 Apr 2008 21:20:22 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZH00L01MFLR500@mail-amer.sun.com>
 (original mail from Gordon.Ross@Sun.COM); Thu, 17 Apr 2008 15:20:21 -0600 (MDT)
Received: from [129.148.19.52] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZH006SVN9JAPF0@mail-amer.sun.com>; Thu,
 17 Apr 2008 15:20:08 -0600 (MDT)
Date: Thu, 17 Apr 2008 17:20:06 -0400
From: Gordon Ross <Gordon.Ross@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <4807BBE3.7020801@Sun.COM>
Sender: Gordon.Ross@sun.com
To: Keyur Desai <Keyur.Desai@sun.com>, James Carlson <James.D.Carlson@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <1208467206.1084.54.camel@localhost>
MIME-version: 1.0
X-Mailer: Evolution 2.12.1
Content-type: multipart/alternative;
 boundary="Boundary_(ID_V5z0X4Rm1wcVHa21PADuUg)"
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
 <480589D9.8040502@Sun.COM> <18439.27742.346433.684438@gargle.gargle.HOWL>
 <4807BBE3.7020801@Sun.COM>
Content-Length: 2600
Status: RO
X-Status: $$$$
X-UID: 0000000029


--Boundary_(ID_V5z0X4Rm1wcVHa21PADuUg)
Content-type: text/plain
Content-transfer-encoding: 7BIT


On Thu, 2008-04-17 at 15:06 -0600, Keyur Desai wrote:
[...]

> > (Not that I care much, but "nbtd" is a pretty obscure name for the
> > service.  "nbt" would be better, and just plain "netbios" would
> > probably be even better still ... though I realize it doesn't provide
> > _all_ of NetBIOS.)
> > 
> 
> The service is named as "nbt" i.e. SMF service with an FMRI of
> "svc:/network/nbt:default". (No preference here. We could call the
> service "netbios")


Technially, "NetBIOS" is an API that can be supported on several
transports,
including: "NetBEUI" (yuch!) and "NetBIOS over TCP" (a.k.a. "NBT").
Yes, people usually mean "NetBIOS over TCP" when they say "NetBIOS",
but the "nbt" name has much precedent in communities of Windows users.

Given the above, I'd recommend keeping the names as shown in the case.

Gordon



--Boundary_(ID_V5z0X4Rm1wcVHa21PADuUg)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1">
</HEAD>
<BODY>
<BR>
On Thu, 2008-04-17 at 15:06 -0600, Keyur Desai wrote:<BR>
[...]
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">&gt; (Not that I care much, but &quot;nbtd&quot; is a pretty obscure name for the</FONT>
<FONT COLOR="#000000">&gt; service.  &quot;nbt&quot; would be better, and just plain &quot;netbios&quot; would</FONT>
<FONT COLOR="#000000">&gt; probably be even better still ... though I realize it doesn't provide</FONT>
<FONT COLOR="#000000">&gt; _all_ of NetBIOS.)</FONT>
<FONT COLOR="#000000">&gt; </FONT>

<FONT COLOR="#000000">The service is named as &quot;nbt&quot; i.e. SMF service with an FMRI of</FONT>
<FONT COLOR="#000000">&quot;svc:/network/nbt:default&quot;. (No preference here. We could call the</FONT>
<FONT COLOR="#000000">service &quot;netbios&quot;)</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
Technially, &quot;NetBIOS&quot; is an API that can be supported on several transports,<BR>
including: &quot;NetBEUI&quot; (yuch!) and &quot;NetBIOS over TCP&quot; (a.k.a. &quot;NBT&quot;).<BR>
Yes, people usually mean &quot;NetBIOS over TCP&quot; when they say &quot;NetBIOS&quot;,<BR>
but the &quot;nbt&quot; name has much precedent in communities of Windows users.<BR>
<BR>
Given the above, I'd recommend keeping the names as shown in the case.<BR>
<BR>
Gordon<BR>
<BR>
<BR>
</BODY>
</HTML>

--Boundary_(ID_V5z0X4Rm1wcVHa21PADuUg)--

From carlsonj@phorcys.east.sun.com Thu Apr 17 14:25:56 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3HLPu1J009791
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 17 Apr 2008 14:25:56 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3HLPsHT006487;
	Thu, 17 Apr 2008 15:25:55 -0600 (MDT)
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 <0JZH00I1BNJ74G00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 14:25:55 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZH00FIJNJ5AX10@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 17 Apr 2008 14:25:54 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m3HLPrQq014777; Thu,
 17 Apr 2008 17:25:53 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m3HLPrVc014774; Thu,
 17 Apr 2008 17:25:53 -0400 (EDT)
Date: Thu, 17 Apr 2008 17:25:53 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <4807BBE3.7020801@Sun.COM>
To: Keyur Desai <Keyur.Desai@sun.com>
Cc: PSARC-ext@sun.com, cifs-eng@sun.com
Message-id: <18439.49249.554062.560215@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
 <480589D9.8040502@Sun.COM> <18439.27742.346433.684438@gargle.gargle.HOWL>
 <4807BBE3.7020801@Sun.COM>
Content-Length: 1990
Status: RO
X-Status: $$$$
X-UID: 0000000030

Keyur Desai writes:
> > In that case, I'd recommend paring down the information (particularly
> > about the exit codes) so that it's clear that the intended
> > administrative interface is SMF.
> 
> The exit codes in nbtd(1M) are the same as those in smbd(1M), which was 
> recommended when smbd(1M) was reviewed during the CIFS server case. 
> (PSARC/2006/715)

The issue is whether or not users should be looking at those codes,
not whether they're similar to or the same as something that may or
may not have been reviewed in some other case.

If users don't invoke the daemon, and aren't expected to use the exit
codes, then they're private implementation details, and ought not be
exposed on a man page.  Otherwise, you'll likely get called out if you
ever need to change them.

Honestly, it's a nit, and I don't much care if you fix it, but I'm
surprised at the amount of discussion it generated.

> We will raise CRs against smbd(1M) and smb(4) manpage, to include 
> references to nbtd(1M) and nmb(4) manpage.

OK.

> The diffs in the smbd(1M) manpage, listed in the fasttrack, calls out 
> for addition of nbtd(1M) and nmb(4) in the SEE ALSO section.

The question was where users would go looking; it sounds like you've
got that answer.

> > (Not that I care much, but "nbtd" is a pretty obscure name for the
> > service.  "nbt" would be better, and just plain "netbios" would
> > probably be even better still ... though I realize it doesn't provide
> > _all_ of NetBIOS.)
> > 
> 
> The service is named as "nbt" i.e. SMF service with an FMRI of
> "svc:/network/nbt:default". (No preference here. We could call the
> service "netbios")

"nbt:default" seems fine.

(In case it comes up, I don't have any more questions.  I'm on
vacation starting ... now.)

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Timothy.Haley@sun.com Fri Apr 18 14:50:15 2008
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 m3ILoFr2017598
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 18 Apr 2008 14:50:15 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3ILoDxL001891
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 18 Apr 2008 22:50:13 +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 <0JZJ00M05JBOHE00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 18 Apr 2008 14:50:12 -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 <0JZJ00IH2JBO06D0@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 18 Apr 2008 14:50:12 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3ILoCGH017162	for
 <PSARC-ext@sun.com>; Fri, 18 Apr 2008 21:50:12 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZJ00101J11K500@mail-amer.sun.com>
 (original mail from Timothy.Haley@Sun.COM)
 for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 18 Apr 2008 15:50:12 -0600 (MDT)
Received: from [172.20.25.27] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZJ001VHJBOIJA0@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 18 Apr 2008 15:50:12 -0600 (MDT)
Date: Fri, 18 Apr 2008 15:50:12 -0600
From: Tim Haley <Timothy.Haley@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <18439.49249.554062.560215@gargle.gargle.HOWL>
Sender: Timothy.Haley@sun.com
To: PSARC-ext@sun.com
Message-id: <48091794.2050001@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_dkuSx2m8y8wDEnJ4mXXxug)"
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
 <18436.58247.480216.52598@gargle.gargle.HOWL> <4804EF1F.2010400@sun.com>
 <480521F3.10101@Sun.COM> <18437.21255.975792.334343@gargle.gargle.HOWL>
 <480589D9.8040502@Sun.COM> <18439.27742.346433.684438@gargle.gargle.HOWL>
 <4807BBE3.7020801@Sun.COM> <18439.49249.554062.560215@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.12 (X11/20080325)
Status: RO
Content-Length: 6040

This is a multi-part message in MIME format.

--Boundary_(ID_dkuSx2m8y8wDEnJ4mXXxug)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

A new spec.txt has been placed in the materials directory, incorporating the 
changes that have come about due to the various discussions.  Diffs between 
old and new specification are attached as well.

thanks,
-tim

--Boundary_(ID_dkuSx2m8y8wDEnJ4mXXxug)
Content-type: text/plain; name=nbtd_ftdiffs
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=nbtd_ftdiffs

--- nbtd_fasttrack_commit.txt.rogi	Tue Apr 15 10:30:19 2008
+++ nbtd_fasttrack_commit.txt	Fri Apr 18 15:39:46 2008
@@ -1,38 +1,12 @@
-
-Copyright 2008 Sun Microsystems
-
+This information is Copyright 2008 Sun Microsystems
 1. Introduction
-   1.1. Project/Component Working Name:
-	nbtd: NetBIOS service daemon.
+    1.1. Project/Component Working Name:
+	 Introduce nbtd, NetBIOS service daemon
+    1.2. Name of Document Author/Supplier:
+	 Author:  Keyur Desai
+    1.3  Date of This Document:
+	 15 April, 2008
 
-   1.2. Name of Document Author/Supplier: Keyur Desai
-
-   1.3. Date of This Document: 04/02/2008
-	
-	1.3.1. Date this project was conceived: 02/02/2008
-
-   1.4. Name of Major Document Customer(s)/Consumer(s):
-	1.4.1. The PAC or CPT you expect to review your project:
-		Solaris PAC
-
-	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:
-		Solaris File Systems
-
-   1.5. Email Aliases:
-    	1.5.1. Responsible Manager:  Joseph.Wesley@Sun.COM
-    	1.5.2. Responsible Engineer: Keyur.Desai@sun.com
-    	1.5.3. Marketing Manager:
-	1.5.4. Interest List: 	     cifs-eng@sun.com
-
-
 4. Technical Description:
 
 OVERVIEW
@@ -69,7 +43,30 @@
         a server list from the local master browser and does not request
         or participate in browser elections.
 
+	The nbtd daemon will start with UID/GID of root/sys, in order to
+        create the door file in /var/run. Once the daemon has created the
+	door file, it will run with a UID/GID of daemon/daemon.
 
+	The following authorizations and profiles will be used.
+
+         - solaris.smf.manage.smb
+
+           The existing solaris.smf.manage.smb authorization, will be used
+           to cover activities that change the state of the service, such as 
+           starting, stopping or refreshing of the nbtd(1M) daemon.
+
+         - solaris.smf.value.smb
+
+           The existing solaris.smf.value.smb authorization, will be used to
+           allow the users to change the nbtd daemon configuration property
+           values.
+
+         - The existing SMB Management right profile will be used.
+
+           SMB Management:::Manage SMB service: 
+           auths=solaris.smf.manage.smb,solaris.smf.value.smb:
+           help=RtSMBMngmnt.html	
+
     4.2. Bug/RFE Number(s):
 
 	6687726: NetBIOS service daemon
@@ -90,7 +87,7 @@
 	Consumed Interfaces
 	-------------------
  	    - libsmb.so
- 	    - libaavl.so
+ 	    - libavl.so
  	    - libnsl.so
  	    - libsocket.so
 
@@ -100,9 +97,9 @@
 	1). Changes to smb(4) manpage
 --------------------------------------------------------------------------
 95,111d94
-< 
+<
 <      netbios_scope
-< 
+<
 <          Specifies the NetBIOS scope identifier, which identifies
 <          logical  NetBIOS  networks that are on the same physical
 <          network. When you specify a  NetBIOS  scope  identifier,
@@ -110,16 +107,16 @@
 <          tems that have the same scope defined. The  value  is  a
 <          text string that represents a domain name and is limited
 <          to 16 characters. By default, no value is set.
-< 
+<
 <          Most environments do not require the use of the  NetBIOS
 <          scope feature. If you must use this feature, ensure that
 <          you track the scope identifier assigned to each node.
-< 
-< 
-< 
+<
+<
+<
 133,142d115
 <      pdc
-< 
+<
 <          Specifies the preferred IP address for the  domain  con-
 <          troller.  This property is sometimes used when there are
 <          multiple domain controllers to  indicate  which  one  is
@@ -126,36 +123,41 @@
 <          preferred.  If the specified domain controller responds,
 <          it is chosen even if the other  domain  controllers  are
 <          also available.  By default, no value is set.
-< 
-< 
+<
+<
 160,178d132
 <      wins_exclude
-< 
+<
 <          Specifies a comma-separated list of  IP  addresses  that
 <          are  to  be  excluded from WINS registration when a WINS
 <          server is configured. By default, no value is set.
-< 
-< 
+<
+<
 <      wins_server_1
-< 
+<
 <          Specifies the IP address of the primary WINS server.  By
 <          default, no value is set.
-< 
-< 
+<
+<
 <      wins_server_2
-< 
+<
 <          Specifies the IP address of the secondary  WINS  server.
 <          By default, no value is set.
-< 
-< 
+<
+<
+196c150
+<      butes(5), smf(5)
+---
+>      butes(5), nbtd(1M), nbt(4), smf(5)
+
 --------------------------------------------------------------------------
 
 	2). Changes to smbd(1M) manpage
 --------------------------------------------------------------------------
 71c71
-<      nbtd(1M), nbt(4), attributes(5), smf(5)
+<      attributes(5), smf(5)
 ---
->      attributes(5), smf(5)
+>      attributes(5), nbtd(1M), nbt(4), smf(5)
 --------------------------------------------------------------------------
 
 	3). New nbtd manpage
@@ -342,7 +344,11 @@
 	attributes(5), smf(5), smb(4)
 --------------------------------------------------------------------------
 
-        
+	5). In addition to the above man page changes, Windows
+	    Interoperability documentation will be updated to cover
+	    these changes.
+
+
     4.10. Packaging & Delivery:
 
 	- SUNWsmbsr and SUNWsmbsu.

--Boundary_(ID_dkuSx2m8y8wDEnJ4mXXxug)--

From gww@eng.sun.com Tue Apr 22 23:02:31 2008
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 m3N62VuB019148
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 22 Apr 2008 23:02:31 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3N62ScX021333;
	Wed, 23 Apr 2008 07:02:30 +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 <0JZR00A03KS5BH00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 22 Apr 2008 23:02:29 -0700 (PDT)
Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZR009P4KS5SVB0@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 22 Apr 2008 23:02:29 -0700 (PDT)
Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224])
	by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m3N62SGr047561; Tue, 22 Apr 2008 23:02:28 -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 m3N62EE6022244; Tue,
 22 Apr 2008 23:02:14 -0700 (PDT)
Received: (from gww@localhost)
	by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m3N62EvQ022243; Tue,
 22 Apr 2008 23:02:14 -0700 (PDT)
Date: Tue, 22 Apr 2008 23:02:14 -0700 (PDT)
From: Gary Winiger <gww@eng.sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
To: Keyur.Desai@sun.com, gww@eng.sun.com
Cc: PSARC-ext@sun.com, cifs-eng@sun.com, tim.haley@sun.com
Message-id: <200804230602.m3N62EvQ022243@marduk.eng.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 511

> >>	4). New nbt manpage
> >>
> >>	  The following SMF properties will be now part of nbtd manifest
> >>	  and will be set via sharectl command by authorized users.

> > 	How does this project meet the SMF policy:
> > 	http://opensolaris.org/os/community/arc/policies/SMF-policy/
> > 	particularly with respect to action and value authorizations,
> > 	Rights Profiles, and as we've been discussing method contexts?

> The following authorizations and profiles will be used.

	And the method context is?

Gary..

From Timothy.Haley@sun.com Wed Apr 23 10:13:06 2008
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 m3NHD585012231
	for <psarc-ext@sac.sfbay.Sun.COM>; Wed, 23 Apr 2008 10:13:06 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3NHCwKp019302;
	Thu, 24 Apr 2008 01:13:04 +0800 (SGT)
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 <0JZS00901FTPSD00@nwk-avmta-2.sfbay.sun.com>; Wed,
 23 Apr 2008 10:13:01 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JZS007BRFTPHU30@nwk-avmta-2.sfbay.sun.com>; Wed,
 23 Apr 2008 10:13:01 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m3NHD11i022580; Wed,
 23 Apr 2008 17:13:01 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JZS00N01FP12500@mail-amer.sun.com>
 (original mail from Timothy.Haley@Sun.COM); Wed,
 23 Apr 2008 11:13:00 -0600 (MDT)
Received: from [172.20.25.27] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JZS00NM2FTJ3X60@mail-amer.sun.com>; Wed,
 23 Apr 2008 11:12:55 -0600 (MDT)
Date: Wed, 23 Apr 2008 11:12:55 -0600
From: Tim Haley <Timothy.Haley@sun.com>
Subject: Re: Introduce nbtd [PSARC/2008/260 FastTrack timeout 04/22/2008]
In-reply-to: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
Sender: Timothy.Haley@sun.com
To: PSARC-ext@sun.com
Cc: cifs-eng@sun.com
Message-id: <480F6E17.4060208@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200804151701.m3FH1gVn005623@spidey.central.sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080325)
Status: RO
Content-Length: 59

This case was approved during today's PSARC meeting.

-tim

