From Wyllys.Ingersoll@sun.com Thu Mar 12 11:12:44 2009
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 n2CICiUq015336
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 11:12:44 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2CICirI003696
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.Com>; Thu, 12 Mar 2009 11:12:44 -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 <0KGE00M05NX8NC00@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.Com
 (ORCPT PSARC-ext@Sun.Com); Thu, 12 Mar 2009 12:12:44 -0600 (MDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00IX1NX6YG30@brm-avmta-1.central.sun.com> for
 PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Thu,
 12 Mar 2009 12:12:42 -0600 (MDT)
Received: from jurassic-x4600.sfbay.sun.com (localhost [127.0.0.1])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CICbD9410488
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 11:12:37 -0700 (PDT)
Received: (from wyllys@localhost)	by jurassic-x4600.sfbay.sun.com
 (8.14.3+Sun/8.14.3/Submit) id n2CICbD7410484; Thu,
 12 Mar 2009 11:12:37 -0700 (PDT)
Date: Thu, 12 Mar 2009 11:12:37 -0700 (PDT)
From: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Subject: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
To: PSARC-ext@sun.com
Message-id: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 5872


Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Tor
    1.2. Name of Document Author/Supplier:
	 Author:  Wyllys Ingersoll
    1.3  Date of This Document:
	12 March, 2009
4. Technical Description

Description
-----------
This case proposes to deliver packages containing the Tor project 
sofware.  Tor (https://www.torproject.org) is software lets
one to participate in a network of virtual tunnels that allow people
and groups to improve their privacy and security on the internet.
Tor provides the foundation for a range of applications that allow 
organizations and individuals to share information over public
networks without compromising their privacy.

See this page for more details: https://www.torproject.org/overview.html.en

Notes:
* Currently we are planning to deliver version 0.2.0.34
* Tor uses only TCP streams and can be used by any application with SOCKS
  support.
* Tor does NOT support IPv6 yet (https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IPv6)
* Tor uses OpenSSL for key generation and for encrypting the data
  between relays.  As it works fine with the OpenSSL currently in Solaris, there are
  no plans to change it to use PKCS11 or KMF.

Least Privilege/RBAC
--------------------
This project will deliver new authorizations to /etc/security/auth_attr
for managing the SMF services for starting and stopping the relay server:
	solaris.smf.value.tor:::Change tor value properties::
	solaris.smf.manage.tor:::Manage tor service states::

The following rights profile will be added to /etc/security/prof_attr:
	Tor Administration::::auths=solaris.smf.manage.tor,solaris.smf.value.tor

The following will be added to /etc/security/exec_attr:
	Tor Administration:solaris:cmd:::/usr/bin/tor:uid=daemon,gid=daemon,privs=basic
	Tor Administration:solaris:cmd:::/usr/bin/tor-gencert:uid=daemon,gid=daemon,privs=basic
	Tor Administration:solaris:cmd:::/usr/bin/tor-resolve:uid=daemon,gid=daemon,privs=basic

tor will run as uid/gid "daemon/daemon".  It does not require special privileges,
it does not listen on privileged ports or access privileged data or directories
on the system.

SMF
---
This project will deliver an SMF manifest and script that will allow
the tor relay daemon to be restarted via SMF.  The SMF service will be:
	svc:/application/security/tor:default (Tor Relay Daemon)

Zones
-----
Tor can (and probably should) be run in a local zone with no restrictions
other than the fact that it needs a working network interface.  There
is no technical reason why it would NOT work in a TX zone, though
that configuration has not been tested.

Auditing
--------
Tor does not make access control decisions and is not an administrative
tool that requires BSM auditing.

Configuration
-------------
Tor is an open source project and has an existing configuration system
that relies on a text based configuration file.  An example config file 
will be delivered in /etc/security/torrc.sample.  We do not plan to put 
any of the Tor configuration settings into SMF because we do not want to 
deviate from the upstream provider if at all possible.

The configuration file contains a long list of options for configuring
the ports and interfaces that the relay will listen to as well as other
details such as logging levels, configuring "hidden" services (see 
https://www.torproject.org/hidden-services.html.en for a detailed description
of the hidden service protocol), and limiting the bandwidth that the relay will use.

The sample configuration file must be manually edited by the administrator
and copied to the /etc/security/torrc in order to be used.  This forces
the administrator to know and acknowlege the features that are being enabled
rather than just blindly turning it on.

The upstream Tor community is fairly active and releases updates several times
each year.  Making Solaris-specific changes (such as putting config options in an
SMF profile) will make it harder to keep up with the community and resync
with the current releases.

Packing Modifications
---------------------
SUNWtor		Tor software for userland
SUNWtor-root	Tor software for Root filesystem

Deliverables
------------
/usr/bin/tor			SFW	Uncommitted
/usr/bin/tor-resolve		SFW	Uncommitted
/usr/bin/tor-gencert		SFW	Uncommitted

/etc/security/torrc.sample	SFW	Uncommitted
/usr/share/tor/geoip		SFW	Uncommitted

/usr/man/man1/tor.1		SFW	Uncommitted
/usr/man/man1/tor-resolve.1	SFW	Uncommitted
/usr/man/man1/tor-gencert.1	SFW	Uncommitted

Details
-------
tor is the main daemon process that is started by the "tor" SMF profile.

tor-resolve is a script to connect to a SOCKS proxy that knows about the SOCKS RESOLVE	
    command, hand it a hostname, and return an IP address.

tor-gencert generates certificates and private keys for  use
     by  Tor  directory  authorities running the v3 Tor directory
     protocol, as used by Tor 0.2.0 and later.  If  you  are  not
     running  a  directory  authority, you don't need to use tor-
     gencert. tor-gencert generates 3 files that the user must then copy
     to the "keys" subdirectory (/var/lib/tor/keys) - "authority_identity_key", 
     "authority_signing_key" and "authority_certificate".

geoip is an ASCII based database of IP-to-Country name mappings.  It is not intended
     to be edited by users.


OpenSource
----------
OSR Review: 9954  (approved - Tor version 0.2.0.30)
            11364 (pending expedited review - Tor version 0.2.0.34)

Tor Project:  https://www.torproject.org
Tor Wiki: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ


Release Taxonomy:  Micro/Patch

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From wyllys.ingersoll@sun.com Thu Mar 12 11:18:08 2009
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 n2CII8vL015744
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 11:18:08 -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 n2CIHAWt034795;
	Thu, 12 Mar 2009 12:18:07 -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 <0KGE005AZO65GO00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 11:18:05 -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 <0KGE00477O5S8710@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 11:17:52 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CIHlLI411546
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 11:17:48 -0700 (PDT)
Date: Thu, 12 Mar 2009 14:17:44 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
To: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B951C8.7030109@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 6269


A copy of the torrc.sample file has been put in the case
directory.

-Wyllys


Wyllys Ingersoll wrote:
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 Tor
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Wyllys Ingersoll
>     1.3  Date of This Document:
> 	12 March, 2009
> 4. Technical Description
> 
> Description
> -----------
> This case proposes to deliver packages containing the Tor project 
> sofware.  Tor (https://www.torproject.org) is software lets
> one to participate in a network of virtual tunnels that allow people
> and groups to improve their privacy and security on the internet.
> Tor provides the foundation for a range of applications that allow 
> organizations and individuals to share information over public
> networks without compromising their privacy.
> 
> See this page for more details: https://www.torproject.org/overview.html.en
> 
> Notes:
> * Currently we are planning to deliver version 0.2.0.34
> * Tor uses only TCP streams and can be used by any application with SOCKS
>   support.
> * Tor does NOT support IPv6 yet (https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IPv6)
> * Tor uses OpenSSL for key generation and for encrypting the data
>   between relays.  As it works fine with the OpenSSL currently in Solaris, there are
>   no plans to change it to use PKCS11 or KMF.
> 
> Least Privilege/RBAC
> --------------------
> This project will deliver new authorizations to /etc/security/auth_attr
> for managing the SMF services for starting and stopping the relay server:
> 	solaris.smf.value.tor:::Change tor value properties::
> 	solaris.smf.manage.tor:::Manage tor service states::
> 
> The following rights profile will be added to /etc/security/prof_attr:
> 	Tor Administration::::auths=solaris.smf.manage.tor,solaris.smf.value.tor
> 
> The following will be added to /etc/security/exec_attr:
> 	Tor Administration:solaris:cmd:::/usr/bin/tor:uid=daemon,gid=daemon,privs=basic
> 	Tor Administration:solaris:cmd:::/usr/bin/tor-gencert:uid=daemon,gid=daemon,privs=basic
> 	Tor Administration:solaris:cmd:::/usr/bin/tor-resolve:uid=daemon,gid=daemon,privs=basic
> 
> tor will run as uid/gid "daemon/daemon".  It does not require special privileges,
> it does not listen on privileged ports or access privileged data or directories
> on the system.
> 
> SMF
> ---
> This project will deliver an SMF manifest and script that will allow
> the tor relay daemon to be restarted via SMF.  The SMF service will be:
> 	svc:/application/security/tor:default (Tor Relay Daemon)
> 
> Zones
> -----
> Tor can (and probably should) be run in a local zone with no restrictions
> other than the fact that it needs a working network interface.  There
> is no technical reason why it would NOT work in a TX zone, though
> that configuration has not been tested.
> 
> Auditing
> --------
> Tor does not make access control decisions and is not an administrative
> tool that requires BSM auditing.
> 
> Configuration
> -------------
> Tor is an open source project and has an existing configuration system
> that relies on a text based configuration file.  An example config file 
> will be delivered in /etc/security/torrc.sample.  We do not plan to put 
> any of the Tor configuration settings into SMF because we do not want to 
> deviate from the upstream provider if at all possible.
> 
> The configuration file contains a long list of options for configuring
> the ports and interfaces that the relay will listen to as well as other
> details such as logging levels, configuring "hidden" services (see 
> https://www.torproject.org/hidden-services.html.en for a detailed description
> of the hidden service protocol), and limiting the bandwidth that the relay will use.
> 
> The sample configuration file must be manually edited by the administrator
> and copied to the /etc/security/torrc in order to be used.  This forces
> the administrator to know and acknowlege the features that are being enabled
> rather than just blindly turning it on.
> 
> The upstream Tor community is fairly active and releases updates several times
> each year.  Making Solaris-specific changes (such as putting config options in an
> SMF profile) will make it harder to keep up with the community and resync
> with the current releases.
> 
> Packing Modifications
> ---------------------
> SUNWtor		Tor software for userland
> SUNWtor-root	Tor software for Root filesystem
> 
> Deliverables
> ------------
> /usr/bin/tor			SFW	Uncommitted
> /usr/bin/tor-resolve		SFW	Uncommitted
> /usr/bin/tor-gencert		SFW	Uncommitted
> 
> /etc/security/torrc.sample	SFW	Uncommitted
> /usr/share/tor/geoip		SFW	Uncommitted
> 
> /usr/man/man1/tor.1		SFW	Uncommitted
> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
> 
> Details
> -------
> tor is the main daemon process that is started by the "tor" SMF profile.
> 
> tor-resolve is a script to connect to a SOCKS proxy that knows about the SOCKS RESOLVE	
>     command, hand it a hostname, and return an IP address.
> 
> tor-gencert generates certificates and private keys for  use
>      by  Tor  directory  authorities running the v3 Tor directory
>      protocol, as used by Tor 0.2.0 and later.  If  you  are  not
>      running  a  directory  authority, you don't need to use tor-
>      gencert. tor-gencert generates 3 files that the user must then copy
>      to the "keys" subdirectory (/var/lib/tor/keys) - "authority_identity_key", 
>      "authority_signing_key" and "authority_certificate".
> 
> geoip is an ASCII based database of IP-to-Country name mappings.  It is not intended
>      to be edited by users.
> 
> 
> OpenSource
> ----------
> OSR Review: 9954  (approved - Tor version 0.2.0.30)
>             11364 (pending expedited review - Tor version 0.2.0.34)
> 
> Tor Project:  https://www.torproject.org
> Tor Wiki: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ
> 
> 
> Release Taxonomy:  Micro/Patch
> 
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open


From carlsonj@phorcys.east.sun.com Thu Mar 12 11:25:01 2009
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 n2CIP1uM016325
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 11:25:01 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2CIOr1Q026531;
	Thu, 12 Mar 2009 18:24:59 GMT
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 <0KGE00G41OHL2M00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 11:24:57 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00E0AOHJO340@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 11:24:56 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2CIOrme028004; Thu,
 12 Mar 2009 14:24:53 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2CIOrRA028001; Thu,
 12 Mar 2009 14:24:53 -0400 (EDT)
Date: Thu, 12 Mar 2009 14:24:53 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <18873.21365.766925.41764@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
Status: RO
Content-Length: 718

Wyllys Ingersoll writes:
> This case proposes to deliver packages containing the Tor project 
> sofware.  Tor (https://www.torproject.org) is software lets
> one to participate in a network of virtual tunnels that allow people
> and groups to improve their privacy and security on the internet.
> Tor provides the foundation for a range of applications that allow 
> organizations and individuals to share information over public
> networks without compromising their privacy.

Very nifty.  +1

-- 
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 Scott.Rotondo@sun.com Thu Mar 12 11:38:01 2009
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 n2CIc07b016968
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 11:38:01 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2CIbvTG006341
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 12 Mar 2009 18:38:00 GMT
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 <0KGE00G07P39SU00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 11:37:57 -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 <0KGE00ENQP38NW40@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu,
 12 Mar 2009 11:37:56 -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 n2CIbtxi018927	for
 <PSARC-ext@sun.com>; Thu, 12 Mar 2009 18:37:55 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGE00900OFBY400@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 12:37:55 -0600 (MDT)
Received: from [129.146.108.62] ([unknown] [129.146.108.62])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGE0055PP2QE090@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 12:37:38 -0600 (MDT)
Date: Thu, 12 Mar 2009 11:37:38 -0700
From: Scott Rotondo <Scott.Rotondo@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
Sender: Scott.Rotondo@sun.com
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B95672.6020005@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Status: RO
Content-Length: 686

> Deliverables
> ------------
> /usr/bin/tor			SFW	Uncommitted
> /usr/bin/tor-resolve		SFW	Uncommitted
> /usr/bin/tor-gencert		SFW	Uncommitted
> 
> /etc/security/torrc.sample	SFW	Uncommitted
> /usr/share/tor/geoip		SFW	Uncommitted
> 
> /usr/man/man1/tor.1		SFW	Uncommitted
> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
> 

/etc/security doesn't seem like an appropriate place for Tor's 
configuration file. Why not put it in /etc/privoxy as it would be on 
other Linux/UNIX systems?

	Scott

-- 
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)

From wyllys.ingersoll@sun.com Thu Mar 12 11:51:25 2009
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 n2CIpPGv017684
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 11:51:25 -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 n2CIpGLl023471;
	Thu, 12 Mar 2009 11:51: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 <0KGE009NTPPOSH00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 11:51: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 <0KGE004L6PP98B40@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 11:51:09 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CIp3te419115
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 11:51:04 -0700 (PDT)
Date: Thu, 12 Mar 2009 14:51:00 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B95672.6020005@sun.com>
To: Scott Rotondo <Scott.Rotondo@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B95994.4090900@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 816

Scott Rotondo wrote:
>> Deliverables
>> ------------
>> /usr/bin/tor            SFW    Uncommitted
>> /usr/bin/tor-resolve        SFW    Uncommitted
>> /usr/bin/tor-gencert        SFW    Uncommitted
>>
>> /etc/security/torrc.sample    SFW    Uncommitted
>> /usr/share/tor/geoip        SFW    Uncommitted
>>
>> /usr/man/man1/tor.1        SFW    Uncommitted
>> /usr/man/man1/tor-resolve.1    SFW    Uncommitted
>> /usr/man/man1/tor-gencert.1    SFW    Uncommitted
>>
> 
> /etc/security doesn't seem like an appropriate place for Tor's 
> configuration file. Why not put it in /etc/privoxy as it would be on 
> other Linux/UNIX systems?
> 
>     Scott
> 

On Linux systems it is in /usr/local/etc/tor - that's the default install
location.
  
I put it in /etc/security since it is a security-related config file.

-w



From Scott.Rotondo@sun.com Thu Mar 12 12:00:17 2009
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 n2CJ0HMT020368
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:00:17 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2CJ0FRN000895
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 12 Mar 2009 12:00:17 -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 <0KGE00H2HQ4GU600@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 12:00:16 -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 <0KGE00ENKQ3OO170@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu,
 12 Mar 2009 11:59:48 -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 n2CIxmFI001233	for
 <PSARC-ext@sun.com>; Thu, 12 Mar 2009 18:59:48 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGE00900OFBY400@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 12:59:48 -0600 (MDT)
Received: from [129.146.108.62] ([unknown] [129.146.108.62])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGE0055TQ3NO640@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 12:59:47 -0600 (MDT)
Date: Thu, 12 Mar 2009 11:59:47 -0700
From: Scott Rotondo <Scott.Rotondo@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B95994.4090900@sun.com>
Sender: Scott.Rotondo@sun.com
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B95BA3.1070101@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Status: RO
Content-Length: 921

Wyllys Ingersoll wrote:

>> /etc/security doesn't seem like an appropriate place for Tor's 
>> configuration file. Why not put it in /etc/privoxy as it would be on 
>> other Linux/UNIX systems?
>>
>>     Scott
>>
> 
> On Linux systems it is in /usr/local/etc/tor - that's the default install
> location.

Maybe /etc/tor is a good choice for Solaris.

>  
> I put it in /etc/security since it is a security-related config file.
> 

It really isn't. /etc/security contains configuration data for 
system-wide OS security subsystems like auditing, RBAC, and Trusted 
Extensions. Lots of other services have their own security-relevant 
configuration settings, but they are kept in their own service 
configuration files and directories, usually under /etc/<service>.

	Scott

-- 
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)

From Wyllys.Ingersoll@sun.com Thu Mar 12 12:03:20 2009
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 n2CJ3J2V014921
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:03:20 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2CJ3GFn027540;
	Thu, 12 Mar 2009 19:03:17 GMT
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 <0KGE00HH7Q9FTB00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:03:15 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00E9NQ9EO180@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:03:14 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CJ39hO422539
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 12:03:10 -0700 (PDT)
Date: Thu, 12 Mar 2009 15:03:06 -0400
From: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B95BA3.1070101@sun.com>
To: Scott Rotondo <Scott.Rotondo@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B95C6A.6080801@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 759


> 
> Maybe /etc/tor is a good choice for Solaris.

It could be, I didn't see the need to create another new subdirectory just
to hold 1 file.


>> I put it in /etc/security since it is a security-related config file.
>>
> 
> It really isn't. /etc/security contains configuration data for 
> system-wide OS security subsystems like auditing, RBAC, and Trusted 
> Extensions. Lots of other services have their own security-relevant 
> configuration settings, but they are kept in their own service 
> configuration files and directories, usually under /etc/<service>.
> 
>     Scott

Is there a stated rule-of-thumb for using /etc/security?  I'm not
objecting to moving the tor config file, I'm just looking for
some sort of precedent or consensus.

-Wyllys



From carlsonj@phorcys.east.sun.com Thu Mar 12 12:22:09 2009
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 n2CJM8XM011723
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:22:08 -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 n2CJM3f8009708;
	Fri, 13 Mar 2009 03:22: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 <0KGE00I09R4QTU00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:22:02 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00E5LR4OO1A0@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:22:01 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2CJLwkM001897; Thu,
 12 Mar 2009 15:21:58 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2CJLwrf001894; Thu,
 12 Mar 2009 15:21:58 -0400 (EDT)
Date: Thu, 12 Mar 2009 15:21:58 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B95C6A.6080801@sun.com>
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <18873.24790.744078.150078@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
Status: RO
Content-Length: 1099

Wyllys Ingersoll writes:
> > It really isn't. /etc/security contains configuration data for 
> > system-wide OS security subsystems like auditing, RBAC, and Trusted 
> > Extensions. Lots of other services have their own security-relevant 
> > configuration settings, but they are kept in their own service 
> > configuration files and directories, usually under /etc/<service>.
> > 
> >     Scott
> 
> Is there a stated rule-of-thumb for using /etc/security?  I'm not
> objecting to moving the tor config file, I'm just looking for
> some sort of precedent or consensus.

The only one I know of is in filesystem(5):

     /etc/security
         Basic Security Module (BSM) configuration files.

The directory seems to predate the ARC.

I agree with Scott that outside of /etc/security is a better idea.
The file configures this service; it doesn't configure system
security.

-- 
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 wyllys.ingersoll@sun.com Thu Mar 12 12:25:20 2009
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 n2CJPJxI011896
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:25:20 -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 n2CJPBGh030124;
	Thu, 12 Mar 2009 13:25:18 -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 <0KGE00F5TRA51W00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 12:25:17 -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 <0KGE004FQRA08960@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 12:25:12 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CJP7Xn426734
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 12:25:08 -0700 (PDT)
Date: Thu, 12 Mar 2009 15:25:04 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18873.24790.744078.150078@gargle.gargle.HOWL>
To: James Carlson <james.d.carlson@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <49B96190.9020506@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 1138

James Carlson wrote:
> Wyllys Ingersoll writes:
>>> It really isn't. /etc/security contains configuration data for 
>>> system-wide OS security subsystems like auditing, RBAC, and Trusted 
>>> Extensions. Lots of other services have their own security-relevant 
>>> configuration settings, but they are kept in their own service 
>>> configuration files and directories, usually under /etc/<service>.
>>>
>>>     Scott
>> Is there a stated rule-of-thumb for using /etc/security?  I'm not
>> objecting to moving the tor config file, I'm just looking for
>> some sort of precedent or consensus.
> 
> The only one I know of is in filesystem(5):
> 
>      /etc/security
>          Basic Security Module (BSM) configuration files.
> 
> The directory seems to predate the ARC.
> 
> I agree with Scott that outside of /etc/security is a better idea.
> The file configures this service; it doesn't configure system
> security.
> 


OK, I will move it to /etc/tor

filesystem(5) should probably be updated at some point to reflect its current, broader,
uses - system-wide security settings for crypto, BSM, KMF, PAM, RBAC, TPM, and TX.

-Wyllys



From carlsonj@phorcys.east.sun.com Thu Mar 12 12:27:38 2009
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 n2CJRcWL012092
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:27:38 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2CJRXGg018327;
	Thu, 12 Mar 2009 19:27:34 GMT
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 <0KGE00J2BRDX4P00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:27:33 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00ERYRDUNUA0@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:27:31 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2CJRSHW001992; Thu,
 12 Mar 2009 15:27:28 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2CJRS9J001989; Thu,
 12 Mar 2009 15:27:28 -0400 (EDT)
Date: Thu, 12 Mar 2009 15:27:28 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B96190.9020506@sun.com>
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <18873.25120.912641.6768@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL> <49B96190.9020506@sun.com>
Status: RO
Content-Length: 589

Wyllys Ingersoll writes:
> OK, I will move it to /etc/tor

OK.  For what it's worth, since it's just a single file, you might
want to consider "/etc/torrc".

> filesystem(5) should probably be updated at some point to reflect its current, broader,
> uses - system-wide security settings for crypto, BSM, KMF, PAM, RBAC, TPM, and TX.

Yep.  Feel free to file a bug.

-- 
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 carlsonj@phorcys.east.sun.com Thu Mar 12 12:29:25 2009
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 n2CJTOK9012188
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:29:25 -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 n2CJTJ7s014765;
	Fri, 13 Mar 2009 03:29:21 +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 <0KGE0060DRGVDQ00@brm-avmta-1.central.sun.com>; Thu,
 12 Mar 2009 13:29:19 -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 <0KGE00IKDRGUYAA0@brm-avmta-1.central.sun.com>; Thu,
 12 Mar 2009 13:29:18 -0600 (MDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2CJTGv4002010; Thu,
 12 Mar 2009 15:29:16 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2CJTGeA002007; Thu,
 12 Mar 2009 15:29:16 -0400 (EDT)
Date: Thu, 12 Mar 2009 15:29:14 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18873.25120.912641.6768@gargle.gargle.HOWL>
To: Wyllys Ingersoll <wyllys.ingersoll@sun.com>,
        Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <18873.25226.523484.540210@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL> <49B96190.9020506@sun.com>
 <18873.25120.912641.6768@gargle.gargle.HOWL>
Status: RO
Content-Length: 606

James Carlson writes:
> Wyllys Ingersoll writes:
> > OK, I will move it to /etc/tor
> 
> OK.  For what it's worth, since it's just a single file, you might
> want to consider "/etc/torrc".

I might have misunderstood what you were saying (because I think
/etc/tor/ as a directory was proposed at one point).  If /etc/tor is
just a plain file, then that sounds like the best answer.

-- 
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 wyllys.ingersoll@sun.com Thu Mar 12 12:32:37 2009
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 n2CJWbM9012287
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:32:37 -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 n2CJWUCA022047;
	Thu, 12 Mar 2009 19:32:34 GMT
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 <0KGE0060PRM7OZ00@brm-avmta-1.central.sun.com>; Thu,
 12 Mar 2009 13:32:31 -0600 (MDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00IMCRLZYJB0@brm-avmta-1.central.sun.com>; Thu,
 12 Mar 2009 13:32:23 -0600 (MDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CJWIEl431421
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 12:32:18 -0700 (PDT)
Date: Thu, 12 Mar 2009 15:32:15 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18873.25226.523484.540210@gargle.gargle.HOWL>
To: James Carlson <james.d.carlson@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <49B9633F.50800@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL> <49B96190.9020506@sun.com>
 <18873.25120.912641.6768@gargle.gargle.HOWL>
 <18873.25226.523484.540210@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 581

James Carlson wrote:
> James Carlson writes:
>> Wyllys Ingersoll writes:
>>> OK, I will move it to /etc/tor
>> OK.  For what it's worth, since it's just a single file, you might
>> want to consider "/etc/torrc".
> 
> I might have misunderstood what you were saying (because I think
> /etc/tor/ as a directory was proposed at one point).  If /etc/tor is
> just a plain file, then that sounds like the best answer.
> 

I meant to put the config file (torrc) into it's own
subdir (/etc/tor/).  It is only 1 file though, so just having 
it as /etc/torrc.sample is fine with me, too.



From carlsonj@phorcys.east.sun.com Thu Mar 12 12:37:47 2009
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 n2CJbloq012523
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 12:37:47 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2CJbhOJ041108;
	Thu, 12 Mar 2009 13:37:46 -0600 (MDT)
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 <0KGE00J1ZRUXMA00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:37:45 -0700 (PDT)
Received: from phorcys.east.sun.com ([129.148.174.143])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE00EGGRUWO3C0@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 12:37:45 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2CJbgCv002956; Thu,
 12 Mar 2009 15:37:42 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2CJbgi5002953; Thu,
 12 Mar 2009 15:37:42 -0400 (EDT)
Date: Thu, 12 Mar 2009 15:37:42 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B9633F.50800@sun.com>
To: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <18873.25734.712638.962031@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL> <49B96190.9020506@sun.com>
 <18873.25120.912641.6768@gargle.gargle.HOWL>
 <18873.25226.523484.540210@gargle.gargle.HOWL> <49B9633F.50800@sun.com>
Status: RO
Content-Length: 780

Wyllys Ingersoll writes:
> James Carlson wrote:
> > I might have misunderstood what you were saying (because I think
> > /etc/tor/ as a directory was proposed at one point).  If /etc/tor is
> > just a plain file, then that sounds like the best answer.
> > 
> 
> I meant to put the config file (torrc) into it's own
> subdir (/etc/tor/).  It is only 1 file though, so just having 
> it as /etc/torrc.sample is fine with me, too.

/etc/torrc.sample isn't the interface here, though.  It's just an
example.  Where does the actual, live configuration file go?

-- 
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 Wyllys.Ingersoll@sun.com Thu Mar 12 13:02:56 2009
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 n2CK2unI014229
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 13:02:56 -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 n2CK2ZqZ016286;
	Thu, 12 Mar 2009 13:02: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 <0KGE00I7QT0UXF10@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 13:02:54 -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 <0KGE004I8T087XE0@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 13:02:32 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CK2RPG438510
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 13:02:27 -0700 (PDT)
Date: Thu, 12 Mar 2009 16:02:24 -0400
From: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18873.25734.712638.962031@gargle.gargle.HOWL>
To: James Carlson <james.d.carlson@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <49B96A50.5030507@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B95672.6020005@sun.com> <49B95994.4090900@sun.com>
 <49B95BA3.1070101@sun.com> <49B95C6A.6080801@sun.com>
 <18873.24790.744078.150078@gargle.gargle.HOWL> <49B96190.9020506@sun.com>
 <18873.25120.912641.6768@gargle.gargle.HOWL>
 <18873.25226.523484.540210@gargle.gargle.HOWL> <49B9633F.50800@sun.com>
 <18873.25734.712638.962031@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 655

James Carlson wrote:
> Wyllys Ingersoll writes:
>> James Carlson wrote:
>>> I might have misunderstood what you were saying (because I think
>>> /etc/tor/ as a directory was proposed at one point).  If /etc/tor is
>>> just a plain file, then that sounds like the best answer.
>>>
>> I meant to put the config file (torrc) into it's own
>> subdir (/etc/tor/).  It is only 1 file though, so just having 
>> it as /etc/torrc.sample is fine with me, too.
> 
> /etc/torrc.sample isn't the interface here, though.  It's just an
> example.  Where does the actual, live configuration file go?
> 

In the same directory - so, the config file would be /etc/torrc



From Truong.Q.Nguyen@sun.com Thu Mar 12 14:43:33 2009
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 n2CLhWDa022196
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 14:43:33 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2CLhUvE008955
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 12 Mar 2009 21:43:32 GMT
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 <0KGE0028VXOJ9D00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@Sun.Com); Thu, 12 Mar 2009 14:43:31 -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 <0KGE00K0ZXOJMQD0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu,
 12 Mar 2009 14:43:31 -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 n2CLhVBM009138	for
 <PSARC-ext@Sun.Com>; Thu, 12 Mar 2009 21:43:31 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGE00H00TI4M000@mail-amer.sun.com> for PSARC-ext@Sun.Com
 (ORCPT PSARC-ext@Sun.Com); Thu, 12 Mar 2009 15:43:31 -0600 (MDT)
Received: from [129.146.226.122] ([unknown] [129.146.226.122])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGE00C22XO176D0@mail-amer.sun.com> for PSARC-ext@Sun.Com
 (ORCPT PSARC-ext@Sun.Com); Thu, 12 Mar 2009 15:43:14 -0600 (MDT)
Date: Thu, 12 Mar 2009 14:43:13 -0700
From: Tony Nguyen <Truong.Q.Nguyen@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
Sender: Truong.Q.Nguyen@sun.com
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B981F1.5000605@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081203)
Status: RO
Content-Length: 765

> SMF
> ---
> This project will deliver an SMF manifest and script that will allow
> the tor relay daemon to be restarted via SMF.  The SMF service will be:
> 	svc:/application/security/tor:default (Tor Relay Daemon)
> 

Wyllys,

With the integration of 2008/580 Solaris host-based firewall, the new 
tor service, with some small changes, can provide fine-grained access 
control to its service and be consistent with existing services. Since 
tor defines listening ports in a configuration file, similar to ssh, you 
can see network/ssh for example. I'm happy to work with you offline to 
figure this out.

Services with no explicit firewall configuration, by default, will 
inherit the global firewall policy which may not always be the desired 
behavior.

-tony

From wyllys.ingersoll@sun.com Thu Mar 12 15:05:32 2009
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 n2CM5VWt024307
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 15:05:32 -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 n2CM5AXc027801;
	Fri, 13 Mar 2009 06:05:29 +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 <0KGE00E9DYP2RF00@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 15:05:26 -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 <0KGE006JPYOFL860@nwk-avmta-1.sfbay.Sun.COM>; Thu,
 12 Mar 2009 15:05:03 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CM4w0U515866
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 15:04:59 -0700 (PDT)
Date: Thu, 12 Mar 2009 18:04:55 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B981F1.5000605@sun.com>
To: Tony Nguyen <Truong.Q.Nguyen@sun.com>, PSARC-ext@sun.com
Message-id: <49B98707.8080704@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B981F1.5000605@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 2179

Tony Nguyen wrote:
> 
> Wyllys,
> 
> With the integration of 2008/580 Solaris host-based firewall, the new 
> tor service, with some small changes, can provide fine-grained access 
> control to its service and be consistent with existing services. Since 
> tor defines listening ports in a configuration file, similar to ssh, you 
> can see network/ssh for example. I'm happy to work with you offline to 
> figure this out.

Tor listens on either 1 or 2 ports, 9001/tcp + (optionally) a SOCKS port 
(9050/tcp by default).  In relay-mode, it just then routes the data onto 
the next Tor node somewhere out on the internet.

It can be allowed to be an "exit" point, which means
that the Tor relay will route the connection to its proper endpoint
(website, IRC server, etc) instead of another Tor node, but the 
"exit policy" is defined in the torrc config file.

The exit policy statement in the torrc config file determines
the services that Tor may connect to.  If the host firewall blocks
the ports before they get to Tor, then the users are simply told
that those destinations are down.  This is from the torrc.sample
file regarding exit policy configuration:

...
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
...


Are you suggesting just adding some firewall_context properties to the
smf profile similar to ssh?  That sounds reasonable if you think it makes
sense here.   I would prefer to NOT modify any of the actual Tor code
as that makes it harder to resync later.


> Services with no explicit firewall configuration, by default, will 
> inherit the global firewall policy which may not always be the desired 
> behavior.

If the global firewall policy is to block ports that Tor would either be listening
to or talking to, then Tor would just report that to the remote user as an
error or an unavailable service.

-Wyllys



From Truong.Q.Nguyen@sun.com Thu Mar 12 15:31:42 2009
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 n2CMVfjU027618
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 15:31:42 -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 n2CMVduS014323
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 13 Mar 2009 06:31:41 +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 <0KGE00J1LZWR8100@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 15:31:39 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGE006Q4ZWJL2A0@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu,
 12 Mar 2009 15:31:32 -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 n2CMVV2f000661	for
 <PSARC-ext@sun.com>; Thu, 12 Mar 2009 22:31:31 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGE00300YX98900@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 16:31:31 -0600 (MDT)
Received: from [129.146.226.122] ([unknown] [129.146.226.122])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGE00KH1ZWHWP90@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Thu, 12 Mar 2009 16:31:29 -0600 (MDT)
Date: Thu, 12 Mar 2009 15:31:29 -0700
From: Tony Nguyen <Truong.Q.Nguyen@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B98707.8080704@sun.com>
Sender: Truong.Q.Nguyen@sun.com
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B98D41.8080306@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B981F1.5000605@sun.com> <49B98707.8080704@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081203)
Status: RO
Content-Length: 2789

Wyllys Ingersoll wrote:
> Tony Nguyen wrote:
>>
>> Wyllys,
>>
>> With the integration of 2008/580 Solaris host-based firewall, the new 
>> tor service, with some small changes, can provide fine-grained access 
>> control to its service and be consistent with existing services. Since 
>> tor defines listening ports in a configuration file, similar to ssh, 
>> you can see network/ssh for example. I'm happy to work with you 
>> offline to figure this out.
> 
> Tor listens on either 1 or 2 ports, 9001/tcp + (optionally) a SOCKS port 
> (9050/tcp by default).  In relay-mode, it just then routes the data onto 
> the next Tor node somewhere out on the internet.
> 
> It can be allowed to be an "exit" point, which means
> that the Tor relay will route the connection to its proper endpoint
> (website, IRC server, etc) instead of another Tor node, but the "exit 
> policy" is defined in the torrc config file.
> 
> The exit policy statement in the torrc config file determines
> the services that Tor may connect to.  If the host firewall blocks
> the ports before they get to Tor, then the users are simply told
> that those destinations are down.  This is from the torrc.sample
> file regarding exit policy configuration:
> 
> ...
> ## If certain IPs and ports are blocked externally, e.g. by your firewall,
> ## you should update your exit policy to reflect this -- otherwise Tor
> ## users will be told that those destinations are down.
> ##
> #ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
> #ExitPolicy accept *:119 # accept nntp as well as default exit policy
> #ExitPolicy reject *:* # no exits allowed
> ...
> 
> 
> Are you suggesting just adding some firewall_context properties to the
> smf profile similar to ssh?  That sounds reasonable if you think it makes
> sense here.   I would prefer to NOT modify any of the actual Tor code
> as that makes it harder to resync later.
> 

Agree, I'm not suggesting changes to Tor code.

Yes, similar to ssh security/tor would need to:

- define firewall_context and firewall_config property groups
- add some code in its method script to get the port numbers from the 
config file and ask the framework to apply configured policy to those 
ports (see create_ipf_rule() in /lib/svc/method/sshd)

> 
>> Services with no explicit firewall configuration, by default, will 
>> inherit the global firewall policy which may not always be the desired 
>> behavior.
> 
> If the global firewall policy is to block ports that Tor would either be 
> listening
> to or talking to, then Tor would just report that to the remote user as an
> error or an unavailable service.

Correct, that's a reasonable behavior. On the other hand, there are 
cases where services would want policy different from the default policy.

-tony

From wyllys.ingersoll@sun.com Thu Mar 12 15:35:48 2009
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 n2CMZlEs028035
	for <psarc-ext@sac.sfbay.sun.com>; Thu, 12 Mar 2009 15:35:48 -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 n2CMZi7m017290;
	Fri, 13 Mar 2009 06:35:45 +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 <0KGF0042903JPU00@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 15:35:43 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGF003WY03DAF20@nwk-avmta-2.sfbay.sun.com>; Thu,
 12 Mar 2009 15:35:37 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2CMZWfI541229
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu,
 12 Mar 2009 15:35:33 -0700 (PDT)
Date: Thu, 12 Mar 2009 18:35:30 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49B98D41.8080306@sun.com>
To: Tony Nguyen <Truong.Q.Nguyen@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49B98E32.3000808@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <49B981F1.5000605@sun.com> <49B98707.8080704@sun.com>
 <49B98D41.8080306@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 1046


> 
> Agree, I'm not suggesting changes to Tor code.
> 
> Yes, similar to ssh security/tor would need to:
> 
> - define firewall_context and firewall_config property groups
> - add some code in its method script to get the port numbers from the 
> config file and ask the framework to apply configured policy to those 
> ports (see create_ipf_rule() in /lib/svc/method/sshd)

Yes, I took a look at that a little while ago, it should be no problem
to do something similar for Tor, at least for the listening ports.


>>> Services with no explicit firewall configuration, by default, will 
>>> inherit the global firewall policy which may not always be the 
>>> desired behavior.
>>
>> If the global firewall policy is to block ports that Tor would either 
>> be listening
>> to or talking to, then Tor would just report that to the remote user 
>> as an
>> error or an unavailable service.
> 
> Correct, that's a reasonable behavior. On the other hand, there are 
> cases where services would want policy different from the default policy.

OK.



From ro@techfak.uni-bielefeld.de Fri Mar 13 05:55:00 2009
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 n2DCswa5023613
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 05:55:00 -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 n2DCsjFr026674;
	Fri, 13 Mar 2009 12:54:56 GMT
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 <0KGG00F1L3VJTN00@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 06:54:55 -0600 (MDT)
Received: from sca-ea-mail-3.sun.com ([192.18.43.21])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG002JM3VINE90@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 06:54:54 -0600 (MDT)
Received: from relay12i.sun.com
 (ip122.net129179-4.block1.us.syntegra.com [129.179.4.122])
	by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2DCeIN7020070;
 Fri, 13 Mar 2009 12:54:54 +0000 (GMT)
Received: from mmp11es.mmp.us.syntegra.com ([160.41.208.11] [160.41.208.11])
 by relay12i.sun.com with ESMTP id BT-MMP-1971424; Fri,
 13 Mar 2009 12:54:21 +0000 (Z)
Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124])
 by mmp11es.mmp.us.syntegra.com with ESMTP id BT-MMP-38602332; Fri,
 13 Mar 2009 12:54:20 +0000 (Z)
