From sh162551@sac.sfbay.sun.com Wed Jul 2 03:19:48 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 m62AJmeV002345 for ; Wed, 2 Jul 2008 03:19:48 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m62AJlem023801; Wed, 2 Jul 2008 03:19:47 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K3D0090BJCXY700@nwk-avmta-1.sfbay.Sun.COM>; Wed, 02 Jul 2008 03:19:45 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K3D0053DJCXXH20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 02 Jul 2008 03:19:45 -0700 (PDT) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m62AJhQY016014; Wed, 02 Jul 2008 03:19:43 -0700 (PDT) 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 m62AJfP1002338; Wed, 02 Jul 2008 03:19:41 -0700 (PDT) Received: (from sh162551@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m62AJfR0002334; Wed, 02 Jul 2008 03:19:41 -0700 (PDT) Date: Wed, 02 Jul 2008 03:19:41 -0700 (PDT) From: Shi-Ying Irene Huang Subject: contact-lookup-applet for OpenSolaris [LSARC/2008/415 FastTrack timeout 07/08/2008] To: lsarc-ext@sun.com Cc: jedy.wang@sun.com Message-id: <200807021019.m62AJfR0002334@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 12334 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: contact-lookup-applet for OpenSolaris 1.2. Name of Document Author/Supplier: Author: Jedy Wang 1.3 Date of This Document: 02 July, 2008 4. Technical Description FCL--FOSS Check List 1.0 Project Information 1.1 Name of project/component contact-lookup-applet 1.2 Author of document Jedy Wang 2.0 Project Summary 2.1 Project Description Contact-lookup-applet is an applet for gnome-panel which can quickly search your Evolution address book. The latest code is available at http://www.burtonini.com/computing/. To use the contact-lookup-applet, the user has to right click the panel and select "Add to Panel..." to add the contact-lookup-applet into the panel and enter the key word in the text entry of the applet. The result will be shown in a popup dialog. 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 Ross Burton 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? [ ] Yes [X] 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? [ ] 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? [ ] Yes [X] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [ ] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [ ] 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 [ ] 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 --------------------------- ------------------- --------------------------- SUNWcontact-lookup-applet Uncommitted package name /usr/lib/contact-lookup-applet Volatile binary of contact- loolup-applet /usr/lib/bonobo/servers/ Volatile bonobo startup file of GNOME_ContactLookupApplet.server contact-lookup-applet /usr/share/lookup-applet/ Project directory stores Private data used by contact-lookup-applet 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- GNOME Committed Committed LSARC/2008/207 Platform Libraries 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 Sun Jul 6 20:23:51 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 m673Nppj026563 for ; Sun, 6 Jul 2008 20:23:51 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m673Nohc043785 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Sun, 6 Jul 2008 21:23:50 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K3M00K019FQX200@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Sun, 06 Jul 2008 21:23:50 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K3M00AWV9FOSYC0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Sun, 06 Jul 2008 21:23:49 -0600 (MDT) 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 m673OFYL020593 for ; Mon, 07 Jul 2008 03:24:15 +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 <0K3M00C019B55K00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Mon, 07 Jul 2008 11:23:19 +0800 (SGT) Received: from [129.158.217.138] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K3M003OZ9EUJPQJ@mail-apac.sun.com>; Mon, 07 Jul 2008 11:23:19 +0800 (SGT) Date: Mon, 07 Jul 2008 11:24:31 +0800 From: Irene Huang Subject: Re: contact-lookup-applet for OpenSolaris [LSARC/2008/415 FastTrack timeout 07/08/2008] In-reply-to: <200807021019.m62AJfR0002334@sac.sfbay.sun.com> Sender: Irene.Huang@Sun.COM To: Shi-Ying Irene Huang Cc: lsarc-ext@Sun.COM, Jedy.Wang@Sun.COM Message-id: <1215401071.9484.28.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807021019.m62AJfR0002334@sac.sfbay.sun.com> Status: RO Content-Length: 13203 If there's any issues with this case, please send an email before the timeout (07/08/2008) Thanks. --Irene On Wed, 2008-07-02 at 03:19 -0700, Shi-Ying Irene Huang wrote: > 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: > contact-lookup-applet for OpenSolaris > 1.2. Name of Document Author/Supplier: > Author: Jedy Wang > 1.3 Date of This Document: > 02 July, 2008 > 4. Technical Description > FCL--FOSS Check List > > 1.0 Project Information > 1.1 Name of project/component > contact-lookup-applet > > 1.2 Author of document > Jedy Wang > > 2.0 Project Summary > 2.1 Project Description > Contact-lookup-applet is an applet for gnome-panel which can quickly > search your Evolution address book. The latest code is available at > http://www.burtonini.com/computing/. > > To use the contact-lookup-applet, the user has to right click the panel > and select "Add to Panel..." to add the contact-lookup-applet into the > panel and enter the key word in the text entry of the applet. The result > will be shown in a popup dialog. > > 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 > Ross Burton > > 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? > [ ] Yes > [X] 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? > [ ] 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? > [ ] Yes > [X] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [ ] 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 > [ ] 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 > --------------------------- ------------------- --------------------------- > SUNWcontact-lookup-applet Uncommitted package name > /usr/lib/contact-lookup-applet Volatile binary of contact- > loolup-applet > /usr/lib/bonobo/servers/ Volatile bonobo startup file of > GNOME_ContactLookupApplet.server contact-lookup-applet > /usr/share/lookup-applet/ Project directory stores > Private data used by > contact-lookup-applet > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > GNOME Committed Committed LSARC/2008/207 > Platform Libraries > > > 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 Jul 7 20:08:06 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m68386fK009855 for ; Mon, 7 Jul 2008 20:08:06 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m683851c028924 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 7 Jul 2008 20:08:06 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K3O00H1B3DHT700@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 07 Jul 2008 21:08:05 -0600 (MDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K3O00EWM3DFVLC0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 07 Jul 2008 21:08:04 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m68397kG019233 for ; Tue, 08 Jul 2008 03:09:07 +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 <0K3O00001352GQ00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 08 Jul 2008 11:05:52 +0800 (SGT) Received: from [129.158.217.138] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K3O00B9A39PREDR@mail-apac.sun.com>; Tue, 08 Jul 2008 11:05:50 +0800 (SGT) Date: Tue, 08 Jul 2008 11:08:41 +0800 From: Irene Huang Subject: Re: contact-lookup-applet for OpenSolaris [LSARC/2008/415 FastTrack timeout 07/08/2008] In-reply-to: <1215401071.9484.28.camel@goalie> Sender: Irene.Huang@sun.com To: Shi-Ying Irene Huang Cc: lsarc-ext@sun.com, Jedy.Wang@sun.com Message-id: <1215486521.10693.13.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807021019.m62AJfR0002334@sac.sfbay.sun.com> <1215401071.9484.28.camel@goalie> Status: RO Content-Length: 14000 Closed as approved. --Irene On Mon, 2008-07-07 at 11:24 +0800, Irene Huang wrote: > If there's any issues with this case, please send an email before the > timeout (07/08/2008) > > Thanks. > > --Irene > On Wed, 2008-07-02 at 03:19 -0700, Shi-Ying Irene Huang wrote: > > 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: > > contact-lookup-applet for OpenSolaris > > 1.2. Name of Document Author/Supplier: > > Author: Jedy Wang > > 1.3 Date of This Document: > > 02 July, 2008 > > 4. Technical Description > > FCL--FOSS Check List > > > > 1.0 Project Information > > 1.1 Name of project/component > > contact-lookup-applet > > > > 1.2 Author of document > > Jedy Wang > > > > 2.0 Project Summary > > 2.1 Project Description > > Contact-lookup-applet is an applet for gnome-panel which can quickly > > search your Evolution address book. The latest code is available at > > http://www.burtonini.com/computing/. > > > > To use the contact-lookup-applet, the user has to right click the panel > > and select "Add to Panel..." to add the contact-lookup-applet into the > > panel and enter the key word in the text entry of the applet. The result > > will be shown in a popup dialog. > > > > 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 > > Ross Burton > > > > 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? > > [ ] Yes > > [X] 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? > > [ ] 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? > > [ ] Yes > > [X] No - continue with next section (section 3.3) > > > > Are 64-bit versions of the libraries being delivered? > > [ ] Yes > > [ ] No - ARC review required > > > > Are static versions of the libraries being delivered? > > [ ] Yes - ARC review required > > [ ] 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 > > [ ] 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 > > --------------------------- ------------------- --------------------------- > > SUNWcontact-lookup-applet Uncommitted package name > > /usr/lib/contact-lookup-applet Volatile binary of contact- > > loolup-applet > > /usr/lib/bonobo/servers/ Volatile bonobo startup file of > > GNOME_ContactLookupApplet.server contact-lookup-applet > > /usr/share/lookup-applet/ Project directory stores > > Private data used by > > contact-lookup-applet > > > > 4.2 Imported Interfaces > > Interface Name Classification Comments > > --------------------------- -------------------- -------------------------- > > GNOME Committed Committed LSARC/2008/207 > > Platform Libraries > > > > > > 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 > > >