From James.Gates@sun.com Fri Aug 29 13:42:20 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 m7TKgJ8Y016952 for ; Fri, 29 Aug 2008 13:42:19 -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 m7TKgG6g018792 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Sat, 30 Aug 2008 04:42:18 +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 <0K6D00B01QUFUA00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.Com); Fri, 29 Aug 2008 13:42:15 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K6D005M6QUE3F70@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.Com); Fri, 29 Aug 2008 13:42:15 -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 m7TKgDfv013934 for ; Fri, 29 Aug 2008 20:42:13 +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 <0K6D00H01QQZ2Z00@fe-emea-10.sun.com> (original mail from James.Gates@Sun.COM) for lsarc-ext@Sun.Com (ORCPT lsarc-ext@Sun.Com); Fri, 29 Aug 2008 21:42:13 +0100 (BST) Received: from [192.168.1.102] ([129.150.65.23]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K6D00H39QTYRZ00@fe-emea-10.sun.com> for lsarc-ext@Sun.Com (ORCPT lsarc-ext@Sun.Com); Fri, 29 Aug 2008 21:42:13 +0100 (BST) Date: Fri, 29 Aug 2008 16:41:14 -0400 From: James Gates Subject: LSARC/2008/556 Integrate PROJ.4 Sender: James.Gates@sun.com To: lsarc-ext@sun.com Cc: =?ISO-8859-15?Q?Magne_M=E6hre?= Message-id: <48B85EEA.5030609@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_pLX5gOigKHHcDuAGWE/kDg)" X-Accept-Language: en-us, en X-PMX-Version: 5.4.1.325704 User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 24140 This is a multi-part message in MIME format. --Boundary_(ID_pLX5gOigKHHcDuAGWE/kDg) Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT I'm sponsoring this case for Magne Mahre. It is closed, automatically approved on account of the FOSS checklist [1] having no questions answered with "ARC review required". The completed FOSS checklist is attached with the onepager and also located in the case directory. [1] http://sac.sfbay/arc/LSARC/2008/061/proposal.txt -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql --Boundary_(ID_pLX5gOigKHHcDuAGWE/kDg) Content-type: text/plain; name=proj4_onepager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=proj4_onepager.txt Template Version: @(#)onepager.txt 1.31 07/08/08 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Integrate PROJ.4 1.2. Name of Document Author/Supplier: Magne Mahre 1.3. Date of This Document: 05/15/2008 2008-05-15 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The Community you expect to review your project: Databases 1.4.2. The ARC(s) you expect to review your project: LSARC 1.5. Email Aliases: 1.5.2. Responsible Engineer: magne.mahre@sun.com 1.5.4. Interest List: databases-discuss@sun.com 2. Project Summary 2.1. Project Description: Integrate PROJ.4, a cartographic projection filter and library, into OpenSolaris and Solaris. 3. Business Summary 3.1. Problem Area: We are providing PROJ.4 primarily as support library for PostGIS, the spatial data extension to the PostgreSQL RDBMS. PROJ.4 provides projection support for PostGIS. The integration is a "best-effort" job, based on 3rd party open source code. 3.2. Market/Requester: PostGIS has been requested for inclusion as part of the Database strategy. 4. Technical Description: 4.1. Details: PROJ.4 is a package that provide functions and a library for forward and inverse transformation between different cartographic projections. It is widely used by open source GIS applications. Links: http://www.remotesensing.org/proj/ 4.5. Interfaces: Provided interfaces: package: SUNWproj uncommitted include files: /usr/include/nad_list.h uncommitted /usr/include/org_proj4_Projections.h uncommitted /usr/include/proj_api.h uncommitted /usr/include/projects.h project private user binaries: /usr/bin/cs2cs uncommitted /usr/bin/geod uncommitted /usr/bin/invgeod uncommitted /usr/bin/invproj uncommitted /usr/bin/nad2bin uncommitted /usr/bin/nad2nad uncommitted /usr/bin/proj uncommitted libraries: /usr/lib/libproj.so.0.5.4 uncommitted /usr/lib/64/libproj.so.0.5.4 uncommitted man files: /usr/share/man/man1/cs2cs.1 uncommitted /usr/share/man/man1/geod.1 uncommitted /usr/share/man/man1/nad2nad.1 uncommitted /usr/share/man/man1/proj.1 uncommitted /usr/share/man/man3/pj_init.3 uncommitted support file / doc.: /usr/share/proj (directory with support files) uncomm. API: see man file 'pj_init' uncommitted Imported interfaces: libm.so.2 libc.so.1 5. Reference Documents: Project home page: http://www.remotesensing.org/proj/ User manual: ftp://ftp.remotesensing.org/proj/OF90-284.pdf 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW / SFWNV 6.5. ARC review type: Fasttrack 6.6. ARC Exposure: open 6.6.1. Rationale: Part of OpenSolaris --Boundary_(ID_pLX5gOigKHHcDuAGWE/kDg) Content-type: text/plain; name=proj4-foss-checklist.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=proj4-foss-checklist.txt FCL--FOSS Check List 0. Introduction 0.1 Document History Version Author Changes Date 0.1 John Fischer Initial Draft 01/11/2008 0.2 John Fischer Modified based upon feedback from ARC members 01/29/2008 0.3 John Fischer Modified based upon feedback during committee 02/12/2008 review 0.4 John Fischer Modified based upon SAC review feedback 04/01/2008 0.5 John Fischer Modified based upon LSARC business meeting 06/10/2008 adding familiarity question and mod dates. 0.6 John Fischer Modified based upon user feedback about 06/20/2008 sections that were unanswerable. 0.2 Purpose Architecture review at Sun has allowed the company to evolve our projects within multiple disjoint groups while still maintaining a cohesive product line. Each architecture review was conducted within Sun's control. With the advent of Free Open Source Software processes the control that Sun as a company can wield has been diminished. Now that Sun is moving to a more fluid delivery mechanism with project Indiana we need to evolve the architecture review process. This document is meant to aid in the architecture review process. Each new project must complete this check list to help ensure that the overall resulting product conforms to Sun product standards. If the project deviates from these standards further review would be necessary by an architecture review committee. After the check list is completed the project team should be able to determine if a project can be automatically approved. This will occur if all checks result in no "ARC review required" answers. A committee member will assist the project team in filing the automatically approved fast track. An automatically approved fast track is still required in order to record the interfaces for future reference. If the project needs to have further review then follow the regular process for getting projects reviewed. 1.0 Project Information 1.1 Name of project/component PROJ.4 1.2 Author of document Magne Mahre 2.0 Project Summary 2.1 Project Description Integration of the PROJ.4 cartographic projection library into Solaris/OpenSolaris. PROJ.4 is used in several GIS applications, and it is a required component for PostGIS, the GIS plugin for PostgreSQL. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [X] Major [ ] Minor [ ] 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 Open Source Geospatial Foundation 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 [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] 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 [X] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] 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? [X] Yes [ ] No If yes are these components packaged to be shared with the other FOSS? [X] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [X] 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? [X] Yes [ ] 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) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ------------------- --------------------------- C API Uncommitted see pj_init.3 below SUNWproj4 Committed Package for PROJ.4 /usr/bin/cs2cs Uncommitted /usr/bin/geod Uncommitted /usr/bin/invgeod Uncommitted symlink to geod /usr/bin/invproj Uncommitted symlink to proj /usr/bin/nad2proj Uncommitted /usr/bin/nad2nad Uncommitted /usr/bin/proj Uncommitted /usr/include/proj_api.h Uncommitted Public include file for API /usr/include/projects.h Project Private Project internal include file /usr/include/nad_list.h Uncommitted /usr/include/org_proj4_Projections.h Uncommitted Java bindings /usr/lib/libproj.so.0.5.4 Uncommitted /usr/lib/libproj.so.0 Uncommitted Symbolic link /usr/lib/libproj.so Uncommitted Symbolic link /usr/lib/64/libproj.so.0.5.4 Uncommitted /usr/lib/64/libproj.so.0 Uncommitted Symbolic link /usr/lib/64/libproj.so Uncommitted Symbolic link /usr/share/man/man1/cs2cs.1 Uncommitted /usr/share/man/man1/geod.1 Uncommitted /usr/share/man/man1/nad2nad.1 Uncommitted /usr/share/man/man1/proj.1 Uncommitted /usr/share/man/man3/pj_init.3 Uncommitted C API /usr/share/proj Uncommitted Project extra files and doc. 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- libc Committed libm Committed Note--Remove all Wizzy, Bang, Slushy, Cherry Flavor, Stingy references above as these are simply examples Brief Interface Classifications - See Appendix C for definitions Volatile - interfaces are fluid and will follow a rapidly changing community Uncommitted - interfaces are still evolving in the community and might follow the community Committed - interfaces are stable in the community Project Private - no review required, just document in table Contracted (interface modifier) - further review required Appendix A - References 1. Solaris Installation Locations Policy http://opensolaris.org/os/community/arc/policies/install-locations/ 2. /usr/gnu Installation ARC case http://opensolaris.org/os/community/arc/caselog/2007/047/ 3. Secure By Default Policy http://opensolaris.org/os/community/arc/policies/secure-by-default/ 4. Network Install Time Securityuy Policy http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ 5. Adding RBAC Authorizations Policy http://opensolaris.org/os/community/arc/bestpractices/rbac-auths/ 6. When to use setuid -vs- RBAC roles and profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and 7. Building RBAC Rights Profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ 8. Solaris Audit Policy http://opensolaris.org/os/community/arc/policies/audit-policy/ 9. Security questionaire http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 10. Interface Taxonomy http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ 11. Plugable Authentication Modules -- PAM http://opensolaris.org/os/community/arc/policies/PAM/ 12. Reusable Passwords In Command Line Arguments and Environment Variables http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ 13. Storing Reusable Passwords on a Filesystem http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 14. Release Taxonomy http://opensolaris.org/os/community/arc/policies/release-taxonomy/ 15. Service Management Facility (SMF) usage http://opensolaris.org/os/community/arc/policies/SMF-policy/ Appendix B - Suggested case materials 1. man pages 2. SMF manifests 3. links to contracts Appendix C - Definitions Submitter an agent responsible for creation of an ARC project along with the materials describing that project. Owner the ARC agent responsible for shepherding the case through review and ensuring a formal opinion is written where required. Maintainer an agent responsible for releasing new versions of a program, typically the "main" contributor or person incharge of making Architectural decisions for the project Contributor an agent who make contributions to a project, typically has a voice in making Architectural decisions for the project Monitoring an agent who is only following the changes made in the community and has no Architectural input into the project Volatile* interfaces that are very fluid and typically follow the originating community. Typically these interfaces can not be imported by other projects. Uncommitted* interfaces that are still evolving but will most likely be present from release to release. Committed* interfaces that are stable and with Sun guaranteeing some level of compatibility from release to release. Project Private* interfaces that are exposed only to or intended to be used only by the project being reviewed. These interfaces can not be imported by other projects. Not-An-Interface* components that are not interfaces. Contracted* (interface modifier) - ARC review of Contract required interfaces that do not allow another project to import can be *Note: see http://opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details --Boundary_(ID_pLX5gOigKHHcDuAGWE/kDg)--