Received: from smarthost.TechFak.Uni-Bielefeld.DE
 ([129.70.137.17] [129.70.137.17]) by relay1i.sun.com with ESMTP id
 BT-MMP-25457729; Fri, 13 Mar 2009 12:54:20 +0000 (Z)
Received: from manam.TechFak.Uni-Bielefeld.DE
 (manam.TechFak.Uni-Bielefeld.DE [129.70.137.47])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by smarthost.TechFak.Uni-Bielefeld.DE
 (Postfix) with ESMTP id F14BF4832C; Fri, 13 Mar 2009 13:54:19 +0100 (CET)
Date: Fri, 13 Mar 2009 13:54:19 +0100
From: Rainer Orth <ro@techfak.uni-bielefeld.de>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: Wyllys Ingersoll's message of
 "Thu, 12 Mar 2009 11:12:37 -0700 (PDT)"
Sender: ro@techfak.uni-bielefeld.de
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE>
MIME-version: 1.0
X-Mailer: Gnus v5.6.44/Emacs 19.34
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
X-Brightmail-Tracker: AAAAAA==
X-Antispam: No, score=0.0/5.0, scanned in 0.296sec at (localhost [127.0.0.1])
	by smf-spamd v1.3.1 - http://smfs.sf.net/
Lines: 24
References: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
Status: RO
Content-Length: 790

Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> writes:

