From Fri Nov 14 14:28:24 2008 Date: Fri, 14 Nov 2008 14:28:24 -0800 (PST) From: Postmaster Subject: Message from mail server Content-Length: 95 Mime-Version: 1.0 Status: RO X-IMAP: 1226701704 3 Delete. This is a system message. --END+PSEUDO-- From sh162551@sac.sfbay.sun.com Mon Nov 3 00:06:59 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 mA386x19006915 for ; Mon, 3 Nov 2008 00:06:59 -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 mA386wYJ019974; Mon, 3 Nov 2008 01:06:59 -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 <0K9Q00F01ZVNJ800@nwk-avmta-1.sfbay.Sun.COM>; Mon, 03 Nov 2008 00:06:59 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K9Q008J7ZVMFUC0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 03 Nov 2008 00:06:58 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mA386uCI049653; Mon, 03 Nov 2008 00:06:56 -0800 (PST) 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 mA386tcR006909; Mon, 03 Nov 2008 00:06:55 -0800 (PST) Received: (from sh162551@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mA386t2R006904; Mon, 03 Nov 2008 00:06:55 -0800 (PST) Date: Mon, 03 Nov 2008 00:06:55 -0800 (PST) From: Shi-Ying Irene Huang Subject: Libical for OpenSolaris [LSARC/2008/677 FastTrack timeout 11/10/2008] To: LSARC-ext@sun.com Cc: jedy.wang@sun.com, jeff.cai@sun.com Message-id: <200811030806.mA386t2R006904@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Content-Length: 13122 Status: RO X-Status: $$$$ X-UID: 0000000001 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Libical for OpenSolaris 1.2. Name of Document Author/Supplier: Author: Jedy Wang 1.3 Date of This Document: 03 November, 2008 4. Technical Description FCL--FOSS Check List 1.0 Project Information 1.1 Name of project/component libical 1.2 Author of document Jedy Wang 2.0 Project Summary 2.1 Project Description Libical is an Open Source (MPL/LGPL) implementation of the IETF's iCalendar Calendaring and Scheduling protocols. (RFC 2445, 2446, and 2447). The latest code is available at http://sourceforge.net/projects/freeassociation/. Libical is used by Evolution mail client. Before a forked version was shipped in Evolution source and Evolution links it statically. But now, the Evolution community decided to use the official release of libical and we plan to make this change for the GNOME 2.26 release. So we will ship libical in Solaris too to make Evolution continue to work. The libical source is licensed under Mozilla Public License 1.0 or GNU Library General Public License 2.1. But for Solaris distribution, we will use LGPL 2.1. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name freeassociation 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? [ ] Yes [ ] No - ARC review required [X] N/A Are these components already in the Solaris WOS? [X] Yes [ ] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [X] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [X] 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 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ------------------- --------------------------- SUNWlibical Uncommitted package name /usr/include/libical/*.h Volatile libical C API /usr/lib/libical.so.0 Volatile library of libical /usr/lib/libicalss.so.0 Volatile library to support store iCal component data to disk in a variety of ways /usr/lib/libicalvcal.so.0 Volatile library to support vCalendar. /usr/lib/pkgconfig/libical.pc Uncommitted pkgconfig file for libical 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- zoneinfo timezone selection Project Private LSARC/2001/015 [1] Berkeley database Volatile LSARC/2007/299 5.0 references [1] Contract with LSARC/2001/015 : http://sac.eng/LSARC/2001/015/contract-2001-015-02 http://sac.eng/LSARC/2001/015/contract-2001-015-03 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: Desktop 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Irene.Huang@Sun.COM Mon Nov 3 00:09:36 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 mA389aqP006929 for ; Mon, 3 Nov 2008 00:09:36 -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 mA389Z3D011254 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 3 Nov 2008 00:09:36 -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 <0K9Q00F01ZZZS900@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 03 Nov 2008 00:09:35 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K9Q00846ZZYFUD0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 03 Nov 2008 00:09:35 -0800 (PST) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mA389YaT012223 for ; Mon, 03 Nov 2008 08:09:34 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K9Q00F01ZVCE400@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Mon, 03 Nov 2008 16:09:34 +0800 (SGT) Received: from [129.158.217.182] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K9Q00IIGZZW5XCH@mail-apac.sun.com>; Mon, 03 Nov 2008 16:09:33 +0800 (SGT) Date: Mon, 03 Nov 2008 16:09:24 +0800 From: Irene Huang Subject: Re: Libical for OpenSolaris [LSARC/2008/677 FastTrack timeout 11/10/2008] In-reply-to: <200811030806.mA386t2R006904@sac.sfbay.sun.com> Sender: Irene.Huang@Sun.COM To: Shi-Ying Irene Huang Cc: LSARC-ext@Sun.COM, jedy.wang@Sun.COM, jeff.cai@Sun.COM Message-id: <490EB1B4.5070404@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_nbe3uI8tCA/PrZZrzkE8nw)" X-PMX-Version: 5.4.1.325704 References: <200811030806.mA386t2R006904@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Content-Length: 18840 Status: RO X-Status: $$$$ X-UID: 0000000002 This is a multi-part message in MIME format. --Boundary_(ID_nbe3uI8tCA/PrZZrzkE8nw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi, all I am sponsoring this case, which is due timeout on 11/10/2008. Attached are the pkgmaps. Thanks --Irene Shi-Ying Irene Huang wrote: > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Libical for OpenSolaris > 1.2. Name of Document Author/Supplier: > Author: Jedy Wang > 1.3 Date of This Document: > 03 November, 2008 > 4. Technical Description > FCL--FOSS Check List > > 1.0 Project Information > 1.1 Name of project/component > libical > > 1.2 Author of document > Jedy Wang > > 2.0 Project Summary > 2.1 Project Description > Libical is an Open Source (MPL/LGPL) implementation of the IETF's > iCalendar Calendaring and Scheduling protocols. (RFC 2445, 2446, and > 2447). The latest code is available at > http://sourceforge.net/projects/freeassociation/. > > Libical is used by Evolution mail client. Before a forked version was > shipped in Evolution source and Evolution links it statically. But now, > the Evolution community decided to use the official release of libical > and we plan to make this change for the GNOME 2.26 release. So we will > ship libical in Solaris too to make Evolution continue to work. > > The libical source is licensed under Mozilla Public License 1.0 or GNU > Library General Public License 2.1. But for Solaris distribution, we > will use LGPL 2.1. > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [X] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [X] Yes > [ ] No > > 2.4 Originating Community > 2.4.1 Community Name > freeassociation > > 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? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Are these components already in the Solaris WOS? > [X] Yes > [ ] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [X] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [X] 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 > > 4.0 Interfaces > (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) > 4.1 Exported Interfaces > > Interface Name Classification Comments > --------------------------- ------------------- --------------------------- > SUNWlibical Uncommitted package name > /usr/include/libical/*.h Volatile libical C API > /usr/lib/libical.so.0 Volatile library of libical > /usr/lib/libicalss.so.0 Volatile library to support > store iCal component > data to disk in a > variety of ways > /usr/lib/libicalvcal.so.0 Volatile library to support > vCalendar. > /usr/lib/pkgconfig/libical.pc Uncommitted pkgconfig file for > libical > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > zoneinfo timezone selection Project > Private LSARC/2001/015 [1] > Berkeley database Volatile LSARC/2007/299 > > 5.0 references > > [1] Contract with LSARC/2001/015 : http://sac.eng/LSARC/2001/015/contract-2001-015-02 > http://sac.eng/LSARC/2001/015/contract-2001-015-03 > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Desktop > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > --Boundary_(ID_nbe3uI8tCA/PrZZrzkE8nw) Content-type: text/plain; name=pkgmap-libical.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=pkgmap-libical.txt : 1 2661 1 i copyright 135 12587 1225351655 1 i depend 237 19584 1225351655 1 d none lib 0755 root bin 1 s none lib/libical.so=libical.so.0 1 s none lib/libical.so.0=libical.so.0.40.0 1 f none lib/libical.so.0.40.0 0755 root bin 907680 29269 1225351651 1 s none lib/libicalss.so=libicalss.so.0 1 s none lib/libicalss.so.0=libicalss.so.0.40.0 1 f none lib/libicalss.so.0.40.0 0755 root bin 281104 25393 1225351652 1 s none lib/libicalvcal.so=libicalvcal.so.0 1 s none lib/libicalvcal.so.0=libicalvcal.so.0.40.0 1 f none lib/libicalvcal.so.0.40.0 0755 root bin 162116 51475 1225351653 1 i pkginfo 629 52041 1225351655 --Boundary_(ID_nbe3uI8tCA/PrZZrzkE8nw) Content-type: text/plain; name=pkgmap-libical-devel.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=pkgmap-libical-devel.txt : 1 834 1 i copyright 135 12587 1225351655 1 i depend 201 16850 1225351655 1 d none include 0755 root bin 1 d none include/libical 0755 root bin 1 f none include/libical/ical.h 0644 root bin 134370 43287 1225351649 1 f none include/libical/icalarray.h 0644 root bin 1614 61128 1223260931 1 f none include/libical/icalattach.h 0644 root bin 1854 28096 1223260931 1 f none include/libical/icalcalendar.h 0644 root bin 1795 19487 1223260933 1 f none include/libical/icalclassify.h 0644 root bin 1166 27193 1223260933 1 f none include/libical/icalcluster.h 0644 root bin 1901 33581 1223260933 1 f none include/libical/icalcomponent.h 0644 root bin 10279 1181 1223260931 1 f none include/libical/icalderivedparameter.h 0644 root bin 13390 56244 1225351649 1 f none include/libical/icalderivedproperty.h 0644 root bin 30898 9934 1225351649 1 f none include/libical/icalderivedvalue.h 0644 root bin 12107 56399 1225351649 1 f none include/libical/icaldirset.h 0644 root bin 3276 23779 1223260933 1 f none include/libical/icaldirsetimpl.h 0644 root bin 1472 51458 1223260933 1 f none include/libical/icalduration.h 0644 root bin 1865 30017 1223260931 1 f none include/libical/icalenums.h 0644 root bin 5584 48721 1223260931 1 f none include/libical/icalerror.h 0644 root bin 5058 28254 1223260931 1 f none include/libical/icalfileset.h 0644 root bin 4165 32206 1223260933 1 f none include/libical/icalfilesetimpl.h 0644 root bin 1543 56608 1223260933 1 f none include/libical/icalgauge.h 0644 root bin 1656 4270 1223260933 1 f none include/libical/icalgaugeimpl.h 0644 root bin 1881 13948 1223260933 1 f none include/libical/icallangbind.h 0644 root bin 2122 43555 1223260931 1 f none include/libical/icalmemory.h 0644 root bin 2811 38685 1223260931 1 f none include/libical/icalmessage.h 0644 root bin 1939 20318 1223260933 1 f none include/libical/icalmime.h 0644 root bin 1112 20783 1223260931 1 f none include/libical/icalparameter.h 0644 root bin 2174 56603 1223260931 1 f none include/libical/icalparser.h 0644 root bin 2921 42296 1223260931 1 f none include/libical/icalperiod.h 0644 root bin 1459 56605 1223260931 1 f none include/libical/icalproperty.h 0644 root bin 4911 45767 1223260931 1 f none include/libical/icalrecur.h 0644 root bin 5784 21906 1223260931 1 f none include/libical/icalrestriction.h 0644 root bin 1751 3900 1223260931 1 f none include/libical/icalset.h 0644 root bin 6077 2002 1223260933 1 f none include/libical/icalspanlist.h 0644 root bin 2259 59056 1223260933 1 f none include/libical/icalss.h 0644 root bin 24359 35478 1225351652 1 f none include/libical/icalssyacc.h 0644 root bin 2864 24500 1223260933 1 f none include/libical/icaltime.h 0644 root bin 10054 26052 1223260931 1 f none include/libical/icaltimezone.h 0644 root bin 5255 51071 1223260931 1 f none include/libical/icaltypes.h 0644 root bin 2830 50004 1223260931 1 f none include/libical/icaltz-util.h 0644 root bin 1250 38017 1223260931 1 f none include/libical/icalvalue.h 0644 root bin 3117 11444 1223260931 1 f none include/libical/icalvcal.h 0644 root bin 1395 48124 1223260934 1 f none include/libical/port.h 0644 root bin 4015 5885 1223260934 1 f none include/libical/pvl.h 0644 root bin 2621 24732 1223260931 1 f none include/libical/sspm.h 0644 root bin 3845 46673 1223260931 1 f none include/libical/vcaltmp.h 0644 root bin 4242 26229 1223260934 1 f none include/libical/vcc.h 0644 root bin 3893 582 1223260934 1 f none include/libical/vobject.h 0644 root bin 14281 51802 1223260934 1 d none lib 0755 root bin 1 d none lib/pkgconfig 0755 root other 1 f none lib/pkgconfig/libical.pc 0644 root bin 261 23267 1225351649 1 i pkginfo 675 56332 1225351655 --Boundary_(ID_nbe3uI8tCA/PrZZrzkE8nw)-- From Irene.Huang@sun.com Sun Nov 9 21:20:54 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 mAA5KrG3027314 for ; Sun, 9 Nov 2008 21:20:54 -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 mAA5KpE5027317 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 10 Nov 2008 05:20:52 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 <0KA30030FQURZT00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Sun, 09 Nov 2008 21:20:51 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KA300K7CQUPSC50@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Sun, 09 Nov 2008 21:20:50 -0800 (PST) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mAA5KmHM028312 for ; Mon, 10 Nov 2008 05:20:48 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KA300201QTROJ00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Mon, 10 Nov 2008 13:20:48 +0800 (SGT) Received: from [129.158.217.182] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KA30019ZQUNGNQ9@mail-apac.sun.com>; Mon, 10 Nov 2008 13:20:48 +0800 (SGT) Date: Mon, 10 Nov 2008 13:20:38 +0800 From: Irene Huang Subject: Re: Libical for OpenSolaris [LSARC/2008/677 FastTrack timeout 11/10/2008] In-reply-to: <490EB1B4.5070404@sun.com> Sender: Irene.Huang@sun.com To: Irene Huang Cc: Shi-Ying Irene Huang , LSARC-ext@sun.com, Jedy.Wang@sun.com, Jeff.Cai@sun.com Message-id: <4917C4A6.9020301@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: <200811030806.mA386t2R006904@sac.sfbay.sun.com> <490EB1B4.5070404@sun.com> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Content-Length: 14518 Status: RO X-Status: $$$$ X-UID: 0000000003 Hi all I am closing this case as approved since there's comments. Thanks --Irene Irene Huang wrote: > Hi, all > > I am sponsoring this case, which is due timeout on 11/10/2008. > Attached are the pkgmaps. > > Thanks > > --Irene > Shi-Ying Irene Huang wrote: >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Libical for OpenSolaris >> 1.2. Name of Document Author/Supplier: >> Author: Jedy Wang >> 1.3 Date of This Document: >> 03 November, 2008 >> 4. Technical Description >> FCL--FOSS Check List >> >> 1.0 Project Information >> 1.1 Name of project/component >> libical >> >> 1.2 Author of document >> Jedy Wang >> >> 2.0 Project Summary >> 2.1 Project Description >> Libical is an Open Source (MPL/LGPL) implementation of the >> IETF's >> iCalendar Calendaring and Scheduling protocols. (RFC 2445, >> 2446, and >> 2447). The latest code is available at >> http://sourceforge.net/projects/freeassociation/. >> >> Libical is used by Evolution mail client. Before a forked >> version was >> shipped in Evolution source and Evolution links it >> statically. But now, >> the Evolution community decided to use the official release >> of libical >> and we plan to make this change for the GNOME 2.26 release. >> So we will >> ship libical in Solaris too to make Evolution continue to work. >> >> The libical source is licensed under Mozilla Public License >> 1.0 or GNU >> Library General Public License 2.1. But for Solaris >> distribution, we >> will use LGPL 2.1. >> >> 2.2 Release binding >> What is is the release binding? >> (see >> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [X] Minor >> [ ] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [X] Yes >> [ ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> freeassociation >> 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 > 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? >> [X] Yes >> [ ] No >> If yes are these components packaged to be shared with the >> other FOSS? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Are these components already in the Solaris WOS? >> [X] Yes >> [ ] No - continue with next section (section 3.2) >> If yes are these newer versions being delivered? >> [X] Yes >> [ ] No - ARC review required >> If yes are the newer versions replacing the existing >> versions? >> [X] 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 4.0 Interfaces >> (see >> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >> for details) >> 4.1 Exported Interfaces >> Interface Name Classification Comments >> --------------------------- ------------------- >> --------------------------- >> SUNWlibical Uncommitted package name >> /usr/include/libical/*.h Volatile libical C >> API >> /usr/lib/libical.so.0 Volatile library >> of libical >> /usr/lib/libicalss.so.0 Volatile library >> to support >> store >> iCal component >> data to >> disk in a >> variety >> of ways >> /usr/lib/libicalvcal.so.0 Volatile library >> to support >> vCalendar. >> /usr/lib/pkgconfig/libical.pc Uncommitted pkgconfig >> file for >> libical >> 4.2 Imported Interfaces >> Interface Name Classification Comments >> --------------------------- -------------------- >> -------------------------- >> zoneinfo timezone selection Project >> Private >> LSARC/2001/015 [1] >> Berkeley database Volatile LSARC/2007/299 >> >> 5.0 references >> >> [1] Contract with LSARC/2001/015 : >> http://sac.eng/LSARC/2001/015/contract-2001-015-02 >> http://sac.eng/LSARC/2001/015/contract-2001-015-03 >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> Desktop >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> >