From sacadmin Wed Nov 12 16:24:16 2008 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAD0OG2A010505; Wed, 12 Nov 2008 16:24:16 -0800 (PST) Received: (from margotm@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mAD0OGkV010501; Wed, 12 Nov 2008 16:24:16 -0800 (PST) Date: Wed, 12 Nov 2008 16:24:16 -0800 (PST) From: Margot Miller Message-Id: <200811130024.mAD0OGkV010501@sac.sfbay.sun.com> To: LSARC-record@sac.sfbay.sun.com Subject: sox [LSARC/2008/706 FastTrack timeout 11/20/2008] Status: RO Content-Length: 535 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: sox 1.2. Name of Document Author/Supplier: Author: Ken Erickson 1.3 Date of This Document: 12 November, 2008 4. Technical Description See the case directory for more detail 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 margot.miller@sun.com Wed Nov 12 21:08:14 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAD58DI7018550 for ; Wed, 12 Nov 2008 21:08:14 -0800 (PST) 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 mAD58A4D004766; Thu, 13 Nov 2008 13:08:11 +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 <0KA900003A9LAR00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 12 Nov 2008 21:08:09 -0800 (PST) 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 <0KA900KBEA9L8690@nwk-avmta-1.sfbay.Sun.COM>; Wed, 12 Nov 2008 21:08:09 -0800 (PST) Received: from [10.7.250.155] (punchin-client-10-7-250-155.SFBay.Sun.COM [10.7.250.155]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mAD57so1643119; Wed, 12 Nov 2008 21:08:01 -0800 (PST) Date: Wed, 12 Nov 2008 21:06:17 -0800 From: Margot Miller Subject: LSARC/2008/706 - sox To: lsarc-ext@sun.com Cc: Ken Erickson Message-id: <491BB5C9.3000601@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 User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 13594 All, I am sponsoring the following fast track for Ken. Timeout is THURSDAY Nov 20th. Requesting patch binding. Man pages are in the case directory. Below is the proposal and FOSS checklist. Thanks Margot ---------------------------------------------------------------------------------------------------------- Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: sox 1.2. Name of Document Author/Supplier: Author: Ken Erickson 1.3 Date of This Document: 30 October 2008 2. Project Summary 2.1. Project Description This project delivers the sox package, version 14.0.1, an audio file conversion and sound effects utility. 4. Technical Description sox (SOund eXchange) is a command line utility, and an associated set of library routines, which convert many different digital audio formats, and can process audio files to add various sound effects. 5. Interfaces Exported interface Classification Interface type =============================== ============== ============== SUNWsound-exchange Uncommitted Package name /usr/bin/sox Uncommitted command /usr/include/sox.h Uncommitted header /usr/include/soxsdtint.h Uncommitted header /usr/lib/libsox.so.0.0.0 Uncommitted library /usr/lib/libsox.so.0 Uncommitted symlink /usr/lib/libsox.so Uncommitted symlink /usr/lib/libsfx.so.0.0.0 Uncommitted library /usr/lib/libsfx.so.0 Uncommitted symlink /usr/lib/libsfx.so Uncommitted symlink /usr/lib/sox Uncommitted directory /usr/lib/sox/*.so.0.0.0 Project Private conversion libraries 5a. Manpages /usr/share/man/man1/sox.1 Uncommitted manpage /usr/share/man/man3/libsox.3 Uncommitted manpage /usr/share/man/man4/soxformat.4 Uncommitted manpage /usr/share/man/man5/soxeffect.5 Uncommitted manpage /usr/share/man/man5/soxexam.5 Uncommitted manpage 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 ---------------------------------------------------------------------------------------------------------- FCL--FOSS Check List 1.0 Project Information 1.1 Name of project/component sox 1.2 Author of document Ken Erickson 2.0 Project Summary 2.1 Project Description 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [ ] Minor [ X] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [ ] Yes [ x] No 2.4 Originating Community 2.4.1 Community Name 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [ x] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [ x] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [ x] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [ x] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [ x] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [ ] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [ ] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [ x] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [ ] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [ ] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [ x] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [ ] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [ x] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [ ] Yes [ x] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [x ] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [ x] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [ x] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [ x] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [ x] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [ x] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [ x] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [ x] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [ x] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [ x] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [ ] Yes [ x] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [ x] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [ x] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) See Fast Track From Darren.Moffat@Sun.COM Thu Nov 13 01:46:04 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAD9k3DE027719 for ; Thu, 13 Nov 2008 01:46:04 -0800 (PST) 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 mAD9k1Ih025121 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 13 Nov 2008 17:46:02 +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 <0KA90080BN4P3B00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 01:46:01 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KA900DV0N4OPM80@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 01:46:01 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAD9k07M016069 for ; Thu, 13 Nov 2008 09:46:00 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KA900C01MVPF600@fe-emea-09.sun.com> (original mail from Darren.Moffat@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 09:46:00 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KA900G5LN4ERC10@fe-emea-09.sun.com>; Thu, 13 Nov 2008 09:45:51 +0000 (GMT) Date: Thu, 13 Nov 2008 09:45:50 +0000 From: Darren J Moffat Subject: Re: LSARC/2008/706 - sox In-reply-to: <491BB5C9.3000601@sun.com> Sender: Darren.Moffat@Sun.COM To: Margot Miller Cc: LSARC-ext@Sun.COM, Ken Erickson , "Garrett D'Amore" Message-id: <491BF74E.8080405@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: <491BB5C9.3000601@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 246 How does this case fit with PSARC 2008/318 ? I believe there shouldn't be any interaction between the two but I want clarification of that since it has been a very long time since I last used sox (probably about 11 years). -- Darren J Moffat From John.Fischer@Sun.COM Thu Nov 13 07:20:41 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADFKfiV007196 for ; Thu, 13 Nov 2008 07:20:41 -0800 (PST) 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 mADFKem6017675 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 13 Nov 2008 07:20:41 -0800 (PST) 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 <0KAA00J0N2MGBI00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 07:20:40 -0800 (PST) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00DSI2MEMU90@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 07:20:38 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mADFKcQ0020050 for ; Thu, 13 Nov 2008 15:20:38 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAA00B012HDAX00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Nov 2008 08:20:38 -0700 (MST) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAA00LKI2MCPI90@mail-amer.sun.com>; Thu, 13 Nov 2008 08:20:37 -0700 (MST) Date: Thu, 13 Nov 2008 07:20:36 -0800 From: John Fischer Subject: Re: LSARC/2008/706 - sox In-reply-to: <491BB5C9.3000601@sun.com> Sender: John.Fischer@Sun.COM To: Margot Miller Cc: John Fischer , lsarc-ext@Sun.COM, Ken Erickson Reply-to: John.Fischer@Sun.COM Message-id: <1226589636.49887.259.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <491BB5C9.3000601@sun.com> Status: RO Content-Length: 14732 Ken, Assuming that sox is useful for application developers if not then please say so.... Is there any reason why the project is not delivering 64-bit versions of the libraries? The project should also provide a pkg-config file to help facilitate the build for developers. Thanks, John On Wed, 2008-11-12 at 21:06, Margot Miller wrote: > All, > > I am sponsoring the following fast track for Ken. Timeout is > THURSDAY Nov 20th. Requesting patch binding. Man pages > are in the case directory. > > Below is the proposal and FOSS checklist. > > Thanks > Margot > > ---------------------------------------------------------------------------------------------------------- > > Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sox > 1.2. Name of Document Author/Supplier: > Author: Ken Erickson > 1.3 Date of This Document: > 30 October 2008 > 2. Project Summary > 2.1. Project Description > > This project delivers the sox package, version 14.0.1, > an audio file conversion and sound effects utility. > > 4. Technical Description > > sox (SOund eXchange) is a command line utility, and an associated > set of library routines, which convert many different digital > audio formats, and can process audio files to add various > sound effects. > > 5. Interfaces > > Exported interface > Classification Interface type > =============================== ============== ============== > SUNWsound-exchange > Uncommitted Package name > /usr/bin/sox > Uncommitted command > /usr/include/sox.h > Uncommitted header > /usr/include/soxsdtint.h > Uncommitted header > /usr/lib/libsox.so.0.0.0 > Uncommitted library > /usr/lib/libsox.so.0 > Uncommitted symlink > /usr/lib/libsox.so > Uncommitted symlink > /usr/lib/libsfx.so.0.0.0 > Uncommitted library > /usr/lib/libsfx.so.0 > Uncommitted symlink > /usr/lib/libsfx.so > Uncommitted symlink > /usr/lib/sox > Uncommitted directory > /usr/lib/sox/*.so.0.0.0 > Project Private conversion libraries > > > > 5a. Manpages > > /usr/share/man/man1/sox.1 Uncommitted manpage > /usr/share/man/man3/libsox.3 Uncommitted manpage > /usr/share/man/man4/soxformat.4 Uncommitted manpage > /usr/share/man/man5/soxeffect.5 Uncommitted manpage > /usr/share/man/man5/soxexam.5 Uncommitted manpage > > > 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 > > ---------------------------------------------------------------------------------------------------------- > FCL--FOSS Check List > 1.0 Project Information > 1.1 Name of project/component > > sox > > 1.2 Author of document > > Ken Erickson > > 2.0 Project Summary > 2.1 Project Description > > 2.2 Release binding > What is is the release binding? > (see > http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [ ] Minor > [ X] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [ ] Yes > [ x] No > > 2.4 Originating Community > 2.4.1 Community Name > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [ x] Monitoring > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [ x] Yes [ ] No - briefly explain > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [ x] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see > http://opensolaris.org/os/community/arc/policies/install-locations/ for > details) > Does this project follow the Install Locations best practice? > [ x] Yes [ ] No - ARC review required > Does this project install into /usr under > [sbin|bin|lib|include|man|share]? > [ x] Yes > [ ] No or N/A > Does this project install into /opt? > [ ] Yes - explain below > [ ] No or N/A > Does this project install into a different directory structure? > [ ] Yes - ARC review required > [ ] No or N/A > Do any of the components of this project conflict with anything > under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for > details) > [ ] Yes - explain below > [ x] No > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [ ] No > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a drive>:\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun > Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ id>\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [ ] Yes > [ x] No > If yes are these components packaged to be shared with the other FOSS? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Are these components already in the Solaris WOS? > [ ] Yes > [ ] No - continue with next section (section 3.2) > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [ x] Yes > [ ] No - continue with next section (section 3.3) > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ x] No - ARC review required > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [x ] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [ x] No > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [ x] No > Does the project integrate any private non-public files into > /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [ x] No > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [ x] No > > 3.4 Security > 3.4.1 Secure By Default > (see > http://opensolaris.org/os/community/arc/policies/secure-by-default/ for > details) > (see > http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for > details) > (see parts of > http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [ x] No - continue with the next section (section 3.4.2) > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > Are network services automatically enabled by the project during > installation? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is the receiver authenticated prior to receiving any sensitive > outbound communication? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > 3.4.2 Authorization > (see > http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [ x] No - continue with next section (section 3.4.3) > If yes then are the setuid/setgid privileges handled by the use of > roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see > http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for > details) > Does this component contain administrative or security enforcing > software? > [ ] Yes - ARC review required > [ x] No - continue to next section (section 3.4.4) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 > for details) > Do the components create audit logs detailing what took place > including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [ x] No - continue to next section (section 3.4.5) > If yes do the components use PAM (plugable authentication modules) > for authentication? > [ ] Yes > [ ] No - ARC review required > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > If yes are the components sufficiently privileged to allow the > requested operations (authentication, password change, process > credential manipulation, audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see > http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ > for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [ x] No - continue to next section (section 3.4.6) > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > If yes are the permissions on the file such to protect exposing > the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see > http://opensolaris.org/os/community/arc/bestpractices/security-questions/ > for details) > Are there any network protocols used by this project? > [ ] Yes > [ x] No - continue with the next section (section 3.5) > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > Do network services for the project make decisions based upon > user, host or service > identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > Do the components make use of secret information during > authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [ x] No - continue with the next section (section 3.6) > If yes do the components support IPv6? > [ ] Yes [ ] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [ x] No Examples of Core Solaris Components include but > are not limited to: > Secure By Default > Authorizations > PAM -- Plugable Authentication Module > Privilege > PRM -- Process Rights Management -- Privilege > Audit > xVm -- Virtualization > zones / Solaris Containers > PRM -- Process Rights Management > RBAC -- Role Based Access Control > TX / Trusted Extensions > ZFS > SMF -- Service Management Facility > FMA -- Fault Management Architecture > SCF -- Smart Card Facility > IPsec > 4.0 Interfaces > (see > http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ > for details) > > See Fast Track > > > > From ken.erickson@Sun.COM Thu Nov 13 12:12:10 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADKC9Xn018018 for ; Thu, 13 Nov 2008 12:12:09 -0800 (PST) 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 mADKBjNm004882; Thu, 13 Nov 2008 20:12:05 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 <0KAA00M1HG41Q100@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 13:12:01 -0700 (MST) Received: from macolaris.kens.net ([10.7.251.241]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00MJDG402O00@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 13:12:01 -0700 (MST) Received: from [IPv6:::1] (localhost [IPv6:::1]) by macolaris.kens.net (8.14.3+Sun/8.14.3) with ESMTP id mADKC0vo108673; Thu, 13 Nov 2008 14:12:00 -0600 (CST) Date: Thu, 13 Nov 2008 14:11:59 -0600 From: Ken Erickson Subject: Re: LSARC/2008/706 - sox In-reply-to: <491BF74E.8080405@Sun.COM> To: Darren J Moffat Cc: Margot Miller , LSARC-ext@Sun.COM, "Garrett D'Amore" Reply-to: ken.erickson@Sun.COM Message-id: <491C8A0F.2@sun.com> Organization: Sun Microsystems, Inc. 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: <491BB5C9.3000601@sun.com> <491BF74E.8080405@Sun.COM> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 858 Darren J Moffat wrote: > How does this case fit with PSARC 2008/318 ? > > I believe there shouldn't be any interaction between the two but I want > clarification of that since it has been a very long time since I last > used sox (probably about 11 years). > > -- > Darren J Moffat There should be no interaction between the two. Sox can work even in the absence of any audio hardware, so long as you aren't trying to play the audio files. It does not rely on any platform specific hardware. -ken -- Ken Erickson | kene@Eng.Sun.COM Sun Microsystems, Inc., Solaris OS Engineering | Voice: (847)663-9471 4150 Network Circle MS UITA01 | Cell: (312)401-6254 Santa Clara, CA 95054 | If you want me to read something, don't send it as a StarOffice or HTML attachment. From Darren.Moffat@Sun.COM Thu Nov 13 12:21:07 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADKL7XP018545 for ; Thu, 13 Nov 2008 12:21:07 -0800 (PST) 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 mADKL6Gc042085 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 13 Nov 2008 13:21:06 -0700 (MST) 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 <0KAA0020FGJ6E600@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Thu, 13 Nov 2008 12:21:06 -0800 (PST) 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 <0KAA00G4SGJ5WXC0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Thu, 13 Nov 2008 12:21:05 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mADKL4Tr001512 for ; Thu, 13 Nov 2008 20:21:04 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAA00G01GFFCZ00@fe-emea-09.sun.com> (original mail from Darren.Moffat@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Thu, 13 Nov 2008 20:21:04 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAA008AAGJ35220@fe-emea-09.sun.com>; Thu, 13 Nov 2008 20:21:04 +0000 (GMT) Date: Thu, 13 Nov 2008 20:21:03 +0000 From: Darren J Moffat Subject: Re: LSARC/2008/706 - sox In-reply-to: <491C8A0F.2@sun.com> Sender: Darren.Moffat@Sun.COM To: Ken.Erickson@Sun.COM Cc: Margot Miller , LSARC-ext@Sun.COM, "Garrett D'Amore" Message-id: <491C8C2F.6010104@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: <491BB5C9.3000601@sun.com> <491BF74E.8080405@Sun.COM> <491C8A0F.2@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080922) Status: RO Content-Length: 677 Ken Erickson wrote: > Darren J Moffat wrote: >> How does this case fit with PSARC 2008/318 ? >> >> I believe there shouldn't be any interaction between the two but I >> want clarification of that since it has been a very long time since I >> last used sox (probably about 11 years). >> >> -- >> Darren J Moffat > > There should be no interaction between the two. Sox can work even in the > absence of any audio hardware, so long as you aren't trying to play > the audio files. It does not rely on any platform specific hardware. So sox can play audio files ? So there is an interaction between sox and the choice of audio API either SADA or OSS ? -- Darren J Moffat From ken.erickson@sun.com Thu Nov 13 12:21:44 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADKLiIT018580 for ; Thu, 13 Nov 2008 12:21:44 -0800 (PST) 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 mADKLfNQ042282; Thu, 13 Nov 2008 13:21:43 -0700 (MST) 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 <0KAA0002DGK59W00@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 13:21:41 -0700 (MST) Received: from macolaris.kens.net ([10.7.251.241]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00MCVGK33E10@brm-avmta-1.central.sun.com>; Thu, 13 Nov 2008 13:21:40 -0700 (MST) Received: from [IPv6:::1] (localhost [IPv6:::1]) by macolaris.kens.net (8.14.3+Sun/8.14.3) with ESMTP id mADKLc3t108697; Thu, 13 Nov 2008 14:21:39 -0600 (CST) Date: Thu, 13 Nov 2008 14:21:38 -0600 From: Ken Erickson Subject: Re: LSARC/2008/706 - sox In-reply-to: <1226589636.49887.259.camel@sr1-umpk-16> To: John.Fischer@sun.com Cc: Margot Miller , lsarc-ext@sun.com Reply-to: ken.erickson@sun.com Message-id: <491C8C52.10304@sun.com> Organization: Sun Microsystems, Inc. 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: <491BB5C9.3000601@sun.com> <1226589636.49887.259.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 15720 John Fischer wrote: > Ken, > > Assuming that sox is useful for application developers > if not then please say so.... > > Is there any reason why the project is not delivering > 64-bit versions of the libraries? I went back and forth about whether or not 64-bit libraries would be useful, but now that you bring it up, I guess I should provide them, since we are documenting it with a manpage. I will add 64-bit libraries. > > The project should also provide a pkg-config file to > help facilitate the build for developers. OK. > > Thanks, > > John > > On Wed, 2008-11-12 at 21:06, Margot Miller wrote: >> All, >> >> I am sponsoring the following fast track for Ken. Timeout is >> THURSDAY Nov 20th. Requesting patch binding. Man pages >> are in the case directory. >> >> Below is the proposal and FOSS checklist. >> >> Thanks >> Margot >> >> ---------------------------------------------------------------------------------------------------------- >> >> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> sox >> 1.2. Name of Document Author/Supplier: >> Author: Ken Erickson >> 1.3 Date of This Document: >> 30 October 2008 >> 2. Project Summary >> 2.1. Project Description >> >> This project delivers the sox package, version 14.0.1, >> an audio file conversion and sound effects utility. >> >> 4. Technical Description >> >> sox (SOund eXchange) is a command line utility, and an associated >> set of library routines, which convert many different digital >> audio formats, and can process audio files to add various >> sound effects. >> >> 5. Interfaces >> >> Exported interface >> Classification Interface type >> =============================== ============== ============== >> SUNWsound-exchange >> Uncommitted Package name >> /usr/bin/sox >> Uncommitted command >> /usr/include/sox.h >> Uncommitted header >> /usr/include/soxsdtint.h >> Uncommitted header >> /usr/lib/libsox.so.0.0.0 >> Uncommitted library >> /usr/lib/libsox.so.0 >> Uncommitted symlink >> /usr/lib/libsox.so >> Uncommitted symlink >> /usr/lib/libsfx.so.0.0.0 >> Uncommitted library >> /usr/lib/libsfx.so.0 >> Uncommitted symlink >> /usr/lib/libsfx.so >> Uncommitted symlink >> /usr/lib/sox >> Uncommitted directory >> /usr/lib/sox/*.so.0.0.0 >> Project Private conversion libraries >> >> >> >> 5a. Manpages >> >> /usr/share/man/man1/sox.1 Uncommitted manpage >> /usr/share/man/man3/libsox.3 Uncommitted manpage >> /usr/share/man/man4/soxformat.4 Uncommitted manpage >> /usr/share/man/man5/soxeffect.5 Uncommitted manpage >> /usr/share/man/man5/soxexam.5 Uncommitted manpage >> >> >> 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 >> >> ---------------------------------------------------------------------------------------------------------- >> FCL--FOSS Check List >> 1.0 Project Information >> 1.1 Name of project/component >> >> sox >> >> 1.2 Author of document >> >> Ken Erickson >> >> 2.0 Project Summary >> 2.1 Project Description >> >> 2.2 Release binding >> What is is the release binding? >> (see >> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [ ] Minor >> [ X] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [ ] Yes >> [ x] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> 2.4.2 Community Involvement >> Indicate Sun's involvement in the community >> [ ] Maintainer >> [ ] Contributor >> [ x] Monitoring >> Will the project team work with the upstream community to resolve >> architectural issues of interest to Sun? >> [ x] Yes [ ] No - briefly explain >> Will we or are we forking from the community? >> [ ] Yes - ARC review required prior to forking >> [ x] No >> >> 3.0 Technical Description >> 3.1 Installation & Sharable >> 3.1.1S Solaris Installation - section only required for Solaris Software >> (see >> http://opensolaris.org/os/community/arc/policies/install-locations/ for >> details) >> Does this project follow the Install Locations best practice? >> [ x] Yes [ ] No - ARC review required >> Does this project install into /usr under >> [sbin|bin|lib|include|man|share]? >> [ x] Yes >> [ ] No or N/A >> Does this project install into /opt? >> [ ] Yes - explain below >> [ ] No or N/A >> Does this project install into a different directory structure? >> [ ] Yes - ARC review required >> [ ] No or N/A >> Do any of the components of this project conflict with anything >> under /usr? >> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for >> details) >> [ ] Yes - explain below >> [ x] No >> If conflicts exist then will this project install under /usr/gnu? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> Is this project installing into /usr/sfw? >> [ ] Yes - ARC review required >> [ ] No >> 3.1.1W Windows Installation - section only required for Windows Software >> (see http://sac.sfbay/WSARC/2002/494 for details) >> Does this project install software into a > drive>:\Program Files\Sun\ or :\Sun\ >> directory? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use the Windows registry? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun >> Microsystems\\ >> for the registry key? >> [ ] Yes >> [ ] No - ARC review required >> Is the project's stored location >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\> id>\Path? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.1.2 Share and Sharable >> Does the module include any components that are used or shared by >> other projects? >> [ ] Yes >> [ x] No >> If yes are these components packaged to be shared with the other FOSS? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> Are these components already in the Solaris WOS? >> [ ] Yes >> [ ] No - continue with next section (section 3.2) >> If yes are these newer versions being delivered? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the newer versions replacing the existing versions? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.2 Exported Libraries >> Are libraries being delivered by this project? >> [ x] Yes >> [ ] No - continue with next section (section 3.3) >> Are 64-bit versions of the libraries being delivered? >> [ ] Yes >> [ x] No - ARC review required >> Are static versions of the libraries being delivered? >> [ ] Yes - ARC review required >> [x ] No >> >> 3.3 Services and the /etc Directory >> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >> [ ] Yes - ARC review required >> [ x] No >> Does the project integrate any new entries into /etc/inittab or >> /etc/inetd.conf? >> [ ] Yes - ARC review required >> [ x] No >> Does the project integrate any private non-public files into >> /etc/default >> or /etc/ configuration files? >> [ ] Yes - ARC review required >> [ x] No >> Does the service manifests method context grant rights above that >> of the noaccess user and basic privilege set? >> [ ] Yes - ARC review required >> [ x] No >> >> 3.4 Security >> 3.4.1 Secure By Default >> (see >> http://opensolaris.org/os/community/arc/policies/secure-by-default/ for >> details) >> (see >> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >> details) >> (see parts of >> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >> addtional details) >> Are there any network services provided by this project? >> [ ] Yes >> [ x] No - continue with the next section (section 3.4.2) >> Are network services enabled by default? >> [ ] Yes - ARC review required >> [ ] No >> [ ] N/A >> Are network services automatically enabled by the project during >> installation? >> [ ] Yes - ARC review required >> [ ] No >> [ ] N/A >> Are inbound network communications denied by default? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> Is inbound data checked to prevent content-based attacks? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> Is the outbound receiver authenticated? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> Is the receiver authenticated prior to receiving any sensitive >> outbound communication? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> 3.4.2 Authorization >> (see >> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> for details) >> Are there any setuid/setgid privileged binaries in the project? >> [ ] Yes - ARC review required >> [ x] No - continue with next section (section 3.4.3) >> If yes then are the setuid/setgid privileges handled by the use of >> roles? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.3 Auditing >> (see >> http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 for >> details) >> Does this component contain administrative or security enforcing >> software? >> [ ] Yes - ARC review required >> [ x] No - continue to next section (section 3.4.4) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >> for details) >> Do the components create audit logs detailing what took place >> including what event >> took place, who was involved, when the event took place? >> [ ] Yes - ARC contract and Audit project team review required >> [ ] No - ARC review required >> 3.4.4 Authentication >> (see http://opensolaris.org/os/community/arc/policies/PAM/) >> Do the components contain any authentication code? >> [ ] Yes >> [ x] No - continue to next section (section 3.4.5) >> If yes do the components use PAM (plugable authentication modules) >> for authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes is a single PAM session maintained during authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the components sufficiently privileged to allow the >> requested operations (authentication, password change, process >> credential manipulation, audit state initialization)? >> [ ] Yes - briefly describe below >> [ ] No - ARC review required >> >> 3.4.5 Passwords >> (see >> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >> for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [ x] No - continue to next section (section 3.4.6) >> If yes are these passwords entered via the CLI or environment? >> [ ] Yes - ARC review required >> [ ] No >> Are passwords stored within the file system for the component? >> [ ] Yes >> [ ] No - continue to next section (section 3.4.6) >> If yes are the permissions on the file such to protect exposing >> the password(s)? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.6 General Security Questions >> (see >> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >> for details) >> Are there any network protocols used by this project? >> [ ] Yes >> [ x] No - continue with the next section (section 3.5) >> Do the components use standard network protocols? >> [ ] Yes >> [ ] No - ARC review required >> Do network services for the project make decisions based upon >> user, host or service >> identities? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> Do the components make use of secret information during >> authentication and/or >> authorization? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> >> 3.5 Networking >> Do the components access the network? >> [ ] Yes >> [ x] No - continue with the next section (section 3.6) >> If yes do the components support IPv6? >> [ ] Yes [ ] No - ARC review required >> >> 3.6 Core Solaris Components >> Do the components of this project compete with or duplicate core >> Solaris components? >> [ ] Yes - ARC review required >> [ x] No Examples of Core Solaris Components include but >> are not limited to: >> Secure By Default >> Authorizations >> PAM -- Plugable Authentication Module >> Privilege >> PRM -- Process Rights Management -- Privilege >> Audit >> xVm -- Virtualization >> zones / Solaris Containers >> PRM -- Process Rights Management >> RBAC -- Role Based Access Control >> TX / Trusted Extensions >> ZFS >> SMF -- Service Management Facility >> FMA -- Fault Management Architecture >> SCF -- Smart Card Facility >> IPsec >> 4.0 Interfaces >> (see >> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >> for details) >> >> See Fast Track >> >> >> >> -- Ken Erickson | kene@Eng.Sun.COM Sun Microsystems, Inc., Solaris OS Engineering | Voice: (847)663-9471 4150 Network Circle MS UITA01 | Cell: (312)401-6254 Santa Clara, CA 95054 | If you want me to read something, don't send it as a StarOffice or HTML attachment. From ken.erickson@sun.com Thu Nov 13 12:32:07 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mADKW6Mk018851 for ; Thu, 13 Nov 2008 12:32:07 -0800 (PST) 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 mADKW1xX016295; Thu, 13 Nov 2008 20:32:02 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 <0KAA00H05H1D7D00@nwk-avmta-2.sfbay.sun.com>; Thu, 13 Nov 2008 12:32:01 -0800 (PST) Received: from macolaris.kens.net ([10.7.251.241]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAA00G36H193Z30@nwk-avmta-2.sfbay.sun.com>; Thu, 13 Nov 2008 12:31:58 -0800 (PST) Received: from [IPv6:::1] (localhost [IPv6:::1]) by macolaris.kens.net (8.14.3+Sun/8.14.3) with ESMTP id mADKVuoe108726; Thu, 13 Nov 2008 14:31:57 -0600 (CST) Date: Thu, 13 Nov 2008 14:31:56 -0600 From: Ken Erickson Subject: Re: LSARC/2008/706 - sox In-reply-to: <491C8C2F.6010104@Sun.COM> To: Darren J Moffat Cc: Margot Miller , LSARC-ext@sun.com, "Garrett D'Amore" Reply-to: ken.erickson@sun.com Message-id: <491C8EBC.90306@sun.com> Organization: Sun Microsystems, Inc. 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: <491BB5C9.3000601@sun.com> <491BF74E.8080405@Sun.COM> <491C8A0F.2@sun.com> <491C8C2F.6010104@Sun.COM> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 1168 Darren J Moffat wrote: > Ken Erickson wrote: >> Darren J Moffat wrote: >>> How does this case fit with PSARC 2008/318 ? >>> >>> I believe there shouldn't be any interaction between the two but I >>> want clarification of that since it has been a very long time since I >>> last used sox (probably about 11 years). >>> >>> -- >>> Darren J Moffat >> >> There should be no interaction between the two. Sox can work even in the >> absence of any audio hardware, so long as you aren't trying to play >> the audio files. It does not rely on any platform specific hardware. > > So sox can play audio files ? So there is an interaction between sox > and the choice of audio API either SADA or OSS ? > sox does the equivalent of "cat audiofile > /dev/audio". So I don't think a particular audio api is relevant. -- Ken Erickson | kene@Eng.Sun.COM Sun Microsystems, Inc., Solaris OS Engineering | Voice: (847)663-9471 4150 Network Circle MS UITA01 | Cell: (312)401-6254 Santa Clara, CA 95054 | If you want me to read something, don't send it as a StarOffice or HTML attachment. From Joerg.Barfurth@Sun.COM Fri Nov 21 04:23:06 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mALCN6XW015542 for ; Fri, 21 Nov 2008 04:23:06 -0800 (PST) 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 mALCN5Js063283 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 21 Nov 2008 05:23:05 -0700 (MST) 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 <0KAO00E01NQHIR00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 21 Nov 2008 04:23:05 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAO005YZNQG8T70@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 21 Nov 2008 04:23:05 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mALCN4Fc012788 for ; Fri, 21 Nov 2008 12:23:04 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAO00I01MEEWR00@fe-emea-10.sun.com> (original mail from Joerg.Barfurth@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 21 Nov 2008 12:23:04 +0000 (GMT) Received: from [10.16.46.62] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAO00FYRNQ4WX40@fe-emea-10.sun.com>; Fri, 21 Nov 2008 12:22:53 +0000 (GMT) Date: Fri, 21 Nov 2008 13:22:59 +0100 From: Joerg Barfurth Subject: Re: LSARC/2008/706 - sox In-reply-to: <491C8EBC.90306@sun.com> Sender: Joerg.Barfurth@Sun.COM To: Ken.Erickson@Sun.COM Cc: Darren J Moffat , Margot Miller , "Garrett D'Amore" , LSARC-ext@Sun.COM Message-id: <4926A823.6020308@sun.com> Organization: Sun Microsystem - Desktop MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <491BB5C9.3000601@sun.com> <491BF74E.8080405@Sun.COM> <491C8A0F.2@sun.com> <491C8C2F.6010104@Sun.COM> <491C8EBC.90306@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081014) Status: RO Content-Length: 517 Ken Erickson schrieb: > sox does the equivalent of "cat audiofile > /dev/audio". So I don't > think a particular audio api is relevant. > Does it use /dev/audio or getenv("AUDIODEV")? - Jörg -- Joerg Barfurth phone: +49 40 23646662 / x66662 Software Engineer mailto:joerg.barfurth@sun.com Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/ From ken.erickson@sun.com Fri Nov 21 08:25:10 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mALGPAbC007791 for ; Fri, 21 Nov 2008 08:25:10 -0800 (PST) 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 mALGP5U4019486; Fri, 21 Nov 2008 08:25:07 -0800 (PST) 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 <0KAO00M0LYXTYM00@nwk-avmta-1.sfbay.Sun.COM>; Fri, 21 Nov 2008 08:25:05 -0800 (PST) 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 <0KAO00HFEYXPIM40@nwk-avmta-1.sfbay.Sun.COM>; Fri, 21 Nov 2008 08:25:01 -0800 (PST) Received: from macolaris.kens.net (punchin-kene.SFBay.Sun.COM [10.7.251.241]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mALGP0Pa458009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Nov 2008 08:25:01 -0800 (PST) Received: from [IPv6:::1] (localhost [IPv6:::1]) by macolaris.kens.net (8.14.3+Sun/8.14.3) with ESMTP id mALGOuPu107936; Fri, 21 Nov 2008 10:24:56 -0600 (CST) Date: Fri, 21 Nov 2008 10:24:56 -0600 From: Ken Erickson Subject: Re: LSARC/2008/706 - sox In-reply-to: <4926A823.6020308@sun.com> To: Joerg Barfurth Cc: Darren J Moffat , Margot Miller , "Garrett D'Amore" , LSARC-ext@sun.com Reply-to: ken.erickson@sun.com Message-id: <4926E0D8.6030803@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <491BB5C9.3000601@sun.com> <491BF74E.8080405@Sun.COM> <491C8A0F.2@sun.com> <491C8C2F.6010104@Sun.COM> <491C8EBC.90306@sun.com> <4926A823.6020308@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 687 It first attempts to do getenv("AUDIODEV") and if that is not set it uses "/dev/audio". -ken Joerg Barfurth wrote: > Ken Erickson schrieb: > >> sox does the equivalent of "cat audiofile > /dev/audio". So I don't >> think a particular audio api is relevant. >> > > Does it use /dev/audio or getenv("AUDIODEV")? > > - Jörg > > -- Ken Erickson | kene@Eng.Sun.COM Sun Microsystems, Inc., Solaris OS Engineering | Voice: (847)663-9471 4150 Network Circle MS UITA01 | Cell: (312)401-6254 Santa Clara, CA 95054 | If you want me to read something, don't send it as a StarOffice or HTML attachment. From margot.miller@sun.com Mon Nov 24 10:46:26 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mAOIkPLq017027 for ; Mon, 24 Nov 2008 10:46:26 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mAOIkCgM008313; Mon, 24 Nov 2008 18:46:23 GMT 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 <0KAU00K1JPHAPP00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 24 Nov 2008 10:46:22 -0800 (PST) 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 <0KAU0032NPHA0EA0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 24 Nov 2008 10:46:22 -0800 (PST) Received: from [10.7.250.155] (punchin-client-10-7-250-155.SFBay.Sun.COM [10.7.250.155]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mAOIk30k933751; Mon, 24 Nov 2008 10:46:09 -0800 (PST) Date: Mon, 24 Nov 2008 10:44:09 -0800 From: Margot Miller Subject: Re: LSARC/2008/706 - sox In-reply-to: <491BB5C9.3000601@sun.com> To: lsarc-ext@sun.com Cc: Ken Erickson Message-id: <492AF5F9.5050801@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: <491BB5C9.3000601@sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 14197 This case is now closed/approved as all issues have been addressed and it has timed out. Thanks Margot Margot Miller wrote: > All, > > I am sponsoring the following fast track for Ken. Timeout is > THURSDAY Nov 20th. Requesting patch binding. Man pages > are in the case directory. > > Below is the proposal and FOSS checklist. > > Thanks > Margot > > ---------------------------------------------------------------------------------------------------------- > > > Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > sox > 1.2. Name of Document Author/Supplier: > Author: Ken Erickson > 1.3 Date of This Document: > 30 October 2008 > 2. Project Summary > 2.1. Project Description > > This project delivers the sox package, version 14.0.1, > an audio file conversion and sound effects utility. > 4. Technical Description > > sox (SOund eXchange) is a command line utility, and an associated > set of library routines, which convert many different digital > audio formats, and can process audio files to add various > sound effects. > 5. Interfaces > > Exported interface > Classification Interface type > =============================== ============== ============== > SUNWsound-exchange > Uncommitted Package name > /usr/bin/sox > Uncommitted command > > /usr/include/sox.h > Uncommitted header > /usr/include/soxsdtint.h > Uncommitted header > /usr/lib/libsox.so.0.0.0 > Uncommitted library > > /usr/lib/libsox.so.0 > Uncommitted symlink > /usr/lib/libsox.so > Uncommitted symlink > /usr/lib/libsfx.so.0.0.0 > Uncommitted library > /usr/lib/libsfx.so.0 > Uncommitted symlink > > /usr/lib/libsfx.so > Uncommitted symlink > /usr/lib/sox > Uncommitted directory > /usr/lib/sox/*.so.0.0.0 > Project Private conversion libraries > > > > 5a. Manpages > > /usr/share/man/man1/sox.1 Uncommitted manpage > /usr/share/man/man3/libsox.3 Uncommitted manpage > /usr/share/man/man4/soxformat.4 Uncommitted manpage > /usr/share/man/man5/soxeffect.5 Uncommitted manpage > /usr/share/man/man5/soxexam.5 Uncommitted manpage > > 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 > > ---------------------------------------------------------------------------------------------------------- > > FCL--FOSS Check List > 1.0 Project Information > 1.1 Name of project/component > > sox > > 1.2 Author of document > > Ken Erickson > > 2.0 Project Summary > 2.1 Project Description > > 2.2 Release binding > What is is the release binding? > (see > http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [ ] Minor > [ X] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [ ] Yes > [ x] No > > 2.4 Originating Community > 2.4.1 Community Name > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [ x] Monitoring > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [ x] Yes [ ] No - briefly explain > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [ x] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris > Software > (see > http://opensolaris.org/os/community/arc/policies/install-locations/ > for details) > Does this project follow the Install Locations best practice? > [ x] Yes [ ] No - ARC review required > Does this project install into /usr under > [sbin|bin|lib|include|man|share]? > [ x] Yes > [ ] No or N/A > Does this project install into /opt? > [ ] Yes - explain below > [ ] No or N/A > Does this project install into a different directory structure? > [ ] Yes - ARC review required > [ ] No or N/A > Do any of the components of this project conflict with anything > under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ > for details) > [ ] Yes - explain below > [ x] No > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [ ] No > 3.1.1W Windows Installation - section only required for Windows > Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a drive>:\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun > Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\ id>\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [ ] Yes > [ x] No > If yes are these components packaged to be shared with the other > FOSS? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Are these components already in the Solaris WOS? > [ ] Yes > [ ] No - continue with next section (section 3.2) > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [ x] Yes > [ ] No - continue with next section (section 3.3) > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ x] No - ARC review required > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [x ] No > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [ x] No > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [ x] No > Does the project integrate any private non-public files into > /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [ x] No > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [ x] No > > 3.4 Security > 3.4.1 Secure By Default (see > http://opensolaris.org/os/community/arc/policies/secure-by-default/ > for details) > (see > http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for > details) > (see parts of > http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [ x] No - continue with the next section (section 3.4.2) > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > Are network services automatically enabled by the project during > installation? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > Is the receiver authenticated prior to receiving any sensitive > outbound communication? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > 3.4.2 Authorization > (see > http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [ x] No - continue with next section (section 3.4.3) > If yes then are the setuid/setgid privileges handled by the use > of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see > http://opensolaris.org/os/community/arc/policies/audit-policy/ for > details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for > details) > Does this component contain administrative or security enforcing > software? > [ ] Yes - ARC review required > [ x] No - continue to next section (section 3.4.4) > (see > http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place > including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [ x] No - continue to next section (section 3.4.5) > If yes do the components use PAM (plugable authentication > modules) for authentication? > [ ] Yes > [ ] No - ARC review required > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > If yes are the components sufficiently privileged to allow the > requested operations (authentication, password change, process > credential manipulation, audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see > http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ > for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [ x] No - continue to next section (section 3.4.6) > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > If yes are the permissions on the file such to protect exposing > the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see > http://opensolaris.org/os/community/arc/bestpractices/security-questions/ > for details) > Are there any network protocols used by this project? > [ ] Yes > [ x] No - continue with the next section (section 3.5) > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > Do network services for the project make decisions based upon > user, host or service > identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > Do the components make use of secret information during > authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [ x] No - continue with the next section (section 3.6) > If yes do the components support IPv6? > [ ] Yes [ ] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [ x] No Examples of Core Solaris Components include but > are not limited to: > Secure By Default > Authorizations > PAM -- Plugable Authentication Module > Privilege > PRM -- Process Rights Management -- Privilege > Audit > xVm -- Virtualization > zones / Solaris Containers > PRM -- Process Rights Management > RBAC -- Role Based Access Control > TX / Trusted Extensions > ZFS > SMF -- Service Management Facility > FMA -- Fault Management Architecture > SCF -- Smart Card Facility > IPsec > 4.0 Interfaces > (see > http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ > for details) > > See Fast Track > > >