> Deliverables
> ------------
> /usr/bin/tor			SFW	Uncommitted
> /usr/bin/tor-resolve		SFW	Uncommitted
> /usr/bin/tor-gencert		SFW	Uncommitted

Does this really belong into /usr/bin?  Is a regular user supposed to
invoke tor or any of the two other commands?  I suppose this is rather for
/usr/sbin (or maybe even /usr/lib or /usr/lib/tor) if the tor binary is for
a daemon controlled by SMF.

> /usr/man/man1/tor.1		SFW	Uncommitted
> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
> /usr/man/man1/tor-gencert.1	SFW	Uncommitted

Similar questions here: shouldn't this be section 1M instead?

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

From wyllys.ingersoll@sun.com Fri Mar 13 06:02:12 2009
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 n2DD2Brx023810
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 06:02:11 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2DD245T001468
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 13 Mar 2009 13:02:10 GMT
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 <0KGG0081347LAJ00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Fri, 13 Mar 2009 06:02:09 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG00KIS47LM7C0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri,
 13 Mar 2009 06:02:09 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2DD2852160123
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri,
 13 Mar 2009 06:02:08 -0700 (PDT)
Date: Fri, 13 Mar 2009 09:02:00 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE>
To: Rainer Orth <ro@techfak.uni-bielefeld.de>
Cc: PSARC-ext@sun.com
Message-id: <49BA5948.5040404@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 1065

Rainer Orth wrote:
> Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> writes:
> 
>> Deliverables
>> ------------
>> /usr/bin/tor			SFW	Uncommitted
>> /usr/bin/tor-resolve		SFW	Uncommitted
>> /usr/bin/tor-gencert		SFW	Uncommitted
> 
> Does this really belong into /usr/bin?  Is a regular user supposed to
> invoke tor or any of the two other commands?  I suppose this is rather for
> /usr/sbin (or maybe even /usr/lib or /usr/lib/tor) if the tor binary is for
> a daemon controlled by SMF.

'tor' should probably move to /usr/lib/ since it is a daemon process started by SMF,
I will update the spec and build environment.

tor-resovle and tor-gencert are commands that a user would use, so they probably
belong in /usr/bin


>> /usr/man/man1/tor.1		SFW	Uncommitted
>> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
>> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
> 
> Similar questions here: shouldn't this be section 1M instead?

.1 is where they live on a Linux system, but if there is consensus that it
should be 1M on Solaris, I have no issue with changing it.

-Wyllys


From carlsonj@phorcys.east.sun.com Fri Mar 13 08:04:53 2009
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 n2DF4qfE001851
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 08:04:53 -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 n2DF4bwx024300;
	Fri, 13 Mar 2009 23:04:50 +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 <0KGG00A0L9W09P00@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 13 Mar 2009 08:04:48 -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 <0KGG0022U9VZ3S50@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 13 Mar 2009 08:04:47 -0700 (PDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2DF4iPA010943; Fri,
 13 Mar 2009 11:04:44 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2DF4hnn010940; Fri,
 13 Mar 2009 11:04:43 -0400 (EDT)
Date: Fri, 13 Mar 2009 11:04:43 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BA5948.5040404@sun.com>
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: Rainer Orth <ro@techfak.uni-bielefeld.de>, PSARC-ext@sun.com
Message-id: <18874.30219.616984.346416@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE> <49BA5948.5040404@sun.com>
Status: RO
Content-Length: 824

Wyllys Ingersoll writes:
> Rainer Orth wrote:
> >> /usr/man/man1/tor.1		SFW	Uncommitted
> >> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
> >> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
> > 
> > Similar questions here: shouldn't this be section 1M instead?
> 
> .1 is where they live on a Linux system, but if there is consensus that it
> should be 1M on Solaris, I have no issue with changing it.

As long as they're intended for ordinary users, section 1 is the right
place for them.  (It's hard to tell, though, whether they're really
meant as administrative tools or as tools for general users.)

-- 
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 ro@techfak.uni-bielefeld.de Fri Mar 13 08:20:50 2009
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 n2DFKo0O019610
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 08:20:50 -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 n2DFKl4s026854;
	Fri, 13 Mar 2009 08:20:50 -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 <0KGG00609AMPAQ00@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 09:20:49 -0600 (MDT)
Received: from sca-ea-mail-3.sun.com ([192.18.43.21])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG0011NAMNXP50@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 09:20:47 -0600 (MDT)
Received: from relay44i.sun.com ([192.5.209.118])
	by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2DEwYxq002809;
 Fri, 13 Mar 2009 15:20:46 +0000 (GMT)
Received: from mms49es.mms.us.syntegra.com ([160.41.221.232] [160.41.221.232])
 by relay44i.sun.com with ESMTP id BT-MMP-1983485; Fri,
 13 Mar 2009 15:20:46 +0000 (Z)
Received: from relay43i.sun.com (relay43i.sun.com [192.5.209.74])
 by mms49es.mms.us.syntegra.com with ESMTP id BT-MMP-26183782; Fri,
 13 Mar 2009 15:20:45 +0000 (Z)
Received: from smarthost.TechFak.Uni-Bielefeld.DE
 ([129.70.137.17] [129.70.137.17]) by relay4i.sun.com with ESMTP id
 BT-MMP-24866830; Fri, 13 Mar 2009 15:20:45 +0000 (Z)
Received: from manam.TechFak.Uni-Bielefeld.DE
 (manam.TechFak.Uni-Bielefeld.DE [129.70.137.47])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)	by smarthost.TechFak.Uni-Bielefeld.DE
 (Postfix) with ESMTP id 03B3148264; Fri, 13 Mar 2009 16:20:45 +0100 (CET)
Date: Fri, 13 Mar 2009 16:20:42 +0100 (MET)
From: Rainer Orth <ro@techfak.uni-bielefeld.de>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BA5948.5040404@sun.com>
To: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Cc: psarc-ext@sun.com
Message-id: <18874.31178.769417.715777@manam.TechFak.Uni-Bielefeld.DE>
MIME-version: 1.0
X-Mailer: VM 6.62 under Emacs 19.34.1
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
X-Brightmail-Tracker: AAAAAA==
X-Antispam: No, score=0.0/5.0, scanned in 0.389sec at (localhost [127.0.0.1])
	by smf-spamd v1.3.1 - http://smfs.sf.net/
References: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE> <49BA5948.5040404@sun.com>
Status: RO
Content-Length: 1534

Wyllys Ingersoll writes:

> Rainer Orth wrote:
> > Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> writes:
> > 
> >> Deliverables
> >> ------------
> >> /usr/bin/tor			SFW	Uncommitted
> >> /usr/bin/tor-resolve		SFW	Uncommitted
> >> /usr/bin/tor-gencert		SFW	Uncommitted
> > 
> > Does this really belong into /usr/bin?  Is a regular user supposed to
> > invoke tor or any of the two other commands?  I suppose this is rather for
> > /usr/sbin (or maybe even /usr/lib or /usr/lib/tor) if the tor binary is for
> > a daemon controlled by SMF.
> 
> 'tor' should probably move to /usr/lib/ since it is a daemon process started by SMF,
> I will update the spec and build environment.

Fine, thanks.

> tor-resovle and tor-gencert are commands that a user would use, so they probably
> belong in /usr/bin

Right, I've checked the man pages.

> >> /usr/man/man1/tor.1		SFW	Uncommitted
> >> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
> >> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
> > 
> > Similar questions here: shouldn't this be section 1M instead?
> 
> .1 is where they live on a Linux system, but if there is consensus that it
> should be 1M on Solaris, I have no issue with changing it.

Solaris is not Linux (thank god) :-)  It should be tor(8) on Linux anyway,
but tor(1M) on Solaris for admin commands.  Since tor-resolve und
tor-gencert are user commands, they should remain in section 1.

	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

From wyllys.ingersoll@sun.com Fri Mar 13 08:36:44 2009
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 n2DFaiRc019812
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 08:36:44 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2DFaZwf008536
	for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 13 Mar 2009 08:36:44 -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 <0KGG00G07BCZED00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com
 (ORCPT psarc-ext@sun.com); Fri, 13 Mar 2009 08:36:35 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG00FT5BCZN910@nwk-avmta-2.sfbay.sun.com> for
 psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri,
 13 Mar 2009 08:36:35 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2DFaXkW178883
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri,
 13 Mar 2009 08:36:34 -0700 (PDT)
Date: Fri, 13 Mar 2009 11:36:27 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18874.31178.769417.715777@manam.TechFak.Uni-Bielefeld.DE>
To: Rainer Orth <ro@techfak.uni-bielefeld.de>
Cc: psarc-ext@sun.com
Message-id: <49BA7D7B.1080400@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <yddwsatmvlw.fsf@manam.TechFak.Uni-Bielefeld.DE> <49BA5948.5040404@sun.com>
 <18874.31178.769417.715777@manam.TechFak.Uni-Bielefeld.DE>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 650


> 
>>>> /usr/man/man1/tor.1		SFW	Uncommitted
>>>> /usr/man/man1/tor-resolve.1	SFW	Uncommitted
>>>> /usr/man/man1/tor-gencert.1	SFW	Uncommitted
>>> Similar questions here: shouldn't this be section 1M instead?
>> .1 is where they live on a Linux system, but if there is consensus that it
>> should be 1M on Solaris, I have no issue with changing it.
> 
> Solaris is not Linux (thank god) :-)  It should be tor(8) on Linux anyway,
> but tor(1M) on Solaris for admin commands.  Since tor-resolve und
> tor-gencert are user commands, they should remain in section 1.
> 
> 	Rainer
> 

OK, I will put tor page in 1M and leave the others in (1).

-Wyllys


From MAILER-DAEMON Fri Mar 13 11:07:14 2009
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 n2DI7EF0025572
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 11:07:14 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2DI72mG004191;
	Fri, 13 Mar 2009 18:07:12 GMT
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 <0KGG0010VIBY8C00@nwk-avmta-2.sfbay.sun.com>; Fri,
 13 Mar 2009 11:07:10 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG00MITIBW8C50@nwk-avmta-2.sfbay.sun.com>; Fri,
 13 Mar 2009 11:07:08 -0700 (PDT)
Received: from rosseau (rosseau.SFBay.Sun.COM [129.146.228.252])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2DI78Sx211519; Fri, 13 Mar 2009 11:07:08 -0700 (PDT)
Date: Fri, 13 Mar 2009 11:07:22 -0700
From: Stephen Hahn <sch@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <20090313180722.GB901@eng.sun.com>
Organization: Solaris Kernel Development; Sun Microsystems, Inc.
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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Status: RO
Content-Length: 1980

* Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> [2009-03-12 18:14]:
> This project will deliver an SMF manifest and script that will allow
> the tor relay daemon to be restarted via SMF.  The SMF service will be:
> 	svc:/application/security/tor:default (Tor Relay Daemon)

  A minor point on naming:  I wonder if

  network/security/tor

  or even

  network/tor

  would be more clear.  The skeleton of the namespace in 2002/547
  (sanitized and included below) didn't really anticipate an
  external-network-mostly service that was security related.

  - Stephen

* What will "man -k onion" return?

----

8.2.3       Service FMRI naming

  In this subsection and those following, we propose a convention for naming
services. Generally, we are trying to introduce only one or two layers of
service groupings to show relations, and naming services proper based on

    * a functional description,
    * a well-known component, or
    * a standard protocol.

These choices may not provide suitable names for all services.

  We propose the following top- (or two-level) names for services:

    * milestone/ Synthetic services for clean dependency statements.
    * device/ General device services.
    * system/ Services concerned with host-centric, non-networked capabilities.
    * system/security/ Low-level host-centric services implementing security facilities.
    * network/ Services concerned with host-centric, network infrastructure capabilities[, and also services implementing standard internet protocols].
    * platform/ Services concerned with host-centric, hardware- or platform-specific capa-
       bilities.
    * application/ General software services.
    * application/management/ Services implementing management facilities.
    * application/security/ Services implementing high-level security facilities.

(It probably cannot be stressed enough that [social and organizational
structures] should not be a basis for service name choices in Solaris.)

----

From carlsonj@phorcys.east.sun.com Fri Mar 13 11:37:46 2009
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 n2DIbk3d025745
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 11:37:46 -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 n2DIbhH9033501;
	Fri, 13 Mar 2009 12:37:45 -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 <0KGG0012VJQWHX00@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 12:37:44 -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 <0KGG00ED7JQVWPB0@brm-avmta-1.central.sun.com>; Fri,
 13 Mar 2009 12:37:43 -0600 (MDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2DIbdYi024646; Fri,
 13 Mar 2009 14:37:39 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n2DIbdcX024643; Fri,
 13 Mar 2009 14:37:39 -0400 (EDT)
Date: Fri, 13 Mar 2009 14:37:39 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <20090313180722.GB901@eng.sun.com>
To: Stephen Hahn <sch@sun.com>
Cc: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>, PSARC-ext@sun.com
Message-id: <18874.42995.342624.862359@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
Status: RO
Content-Length: 1620

Stephen Hahn writes:
> * Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> [2009-03-12 18:14]:
> > This project will deliver an SMF manifest and script that will allow
> > the tor relay daemon to be restarted via SMF.  The SMF service will be:
> > 	svc:/application/security/tor:default (Tor Relay Daemon)
> 
>   A minor point on naming:  I wonder if
> 
>   network/security/tor
> 
>   or even
> 
>   network/tor

network/tor makes more sense to me.  The other residents of
network/security are specifically security protocols (Kerberos), and
it's not clear that this belongs.

But the line between "application" and "network" has never been
apparent to me.  There are many things in svc:/application that are
actually networking features, such as application/print/rfc1179 and
everything under application/management/*, as well as things under
svc:/network that don't seem to be related to networking (such as
network/rpc/meta and network/npiv_config).

(Our FMRI structure within svc:/network is also quite unclear.  In
some cases, the path components represent implementation details [such
as '/rpc/'], and in other cases, they represent groupings around a
particular technology or protocol [such as '/dns/'].)

The lack of a clear structure here was one of the comments on the
original Greenline case.

> * What will "man -k onion" return?

Depends on how much you've had to drink, I'd guess.  ;-}

-- 
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 wyllys.ingersoll@sun.com Fri Mar 13 12:22:16 2009
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 n2DJMFSP020022
	for <psarc-ext@sac.sfbay.sun.com>; Fri, 13 Mar 2009 12:22:16 -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 n2DJMCk6062972;
	Fri, 13 Mar 2009 13:22:14 -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 <0KGG00H0FLT1H200@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 13 Mar 2009 12:22:13 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGG00F3KLSY4J70@nwk-avmta-1.sfbay.Sun.COM>; Fri,
 13 Mar 2009 12:22:10 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2DJM9AC227519
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri,
 13 Mar 2009 12:22:10 -0700 (PDT)
Date: Fri, 13 Mar 2009 15:22:03 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <18874.42995.342624.862359@gargle.gargle.HOWL>
To: James Carlson <james.d.carlson@sun.com>
Cc: Stephen Hahn <sch@sun.com>, PSARC-ext@sun.com
Message-id: <49BAB25B.3070908@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 650

James Carlson wrote:
> Stephen Hahn writes:
>> * Wyllys Ingersoll <Wyllys.Ingersoll@sun.com> [2009-03-12 18:14]:
>>> This project will deliver an SMF manifest and script that will allow
>>> the tor relay daemon to be restarted via SMF.  The SMF service will be:
>>> 	svc:/application/security/tor:default (Tor Relay Daemon)
>>   A minor point on naming:  I wonder if
>>
>>   network/security/tor
>>
>>   or even
>>
>>   network/tor
> 
> network/tor makes more sense to me.  The other residents of
> network/security are specifically security protocols (Kerberos), and
> it's not clear that this belongs.


I will change it to /network/tor

-Wyllys



From wyllys.ingersoll@sun.com Mon Mar 16 06:44:24 2009
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 n2GDiNSr000308
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 16 Mar 2009 06:44:24 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2GDiK6O034382
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 16 Mar 2009 07:44:23 -0600 (MDT)
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 <0KGL00L5PQ5YT200@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 16 Mar 2009 06:44:22 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGL00BEZQ5URAF0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 16 Mar 2009 06:44:18 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2GDiHow769892
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <PSARC-ext@sun.com>; Mon, 16 Mar 2009 06:44:18 -0700 (PDT)
Date: Mon, 16 Mar 2009 09:44:09 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BAB25B.3070908@sun.com>
To: PSARC-ext@sun.com
Message-id: <49BE57A9.1080803@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_nN6tIJYUwYNdR6wmT8UbkA)"
X-PMX-Version: 5.4.1.325704
References: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL> <49BAB25B.3070908@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 6379

This is a multi-part message in MIME format.

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


I exchanged email with the lead engineer for the Tor project and he told me that
Tor will use whatever it considers reasonable defaults if it doesn't find a 
config file (/etc/torrc).  So, instead of delivering a sample config file, 
I think it is better to deliver a working config file in /etc/torrc with 2 ports 
enabled by default - 9050 for socks, and 9001 for the standard Tor relay connections.  
I will not deliver the sample file.  

Also, Tor may be configured to listen on privileged ports such as 443 if it is set up 
as a bridge relay, so it will need the priv_net_privaddr privilege in addition to the 
"basic" set, I will add this to the /usr/lib/tor entry in /etc/security/exec_attr.

I have updated the spec and put a copy in the case directory.  I've also
attached it to this email for reference.

-Wyllys


--Boundary_(ID_nN6tIJYUwYNdR6wmT8UbkA)
Content-type: text/plain; name=tor-ft-2.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=tor-ft-2.txt


Description
-----------
This case proposes to deliver packages containing the Tor project 
sofware.  Tor (https://www.torproject.org) is software lets
one to participate in a network of virtual tunnels that allow people
and groups to improve their privacy and security on the internet.
Tor provides the foundation for a range of applications that allow 
organizations and individuals to share information over public
networks without compromising their privacy.

See this page for more details: https://www.torproject.org/overview.html.en

Notes:
* Currently we are planning to deliver version 0.2.0.34
* Tor uses only TCP streams and can be used by any application with SOCKS
  support.
* Tor does NOT support IPv6 yet (https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IPv6)
* Tor uses OpenSSL for key generation and for encrypting the data
  between relays.  As it works fine with the OpenSSL currently in Solaris, there are
  no plans to change it to use PKCS11 or KMF.

Least Privilege/RBAC
--------------------
This project will deliver new authorizations to /etc/security/auth_attr
for managing the SMF services for starting and stopping the relay server:
	solaris.smf.value.tor:::Change tor value properties::
	solaris.smf.manage.tor:::Manage tor service states::

The following rights profile will be added to /etc/security/prof_attr:
	Tor Administration::::auths=solaris.smf.manage.tor,solaris.smf.value.tor

The following will be added to /etc/security/exec_attr:
	Tor Administration:solaris:cmd:::/usr/lib/tor:uid=daemon,gid=daemon,privs=basic,priv_net_privaddr
	Tor Administration:solaris:cmd:::/usr/bin/tor-gencert:uid=daemon,gid=daemon,privs=basic
	Tor Administration:solaris:cmd:::/usr/bin/tor-resolve:uid=daemon,gid=daemon,privs=basic

Tor will run as uid/gid "daemon/daemon".  It may be configured to listen on a privileged port such 
as 443 if it is configured as a bridge relay and therefore the "priv_net_privaddr" is needed in 
addition to the basic privilege profile.

SMF
---
This project will deliver an SMF manifest and script that will allow
the tor relay daemon to be restarted via SMF.  The SMF service will be:
	svc:/network/tor:default (Tor Relay Daemon)

Zones
-----
Tor can (and probably should) be run in a local zone with no restrictions
other than the fact that it needs a working network interface.  There
is no technical reason why it would NOT work in a TX zone, though
that configuration has not been tested.

Auditing
--------
Tor does not make access control decisions and is not an administrative
tool that requires BSM auditing.

Configuration
-------------
Tor is an open source project and has an existing configuration system
that relies on a text based configuration file.  An configuration file 
will be delivered in /etc/torrc.  The delivered configuration file will
enable Tor to listen on port 9050 for SOCKS connections and on port 9001
for Tor relay connections.  All other ports will be disabled.

The configuration file contains a long list of options for configuring
the ports and interfaces that the relay will listen to as well as other
details such as logging levels, configuring "hidden" services (see 
https://www.torproject.org/hidden-services.html.en for a detailed description
of the hidden service protocol), and limiting the bandwidth that the relay will use.

The upstream Tor community is fairly active and releases updates several times
each year.  Making Solaris-specific changes (such as putting config options in an
SMF profile) will make it harder to keep up with the community and resync
with the current releases.

Packing Modifications
---------------------
SUNWtor		Tor software for userland
SUNWtor-root	Tor software for Root filesystem

Deliverables
------------
/usr/lib/tor			SFW	Uncommitted
/usr/bin/tor-resolve		SFW	Uncommitted
/usr/bin/tor-gencert		SFW	Uncommitted

/etc/torrc			SFW	Uncommitted
/usr/share/tor/geoip		SFW	Uncommitted

/usr/man/man1m/tor.1m		SFW	Uncommitted
/usr/man/man1/tor-resolve.1	SFW	Uncommitted
/usr/man/man1/tor-gencert.1	SFW	Uncommitted

Details
-------
tor is the main daemon process that is started by the "tor" SMF profile.

tor-resolve is a script to connect to a SOCKS proxy that knows about the SOCKS RESOLVE	
    command, hand it a hostname, and return an IP address.

tor-gencert generates certificates and private keys for  use
     by  Tor  directory  authorities running the v3 Tor directory
     protocol, as used by Tor 0.2.0 and later.  If  you  are  not
     running  a  directory  authority, you don't need to use tor-
     gencert. tor-gencert generates 3 files that the user must then copy
     to the "keys" subdirectory (/var/lib/tor/keys) - "authority_identity_key", 
     "authority_signing_key" and "authority_certificate".

geoip is an ASCII based database of IP-to-Country name mappings.  It is not intended
     to be edited by users.


OpenSource
----------
OSR Review: 9954  (approved - Tor version 0.2.0.30)
            11364 (pending expedited review - Tor version 0.2.0.34)

Tor Project:  https://www.torproject.org
Tor Wiki: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ

Release Taxonomy:  Micro/Patch

--Boundary_(ID_nN6tIJYUwYNdR6wmT8UbkA)--

From Scott.Rotondo@Sun.COM Mon Mar 16 14:32:24 2009
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 n2GLWNh8004466
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 16 Mar 2009 14:32:24 -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 n2GLWFOi013122
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 17 Mar 2009 05:32:22 +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 <0KGM00M0ZBTXEZ00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 16 Mar 2009 14:32:21 -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 <0KGM00HRMBTWBEA0@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 16 Mar 2009 14:32:20 -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 n2GLWKa4004997	for
 <PSARC-ext@sun.com>; Mon, 16 Mar 2009 21:32:20 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGM00000A17E100@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 16 Mar 2009 15:32:20 -0600 (MDT)
Received: from [129.146.108.62] ([unknown] [129.146.108.62])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGM00N5TBTE1ZB0@mail-amer.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 16 Mar 2009 15:32:02 -0600 (MDT)
Date: Mon, 16 Mar 2009 14:32:02 -0700
From: Scott Rotondo <Scott.Rotondo@Sun.COM>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BE57A9.1080803@sun.com>
Sender: Scott.Rotondo@Sun.COM
To: Wyllys Ingersoll <Wyllys.Ingersoll@Sun.COM>
Cc: PSARC-ext@Sun.COM
Message-id: <49BEC552.90002@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL> <49BAB25B.3070908@sun.com>
 <49BE57A9.1080803@sun.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080422)
Status: RO
Content-Length: 1073

Wyllys Ingersoll wrote:
> 
> I exchanged email with the lead engineer for the Tor project and he told 
> me that
> Tor will use whatever it considers reasonable defaults if it doesn't 
> find a config file (/etc/torrc).  So, instead of delivering a sample 
> config file, I think it is better to deliver a working config file in 
> /etc/torrc with 2 ports enabled by default - 9050 for socks, and 9001 
> for the standard Tor relay connections.  I will not deliver the sample 
> file. 
> Also, Tor may be configured to listen on privileged ports such as 443 if 
> it is set up as a bridge relay, so it will need the priv_net_privaddr 
> privilege in addition to the "basic" set, I will add this to the 
> /usr/lib/tor entry in /etc/security/exec_attr.
> 

I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
think you'd need to specify the privilege in the service manifest rather 
than exec_attr.

	Scott


-- 
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)

From wyllys.ingersoll@sun.com Mon Mar 16 14:39:06 2009
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 n2GLd51E004598
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 16 Mar 2009 14:39: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 n2GLcwfJ016418;
	Tue, 17 Mar 2009 05:39:03 +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 <0KGM00M07C52RR00@nwk-avmta-2.sfbay.sun.com>; Mon,
 16 Mar 2009 14:39:02 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGM00HALC52BBB0@nwk-avmta-2.sfbay.sun.com>; Mon,
 16 Mar 2009 14:39:02 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2GLd1cu854150
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon,
 16 Mar 2009 14:39:01 -0700 (PDT)
Date: Mon, 16 Mar 2009 17:38:52 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BEC552.90002@sun.com>
To: Scott Rotondo <Scott.Rotondo@sun.com>
Cc: PSARC-ext@sun.com
Message-id: <49BEC6EC.20104@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL> <49BAB25B.3070908@sun.com>
 <49BE57A9.1080803@sun.com> <49BEC552.90002@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 1032

Scott Rotondo wrote:
> Wyllys Ingersoll wrote:
>>
>> I exchanged email with the lead engineer for the Tor project and he 
>> told me that
>> Tor will use whatever it considers reasonable defaults if it doesn't 
>> find a config file (/etc/torrc).  So, instead of delivering a sample 
>> config file, I think it is better to deliver a working config file in 
>> /etc/torrc with 2 ports enabled by default - 9050 for socks, and 9001 
>> for the standard Tor relay connections.  I will not deliver the sample 
>> file. Also, Tor may be configured to listen on privileged ports such 
>> as 443 if it is set up as a bridge relay, so it will need the 
>> priv_net_privaddr privilege in addition to the "basic" set, I will add 
>> this to the /usr/lib/tor entry in /etc/security/exec_attr.
>>
> 
> I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
> think you'd need to specify the privilege in the service manifest rather 
> than exec_attr.
> 
>     Scott

Yes, correct, it needs to be added there as well.

-Wyllys




From Darren.Moffat@sun.com Tue Mar 17 02:27:02 2009
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 n2H9R16w014102
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 17 Mar 2009 02:27:02 -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 n2H9Qvc0034133
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 17 Mar 2009 03:27: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 <0KGN00B1L8X0BL00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Tue, 17 Mar 2009 02:27:00 -0700 (PDT)
Received: from gmp-eb-inf-1.sun.com ([192.18.6.21])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGN007YU8WZ5W40@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue,
 17 Mar 2009 02:27:00 -0700 (PDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n2H9QxU3009474	for
 <PSARC-ext@sun.com>; Tue, 17 Mar 2009 09:26:59 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KGN00300858Q400@fe-emea-10.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Tue, 17 Mar 2009 09:26:59 +0000 (GMT)
Received: from [129.156.173.21] ([unknown] [129.156.173.21])
 by fe-emea-10.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KGN006AY8WHB4C0@fe-emea-10.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Tue, 17 Mar 2009 09:26:44 +0000 (GMT)
Date: Tue, 17 Mar 2009 09:26:41 +0000
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BEC6EC.20104@sun.com>
Sender: Darren.Moffat@sun.com
To: Wyllys Ingersoll <Wyllys.Ingersoll@sun.com>
Cc: Scott Rotondo <Scott.Rotondo@sun.com>, PSARC-ext@sun.com
Message-id: <49BF6CD1.6050007@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL> <49BAB25B.3070908@sun.com>
 <49BE57A9.1080803@sun.com> <49BEC552.90002@sun.com> <49BEC6EC.20104@sun.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081201)
Status: RO
Content-Length: 1186

Wyllys Ingersoll wrote:
> Scott Rotondo wrote:
>> Wyllys Ingersoll wrote:
>>>
>>> I exchanged email with the lead engineer for the Tor project and he 
>>> told me that
>>> Tor will use whatever it considers reasonable defaults if it doesn't 
>>> find a config file (/etc/torrc).  So, instead of delivering a sample 
>>> config file, I think it is better to deliver a working config file in 
>>> /etc/torrc with 2 ports enabled by default - 9050 for socks, and 9001 
>>> for the standard Tor relay connections.  I will not deliver the 
>>> sample file. Also, Tor may be configured to listen on privileged 
>>> ports such as 443 if it is set up as a bridge relay, so it will need 
>>> the priv_net_privaddr privilege in addition to the "basic" set, I 
>>> will add this to the /usr/lib/tor entry in /etc/security/exec_attr.
>>>
>>
>> I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
>> think you'd need to specify the privilege in the service manifest 
>> rather than exec_attr.
>>
>>     Scott
> 
> Yes, correct, it needs to be added there as well.

Or the SMF service can specific the name of the RBAC profile to use for 
the method credential.

-- 
Darren J Moffat

From wyllys.ingersoll@Sun.COM Tue Mar 17 06:47:16 2009
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 n2HDlFJ0015748
	for <psarc-ext@sac.sfbay.sun.com>; Tue, 17 Mar 2009 06:47:15 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2HDlD97007095;
	Tue, 17 Mar 2009 06:47:14 -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 <0KGN00B01KYP5300@nwk-avmta-2.sfbay.sun.com>; Tue,
 17 Mar 2009 06:47:13 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KGN002N5KYONOC0@nwk-avmta-2.sfbay.sun.com>; Tue,
 17 Mar 2009 06:47:12 -0700 (PDT)
Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n2HDlBp0995868
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue,
 17 Mar 2009 06:47:12 -0700 (PDT)
Date: Tue, 17 Mar 2009 09:47:01 -0400
From: Wyllys Ingersoll <wyllys.ingersoll@Sun.COM>
Subject: Re: Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]
In-reply-to: <49BF6CD1.6050007@Sun.COM>
To: Darren J Moffat <Darren.Moffat@Sun.COM>
Cc: Scott Rotondo <Scott.Rotondo@Sun.COM>, PSARC-ext@Sun.COM
Message-id: <49BFA9D5.2000209@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: <200903121812.n2CICbD7410484@jurassic-x4600.sfbay.sun.com>
 <20090313180722.GB901@eng.sun.com>
 <18874.42995.342624.862359@gargle.gargle.HOWL> <49BAB25B.3070908@sun.com>
 <49BE57A9.1080803@sun.com> <49BEC552.90002@sun.com> <49BEC6EC.20104@sun.com>
 <49BF6CD1.6050007@Sun.COM>
User-Agent: Thunderbird 2.0.0.18 (X11/20090112)
Status: RO
Content-Length: 1550

Darren J Moffat wrote:
> Wyllys Ingersoll wrote:
>> Scott Rotondo wrote:
>>> Wyllys Ingersoll wrote:
>>>>
>>>> I exchanged email with the lead engineer for the Tor project and he 
>>>> told me that
>>>> Tor will use whatever it considers reasonable defaults if it doesn't 
>>>> find a config file (/etc/torrc).  So, instead of delivering a sample 
>>>> config file, I think it is better to deliver a working config file 
>>>> in /etc/torrc with 2 ports enabled by default - 9050 for socks, and 
>>>> 9001 for the standard Tor relay connections.  I will not deliver the 
>>>> sample file. Also, Tor may be configured to listen on privileged 
>>>> ports such as 443 if it is set up as a bridge relay, so it will need 
>>>> the priv_net_privaddr privilege in addition to the "basic" set, I 
>>>> will add this to the /usr/lib/tor entry in /etc/security/exec_attr.
>>>>
>>>
>>> I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
>>> think you'd need to specify the privilege in the service manifest 
>>> rather than exec_attr.
>>>
>>>     Scott
>>
>> Yes, correct, it needs to be added there as well.
> 
> Or the SMF service can specific the name of the RBAC profile to use for 
> the method credential.
> 

Upon closer examination, I don't think any of the Tor executables belong in
an exec_attr entry - 2 of them are just simple userland utilities that 
do not require or need any special privilege and the Tor daemon itself
can get its necessary privileges from the SMF profile.  I'm going to
remove the exec_attr entries.

-Wyllys


