From sacadmin Wed Dec 26 23:46:37 2007 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 lBR7kbqG024259; Wed, 26 Dec 2007 23:46:37 -0800 (PST) Received: (from sh162551@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id lBR7kb1m024254; Wed, 26 Dec 2007 23:46:37 -0800 (PST) Date: Wed, 26 Dec 2007 23:46:37 -0800 (PST) From: Shi-Ying Irene Huang Message-Id: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> To: LSARC@sac.sfbay.sun.com Cc: solaris-battery-team@sun.com Subject: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Status: RO Content-Length: 13422 Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: GNOME Power Manager 1.2. Name of Document Author/Supplier: Author: Simon Zheng 1.3 Date of This Document: 26 December, 2007 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: GNOME Power Manager 1.2. Name of Document Author/Supplier: Author: Simon Zheng 1.3 Date of This Document: Dec 27th, 2007 2. Background This project provides Solaris users with a GNOME Power Manager infrastructure. Solaris has integrated HAL via PSARC/2005/399 Tamarack project, and PSARC 2006/601 Battery project and PSARC/2007/679 CPUFreq HAL enhance more power management properties. Based on them, GNOME Power Manager will be able to support many power management features, such as suspending, hibernating, brightness adjustment, lid closure action, CPU frequency scaling, and etc. 3. Business Consideration GNOME Power Manager[1] supplies many modern power management features. It's valuable to attract more developer users for Solaris, especially laptop users. Also, it has been a part of official GNOME release since GNOME 2.14 and is delivered in many Linux distributions at present. So this project can fill the gap between Linux and Solaris too. 4. Technical Description This project will port GNOME Power Manager to Solaris, which stems from GNOME community. Then we'll keep tracking community and provide upstream changes back to them. 4.1 Framework +-----------------------------------------------------------------------+ | | |gnome-brightness-applet gnome-power-statistics gnome-power-preference | | | +--------------------------------+ | | D-Bus interface | | | org.freedesktop.PowerManagement| | +--------------------------------+ | | gnome-power-manager | | | daemon | | +--------------------------------+--------------------------------------+ ^ | (D-bus) | JDS consolidation (up) -----------------+-------------------------------------------------------------- | ON consolidation (below) | (D-bus) v +-----------------------------------------+ | HAL daemon (hald) | +----------------+ +------------------+ | |hald-addon-acpi | |hald-addon-cpufreq| | |daemon | |daemon | | +-------------------------------------+---+ ^ | | +-----------------+ | | Power.conf | | | pmconfig utility| | +-----------------+ | | user space ---------+-------------------------+--------------------------------------- | | kernel space v v +-------------------+ +-------------------+ | battery, lid | | power management | | brightness drivers| | framewok | +-------------------+ +-------------------+ GNOME Power Manager infrastructure is composed of several parts, gnome-power-manager daemon, gnome-power-preferences, gnome-power-statistics, gnome-brightness and D-Bus interfaces "org.freedesktop.PowerManagement". gnome-power-manager daemon is a backend session-daemon which is automatically started by gnome-session when logging in GNOME desktop session. It provides a complete and integrated solution to power management under GNOME desktop environment. It supports suspending, hibernating, screen blanking, lid closure action, CPU frequency scaling, and etc. gnome-power-preferences is a GUI configuration program. It allows users to define their favorite policies in terms of power source. These policies are enforced by gnome-power-manager daemon. gnome-power-statistics is also a GUI program and allows users to visualize the power consumption of laptop hardware. gnome-brightness-applet is a gnome-panel applet, which serves for displaying and adjusting LCD screen brightness level. And D-Bus interfaces "org.freedesktop.PowerManagement" are exported to be used for other up-level applications. 4.2 Battery monitor & configuration switching GNOME Power Manager not only reports battery status but also supports power management policies. Using gnome-power-preferences users are able to define different policies for AC and battery. The policy may be an action when battery becomes very low, or what action would be triggered when lid is closed. Then, when switching the power source, corresponding policy will be switched accordingly. For example, unplugging AC adapter, GNOME Power Manager immediately replaces battery's policy with AC's. This makes system look smarter. 4.3 Brightness, lid and power buttons On laptop, when brightness up/down is pressed, gnome-power-manager will receive relevant button event and then pop up a progress bar to show brightness status. When lid is closed, GNOME Power Manager will trigger a defined action, such as blank screen, suspend, hibernate. Pressing power button, it will also do the specified policy. All above buttons events require HAL support. 4.4 CPU frequency scaling At present, CPUFreq HAL supports two types of CPU power management policies, "On Demand" and "Performance". "On Demand" means dynamic CPU frequency scaling is performed by monitoring CPU utilization and scaling the frequency when appropriate. "Performance" means getting full CPU utilization all the time. Both policies can be configured from GNOME Power Manager. 4.5 Suspend/hibernate and its capability and authorization checking Suspend (suspend to RAM) and hibernate (suspend to disk) functionalities are based on the HAL D-Bus interface "org.freedesktop.Hal.Device.SystemPowerManagement". Before showing users suspend/hibernate configuration, GNOME Power Manager will check both hardware capability and user authorization. Hardware capability checking relies on HAL's interface "power_management.can_suspend", and user authorization checking uses HAL's libpolkit. 4.6 Dependency GNOME Power Manager heavily depends on HAL layer. Some basic HAL calling methods, such as "GetPropertyString" and "SetPropertyString", are provided by "Removable Media Enhancements in Solaris" (PSARC/2005/399). Libpolkit is also from the same. Battery interfaces are from Battery Project (PSARC/2006/601). CPUFreq scaling interfaces is supplied by CPUFreq HAL (PSARC/2007/679). Other interfaces about suspend/hibernate, Brightness, lid and power button are under development and will be provided soon. In addition, screen blanking depends on X11 DPMS extension (PSARC/1998/299). 5. Interface Tables Exported Interface Interface Name Classification Comment ------------------- --------------- -------------- SUNWgnome-power-manager-root Uncommitted GNOME Power Manager - / filesystem /etc/gconf/schemas/gnome-power-manager.schemas Volatile Gconf schema definition file SUNWgnome-power-manager Uncommitted GNOME Power Manager /usr/bin/gnome-power-manager Volatile Session daemon /usr/bin/gnome-power-preferences Volatile Configuration GUI /usr/bin/gnome-power-statistic Volatile GUI to show power consumption statistic /usr/lib/gnome-brightness-applet Volatile gnome-panel applet to adjust brightness /usr/lib/gnome-power-bugreport.sh Volatile Bug reporter tool /usr/lib/gnome-power-cmd.sh Volatile Command-line tool to run suspend/hibernate/shutdown. /usr/lib/bonobo/servers/GNOME_BrightnessApplet.server Volatile Bonobo service configuration file /usr/share/applications/gnome-power-preferences.desktop Volatile Start menu configuration file /usr/share/applications/gnome-power-statistic.desktop Volatile The same as above /usr/share/gnome/autostart/gnome-power-manager.desktop Volatile Autostart configuration /usr/share/dbus-1/services/gnome-power-manager.service Volatile D-Bus services configuration file /usr/share/gnome-2.0/ui/GNOME_BrightnessApplet.xml Volatile Gnome-panel configuration file /usr/share/gnome-power-manager Volatile Installation location for glade files, images /usr/share/gnome/help/gnome-power-manager Volatile GNOME help documentation Exported Interface Please see attached. All interfaces are Volatile. Imported Interface Interface Name Classification ARC Case Comment ------------------- --------------- -------------- --------------------------------- GNOME Committed Platform Libraries Committed LSARC/2007/520 GTK+ library GNOME 2.20 gnome-panel Volatile LSARC/2001/348 Window Navigator Construction Kit GNOME Panel D-BUS Volatile LSARC/2006/368 D-Bus library. D-BUS Message Bus System libXext/libX11 Committed PSARC/1998/299 DPMS extension X11R6.4: Update/upgrade of X Server HAL API Volatile PSARC/2005/399 Basic HAL API Tamarack: Removable Media Enhancements libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate Tamarack: Removable Media Enhancements Battery HAL Volatile PSARC/2006/601 Transfer ACPI battery event Battery Project CPUfreq HAL Volatile PSARC/2007/679 Supply CPU freq scaling backend CPUfreq HAL HAL suspend/hibernate,lid, Volatile TBD in PSARC soon Transfer suspend/hibernate, ACPI lid, brightness, power buttons event brightness and power buttons event 6. Resources and Schedule 6.1 Release Binding Target to a minor release of Solaris 6.2 Resources: 4.00 man month Development Engineering 1.0 man month Test Engineering 0.25 man month RE integration 0.5 man month Doc. writer 0.5 man month Program management 6.3. Consolidation C-team Name: JDS/GNOME 6.4. ARC review type: FastTrack 7. References [1] GNOME Power Mnanger homepage www.gnome.org/projects/gnome-power-manager [2] OpenSolaris laptop project http://www.opensolaris.org/os/community/laptop/ Related ARC case LSARC/2007/520 GNOME 2.20 LSARC/2001/348 GNOME Panel LSARC/2006/368 D-BUS Message Bus System PSARC/1998/299 X11R6.4: Update/upgrade of X Server PSARC/2005/399 Tamarack: Removable Media Enhancements in Solaris PSARC/2006/601 Battery Project PSARC/2007/679 CPUFreq HAL TBD in PSARC soon Suspend/hibernate, lid, brightness and power buttons HAL & driver 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: JDS 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From sacadmin Fri Dec 28 01:47:03 2007 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBS9l3TM011647; Fri, 28 Dec 2007 01:47:03 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id lBS9l2Ci021097; Fri, 28 Dec 2007 01:47:03 -0800 (PST) Received: from fe-apac-02.sun.com (fe-apac-02.sun.com [192.18.19.173] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lBS9kvZL007587; Fri, 28 Dec 2007 09:46:57 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 <0JTR007016Q6PT00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Fri, 28 Dec 2007 17:46:57 +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 <0JTR00GOX7682F21@mail-apac.sun.com>; Fri, 28 Dec 2007 17:46:57 +0800 (SGT) Date: Fri, 28 Dec 2007 17:44:51 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Sender: Irene.Huang@sun.com To: Shi-Ying Irene Huang Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1198835091.14899.61.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Status: RO Content-Length: 336 Hi, all On Wed, 2007-12-26 at 23:46 -0800, Shi-Ying Irene Huang wrote: > > > Exported Interface > > Please see attached. All interfaces are Volatile. > for the list of exported interfaces, please refer to http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/power-management-spec-0.2.html --Irene From sacadmin Wed Jan 2 11:18:36 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m02JIaPp003849; Wed, 2 Jan 2008 11:18:36 -0800 (PST) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m02JIZfq005909; Wed, 2 Jan 2008 11:18:35 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m02JIUIU003877; Wed, 2 Jan 2008 11:18:30 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU100L014PEXK00@fe-sfbay-10.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Wed, 02 Jan 2008 11:18:30 -0800 (PST) Received: from [129.146.104.83] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU100M6M6YHV3C0@fe-sfbay-10.sun.com>; Wed, 02 Jan 2008 11:18:28 -0800 (PST) Date: Wed, 02 Jan 2008 11:22:53 -0800 From: Artem Kachitchkine Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Sender: Artem.Kachitchkin@sun.com To: Shi-Ying Irene Huang Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477BE48D.70003@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 442 > libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate > Tamarack: Removable > Media Enhancements Since our current libpolkit implementation uses RBAC for backend, you need to list specifically what RBAC authorizations are used. -Artem From sacadmin Wed Jan 2 11:31:10 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m02JVAri004246; Wed, 2 Jan 2008 11:31:10 -0800 (PST) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m02JVAlZ012247; Wed, 2 Jan 2008 11:31:10 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m02JV5lO005472; Wed, 2 Jan 2008 11:31:05 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU1004017B41R00@fe-sfbay-09.sun.com> (original mail from Alan.Coopersmith@Sun.COM); Wed, 02 Jan 2008 11:31:05 -0800 (PST) Received: from [129.146.108.211] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU100KD37JOJUB0@fe-sfbay-09.sun.com>; Wed, 02 Jan 2008 11:31:01 -0800 (PST) Date: Wed, 02 Jan 2008 11:31:00 -0800 From: Alan Coopersmith Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Sender: Alan.Coopersmith@sun.com To: Shi-Ying Irene Huang Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477BE674.50803@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Enigmail-Version: 0.95.1 References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071203) Status: RO Content-Length: 792 Shi-Ying Irene Huang wrote: > 4.3 Brightness, lid and power buttons > On laptop, when brightness up/down is pressed, gnome-power-manager will receive > relevant button event and then pop up a progress bar to show brightness status. > When lid is closed, GNOME Power Manager will trigger a defined action, such as > blank screen, suspend, hibernate. Pressing power button, it will also do the > specified policy. All above buttons events require HAL support. Currently pressing the power button calls /usr/openwin/bin/sys-suspend (from the CDE consolidation, despite the path) - does this project replace that framework? Will it allow CDE to remove the sys-suspend command? -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From sacadmin Wed Jan 2 11:50:24 2008 Received: from zruty.sfbay.sun.com (zruty [129.146.168.40]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m02JoOA3004366; Wed, 2 Jan 2008 11:50:24 -0800 (PST) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id m02JoN15001551; Wed, 2 Jan 2008 11:50:23 -0800 (PST) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id m02JoN91001550; Wed, 2 Jan 2008 11:50:23 -0800 (PST) Date: Wed, 2 Jan 2008 11:50:22 -0800 From: Danek Duvall To: Shi-Ying Irene Huang Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Message-ID: <20080102195022.GT17670@zruty.sfbay.sun.com> References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2703 On Wed, Dec 26, 2007 at 11:46:37PM -0800, Shi-Ying Irene Huang wrote: > Imported Interface > > Interface Name Classification ARC Case Comment > ------------------- --------------- -------------- --------------------------------- > GNOME Committed Platform Libraries Committed LSARC/2007/520 GTK+ library > GNOME 2.20 > > gnome-panel Volatile LSARC/2001/348 Window Navigator Construction Kit > GNOME Panel > > D-BUS Volatile LSARC/2006/368 D-Bus library. > D-BUS Message Bus System > > libXext/libX11 Committed PSARC/1998/299 DPMS extension > X11R6.4: Update/upgrade > of X Server > > HAL API Volatile PSARC/2005/399 Basic HAL API Tamarack: Removable > Media Enhancements > > libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate > Tamarack: Removable > Media Enhancements > > Battery HAL Volatile PSARC/2006/601 Transfer ACPI battery event > Battery Project > > CPUfreq HAL Volatile PSARC/2007/679 Supply CPU freq scaling backend > CPUfreq HAL > > HAL suspend/hibernate,lid, Volatile TBD in PSARC soon Transfer suspend/hibernate, ACPI lid, > brightness, power buttons event brightness and power buttons event Looks like we'll need to see some contracts for the Volatile interfaces, at least the ones not delivered by JDS (I'd be comfortable thinking of these as Consolidation Private). Danek From sacadmin Wed Jan 2 15:46:19 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m02NkIE5013869; Wed, 2 Jan 2008 15:46:18 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m02NkIJQ023177; Wed, 2 Jan 2008 15:46:18 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m02NjUfK002151; Wed, 2 Jan 2008 15:45:30 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m02NjUoR002150; Wed, 2 Jan 2008 15:45:30 -0800 (PST) Date: Wed, 2 Jan 2008 15:45:30 -0800 (PST) From: Gary Winiger Message-Id: <200801022345.m02NjUoR002150@marduk.eng.sun.com> To: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com Cc: solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Status: RO Content-Length: 2239 > 4.2 Battery monitor & configuration switching > GNOME Power Manager not only reports battery status but also supports power > management policies. Using gnome-power-preferences users are able to define > different policies for AC and battery. The policy may be an action when battery > becomes very low, or what action would be triggered when lid is closed. Then, > when switching the power source, corresponding policy will be switched accordingly. > For example, unplugging AC adapter, GNOME Power Manager immediately replaces > battery's policy with AC's. This makes system look smarter. > > 4.3 Brightness, lid and power buttons > On laptop, when brightness up/down is pressed, gnome-power-manager will receive > relevant button event and then pop up a progress bar to show brightness status. > When lid is closed, GNOME Power Manager will trigger a defined action, such as > blank screen, suspend, hibernate. Pressing power button, it will also do the > specified policy. All above buttons events require HAL support. > > 4.4 CPU frequency scaling > At present, CPUFreq HAL supports two types of CPU power management policies, "On > Demand" and "Performance". "On Demand" means dynamic CPU frequency scaling is > performed by monitoring CPU utilization and scaling the frequency when appropriate. > "Performance" means getting full CPU utilization all the time. Both policies can > be configured from GNOME Power Manager. > > 4.5 Suspend/hibernate and its capability and authorization checking > Suspend (suspend to RAM) and hibernate (suspend to disk) functionalities are based on > the HAL D-Bus interface "org.freedesktop.Hal.Device.SystemPowerManagement". Before > showing users suspend/hibernate configuration, GNOME Power Manager will check both > hardware capability and user authorization. Hardware capability checking relies on > HAL's interface "power_management.can_suspend", and user authorization checking uses > HAL's libpolkit. It would seem some of this functionality should not be present on all systems or to all users. What are the policies enforced? How are the policies enforced? Are there new access control mechnaisms? What are the access controls and how are they audited? Gary.. From sacadmin Wed Jan 2 18:30:25 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m032UPvG017611; Wed, 2 Jan 2008 18:30:25 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m032UO6T054349; Wed, 2 Jan 2008 18:30:24 -0800 (PST) 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 m032UIOD021973; Thu, 3 Jan 2008 02:30:18 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 <0JU100601QSTVN00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 03 Jan 2008 10:30:18 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU100CBSQYDUF1R@mail-apac.sun.com>; Thu, 03 Jan 2008 10:30:18 +0800 (SGT) Date: Thu, 03 Jan 2008 10:30:36 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477BE48D.70003@sun.com> Sender: Simon.Zheng@sun.com To: Artem Kachitchkine Cc: Shi-Ying Irene Huang , LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199327436.2236.18.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> <477BE48D.70003@sun.com> Status: RO Content-Length: 1062 Hi Artem, Fine. I would like add PolicyKit privileges as below. "hal-power-suspend" "hal-power-hibernate" "hal-power-shutdown" "hal-power-reboot" Currently we plan GNOME Power Manager doesn't use RBAC auth directly, instead, it still uses community PolicyKit privileges. And then, libpolkit implementation maps these PolicyKit privileges to real RBAC authorizations. This way is the same as what solaris mounting has done now. Soon Phi will also file an ARC case to enhance libpolkit to support these new authorizations. Thanks, -Simon On Wed, 2008-01-02 at 11:22 -0800, Artem Kachitchkine wrote: > > libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate > > Tamarack: Removable > > Media Enhancements > > Since our current libpolkit implementation uses RBAC for backend, you > need to list specifically what RBAC authorizations are used. > > -Artem From sacadmin Wed Jan 2 18:49:18 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m032nITO017774; Wed, 2 Jan 2008 18:49:18 -0800 (PST) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m032nI00059697; Wed, 2 Jan 2008 18:49:18 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m032nDPO009193; Wed, 2 Jan 2008 18:49:13 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU100601RSSGC00@fe-sfbay-09.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Wed, 02 Jan 2008 18:49:13 -0800 (PST) Received: from [129.150.16.15] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU100IR2RU0P290@fe-sfbay-09.sun.com>; Wed, 02 Jan 2008 18:49:13 -0800 (PST) Date: Wed, 02 Jan 2008 18:46:22 -0800 From: Artem Kachitchkine Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <1199327436.2236.18.camel@goaltender> Sender: Artem.Kachitchkin@sun.com To: "simon.zheng@sun.com" Cc: Shi-Ying Irene Huang , LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477C4C7E.9050004@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> <477BE48D.70003@sun.com> <1199327436.2236.18.camel@goaltender> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 781 simon.zheng@sun.com wrote: > Hi Artem, > > Fine. I would like add PolicyKit privileges as below. > > "hal-power-suspend" > "hal-power-hibernate" > "hal-power-shutdown" > "hal-power-reboot" > > Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > instead, it still uses community PolicyKit privileges. > > And then, libpolkit implementation maps these PolicyKit privileges to > real RBAC authorizations. This way is the same as what solaris mounting > has done now. Soon Phi will also file an ARC case to enhance libpolkit > to support these new authorizations. To clarify, what you're saying is: this case depend on the future libpolkit case, and the project reviewed in this case will not integrate until the libpolkit case integrates, correct? -Artem From sacadmin Wed Jan 2 18:58:35 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m032wZlR018148; Wed, 2 Jan 2008 18:58:35 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m032wXiO020373; Wed, 2 Jan 2008 18:58:34 -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 m032wS0a023282; Thu, 3 Jan 2008 02:58:28 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 <0JU100L01S0IBB00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Thu, 03 Jan 2008 10:58:28 +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 <0JU100LCRS9FPBKC@mail-apac.sun.com>; Thu, 03 Jan 2008 10:58:28 +0800 (SGT) Date: Thu, 03 Jan 2008 10:56:19 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <20080102195022.GT17670@zruty.sfbay.sun.com> Sender: Irene.Huang@sun.com To: Danek Duvall Cc: Shi-Ying Irene Huang , LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199328979.14899.114.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> <20080102195022.GT17670@zruty.sfbay.sun.com> Status: RO Content-Length: 2888 Danek, On Wed, 2008-01-02 at 11:50 -0800, Danek Duvall wrote: > On Wed, Dec 26, 2007 at 11:46:37PM -0800, Shi-Ying Irene Huang wrote: > > > Imported Interface > > > > Interface Name Classification ARC Case Comment > > ------------------- --------------- -------------- --------------------------------- > > GNOME Committed Platform Libraries Committed LSARC/2007/520 GTK+ library > > GNOME 2.20 > > > > gnome-panel Volatile LSARC/2001/348 Window Navigator Construction Kit > > GNOME Panel > > > > D-BUS Volatile LSARC/2006/368 D-Bus library. > > D-BUS Message Bus System > > > > libXext/libX11 Committed PSARC/1998/299 DPMS extension > > X11R6.4: Update/upgrade > > of X Server > > > > HAL API Volatile PSARC/2005/399 Basic HAL API Tamarack: Removable > > Media Enhancements > > > > libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate > > Tamarack: Removable > > Media Enhancements > > > > Battery HAL Volatile PSARC/2006/601 Transfer ACPI battery event > > Battery Project > > > > CPUfreq HAL Volatile PSARC/2007/679 Supply CPU freq scaling backend > > CPUfreq HAL > > > > HAL suspend/hibernate,lid, Volatile TBD in PSARC soon Transfer suspend/hibernate, ACPI lid, > > brightness, power buttons event brightness and power buttons event > > Looks like we'll need to see some contracts for the Volatile interfaces, at > least the ones not delivered by JDS (I'd be comfortable thinking of these > as Consolidation Private). Yes, we are working on that :) --Irene > > Danek From sacadmin Wed Jan 2 19:20:19 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m033KIii018328; Wed, 2 Jan 2008 19:20:19 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m033KHbh025556; Wed, 2 Jan 2008 19:20:18 -0800 (PST) Received: from fe-apac-04.sun.com (fe-apac-04.sun.com [192.18.19.175] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m033KCEr022049; Thu, 3 Jan 2008 03:20:12 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 <0JU100B01SMW1I00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 03 Jan 2008 11:20:12 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU100FBQT9NHDG0@mail-apac.sun.com>; Thu, 03 Jan 2008 11:20:12 +0800 (SGT) Date: Thu, 03 Jan 2008 11:20:33 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477C4C7E.9050004@sun.com> Sender: Simon.Zheng@sun.com To: Artem Kachitchkine Cc: Shi-Ying Irene Huang , LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199330433.2236.43.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> <477BE48D.70003@sun.com> <1199327436.2236.18.camel@goaltender> <477C4C7E.9050004@sun.com> Status: RO Content-Length: 1020 On Wed, 2008-01-02 at 18:46 -0800, Artem Kachitchkine wrote: > simon.zheng@sun.com wrote: > > Hi Artem, > > > > Fine. I would like add PolicyKit privileges as below. > > > > "hal-power-suspend" > > "hal-power-hibernate" > > "hal-power-shutdown" > > "hal-power-reboot" > > > > Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > > instead, it still uses community PolicyKit privileges. > > > > And then, libpolkit implementation maps these PolicyKit privileges to > > real RBAC authorizations. This way is the same as what solaris mounting > > has done now. Soon Phi will also file an ARC case to enhance libpolkit > > to support these new authorizations. > > To clarify, what you're saying is: this case depend on the future > libpolkit case, and the project reviewed in this case will not integrate > until the libpolkit case integrates, correct? Right! Current schedule is that enhanced libpolkit is integrated into SNV_83 and then GNOME Power Manager will put into SNV_88. > > -Artem From sacadmin Wed Jan 2 20:02:13 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0342DTY019210; Wed, 2 Jan 2008 20:02:13 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0342C77035106; Wed, 2 Jan 2008 20:02:13 -0800 (PST) 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 m03427Gt025894; Thu, 3 Jan 2008 04:02:07 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 <0JU100L01V13D700@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 03 Jan 2008 12:02:07 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU100CF8V7HUFAR@mail-apac.sun.com>; Thu, 03 Jan 2008 12:02:07 +0800 (SGT) Date: Thu, 03 Jan 2008 12:02:28 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801022345.m02NjUoR002150@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199332948.2236.64.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801022345.m02NjUoR002150@marduk.eng.sun.com> Status: RO Content-Length: 3241 On Wed, 2008-01-02 at 15:45 -0800, Gary Winiger wrote: > > 4.2 Battery monitor & configuration switching > > GNOME Power Manager not only reports battery status but also supports power > > management policies. Using gnome-power-preferences users are able to define > > different policies for AC and battery. The policy may be an action when battery > > becomes very low, or what action would be triggered when lid is closed. Then, > > when switching the power source, corresponding policy will be switched accordingly. > > For example, unplugging AC adapter, GNOME Power Manager immediately replaces > > battery's policy with AC's. This makes system look smarter. > > > > 4.3 Brightness, lid and power buttons > > On laptop, when brightness up/down is pressed, gnome-power-manager will receive > > relevant button event and then pop up a progress bar to show brightness status. > > When lid is closed, GNOME Power Manager will trigger a defined action, such as > > blank screen, suspend, hibernate. Pressing power button, it will also do the > > specified policy. All above buttons events require HAL support. > > > > 4.4 CPU frequency scaling > > At present, CPUFreq HAL supports two types of CPU power management policies, "On > > Demand" and "Performance". "On Demand" means dynamic CPU frequency scaling is > > performed by monitoring CPU utilization and scaling the frequency when appropriate. > > "Performance" means getting full CPU utilization all the time. Both policies can > > be configured from GNOME Power Manager. > > > > 4.5 Suspend/hibernate and its capability and authorization checking > > Suspend (suspend to RAM) and hibernate (suspend to disk) functionalities are based on > > the HAL D-Bus interface "org.freedesktop.Hal.Device.SystemPowerManagement". Before > > showing users suspend/hibernate configuration, GNOME Power Manager will check both > > hardware capability and user authorization. Hardware capability checking relies on > > HAL's interface "power_management.can_suspend", and user authorization checking uses > > HAL's libpolkit. > > It would seem some of this functionality should not be present > on all systems or to all users. What are the policies enforced? > How are the policies enforced? Are there new access control > mechnaisms? What are the access controls and how are they audited? Yeah. These functionalities are possibly unavailable on some system or for some users. Before doing real work, GNOME Power Manager will check hardware capability and user authorization. There's no new mechnaisms to be introduced. User authorizations is checked by calling libpolkit API (defined in PSARC/2005/399). Checking Hardware capability only calls some HAL interfaces, for example, "power_management.can_suspend", and then checks returning value. So these access controls are all based on HAL framework and libpolkit, which would fit audit requirement I think. BTW, list ARC cases related to hardware capability and user auths below. - libpolkit PSARC/2005/399 - HAL API PSARC/2005/399 - Battery HAL PSARC/2006/601 - CPUfreq HAL PSARC/2007/679 - HAL suspend/hibernate,lid, brightness, power buttons event TBD in PSARC soon -Simon > > Gary.. From sacadmin Wed Jan 2 20:42:23 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m034gMcT019326; Wed, 2 Jan 2008 20:42:23 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m034gMgW044065; Wed, 2 Jan 2008 20:42:22 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m034fYXN002456; Wed, 2 Jan 2008 20:41:34 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m034fYtO002455; Wed, 2 Jan 2008 20:41:34 -0800 (PST) Date: Wed, 2 Jan 2008 20:41:34 -0800 (PST) From: Gary Winiger Message-Id: <200801030441.m034fYtO002455@marduk.eng.sun.com> To: gww@eng.sun.com, Simon.Zheng@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com X-Sun-Charset: US-ASCII Status: RO Content-Length: 2514 > > > hardware capability and user authorization. Hardware capability checking relies on > > > HAL's interface "power_management.can_suspend", and user authorization checking uses > > > HAL's libpolkit. > > > > It would seem some of this functionality should not be present > > on all systems or to all users. What are the policies enforced? > > How are the policies enforced? Are there new access control > > mechnaisms? What are the access controls and how are they audited? > > Yeah. These functionalities are possibly unavailable on some system or > for some users. Before doing real work, GNOME Power Manager will check > hardware capability and user authorization. > > There's no new mechnaisms to be introduced. User authorizations is > checked by calling libpolkit API (defined in PSARC/2005/399). Checking > Hardware capability only calls some HAL interfaces, for example, > "power_management.can_suspend", and then checks returning value. So > these access controls are all based on HAL framework and libpolkit, > which would fit audit requirement I think. > > BTW, list ARC cases related to hardware capability and user auths below. > > - libpolkit PSARC/2005/399 > - HAL API PSARC/2005/399 This provides for solaris.device.mount.removable, ... allloptions.removable, fixed, alloptions.fixed And appropriate audit for them. > - Battery HAL PSARC/2006/601 I find no authorizations here. > - CPUfreq HAL PSARC/2007/679 This seems to provide for solaris.system.power.cpu and appears to provide for audit, though this project has not putback. So I guess this is not only a case dependency not listed in the spec, but also a putback dependency. > - HAL suspend/hibernate,lid, brightness, power buttons event > TBD in PSARC soon Are you asserting yet another case and putback dependency? And what is the relationship with the current case (702) and statement: Fine. I would like add PolicyKit privileges as below. "hal-power-suspend" "hal-power-hibernate" "hal-power-shutdown" "hal-power-reboot" Currently we plan GNOME Power Manager doesn't use RBAC auth directly, instead, it still uses community PolicyKit privileges. How does this relate to the Solaris RBAC policy and Solaris Audit? Are you saying the current case (702) is a GUI front end that does supports no policy and does nothing but call HAL interfaces? Is there some sort of big picture that shows how this all fits together to be useful/usable to Solaris users? Gary.. From sacadmin Wed Jan 2 20:45:43 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m034jhR7019350; Wed, 2 Jan 2008 20:45:43 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m034jhn3044663; Wed, 2 Jan 2008 20:45:43 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m034itrG002465; Wed, 2 Jan 2008 20:44:55 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m034itQu002464; Wed, 2 Jan 2008 20:44:55 -0800 (PST) Date: Wed, 2 Jan 2008 20:44:55 -0800 (PST) From: Gary Winiger Message-Id: <200801030444.m034itQu002464@marduk.eng.sun.com> To: gww@eng.sun.com, Simon.Zheng@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com X-Sun-Charset: US-ASCII Status: RO Content-Length: 949 > > > hardware capability and user authorization. Hardware capability checking relies on > > > HAL's interface "power_management.can_suspend", and user authorization checking uses > > > HAL's libpolkit. > > > > It would seem some of this functionality should not be present > > on all systems or to all users. What are the policies enforced? > > How are the policies enforced? Are there new access control > > mechnaisms? What are the access controls and how are they audited? > > Yeah. These functionalities are possibly unavailable on some system or > for some users. Before doing real work, GNOME Power Manager will check > hardware capability and user authorization. So this GUI is checking authorizations. It would seem to be useful to specify what authorizations are being checked and what decisions are being made based on those checks. If it's an access control decision, then details are needed as well as audit. Gary.. From sacadmin Wed Jan 2 21:37:07 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m035b7nC019868; Wed, 2 Jan 2008 21:37:07 -0800 (PST) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m035b7Uk033252; Wed, 2 Jan 2008 21:37:07 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m035b2Vi026701; Wed, 2 Jan 2008 21:37:02 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU100401ZGW7W00@fe-sfbay-10.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Wed, 02 Jan 2008 21:37:02 -0800 (PST) Received: from [129.150.16.15] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU100MFTZLPJ870@fe-sfbay-10.sun.com>; Wed, 02 Jan 2008 21:37:02 -0800 (PST) Date: Wed, 02 Jan 2008 21:34:11 -0800 From: Artem Kachitchkine Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801030444.m034itQu002464@marduk.eng.sun.com> Sender: Artem.Kachitchkin@sun.com To: Gary Winiger Cc: Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477C73D3.1040806@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200801030444.m034itQu002464@marduk.eng.sun.com> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 1440 >> Yeah. These functionalities are possibly unavailable on some system or >> for some users. Before doing real work, GNOME Power Manager will check >> hardware capability and user authorization. > > So this GUI is checking authorizations. It would seem to be > useful to specify what authorizations are being checked and what > decisions are being made based on those checks. If it's an > access control decision, then details are needed as well as > audit. I think the project team needs be careful with terminology and more specific with their responses and avoid handwaving like this: > So these access controls are all based on HAL framework and libpolkit, > which would fit audit requirement I think. If the GUI indeed enforces policies, provides access control and, for these purposes, runs with any kind of elevated privileges, that's a red flag for reviewers, requiring much more scrutiny. I doubt it, but it needs to be clarified. My understanding is that the GNOME Power Manager is a mere consumer of the core functionality provided by the PSARC cases listed elsewhere. Whether the HAL backends that implement PM DBus methods provide access control, or the related Solaris subsystems invoked by the backends, it would seem that respective PSARC cases should provide authorizations and audit, and if they do not, those cases are incomplete. Documentation for this case does not make it clear enough. -Artem From sacadmin Wed Jan 2 22:07:55 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0367tba020340; Wed, 2 Jan 2008 22:07:55 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0367sF6064625; Wed, 2 Jan 2008 22:07:54 -0800 (PST) Received: from fe-apac-02.sun.com (fe-apac-02.sun.com [192.18.19.173] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0367mps028855; Thu, 3 Jan 2008 06:07:48 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 <0JU200M010YUK400@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 03 Jan 2008 14:07:48 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU200G2U10Y2GC0@mail-apac.sun.com>; Thu, 03 Jan 2008 14:07:48 +0800 (SGT) Date: Thu, 03 Jan 2008 14:08:07 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801030441.m034fYtO002455@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199340487.2236.132.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801030441.m034fYtO002455@marduk.eng.sun.com> Status: RO Content-Length: 4719 On Wed, 2008-01-02 at 20:41 -0800, Gary Winiger wrote: > > > > hardware capability and user authorization. Hardware capability checking relies on > > > > HAL's interface "power_management.can_suspend", and user authorization checking uses > > > > HAL's libpolkit. > > > > > > It would seem some of this functionality should not be present > > > on all systems or to all users. What are the policies enforced? > > > How are the policies enforced? Are there new access control > > > mechnaisms? What are the access controls and how are they audited? > > > > Yeah. These functionalities are possibly unavailable on some system or > > for some users. Before doing real work, GNOME Power Manager will check > > hardware capability and user authorization. > > > > There's no new mechnaisms to be introduced. User authorizations is > > checked by calling libpolkit API (defined in PSARC/2005/399). Checking > > Hardware capability only calls some HAL interfaces, for example, > > "power_management.can_suspend", and then checks returning value. So > > these access controls are all based on HAL framework and libpolkit, > > which would fit audit requirement I think. > > > > BTW, list ARC cases related to hardware capability and user auths below. Some functionalities like battery mornitoring doesn't check user auths. List all actions that need to do user auths checking. - Set cpufreq policy - Suspend - hibernate - shutdown - reboot, > > > > - libpolkit PSARC/2005/399 > > - HAL API PSARC/2005/399 > > This provides for solaris.device.mount.removable, > ... allloptions.removable, fixed, alloptions.fixed > And appropriate audit for them. > > > - Battery HAL PSARC/2006/601 > > I find no authorizations here. Battery monitoring doesn't need to check user authorization because we only display batttery power volume. > > > - CPUfreq HAL PSARC/2007/679 > > This seems to provide for solaris.system.power.cpu > and appears to provide for audit, though this project has not > putback. So I guess this is not only a case dependency not > listed in the spec, but also a putback dependency. Right! > > > - HAL suspend/hibernate,lid, brightness, power buttons event > > TBD in PSARC soon > > Are you asserting yet another case and putback dependency? Yes. GNOME Power Manager depends on this new PSARC case, which will be filed in the near feature. > > And what is the relationship with the current case (702) and > statement: > Fine. I would like add PolicyKit privileges as below. > > "hal-power-suspend" > "hal-power-hibernate" > "hal-power-shutdown" > "hal-power-reboot" The above is PolicyKit privilege from GNOME community. Because GNOME Power Manager stems from community, we still keep them. Then libpolkit will map them to RBAC auths and do real checking. > > Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > instead, it still uses community PolicyKit privileges. > > How does this relate to the Solaris RBAC policy and Solaris > Audit? In fact, it has nothing to do with this case. GNOME Power Manager only calls libpolkit API libpolkit_is_uid_allowed_for_privilege(). If you are interested in how to map PolKit privileges to RBAC auths, please look at libpolkit code. http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/policykit/libpolkit/common/libpolkit-rbac.c#116 > > Are you saying the current case (702) is a GUI front end that > does supports no policy and does nothing but call HAL interfaces? Yeah. For CPUfreq, Suspend/Hibernate feature, GNOME Power Manager is regarded as a frontend and HAL is its backend. > > Is there some sort of big picture that shows how this all fits > together to be useful/usable to Solaris users? Sorry, no specifal picture. I think everything looks easy from GNOME Power Manager's side. But HAL and libpolkit internal implementation might be a little complicated, they have to consider more about security and audit. Let me try to describe calling flow in the sight of GNOME Power Manager. For example with suspend, Step 1: Check HAL's property "power_management.can_suspend" to see if current system supports suspend to ram. Step 2: If yes, calling libpolkit_is_uid_allowed_for_privilege(), GNOME Power Manager checks if current user has auth to suspend. Step 3: If yes, GNOME Power Manager shows user configuration option about suspend. For example, suspend when laptop lid is closed. Step 4: After that, when lid is closed, GNOME Power Manager will directly call method "suspend" of HAL D-Bus interface "org.freedesktop.Hal.Device.SystemPowerManagement" interface. Step 5: system is suspended successfully. Thanks, -Simon > > Gary.. From sacadmin Wed Jan 2 22:31:08 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m036V8SJ020488; Wed, 2 Jan 2008 22:31:08 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m036V7O8003860; Wed, 2 Jan 2008 22:31:08 -0800 (PST) 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 m036V2ej001997; Thu, 3 Jan 2008 06:31:02 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 <0JU200K011ZJ7B00@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) ; Thu, 03 Jan 2008 14:31:02 +0800 (SGT) Received: from [129.158.217.244] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU200CFP23OUA5Y@mail-apac.sun.com>; Thu, 03 Jan 2008 14:31:02 +0800 (SGT) Date: Thu, 03 Jan 2008 14:25:12 +0800 From: Jeff Cai Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477C73D3.1040806@sun.com> Sender: Jeff.Cai@sun.com To: Artem Kachitchkine Cc: Gary Winiger , Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199341512.976.17.camel@champoinpoint> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801030444.m034itQu002464@marduk.eng.sun.com> <477C73D3.1040806@sun.com> Status: RO Content-Length: 2097 On Wed, 2008-01-02 at 21:34 -0800, Artem Kachitchkine wrote: > >> Yeah. These functionalities are possibly unavailable on some system or > >> for some users. Before doing real work, GNOME Power Manager will check > >> hardware capability and user authorization. > > > > So this GUI is checking authorizations. It would seem to be > > useful to specify what authorizations are being checked and what > > decisions are being made based on those checks. If it's an > > access control decision, then details are needed as well as > > audit. > > I think the project team needs be careful with terminology and more > specific with their responses and avoid handwaving like this: > > > So these access controls are all based on HAL framework and libpolkit, > > which would fit audit requirement I think. > > If the GUI indeed enforces policies, provides access control and, for > these purposes, runs with any kind of elevated privileges, that's a red > flag for reviewers, requiring much more scrutiny. I doubt it, but it > needs to be clarified. All the access controls will be performed by HAL or libpolkit. GPM invokes libpolkit API "libpolkit_is_uid_allowed_for_privilege" to get whether the user has the permission to perform specified actions such as suspend, hibernate etc, so GPM can decide whether show the menu command to the user. Before performing the real action behavior, HAL will also check the user permissions, which should be included in another ARC case. If the user has no permission, HAL will return an error code to GPM, and the action fails. > > My understanding is that the GNOME Power Manager is a mere consumer of > the core functionality provided by the PSARC cases listed elsewhere. > Whether the HAL backends that implement PM DBus methods provide access > control, or the related Solaris subsystems invoked by the backends, it > would seem that respective PSARC cases should provide authorizations and > audit, and if they do not, those cases are incomplete. Yes. > Documentation for > this case does not make it clear enough. > > -Artem From sacadmin Thu Jan 3 23:16:31 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m047GVXj015351; Thu, 3 Jan 2008 23:16:31 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m047GUQ7065488; Thu, 3 Jan 2008 23:16:30 -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 m047GONb012952; Fri, 4 Jan 2008 07:16:24 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 <0JU300E01YRLXW00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Fri, 04 Jan 2008 15:16:24 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU300LS8YVBPBUH@mail-apac.sun.com>; Fri, 04 Jan 2008 15:16:24 +0800 (SGT) Date: Fri, 04 Jan 2008 15:16:45 +0800 From: "simon.zheng" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477BE674.50803@sun.com> Sender: Simon.Zheng@sun.com To: Alan Coopersmith Cc: Shi-Ying Irene Huang , LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199431005.5901.59.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.21.4 Content-type: text/plain Content-transfer-encoding: 8BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> <477BE674.50803@sun.com> Status: RO Content-Length: 1451 On Wed, 2008-01-02 at 11:31 -0800, Alan Coopersmith wrote: > Shi-Ying Irene Huang wrote: > > 4.3 Brightness, lid and power buttons > > On laptop, when brightness up/down is pressed, gnome-power-manager will receive > > relevant button event and then pop up a progress bar to show brightness status. > > When lid is closed, GNOME Power Manager will trigger a defined action, such as > > blank screen, suspend, hibernate. Pressing power button, it will also do the > > specified policy. All above buttons events require HAL support. > > Currently pressing the power button calls /usr/openwin/bin/sys-suspend (from the > CDE consolidation, despite the path) - does this project replace that framework? Actually what you mention belongs to HAL internal implementation details. This project won't involve in any sys-suspend issue and leave to its dependency, another new HAL case which will be coming soon. I think HAL will deal with power button pressing event from kernel, then notify GNOME Power Manager. From GNOME Power Manager's side, it only deals with button event signal emitted from HAL layer and then does user's prefered action, i.e. suspend or shutdown. > Will it allow CDE to remove the sys-suspend command? The same as the above, this project won't call low-level commands directly. But as I known, currently there's another ongoing project that will provide an alternative to sys-suspend command or enhance it. Thanks, -Simon From sacadmin Fri Jan 4 10:43:07 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m04Ih7Ve025387; Fri, 4 Jan 2008 10:43:07 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m04Ih68J011102; Fri, 4 Jan 2008 10:43:06 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m04IgHkh006114; Fri, 4 Jan 2008 10:42:17 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m04IgHMQ006113; Fri, 4 Jan 2008 10:42:17 -0800 (PST) Date: Fri, 4 Jan 2008 10:42:17 -0800 (PST) From: Gary Winiger Message-Id: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> To: Simon.Zheng@sun.com, gww@eng.sun.com Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Status: RO Content-Length: 2440 > > Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > > instead, it still uses community PolicyKit privileges. > > > > How does this relate to the Solaris RBAC policy and Solaris > > Audit? > > In fact, it has nothing to do with this case. GNOME Power Manager only > calls libpolkit API libpolkit_is_uid_allowed_for_privilege(). > > If you are interested in how to map PolKit privileges to RBAC auths, > please look at libpolkit code. > http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/policykit/libpolkit/common/libpolkit-rbac.c#116 I'm not interested in reading code. I'm interested in the architecture of things relevant to this case. In one place the project stated that the GUI will examine authorizations. "Yeah. These functionalities are possibly unavailable on some system or for some users. Before doing real work, GNOME Power Manager will check hardware capability and user authorization." "List all actions that need to do user auths checking. - Set cpufreq policy - Suspend - hibernate - shutdown - reboot, " Yet it leaves this incomplete. What authorizations? How does this project which seems to be saying it uses PolicyKit privileges know the mapping so it can call chkauthattr()? Does this project run as the user? If not how does it get the username or call HAL/DBUS in the user context? Does this project run with any privileges above the user's? Does it check authorizations every time it is invoked, to present the user with a list of current capabilities only? Does it check authorization only when told to do something? How does it audit any access control decisions? > > Is there some sort of big picture that shows how this all fits > > together to be useful/usable to Solaris users? > > Sorry, no specifal picture. I think everything looks easy from GNOME > Power Manager's side. Perhaps, but that's not what I'm asking. How does this project serve the customer? Do we have a shiny new toy that no one can use? What does this project provide that enables the GUI to be useful? If the answer is nothing, then what project does provide it? Is there another project dependency on that project? What's the general gist of that project? I suspect there's been enough discussion to warrent a new/final spec to capture what depencences this case has and what it will be doing and delivering. Gary.. From sacadmin Fri Jan 4 20:37:36 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m054bawB002405; Fri, 4 Jan 2008 20:37:36 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m054bY0b062179; Fri, 4 Jan 2008 20:37: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-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m054bS6r015255; Sat, 5 Jan 2008 04:37:29 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 <0JU500M01LY2QK00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Sat, 05 Jan 2008 12:37:28 +0800 (SGT) Received: from [129.150.16.69] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU500LMWM66PB0L@mail-apac.sun.com>; Sat, 05 Jan 2008 12:37:28 +0800 (SGT) Date: Sat, 05 Jan 2008 12:37:19 +0800 From: "simon.zheng" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477F097F.10500@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) Status: RO Content-Length: 7064 Gary Winiger wrote: >>> Currently we plan GNOME Power Manager doesn't use RBAC auth directly, >>> instead, it still uses community PolicyKit privileges. >>> >>> How does this relate to the Solaris RBAC policy and Solaris >>> Audit? >>> >> In fact, it has nothing to do with this case. GNOME Power Manager only >> calls libpolkit API libpolkit_is_uid_allowed_for_privilege(). >> >> If you are interested in how to map PolKit privileges to RBAC auths, >> please look at libpolkit code. >> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/policykit/libpolkit/common/libpolkit-rbac.c#116 >> > > I'm not interested in reading code. I'm interested in the > architecture of things relevant to this case. In one place the > project stated that the GUI will examine authorizations. > > "Yeah. These functionalities are possibly > unavailable on some system or for some users. > Before doing real work, GNOME Power Manager will > check hardware capability and user authorization." > > "List all actions that need to do user auths checking. > > - Set cpufreq policy > - Suspend > - hibernate > - shutdown > - reboot, " > > Yet it leaves this incomplete. What authorizations? How does > this project which seems to be saying it uses PolicyKit privileges > know the mapping so it can call chkauthattr()? Does this project > run as the user? If not how does it get the username or call > HAL/DBUS in the user context? > Does this project run with any privileges above the user's? > Does it check authorizations every time it is invoked, to > present the user with a list of current capabilities only? Does > it check authorization only when told to do something? How does > it audit any access control decisions? > Maybe it's unsuitable to say "authorization" because this project doesn't call any chkauthattr() directly. To make it clear, please allow me use "PolicyKit privileges" instead of "authorization". Strickly "PolicyKit privileges" is a only concept from GNOME community. On Solaris, "PolicyKit privileges" is supported by libpolkit. This project will query libpolkit about some new "PolicyKit privileges", which will be supported in the coming PSARC hal case. "hal-power-cpu" "hal-power-suspend" "hal-power-hibernate" "hal-power-shutdown" "hal-power-reboot" GNOME Power Manager is a mere consumer of the core functionality provided by the PSARC cases. Real access control is completed inside libpolkit. And exact names of relevant authorizations will be listed in the coming two PSARC cases. gnome-power-manager session daemon is responsible for talking with HAL layer through D-Bus and libpolkit. This session daemon is autostarted by gnome-session when the user login JDS. It's unprivileged I think. And login user is the owner of gnome-power-manager. There's two cases to query libpolkit if the user is allowed for doing something. One is when we present the user a list of current capabilities, another is before calling corresponding hal method, i.e. suspend system. > >>> Is there some sort of big picture that shows how this all fits >>> together to be useful/usable to Solaris users? >>> >> Sorry, no specifal picture. I think everything looks easy from GNOME >> Power Manager's side. >> > > Perhaps, but that's not what I'm asking. How does this project > serve the customer? Do we have a shiny new toy that no one can > use? What does this project provide that enables the GUI to be > useful? If the answer is nothing, then what project does provide > it? Is there another project dependency on that project? What's > the general gist of that project? > > I suspect there's been enough discussion to warrent a new/final > spec to capture what depencences this case has and what it > will be doing and delivering. > I think I misunderstand what you want eariler.:) To clarify, this project will deliver several power-aware applications, and we call them together Desktop GNOME Power Manager infrastructure. The block diagram is as below. 4.1 Framework +----------------------------------------------------------------------+ | | |gnome-brightness-applet gnome-power-statistics gnome-power-preference | | | +--------------------------------------------+ | | D-Bus interface | | | org.freedesktop.PowerManagement | | +--------------------------------------------+ | | gnome-power-manager session | | | daemon | | +-----------------------------------------+--+-------------------------+ ^ ^ | (D-bus) | | | JDS consolidation (up) -----------------+-----------------------------+----------------------------- | | ON consolidation (below) | (D-bus) | v V +-----------------------------------------+ +-----------+ | HAL daemon (hald) | | libpolkit | +----------------+ +------------------+ | +-----------+ |hald-addon-acpi | |hald-addon-cpufreq| | |daemon | |daemon | | +-------------------------------------+---+ ^ | | +-----------------+ | | Power.conf | | | pmconfig utility| | +-----------------+ | | user space ---------+-------------------------+--------------------------------------- | | kernel space v v +-------------------+ +-------------------+ | battery, lid | | power management | | brightness drivers| | framewok | +-------------------+ +-------------------+ Among them, gnome-power-preferences, gnome-power-statistics, gnome-brightness-applet are GUI applications, which serve desktop users. In addition, system tray icon controlled by gnome-power-manager is also visiable for users. Screenshot is here http://jdsbj.prc/wiki//index.php/Evaluation_of_GNOME_Power_Manager#ScreenShots_from_Linux Regarding depencency, particularly below two are putback dependency. CPUfreq HAL PSARC/2007/679 HAL suspend/hibernate, and lid, brightness, power buttons event TBD in PSARC case soon -Simon > Gary.. > From sacadmin Sat Jan 5 08:21:13 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m05GLDS9009275; Sat, 5 Jan 2008 08:21:13 -0800 (PST) Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m05GLCoD031932; Sat, 5 Jan 2008 08:21:13 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m05GLCZR001781; Sat, 5 Jan 2008 16:21:12 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU600J01IO4AC00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM); Sat, 05 Jan 2008 09:21:12 -0700 (MST) Received: from 129.145.154.78 ([129.145.154.78]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU6007N0IRB1N50@mail-amer.sun.com>; Sat, 05 Jan 2008 09:21:12 -0700 (MST) Date: Sat, 05 Jan 2008 08:21:11 -0800 From: John Fischer Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477F097F.10500@sun.com> Sender: John.Fischer@sun.com To: "simon.zheng" Cc: John Fischer , Gary Winiger , LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Reply-to: John.Fischer@sun.com Message-id: <1199550070.20228.8.camel@sr1-umpk-28> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301c Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> <477F097F.10500@sun.com> Status: RO Content-Length: 7622 Irene and Simon, At this point in time we need to have a summary of the issues and their current state. We also need to extend the timer. Once we have the issues resolved we will need a new specification. Thanks, John On Fri, 2008-01-04 at 20:37, simon.zheng wrote: > Gary Winiger wrote: > >>> Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > >>> instead, it still uses community PolicyKit privileges. > >>> > >>> How does this relate to the Solaris RBAC policy and Solaris > >>> Audit? > >>> > >> In fact, it has nothing to do with this case. GNOME Power Manager only > >> calls libpolkit API libpolkit_is_uid_allowed_for_privilege(). > >> > >> If you are interested in how to map PolKit privileges to RBAC auths, > >> please look at libpolkit code. > >> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/policykit/libpolkit/common/libpolkit-rbac.c#116 > >> > > > > I'm not interested in reading code. I'm interested in the > > architecture of things relevant to this case. In one place the > > project stated that the GUI will examine authorizations. > > > > "Yeah. These functionalities are possibly > > unavailable on some system or for some users. > > Before doing real work, GNOME Power Manager will > > check hardware capability and user authorization." > > > > "List all actions that need to do user auths checking. > > > > - Set cpufreq policy > > - Suspend > > - hibernate > > - shutdown > > - reboot, " > > > > Yet it leaves this incomplete. What authorizations? How does > > this project which seems to be saying it uses PolicyKit privileges > > know the mapping so it can call chkauthattr()? Does this project > > run as the user? If not how does it get the username or call > > HAL/DBUS in the user context? > > Does this project run with any privileges above the user's? > > Does it check authorizations every time it is invoked, to > > present the user with a list of current capabilities only? Does > > it check authorization only when told to do something? How does > > it audit any access control decisions? > > > Maybe it's unsuitable to say "authorization" because this project > doesn't call any chkauthattr() directly. To make it clear, please allow > me use "PolicyKit privileges" instead of "authorization". Strickly > "PolicyKit privileges" is a only concept from GNOME community. On > Solaris, "PolicyKit privileges" is supported by libpolkit. This project > will query libpolkit about some new "PolicyKit privileges", which will > be supported in the coming PSARC hal case. > > "hal-power-cpu" > "hal-power-suspend" > "hal-power-hibernate" > "hal-power-shutdown" > "hal-power-reboot" > > GNOME Power Manager is a mere consumer of the core functionality provided by the PSARC cases. Real access control is completed inside libpolkit. And exact names of relevant authorizations will be listed in the coming two PSARC cases. > > gnome-power-manager session daemon is responsible for talking with HAL layer through D-Bus and libpolkit. This session daemon is autostarted by gnome-session when the user login JDS. It's unprivileged I think. And login user is the owner of gnome-power-manager. > > There's two cases to query libpolkit if the user is allowed for doing something. One is when we present the user a list of current capabilities, another is before calling corresponding hal method, i.e. suspend system. > > > > > >>> Is there some sort of big picture that shows how this all fits > >>> together to be useful/usable to Solaris users? > >>> > >> Sorry, no specifal picture. I think everything looks easy from GNOME > >> Power Manager's side. > >> > > > > Perhaps, but that's not what I'm asking. How does this project > > serve the customer? Do we have a shiny new toy that no one can > > use? What does this project provide that enables the GUI to be > > useful? If the answer is nothing, then what project does provide > > it? Is there another project dependency on that project? What's > > the general gist of that project? > > > > I suspect there's been enough discussion to warrent a new/final > > spec to capture what depencences this case has and what it > > will be doing and delivering. > > > I think I misunderstand what you want eariler.:) > > To clarify, this project will deliver several power-aware applications, > and we call them together Desktop GNOME Power Manager infrastructure. > The block diagram is as below. > > 4.1 Framework > > +----------------------------------------------------------------------+ > | | > |gnome-brightness-applet gnome-power-statistics gnome-power-preference | > | | > +--------------------------------------------+ | > | D-Bus interface | | > | org.freedesktop.PowerManagement | | > +--------------------------------------------+ | > | gnome-power-manager session | | > | daemon | | > +-----------------------------------------+--+-------------------------+ > ^ ^ > | (D-bus) | > | | JDS consolidation (up) > -----------------+-----------------------------+----------------------------- > | | ON consolidation (below) > | (D-bus) | > v V > +-----------------------------------------+ +-----------+ > | HAL daemon (hald) | | libpolkit | > +----------------+ +------------------+ | +-----------+ > |hald-addon-acpi | |hald-addon-cpufreq| | > |daemon | |daemon | | > +-------------------------------------+---+ > ^ | > | +-----------------+ > | | Power.conf | > | | pmconfig utility| > | +-----------------+ > | | user space > ---------+-------------------------+--------------------------------------- > | | kernel space > v v > +-------------------+ +-------------------+ > | battery, lid | | power management | > | brightness drivers| | framewok | > +-------------------+ +-------------------+ > > Among them, gnome-power-preferences, gnome-power-statistics, gnome-brightness-applet are GUI applications, which serve desktop users. In addition, system tray icon controlled by gnome-power-manager is also visiable for users. Screenshot is here > http://jdsbj.prc/wiki//index.php/Evaluation_of_GNOME_Power_Manager#ScreenShots_from_Linux > > Regarding depencency, particularly below two are putback dependency. > CPUfreq HAL PSARC/2007/679 > HAL suspend/hibernate, and lid, brightness, power buttons event TBD in PSARC case soon > > -Simon > > > > Gary.. > > > From sacadmin Sat Jan 5 09:26:18 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m05HQIwT009827; Sat, 5 Jan 2008 09:26:18 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m05HQGKX045754; Sat, 5 Jan 2008 09:26:17 -0800 (PST) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m05HQBms023138; Sat, 5 Jan 2008 17:26:11 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 <0JU600401LI2F800@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) ; Sun, 06 Jan 2008 01:26:10 +0800 (SGT) Received: from [129.150.144.12] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU600C62LRLUAE3@mail-apac.sun.com>; Sun, 06 Jan 2008 01:26:10 +0800 (SGT) Date: Sun, 06 Jan 2008 01:26:08 +0800 From: Jeff Cai Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> Sender: Jeff.Cai@sun.com To: Gary Winiger Cc: Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477FBDB0.10700@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) Status: RO Content-Length: 2137 Gary, I'll make some additional comments. > Yet it leaves this incomplete. What authorizations? How does > These new authorizations will be defined in libpolkit, which will be provided by power management team. (Randy Fishel and Phi Tran). I think they are still in discussion. Of course, as a consumer of libpolkit, GPM case depends on libpolkit case. > this project which seems to be saying it uses PolicyKit privileges > know the mapping so it can call chkauthattr()? Does this project > chkauthattr is called in libpolkit. GPM just calls libpolkit API libpolkit_is_uid_allowed_for_privilege . Here I take suspend permission checkingas an example: libpolkit_is_uid_allowed_for_privilege(ctx, " hal-power-suspend", "user_name", "", NULL, &is_allowed, &is_temporary, NULL); In this example, "hal-power-suspend" right will be mapped to a new defined authorization in this function. > run as the user? If not how does it get the username or call > Yes, it runs as the user. > HAL/DBUS in the user context? > Does this project run with any privileges above the user's? > No. > Does it check authorizations every time it is invoked, to > > present the user with a list of current capabilities only? Does > Every time when GPM is started, it will check the user permission to decide whether to show those options to the user. > it check authorization only when told to do something? How does > Before some actions are really performed, similar checking will also be done. Though it is redundant because it will also be checked in HAL, this can improve the performance by reducing communication through DBus. > it audit any access control decisions? > All events and actions related power management will be recorded into memory by gnome-power-manager and can be seen from gnome-power-statistics. All failure permission checking requests will be logged into sys log. Jeff From sacadmin Sat Jan 5 09:37:13 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m05HbDl3009865; Sat, 5 Jan 2008 09:37:13 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m05HbC4Y020529; Sat, 5 Jan 2008 09:37:13 -0800 (PST) Received: from fe-apac-03.sun.com (fe-apac-03.sun.com [192.18.19.174] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m05Hb75f021238; Sat, 5 Jan 2008 17:37:07 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 <0JU600G01M0RY000@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) ; Sun, 06 Jan 2008 01:37:07 +0800 (SGT) Received: from [129.150.144.12] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU60084CM9TA0D1@mail-apac.sun.com>; Sun, 06 Jan 2008 01:37:07 +0800 (SGT) Date: Sun, 06 Jan 2008 01:37:05 +0800 From: Jeff Cai Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> Sender: Jeff.Cai@sun.com To: Gary Winiger Cc: Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477FC041.1080600@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) Status: RO Content-Length: 1963 (Sorry, Resend to resolve the format problem) Gary, I'll make some additional comments. > Yet it leaves this incomplete. What authorizations? How does > These new authorizations will be defined in libpolkit, which will be provided by power management team. (Randy Fishel and Phi Tran). I think they are still in discussion. Of course, as a consumer of libpolkit, GPM case depends on libpolkit case. > this project which seems to be saying it uses PolicyKit privileges > know the mapping so it can call chkauthattr()? Does this project > chkauthattr is called in libpolkit. GPM just calls libpolkit API libpolkit_is_uid_allowed_for_privilege Here I take suspend permission checkingas an example: libpolkit_is_uid_allowed_for_privilege(ctx, "hal-power-suspend", "user_name", "", NULL, &is_allowed, &is_temporary, NULL); In this example, "hal-power-suspend" right will be mapped to a new defined authorization in this function. > run as the user? If not how does it get the username or call > Yes, it runs as the user. > HAL/DBUS in the user context? > Does this project run with any privileges above the user's? > No. > Does it check authorizations every time it is invoked, to > > present the user with a list of current capabilities only? Does > Every time when GPM is started, it will check the user permission to decide whether to show those options to the user. > it check authorization only when told to do something? How does > Before some actions are really performed, similar checking will also be done. Though it is redundant because it will also be checked in HAL, this can improve the performance by reducing communication through DBus. > it audit any access control decisions? > All events and actions related power management will be recorded into memory by gnome-power-manager and can be seen from gnome-power-statistics. All failure permission checking requests will be logged into sys log. Jeff From sacadmin Sat Jan 5 11:00:17 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m05J0H59010762; Sat, 5 Jan 2008 11:00:17 -0800 (PST) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m05J0HXa036451; Sat, 5 Jan 2008 11:00:17 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m05J0CaR011792; Sat, 5 Jan 2008 11:00:12 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU600I01Q4A6600@fe-sfbay-10.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Sat, 05 Jan 2008 11:00:12 -0800 (PST) Received: from [192.168.1.100] ([75.6.231.214]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU600I1MQ4B5D00@fe-sfbay-10.sun.com>; Sat, 05 Jan 2008 11:00:12 -0800 (PST) Date: Sat, 05 Jan 2008 10:57:08 -0800 From: Artem Kachitchkine Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <477FC041.1080600@sun.com> Sender: Artem.Kachitchkin@sun.com To: Jeff Cai Cc: Gary Winiger , Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <477FD304.5040707@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> <477FC041.1080600@sun.com> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 661 >> Does it check authorizations every time it is invoked, to >> present the user with a list of current capabilities only? Does >> > Every time when GPM is started, it will check the user permission to > decide whether to show those options to the user. In other words, GPM only checks PolicyKit privileges for UI convenience, not for access control. It is not to prevent users from doing something, it is basically to tell the user: if you try this, you would be denied. This is not what a well-written application would do, but there's not much we can do right now, as Solaris has chosen to be a passive consumer of GNOME (for the most part). -Artem From sacadmin Mon Jan 7 01:13:59 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m079DxwQ003704; Mon, 7 Jan 2008 01:13:59 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m079Dw8g016369; Mon, 7 Jan 2008 01:13:59 -0800 (PST) Received: from fe-apac-03.sun.com (fe-apac-03.sun.com [192.18.19.174] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m079Dr0o013928; Mon, 7 Jan 2008 09:13:53 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 <0JU900G01N976V00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Mon, 07 Jan 2008 17:13:53 +0800 (SGT) Received: from [129.158.217.133] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JU9008DEOB3A0F1@mail-apac.sun.com>; Mon, 07 Jan 2008 17:13:52 +0800 (SGT) Date: Mon, 07 Jan 2008 17:14:11 +0800 From: "simon.zheng" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <1199550070.20228.8.camel@sr1-umpk-28> Sender: Simon.Zheng@sun.com To: John.Fischer@sun.com Cc: Gary Winiger , LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1199697251.24271.33.camel@goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.21.4 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801041842.m04IgHMQ006113@marduk.eng.sun.com> <477F097F.10500@sun.com> <1199550070.20228.8.camel@sr1-umpk-28> Status: RO Content-Length: 8182 John, Thanks for your suggestion. We'll try to check with HAL and PM team again, then post the summary of the issues ARCs raised, especially what Gary concerned about before. Thanks, -Simon On Sat, 2008-01-05 at 08:21 -0800, John Fischer wrote: > Irene and Simon, > > At this point in time we need to have a summary of the issues and > their current state. We also need to extend the timer. Once we > have the issues resolved we will need a new specification. > > Thanks, > > John > > > On Fri, 2008-01-04 at 20:37, simon.zheng wrote: > > Gary Winiger wrote: > > >>> Currently we plan GNOME Power Manager doesn't use RBAC auth directly, > > >>> instead, it still uses community PolicyKit privileges. > > >>> > > >>> How does this relate to the Solaris RBAC policy and Solaris > > >>> Audit? > > >>> > > >> In fact, it has nothing to do with this case. GNOME Power Manager only > > >> calls libpolkit API libpolkit_is_uid_allowed_for_privilege(). > > >> > > >> If you are interested in how to map PolKit privileges to RBAC auths, > > >> please look at libpolkit code. > > >> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/policykit/libpolkit/common/libpolkit-rbac.c#116 > > >> > > > > > > I'm not interested in reading code. I'm interested in the > > > architecture of things relevant to this case. In one place the > > > project stated that the GUI will examine authorizations. > > > > > > "Yeah. These functionalities are possibly > > > unavailable on some system or for some users. > > > Before doing real work, GNOME Power Manager will > > > check hardware capability and user authorization." > > > > > > "List all actions that need to do user auths checking. > > > > > > - Set cpufreq policy > > > - Suspend > > > - hibernate > > > - shutdown > > > - reboot, " > > > > > > Yet it leaves this incomplete. What authorizations? How does > > > this project which seems to be saying it uses PolicyKit privileges > > > know the mapping so it can call chkauthattr()? Does this project > > > run as the user? If not how does it get the username or call > > > HAL/DBUS in the user context? > > > Does this project run with any privileges above the user's? > > > Does it check authorizations every time it is invoked, to > > > present the user with a list of current capabilities only? Does > > > it check authorization only when told to do something? How does > > > it audit any access control decisions? > > > > > Maybe it's unsuitable to say "authorization" because this project > > doesn't call any chkauthattr() directly. To make it clear, please allow > > me use "PolicyKit privileges" instead of "authorization". Strickly > > "PolicyKit privileges" is a only concept from GNOME community. On > > Solaris, "PolicyKit privileges" is supported by libpolkit. This project > > will query libpolkit about some new "PolicyKit privileges", which will > > be supported in the coming PSARC hal case. > > > > "hal-power-cpu" > > "hal-power-suspend" > > "hal-power-hibernate" > > "hal-power-shutdown" > > "hal-power-reboot" > > > > GNOME Power Manager is a mere consumer of the core functionality provided by the PSARC cases. Real access control is completed inside libpolkit. And exact names of relevant authorizations will be listed in the coming two PSARC cases. > > > > gnome-power-manager session daemon is responsible for talking with HAL layer through D-Bus and libpolkit. This session daemon is autostarted by gnome-session when the user login JDS. It's unprivileged I think. And login user is the owner of gnome-power-manager. > > > > There's two cases to query libpolkit if the user is allowed for doing something. One is when we present the user a list of current capabilities, another is before calling corresponding hal method, i.e. suspend system. > > > > > > > > > >>> Is there some sort of big picture that shows how this all fits > > >>> together to be useful/usable to Solaris users? > > >>> > > >> Sorry, no specifal picture. I think everything looks easy from GNOME > > >> Power Manager's side. > > >> > > > > > > Perhaps, but that's not what I'm asking. How does this project > > > serve the customer? Do we have a shiny new toy that no one can > > > use? What does this project provide that enables the GUI to be > > > useful? If the answer is nothing, then what project does provide > > > it? Is there another project dependency on that project? What's > > > the general gist of that project? > > > > > > I suspect there's been enough discussion to warrent a new/final > > > spec to capture what depencences this case has and what it > > > will be doing and delivering. > > > > > I think I misunderstand what you want eariler.:) > > > > To clarify, this project will deliver several power-aware applications, > > and we call them together Desktop GNOME Power Manager infrastructure. > > The block diagram is as below. > > > > 4.1 Framework > > > > +----------------------------------------------------------------------+ > > | | > > |gnome-brightness-applet gnome-power-statistics gnome-power-preference | > > | | > > +--------------------------------------------+ | > > | D-Bus interface | | > > | org.freedesktop.PowerManagement | | > > +--------------------------------------------+ | > > | gnome-power-manager session | | > > | daemon | | > > +-----------------------------------------+--+-------------------------+ > > ^ ^ > > | (D-bus) | > > | | JDS consolidation (up) > > -----------------+-----------------------------+----------------------------- > > | | ON consolidation (below) > > | (D-bus) | > > v V > > +-----------------------------------------+ +-----------+ > > | HAL daemon (hald) | | libpolkit | > > +----------------+ +------------------+ | +-----------+ > > |hald-addon-acpi | |hald-addon-cpufreq| | > > |daemon | |daemon | | > > +-------------------------------------+---+ > > ^ | > > | +-----------------+ > > | | Power.conf | > > | | pmconfig utility| > > | +-----------------+ > > | | user space > > ---------+-------------------------+--------------------------------------- > > | | kernel space > > v v > > +-------------------+ +-------------------+ > > | battery, lid | | power management | > > | brightness drivers| | framewok | > > +-------------------+ +-------------------+ > > > > Among them, gnome-power-preferences, gnome-power-statistics, gnome-brightness-applet are GUI applications, which serve desktop users. In addition, system tray icon controlled by gnome-power-manager is also visiable for users. Screenshot is here > > http://jdsbj.prc/wiki//index.php/Evaluation_of_GNOME_Power_Manager#ScreenShots_from_Linux > > > > Regarding depencency, particularly below two are putback dependency. > > CPUfreq HAL PSARC/2007/679 > > HAL suspend/hibernate, and lid, brightness, power buttons event TBD in PSARC case soon > > > > -Simon > > > > > > > Gary.. > > > > > > From sacadmin Mon Jan 7 11:52:58 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m07JqwC0016184; Mon, 7 Jan 2008 11:52:58 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m07JqvqA015028; Mon, 7 Jan 2008 11:52:58 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m07Jq5PY009134; Mon, 7 Jan 2008 11:52:05 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m07Jq5k4009133; Mon, 7 Jan 2008 11:52:05 -0800 (PST) Date: Mon, 7 Jan 2008 11:52:05 -0800 (PST) From: Gary Winiger Message-Id: <200801071952.m07Jq5k4009133@marduk.eng.sun.com> To: Simon.Zheng@sun.com, gww@eng.sun.com Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] Status: RO Content-Length: 1870 > >> Sorry, no specifal picture. I think everything looks easy from GNOME > >> Power Manager's side. > >> > > > > Perhaps, but that's not what I'm asking. How does this project > > serve the customer? Do we have a shiny new toy that no one can > > use? What does this project provide that enables the GUI to be > > useful? If the answer is nothing, then what project does provide > > it? Is there another project dependency on that project? What's > > the general gist of that project? > > > > I suspect there's been enough discussion to warrent a new/final > > spec to capture what depencences this case has and what it > > will be doing and delivering. > > > I think I misunderstand what you want eariler.:) > > To clarify, this project will deliver several power-aware applications, > and we call them together Desktop GNOME Power Manager infrastructure. > The block diagram is as below. I guess I have still not been clear. If I understand correctly, this project proposes a GUI that calls HAL in the context of a user. HAL (policykit) enforces some set of authorizations via other projects upon which this project is dependent. (The battery status query doesn't really require authorization.) Part of the big picture I've been asking about is: Which users are authorized to do the operations that require authorization? How do they get authorized? How is this project useful (other than reporting battery status) without some idea of who and how the user gets authorized? If that is not part of this project, what project is it part of? Hopefully the new spec will discuss this along with all the case dependences. A further question: since authorizations can be granted to/removed from a user at any time, how will the GUI present what the user is allowed to do (modulo the HW capabilities of the system)? Gary.. From sacadmin Tue Jan 8 02:25:41 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m08APf1u009139; Tue, 8 Jan 2008 02:25:41 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m08APePE038166; Tue, 8 Jan 2008 02:25:40 -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 m08APYVI024881; Tue, 8 Jan 2008 10:25:34 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 <0JUB00G01M5QHQ00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Tue, 08 Jan 2008 18:25:34 +0800 (SGT) Received: from [129.158.217.183] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JUB00LDCMALPBJX@mail-apac.sun.com>; Tue, 08 Jan 2008 18:25:34 +0800 (SGT) Date: Tue, 08 Jan 2008 18:25:33 +0800 From: "simon.zheng" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/10/2008] In-reply-to: <200801071952.m07Jq5k4009133@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <47834F9D.6050205@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: <200801071952.m07Jq5k4009133@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) Status: RO Content-Length: 5043 Hi Gary, Gary Winiger wrote: >>>> Sorry, no specifal picture. I think everything looks easy from GNOME >>>> Power Manager's side. >>>> >>>> >>> Perhaps, but that's not what I'm asking. How does this project >>> serve the customer? Do we have a shiny new toy that no one can >>> use? What does this project provide that enables the GUI to be >>> useful? If the answer is nothing, then what project does provide >>> it? Is there another project dependency on that project? What's >>> the general gist of that project? >>> >>> I suspect there's been enough discussion to warrent a new/final >>> spec to capture what depencences this case has and what it >>> will be doing and delivering. >>> >>> >> I think I misunderstand what you want eariler.:) >> >> To clarify, this project will deliver several power-aware applications, >> and we call them together Desktop GNOME Power Manager infrastructure. >> The block diagram is as below. >> > > I guess I have still not been clear. If I understand correctly, > this project proposes a GUI that calls HAL in the context of > a user. HAL (policykit) enforces some set of authorizations > via other projects upon which this project is dependent. (The > battery status query doesn't really require authorization.) > Right! Since applications in this project are unable to override any privilege and authorization, they are unprivileged. Running real actions have to turn to HAL or libpolkit. > Part of the big picture I've been asking about is: > Which users are authorized to do the operations that require > authorization? > How do they get authorized? > Checking with HAL and Power Management team, some new HAL-related PSARC case is about to be filed, including lid switching, brightness, power button, suspend/hibernate. Revelant RBAC auths details will be documented there. Based on them, we'll post a new spec, which will describe when we check via libpolkit and what's done in response to checking result. > How is this project useful (other than reporting battery status) > without some idea of who and how the user gets authorized? > If that is not part of this project, what project is it part of? > > Do you point the role of this project or purpose? If yes, try to answer below. This project has provided with GUI directly faced with end users. So no extra project above this project is needed. Actually different applications in this project play different roles well, policy agent, or configuration tool, or displaying status. For example, - gnome-power-preferences is a configuration GUI. Through it, desktop user defines his favorite power management policy (such as suspend when lid is closed). - gnome-power-manager session daemon is basically a policy agent talking with HAL layer. It receives HAL event and enforce prefined policy (calling HAL method to do real job). - gnome-brightness-applet serves a GUI to adjust brightness. I guess feature list maybe a bit unclear in preview spec. List again other than battery. - CPUfreq. Allow the GUI user to set CPU power management policy conveniently. - Laptop lid switching. When lid is closed, GPM will trigger an action predefined by the desktop user, blank screen or suspend, hibernate. Particularly, blanking screen relies on X11 extension DPMS (PSARC/1998/299). - Brightness adjustment. A GUI application will be provided for user to adjust LCD brightness manually, which looks like voice volume adjustment. Also, for laptop user, when pressing hotkey brightness down/up (i.e. "Fn+F6/F7" on Toshiba laptop), GPM will pop up a progress bar to show brightness status. - Power button. After you login JDS, pressing power button will make HAL emit a signal to notify GPM. Then GPM will take a prefined action, suspend or hibernate or shutdown. - Suspend/Hibernate buttons. On system tray area, GPM provides user some shortcut button to suspend/hibernate system. - Power consumption statistics. A separate application will draw some graphs, which allow the user to visualize how the battery power volume is consumed in his system. > Hopefully the new spec will discuss this along with all the > case dependences. > > Sure. > A further question: since authorizations can be granted to/removed > from a user at any time, how will the GUI present what the user > is allowed to do (modulo the HW capabilities of the system)? > Yes, this inconsistent case possibly happens. We'll try our best to avoid it. Firstly, the inconsistent chance is very small since we check *every time* populating graph interface. For example of suspend button, button actually is *not* always showed on desktop. Only when you click GPM tray icon, button is populated. Once move out mouse, button disappeared. So most of auths change is fine with this project. Secondly, in case the inconsistent thing occurs, auths checking inside HAL layer will make sure nothing is done. hald is privileged and will check auth before running real action. -Simon > Gary.. > From sacadmin Tue Jan 15 22:30:22 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0G6UM8B010899; Tue, 15 Jan 2008 22:30:22 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0G6ULQu045204; Tue, 15 Jan 2008 22:30:22 -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 m0G6UGc1006239; Wed, 16 Jan 2008 06:30:16 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 <0JUQ00B014QDQ800@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Wed, 16 Jan 2008 14:30:15 +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 <0JUQ007PR4QEXDP6@mail-apac.sun.com>; Wed, 16 Jan 2008 14:30:15 +0800 (SGT) Date: Wed, 16 Jan 2008 14:28:05 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/24/2008] In-reply-to: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Sender: Irene.Huang@sun.com To: Shi-Ying Irene Huang Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com, Irene Huang Message-id: <1200464886.1647.108.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200712270746.lBR7kb1m024254@sac.sfbay.sun.com> Status: RO Content-Length: 14384 LSARC, The updated spec file for Gnome Power Manager can be found at http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-V2.txt The diff from the first version of GPM-spec (gpm-one-pager.txt) is at http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM_spec_v2.diff I am setting the new timeout to be Jan 24th, 2008. Please review Thanks --Irene On Wed, 2007-12-26 at 23:46 -0800, Shi-Ying Irene Huang wrote: > Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI > This information is Copyright 2007 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > GNOME Power Manager > 1.2. Name of Document Author/Supplier: > Author: Simon Zheng > 1.3 Date of This Document: > 26 December, 2007 > 4. Technical Description > 1. Introduction > 1.1. Project/Component Working Name: > GNOME Power Manager > > 1.2. Name of Document Author/Supplier: > Author: Simon Zheng > > 1.3 Date of This Document: > Dec 27th, 2007 > > 2. Background > This project provides Solaris users with a GNOME Power Manager infrastructure. > Solaris has integrated HAL via PSARC/2005/399 Tamarack project, and PSARC 2006/601 > Battery project and PSARC/2007/679 CPUFreq HAL enhance more power management > properties. Based on them, GNOME Power Manager will be able to support many > power management features, such as suspending, hibernating, brightness adjustment, > lid closure action, CPU frequency scaling, and etc. > > 3. Business Consideration > GNOME Power Manager[1] supplies many modern power management features. It's > valuable to attract more developer users for Solaris, especially laptop users. > Also, it has been a part of official GNOME release since GNOME 2.14 and is > delivered in many Linux distributions at present. So this project can fill the > gap between Linux and Solaris too. > > 4. Technical Description > This project will port GNOME Power Manager to Solaris, which stems from GNOME > community. Then we'll keep tracking community and provide upstream changes > back to them. > > 4.1 Framework > > +-----------------------------------------------------------------------+ > | | > |gnome-brightness-applet gnome-power-statistics gnome-power-preference | > | | > +--------------------------------+ | > | D-Bus interface | | > | org.freedesktop.PowerManagement| | > +--------------------------------+ | > | gnome-power-manager | | > | daemon | | > +--------------------------------+--------------------------------------+ > ^ > | (D-bus) > | JDS consolidation (up) > -----------------+-------------------------------------------------------------- > | ON consolidation (below) > | (D-bus) > v > +-----------------------------------------+ > | HAL daemon (hald) | > +----------------+ +------------------+ | > |hald-addon-acpi | |hald-addon-cpufreq| | > |daemon | |daemon | | > +-------------------------------------+---+ > ^ | > | +-----------------+ > | | Power.conf | > | | pmconfig utility| > | +-----------------+ > | | user space > ---------+-------------------------+--------------------------------------- > | | kernel space > v v > +-------------------+ +-------------------+ > | battery, lid | | power management | > | brightness drivers| | framewok | > +-------------------+ +-------------------+ > > GNOME Power Manager infrastructure is composed of several parts, gnome-power-manager > daemon, gnome-power-preferences, gnome-power-statistics, gnome-brightness and D-Bus > interfaces "org.freedesktop.PowerManagement". > > gnome-power-manager daemon is a backend session-daemon which is automatically started > by gnome-session when logging in GNOME desktop session. It provides a complete and > integrated solution to power management under GNOME desktop environment. It supports > suspending, hibernating, screen blanking, lid closure action, CPU frequency scaling, > and etc. > > gnome-power-preferences is a GUI configuration program. It allows users to define > their favorite policies in terms of power source. These policies are enforced by > gnome-power-manager daemon. > > gnome-power-statistics is also a GUI program and allows users to visualize the power > consumption of laptop hardware. > > gnome-brightness-applet is a gnome-panel applet, which serves for displaying and > adjusting LCD screen brightness level. > > And D-Bus interfaces "org.freedesktop.PowerManagement" are exported to be used for > other up-level applications. > > 4.2 Battery monitor & configuration switching > GNOME Power Manager not only reports battery status but also supports power > management policies. Using gnome-power-preferences users are able to define > different policies for AC and battery. The policy may be an action when battery > becomes very low, or what action would be triggered when lid is closed. Then, > when switching the power source, corresponding policy will be switched accordingly. > For example, unplugging AC adapter, GNOME Power Manager immediately replaces > battery's policy with AC's. This makes system look smarter. > > 4.3 Brightness, lid and power buttons > On laptop, when brightness up/down is pressed, gnome-power-manager will receive > relevant button event and then pop up a progress bar to show brightness status. > When lid is closed, GNOME Power Manager will trigger a defined action, such as > blank screen, suspend, hibernate. Pressing power button, it will also do the > specified policy. All above buttons events require HAL support. > > 4.4 CPU frequency scaling > At present, CPUFreq HAL supports two types of CPU power management policies, "On > Demand" and "Performance". "On Demand" means dynamic CPU frequency scaling is > performed by monitoring CPU utilization and scaling the frequency when appropriate. > "Performance" means getting full CPU utilization all the time. Both policies can > be configured from GNOME Power Manager. > > 4.5 Suspend/hibernate and its capability and authorization checking > Suspend (suspend to RAM) and hibernate (suspend to disk) functionalities are based on > the HAL D-Bus interface "org.freedesktop.Hal.Device.SystemPowerManagement". Before > showing users suspend/hibernate configuration, GNOME Power Manager will check both > hardware capability and user authorization. Hardware capability checking relies on > HAL's interface "power_management.can_suspend", and user authorization checking uses > HAL's libpolkit. > > 4.6 Dependency > GNOME Power Manager heavily depends on HAL layer. Some basic HAL calling methods, > such as "GetPropertyString" and "SetPropertyString", are provided by "Removable > Media Enhancements in Solaris" (PSARC/2005/399). Libpolkit is also from the same. > Battery interfaces are from Battery Project (PSARC/2006/601). CPUFreq scaling > interfaces is supplied by CPUFreq HAL (PSARC/2007/679). Other interfaces about > suspend/hibernate, Brightness, lid and power button are under development and will > be provided soon. In addition, screen blanking depends on X11 DPMS extension > (PSARC/1998/299). > > > 5. Interface Tables > > Exported Interface > > Interface Name Classification Comment > ------------------- --------------- -------------- > SUNWgnome-power-manager-root Uncommitted GNOME Power Manager - / filesystem > > /etc/gconf/schemas/gnome-power-manager.schemas Volatile Gconf schema definition file > > > SUNWgnome-power-manager Uncommitted GNOME Power Manager > > /usr/bin/gnome-power-manager Volatile Session daemon > > /usr/bin/gnome-power-preferences Volatile Configuration GUI > > /usr/bin/gnome-power-statistic Volatile GUI to show power consumption statistic > > /usr/lib/gnome-brightness-applet Volatile gnome-panel applet to adjust brightness > > /usr/lib/gnome-power-bugreport.sh Volatile Bug reporter tool > > /usr/lib/gnome-power-cmd.sh Volatile Command-line tool to run suspend/hibernate/shutdown. > > /usr/lib/bonobo/servers/GNOME_BrightnessApplet.server Volatile Bonobo service configuration file > > /usr/share/applications/gnome-power-preferences.desktop Volatile Start menu configuration file > > /usr/share/applications/gnome-power-statistic.desktop Volatile The same as above > > /usr/share/gnome/autostart/gnome-power-manager.desktop Volatile Autostart configuration > > /usr/share/dbus-1/services/gnome-power-manager.service Volatile D-Bus services configuration file > > /usr/share/gnome-2.0/ui/GNOME_BrightnessApplet.xml Volatile Gnome-panel configuration file > > /usr/share/gnome-power-manager Volatile Installation location for glade files, images > > /usr/share/gnome/help/gnome-power-manager Volatile GNOME help documentation > > > > Exported Interface > > Please see attached. All interfaces are Volatile. > > > Imported Interface > > Interface Name Classification ARC Case Comment > ------------------- --------------- -------------- --------------------------------- > GNOME Committed Platform Libraries Committed LSARC/2007/520 GTK+ library > GNOME 2.20 > > gnome-panel Volatile LSARC/2001/348 Window Navigator Construction Kit > GNOME Panel > > D-BUS Volatile LSARC/2006/368 D-Bus library. > D-BUS Message Bus System > > libXext/libX11 Committed PSARC/1998/299 DPMS extension > X11R6.4: Update/upgrade > of X Server > > HAL API Volatile PSARC/2005/399 Basic HAL API Tamarack: Removable > Media Enhancements > > libpolkit Volatile PSARC/2005/399 Check permission to suspend/hibernate > Tamarack: Removable > Media Enhancements > > Battery HAL Volatile PSARC/2006/601 Transfer ACPI battery event > Battery Project > > CPUfreq HAL Volatile PSARC/2007/679 Supply CPU freq scaling backend > CPUfreq HAL > > HAL suspend/hibernate,lid, Volatile TBD in PSARC soon Transfer suspend/hibernate, ACPI lid, > brightness, power buttons event brightness and power buttons event > > > 6. Resources and Schedule > 6.1 Release Binding > Target to a minor release of Solaris > > 6.2 Resources: > 4.00 man month Development Engineering > 1.0 man month Test Engineering > 0.25 man month RE integration > 0.5 man month Doc. writer > 0.5 man month Program management > > 6.3. Consolidation C-team Name: JDS/GNOME > > 6.4. ARC review type: FastTrack > > > 7. References > [1] GNOME Power Mnanger homepage > www.gnome.org/projects/gnome-power-manager > > [2] OpenSolaris laptop project > http://www.opensolaris.org/os/community/laptop/ > > Related ARC case > LSARC/2007/520 GNOME 2.20 > LSARC/2001/348 GNOME Panel > LSARC/2006/368 D-BUS Message Bus System > PSARC/1998/299 X11R6.4: Update/upgrade of X Server > PSARC/2005/399 Tamarack: Removable Media Enhancements in Solaris > PSARC/2006/601 Battery Project > PSARC/2007/679 CPUFreq HAL > TBD in PSARC soon Suspend/hibernate, lid, brightness and power buttons HAL & driver > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > JDS > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From sacadmin Wed Jan 16 11:33:33 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0GJXXPf029435; Wed, 16 Jan 2008 11:33:33 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0GJXXoI063881; Wed, 16 Jan 2008 11:33:33 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m0GJWSlN003462; Wed, 16 Jan 2008 11:32:28 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m0GJWS31003461; Wed, 16 Jan 2008 11:32:28 -0800 (PST) Date: Wed, 16 Jan 2008 11:32:28 -0800 (PST) From: Gary Winiger Message-Id: <200801161932.m0GJWS31003461@marduk.eng.sun.com> To: sh162551@sac.sfbay.sun.com, Irene.Huang@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/24/2008] Cc: LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com X-Sun-Charset: US-ASCII Status: RO Content-Length: 751 > The updated spec file for Gnome Power Manager can be found at > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-V2.txt > > The diff from the first version of GPM-spec (gpm-one-pager.txt) is at > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM_spec_v2.diff > > I am setting the new timeout to be Jan 24th, 2008. I'm away on holiday and have interest here as noted before. I won't have the opportunity to review before the 24th. I hope to be able to review then. In particular with relationship to currently running and past PSARC cases. I did get a private copy from Simon 2300 Monday asking for review, so I really didn't expect to see the case restarted Tue at 2200. Cutting to the chase, More time Please. Gary.. From sacadmin Wed Jan 16 17:56:52 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0H1uqGZ017824; Wed, 16 Jan 2008 17:56:52 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0H1up09029120; Wed, 16 Jan 2008 17:56:51 -0800 (PST) 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 m0H1uj4e015072; Thu, 17 Jan 2008 01:56:45 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 <0JUR00L01MQFOR00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Thu, 17 Jan 2008 09:56:45 +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 <0JUR00C5MMQKG2D0@mail-apac.sun.com>; Thu, 17 Jan 2008 09:56:45 +0800 (SGT) Date: Thu, 17 Jan 2008 09:54:35 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/24/2008] In-reply-to: <200801161932.m0GJWS31003461@marduk.eng.sun.com> Sender: Irene.Huang@sun.com To: Gary Winiger Cc: sh162551@sac.sfbay.sun.com, LSARC@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1200534875.1647.136.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801161932.m0GJWS31003461@marduk.eng.sun.com> Status: RO Content-Length: 931 Hi, Gary Let's put the timeout to be Jan 31st, would that be fine for you? --Irene On Wed, 2008-01-16 at 11:32 -0800, Gary Winiger wrote: > > The updated spec file for Gnome Power Manager can be found at > > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-V2.txt > > > > The diff from the first version of GPM-spec (gpm-one-pager.txt) is at > > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM_spec_v2.diff > > > > I am setting the new timeout to be Jan 24th, 2008. > > I'm away on holiday and have interest here as noted before. > I won't have the opportunity to review before the 24th. > I hope to be able to review then. In particular with relationship > to currently running and past PSARC cases. > I did get a private copy from Simon 2300 Monday asking for > review, so I really didn't expect to see the case restarted > Tue at 2200. > > Cutting to the chase, More time Please. > > Gary.. From sacadmin Mon Jan 28 16:47:16 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0T0lG4U029500; Mon, 28 Jan 2008 16:47:16 -0800 (PST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0T0lFhU053985; Mon, 28 Jan 2008 16:47:15 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m0T0jtsw029709; Mon, 28 Jan 2008 16:45:55 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m0T0jtYv029708; Mon, 28 Jan 2008 16:45:55 -0800 (PST) Date: Mon, 28 Jan 2008 16:45:55 -0800 (PST) From: Gary Winiger Message-Id: <200801290045.m0T0jtYv029708@marduk.eng.sun.com> To: Irene.Huang@sun.com, gww@eng.sun.com Cc: LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/24/2008] Status: RO Content-Length: 1163 > Let's put the timeout to be Jan 31st, would that be fine for you? Thanks. And thanks for the updated spec. I'd hoped to get to this yesterday, but here goes: It's unlikely I'll be able to attend the meeting tomorrow -- personal conflicts, but I'll try to get to any email before the meeting. In any case I think these are minor. Issue or maybe Nit: The PSARC/2007/679 CPUFreq HAL and PSARC/2008/021 GNOME Power Manager support cases export polkit privileges. CPUFreq seems to have a contract in place for importing the polkit privileges here. I see no prototype contract fot the PSARC GPM case. Secondly, the PSARC GPM case is implying that the LSARC GPM case is to specify the the default values for lid, brightness, power and by implication CPUFreq. IMO, that is backwards, and still needs to be worked out. Issue: Lid switching. It would seem to me that entering screen lock would be a required action in the set of selectable actions -- and from a security perspective the default. It certainly is a selectable option on MacOS: "Require password to wake this computer from sleep or screen saver" is what it is called. Gary.. From sacadmin Mon Jan 28 23:27:36 2008 Received: from marduk.eng.sun.com (marduk [129.146.108.224]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0T7Ra7K007222 for ; Mon, 28 Jan 2008 23:27:36 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m0T7QG1B001550; Mon, 28 Jan 2008 23:26:16 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m0T7QGoI001549; Mon, 28 Jan 2008 23:26:16 -0800 (PST) Date: Mon, 28 Jan 2008 23:26:16 -0800 (PST) From: Gary Winiger Message-Id: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> To: gww@eng.sun.com, Phi.Tran@sun.com Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout 01/30/2008] 2007/702 Cc: David.Chieu@sun.com, Irene.Huang@sun.com, PSARC-ext@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com, lsarc@sac.sfbay.sun.com X-Sun-Charset: US-ASCII x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1165 Phi, > >> And most importantly, it would seem to me that entering > >> screen lock would be a required action in the set of selectable > >> actions -- and from a security perspective the default. > >> It certainly is a selectable option on MacOS: > >> "Require password to wake this computer from sleep or screen > >> saver" is what it is called. > > > > > > Screen locking is not required. What policy are you referencing that > > makes it a requirement? > > I thought you meant a separate action, but if you mean GPM must lock the > screen before sleeping, etc., then yes, that will happen. I'm not concerned that it be a separate GPM (either PSARC or LSARC case) action, but that it be supportable during such things as lid close/sleep/hibernate. > >> How does this case provide for a screen lock on lid switching? > >> > > This PSARC case doesn't directly handle the screen locking, but GPM > will call the xscreensaver-command before the actions such as suspend > or blank screen. Too many GPMs, I presume you mean LSARC 2007/702 GPM. It would be really good to have it specify its architectural operations. Gary.. From gww@eng.sun.com Mon Jan 28 23:27:42 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0T7RgxH007245 for ; Mon, 28 Jan 2008 23:27:42 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0T7Re6n001177; Mon, 28 Jan 2008 23:27:41 -0800 (PST) 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 <0JVE00G0FA23JK00@brm-avmta-1.central.sun.com>; Tue, 29 Jan 2008 00:27:39 -0700 (MST) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVE00LV1A22BI60@brm-avmta-1.central.sun.com>; Tue, 29 Jan 2008 00:27:38 -0700 (MST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0T7RaaK065205; Mon, 28 Jan 2008 23:27:36 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m0T7QG1B001550; Mon, 28 Jan 2008 23:26:16 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m0T7QGoI001549; Mon, 28 Jan 2008 23:26:16 -0800 (PST) Date: Mon, 28 Jan 2008 23:26:16 -0800 (PST) From: Gary Winiger Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout 01/30/2008] 2007/702 To: gww@eng.sun.com, Phi.Tran@sun.com Cc: David.Chieu@sun.com, Irene.Huang@sun.com, PSARC-ext@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com, lsarc@sac.sfbay.sun.com Message-id: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.2.0.264296 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1165 Phi, > >> And most importantly, it would seem to me that entering > >> screen lock would be a required action in the set of selectable > >> actions -- and from a security perspective the default. > >> It certainly is a selectable option on MacOS: > >> "Require password to wake this computer from sleep or screen > >> saver" is what it is called. > > > > > > Screen locking is not required. What policy are you referencing that > > makes it a requirement? > > I thought you meant a separate action, but if you mean GPM must lock the > screen before sleeping, etc., then yes, that will happen. I'm not concerned that it be a separate GPM (either PSARC or LSARC case) action, but that it be supportable during such things as lid close/sleep/hibernate. > >> How does this case provide for a screen lock on lid switching? > >> > > This PSARC case doesn't directly handle the screen locking, but GPM > will call the xscreensaver-command before the actions such as suspend > or blank screen. Too many GPMs, I presume you mean LSARC 2007/702 GPM. It would be really good to have it specify its architectural operations. Gary.. From sacadmin Mon Jan 28 23:49:21 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0T7nLVg007311 for ; Mon, 28 Jan 2008 23:49:21 -0800 (PST) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0T7nLOn005945 for ; Mon, 28 Jan 2008 23:49:21 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0T7nGps020721 for ; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVE00C01AYLLG00@fe-sfbay-09.sun.com> (original mail from Phi.Tran@Sun.COM) for lsarc@sac.eng.sun.com; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVE00M54B23QOC0@fe-sfbay-09.sun.com>; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Date: Mon, 28 Jan 2008 23:58:48 -0800 From: Phi Tran Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout 01/30/2008] 2007/702 In-reply-to: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> Sender: Phi.Tran@sun.com To: Gary Winiger Cc: David.Chieu@sun.com, Irene.Huang@sun.com, PSARC-ext@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com, lsarc@sac.sfbay.sun.com Message-id: <479EDCB8.7030104@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 Status: RO Content-Length: 1424 Gary Winiger wrote: > Phi, > > >>>> And most importantly, it would seem to me that entering >>>> screen lock would be a required action in the set of selectable >>>> actions -- and from a security perspective the default. >>>> It certainly is a selectable option on MacOS: >>>> "Require password to wake this computer from sleep or screen >>>> saver" is what it is called. >>> >>> >>>Screen locking is not required. What policy are you referencing that >>>makes it a requirement? >> >>I thought you meant a separate action, but if you mean GPM must lock the >>screen before sleeping, etc., then yes, that will happen. > > > I'm not concerned that it be a separate GPM (either PSARC or > LSARC case) action, but that it be supportable during such > things as lid close/sleep/hibernate. > > >>>> How does this case provide for a screen lock on lid switching? >>>> >> >>This PSARC case doesn't directly handle the screen locking, but GPM >>will call the xscreensaver-command before the actions such as suspend >>or blank screen. > > > Too many GPMs, I presume you mean LSARC 2007/702 GPM. It would > be really good to have it specify its architectural operations. Yes, I meant the LSARC case. Thinking about it now, I should have called my case Philadelphia to help avoid some confusion :) We'll work together with the JDS folks to detail more about the architectural operations. Phi From Phi.Tran@sun.com Mon Jan 28 23:49:25 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 m0T7nN9c007316 for ; Mon, 28 Jan 2008 23:49:24 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m0T7nIc7026413; Tue, 29 Jan 2008 15:49:21 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVE00J05B25R300@nwk-avmta-1.sfbay.Sun.COM>; Mon, 28 Jan 2008 23:49:17 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVE00HOTB24EG10@nwk-avmta-1.sfbay.Sun.COM>; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0T7nG9Z020722; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVE00C01AYLLG00@fe-sfbay-09.sun.com> (original mail from Phi.Tran@Sun.COM); Mon, 28 Jan 2008 23:49:16 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVE00M54B23QOC0@fe-sfbay-09.sun.com>; Mon, 28 Jan 2008 23:49:16 -0800 (PST) Date: Mon, 28 Jan 2008 23:58:48 -0800 From: Phi Tran Subject: Re: GNOME Power Management Support [PSARC/2008/021 FastTrack timeout 01/30/2008] 2007/702 In-reply-to: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> Sender: Phi.Tran@sun.com To: Gary Winiger Cc: David.Chieu@sun.com, Irene.Huang@sun.com, PSARC-ext@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com, lsarc@sac.sfbay.sun.com Message-id: <479EDCB8.7030104@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200801290726.m0T7QGoI001549@marduk.eng.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 Status: RO Content-Length: 1424 Gary Winiger wrote: > Phi, > > >>>> And most importantly, it would seem to me that entering >>>> screen lock would be a required action in the set of selectable >>>> actions -- and from a security perspective the default. >>>> It certainly is a selectable option on MacOS: >>>> "Require password to wake this computer from sleep or screen >>>> saver" is what it is called. >>> >>> >>>Screen locking is not required. What policy are you referencing that >>>makes it a requirement? >> >>I thought you meant a separate action, but if you mean GPM must lock the >>screen before sleeping, etc., then yes, that will happen. > > > I'm not concerned that it be a separate GPM (either PSARC or > LSARC case) action, but that it be supportable during such > things as lid close/sleep/hibernate. > > >>>> How does this case provide for a screen lock on lid switching? >>>> >> >>This PSARC case doesn't directly handle the screen locking, but GPM >>will call the xscreensaver-command before the actions such as suspend >>or blank screen. > > > Too many GPMs, I presume you mean LSARC 2007/702 GPM. It would > be really good to have it specify its architectural operations. Yes, I meant the LSARC case. Thinking about it now, I should have called my case Philadelphia to help avoid some confusion :) We'll work together with the JDS folks to detail more about the architectural operations. Phi From sacadmin Tue Jan 29 03:34:40 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0TBYerO012660; Tue, 29 Jan 2008 03:34:40 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0TBYdBM024227; Tue, 29 Jan 2008 03:34:40 -0800 (PST) Received: from fe-apac-03.sun.com (fe-apac-03.sun.com [192.18.19.174] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0TBYaDW007587; Tue, 29 Jan 2008 11:34:36 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 <0JVE00301KSKQ100@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Tue, 29 Jan 2008 19:34:34 +0800 (SGT) Received: from [129.158.217.123] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JVE00ANILHJTQ42@mail-apac.sun.com>; Tue, 29 Jan 2008 19:34:33 +0800 (SGT) Date: Tue, 29 Jan 2008 19:34:56 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack timeout 01/24/2008] In-reply-to: <200801290045.m0T0jtYv029708@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: Irene.Huang@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1201606496.1883.95.camel@setpoint> MIME-version: 1.0 X-Mailer: Evolution 2.12.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200801290045.m0T0jtYv029708@marduk.eng.sun.com> Status: RO Content-Length: 2404 On Mon, 2008-01-28 at 16:45 -0800, Gary Winiger wrote: > > Let's put the timeout to be Jan 31st, would that be fine for you? > > Thanks. And thanks for the updated spec. > > I'd hoped to get to this yesterday, but here goes: > It's unlikely I'll be able to attend the meeting tomorrow > -- personal conflicts, but I'll try to get to any email before > the meeting. In any case I think these are minor. > > Issue or maybe Nit: The PSARC/2007/679 CPUFreq HAL and > PSARC/2008/021 GNOME Power Manager support cases export > polkit privileges. CPUFreq seems to have a contract > in place for importing the polkit privileges here. > I see no prototype contract fot the PSARC GPM case. Gary, thanks for your review again. To be more clear, we'll make a new contract with PSARC case for libpolkit interfaces. > Secondly, the PSARC GPM case is implying that the > LSARC GPM case is to specify the the default values > for lid, brightness, power and by implication CPUFreq. > IMO, that is backwards, and still needs to be worked out. Sure, we'll work together with them for this. Here, I would like add a little comments. So far GPM is a only session-wide utilities, and hald is a system-wide service. GPM is a consumer of HAL. Without consumer, nothing will be done in HAL. So the default value is left to actual consumer's side. Each user logs into JDS for the first time will get these default values, lid do nothing, brightness do nothing, power button is set as "ask me". And then, only if the user has enough permission, these value are allowed to change. I will describe the default values in next version of spec. > > Issue: Lid switching. It would seem to me that entering > screen lock would be a required action in the set of selectable > actions -- and from a security perspective the default. > It certainly is a selectable option on MacOS: > "Require password to wake this computer from sleep or screen > saver" is what it is called. Good question. Currently LSARC GPM has supported screen lock, which is associated with 3 actions, blank screen, suspend and hibernate. I think I miss this in previous spec. I'll state this on our next spec. Additionally, project team would like to add an checkbox on configuration GUI to allow user to disable or enable "screen lock when blanking screen or resuming". By default, it's enabled. Thanks, -Simon > > Gary.. From gww@eng.sun.com Mon Feb 4 09:43:24 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m14HhOGo010166 for ; Mon, 4 Feb 2008 09:43:24 -0800 (PST) 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 m14HhN20026179; Mon, 4 Feb 2008 09:43:24 -0800 (PST) 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 <0JVQ00G0B6KB6200@brm-avmta-1.central.sun.com>; Mon, 04 Feb 2008 10:43:23 -0700 (MST) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVQ006026K9U280@brm-avmta-1.central.sun.com>; Mon, 04 Feb 2008 10:43:21 -0700 (MST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m14Hgw3K002733; Mon, 04 Feb 2008 09:42:58 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m14HfTX8014655; Mon, 04 Feb 2008 09:41:29 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m14HfTRw014654; Mon, 04 Feb 2008 09:41:29 -0800 (PST) Date: Mon, 04 Feb 2008 09:41:29 -0800 (PST) From: Gary Winiger Subject: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends To: lsarc@sun.com, psarc-ext@sun.com, tpm@eng.sun.com Cc: Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, gww@eng.sun.com, james.hughes@sun.com, john.plocher@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <200802041741.m14HfTRw014654@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 5622 I wanted to update the case relative to the meeting I had with the case owner, submitter, and other's of the ON power management team after PSARC 30 Jan. As an aside, I'll not be present at 6 Feb PSARC and will be in and out on personal business the next couple weeks. Sorry for the length. I'm trying to bring too many things together in too short a time. I have to take some personal time over the next few weeks. This whole thing is looking more and more to me like a train wreck. I'm still quite concerned that there is no coordinated big picture of how things fit together from PSARC/2005/339 Tamarack: Removable Media Enhancements (which I was lead to believe introduced libpolkit interpreted by hald) and now PSARC/2007/679 CPUFreq HAL and PSARC/2008/021 HAL Power Mgmt Support which seemingly add to the Tamarack hald/libpolkit and finally LSARC/2007/702 GNOME Power Manager which seemingly calls the Tamarack hald/libpolkit to effect system power management. PSARC/2008/034 Defining Workstation Owner also may come into play. Recent communications with the Tamarack team now lead me to believe libpolkit and it's associated daemon are not part of Solaris, so I don't know what to think here. I'm leaning on the derail lever for 2008/021 and 2007/702. However, I'm concerned that will prove non-productive. Including/porting stuff from the GNOME community is fine. When it comes to system defaults, security considerations/interfaces, administration, ... I believe it needs to be looked at as a whole with how it models and fits with Solaris. IMO, we're seeing cases of what separate groups are good at doing; created a bunch of nice shiny components that are not necessarily integrated into a meaningful user/admin experience. What I'm asking/looking for is the architectural vision/guidance for the ARCs to be able to review the components as meaningful in fitting into the big picture. I've pointed out to the various recent project teams, that an umbrella case seems to be missing and have given the example of the Sparks umbrella, PSARC/2006/247 NSS2 (Sparks,Reno,Winchester,Duckwater) Umbrella case. As an ARC member, I believe it's my job to ask for that information. Not getting it, to get far more information from the individual cases than would be necessary with an Umbrella. As an engineer, I believe it's my job to contribute to the solution, thus the meeting 30 Jan. I'm happy to be involved further where ever I may be able to add to a solution. So what transpired at the 30 Jan meeting: 1) to avoid name confusion between PSARC/2008/021 and LSARC/2007/207, PSARC/2008/021 is to be renamed HAL Power Management Support. (This seems to have taken place) 2) the case 2008/021 owner, submitter and power mgmt project are to submit a new case designed to outline/specify the user out of the box experience based on the recent PSARC and LSARC power related cases. 3) I'm to engage the DE sponsor for the site doing the GPM GUI and other desktop ports to get the desktop/administrative interface architect(s) involved to describe the overall Sun/Solaris architecture in which these components fit. (I've engaged the DE sponsor, who agreed it's something he should facilitate, and I've engaged others in the power management organization.) Perhaps everything is there and I've just missed it. The folk I've been conversing with haven't seemed to point to the overall architecture. I continue to get the feeling from the individual project teams that it's "not my problem/charter, that's another teams problem/charter." I believe without information from 2 and 3 relative to defaults on install, the user/admin model (an umbrella), there's not enough information to understand the overall architecture of where these components fit and how they will make up a usable user/admin experience. Thus, I believe, these cases are either dependent on other cases, or are incompletely specified, in either case, I believe, they are not yet ready for approval. Perhaps there are additional business areas also involved relative to various uses of Solaris for such environments as Individual Desktop/Laptop, Shared Desktop, Server, ... However, I believe, independent of such business decisions there's missing architecture (or architectural information). In an out of band conversation, Artem pointed to the "Authorizations" screenshot relative to Ubuntu's use of PolicyKit: http://arstechnica.com/news.ars/post/20080202-first-look-ubuntu-8-04-hardy-heron-alpha-4.html Gosh, remember Viper/Seabreeze/AdminSuite3/SMC in one form or another since S7 ;-) Offline discussions with the power management group lead me to question the efficacy of the various stated default settings. It's my understanding that GPM (LSARC 2007/702) delivers the default settings. And that they are only for the logged in user. My original questions were about the "system" defaults, not the "user" defaults. If my understanding is correct when the user is not logged in, lid closure will do nothing, leaving a laptop up and running. This seems like it would discharge the battery far more quickly than desired. I can't say for sure how my MacBook came from the factory, but if I logout, and close the lid, it seems to "sleep". Perhaps I've misunderstood. And I'll ask again of all the related cases, what are the system defaults for power, especially lid? Out of the box, how does the user/admin modify them? How do they persist across logins and reboots? If committee (PSARC/LSARC) members believe I'm off in the ozone, I'll go back to my day other jobs and stand aside. Gary.. From sacadmin Mon Feb 4 09:43:36 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m14Hhauf010229 for ; Mon, 4 Feb 2008 09:43:36 -0800 (PST) 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 m14HhN20026179; Mon, 4 Feb 2008 09:43:24 -0800 (PST) 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 <0JVQ00G0B6KB6200@brm-avmta-1.central.sun.com>; Mon, 04 Feb 2008 10:43:23 -0700 (MST) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVQ006026K9U280@brm-avmta-1.central.sun.com>; Mon, 04 Feb 2008 10:43:21 -0700 (MST) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m14Hgw3K002733; Mon, 04 Feb 2008 09:42:58 -0800 (PST) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m14HfTX8014655; Mon, 04 Feb 2008 09:41:29 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m14HfTRw014654; Mon, 04 Feb 2008 09:41:29 -0800 (PST) Date: Mon, 04 Feb 2008 09:41:29 -0800 (PST) From: Gary Winiger Subject: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends To: lsarc@sun.com, psarc-ext@sun.com, tpm@eng.sun.com Cc: Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, gww@eng.sun.com, james.hughes@sun.com, john.plocher@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <200802041741.m14HfTRw014654@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 5622 I wanted to update the case relative to the meeting I had with the case owner, submitter, and other's of the ON power management team after PSARC 30 Jan. As an aside, I'll not be present at 6 Feb PSARC and will be in and out on personal business the next couple weeks. Sorry for the length. I'm trying to bring too many things together in too short a time. I have to take some personal time over the next few weeks. This whole thing is looking more and more to me like a train wreck. I'm still quite concerned that there is no coordinated big picture of how things fit together from PSARC/2005/339 Tamarack: Removable Media Enhancements (which I was lead to believe introduced libpolkit interpreted by hald) and now PSARC/2007/679 CPUFreq HAL and PSARC/2008/021 HAL Power Mgmt Support which seemingly add to the Tamarack hald/libpolkit and finally LSARC/2007/702 GNOME Power Manager which seemingly calls the Tamarack hald/libpolkit to effect system power management. PSARC/2008/034 Defining Workstation Owner also may come into play. Recent communications with the Tamarack team now lead me to believe libpolkit and it's associated daemon are not part of Solaris, so I don't know what to think here. I'm leaning on the derail lever for 2008/021 and 2007/702. However, I'm concerned that will prove non-productive. Including/porting stuff from the GNOME community is fine. When it comes to system defaults, security considerations/interfaces, administration, ... I believe it needs to be looked at as a whole with how it models and fits with Solaris. IMO, we're seeing cases of what separate groups are good at doing; created a bunch of nice shiny components that are not necessarily integrated into a meaningful user/admin experience. What I'm asking/looking for is the architectural vision/guidance for the ARCs to be able to review the components as meaningful in fitting into the big picture. I've pointed out to the various recent project teams, that an umbrella case seems to be missing and have given the example of the Sparks umbrella, PSARC/2006/247 NSS2 (Sparks,Reno,Winchester,Duckwater) Umbrella case. As an ARC member, I believe it's my job to ask for that information. Not getting it, to get far more information from the individual cases than would be necessary with an Umbrella. As an engineer, I believe it's my job to contribute to the solution, thus the meeting 30 Jan. I'm happy to be involved further where ever I may be able to add to a solution. So what transpired at the 30 Jan meeting: 1) to avoid name confusion between PSARC/2008/021 and LSARC/2007/207, PSARC/2008/021 is to be renamed HAL Power Management Support. (This seems to have taken place) 2) the case 2008/021 owner, submitter and power mgmt project are to submit a new case designed to outline/specify the user out of the box experience based on the recent PSARC and LSARC power related cases. 3) I'm to engage the DE sponsor for the site doing the GPM GUI and other desktop ports to get the desktop/administrative interface architect(s) involved to describe the overall Sun/Solaris architecture in which these components fit. (I've engaged the DE sponsor, who agreed it's something he should facilitate, and I've engaged others in the power management organization.) Perhaps everything is there and I've just missed it. The folk I've been conversing with haven't seemed to point to the overall architecture. I continue to get the feeling from the individual project teams that it's "not my problem/charter, that's another teams problem/charter." I believe without information from 2 and 3 relative to defaults on install, the user/admin model (an umbrella), there's not enough information to understand the overall architecture of where these components fit and how they will make up a usable user/admin experience. Thus, I believe, these cases are either dependent on other cases, or are incompletely specified, in either case, I believe, they are not yet ready for approval. Perhaps there are additional business areas also involved relative to various uses of Solaris for such environments as Individual Desktop/Laptop, Shared Desktop, Server, ... However, I believe, independent of such business decisions there's missing architecture (or architectural information). In an out of band conversation, Artem pointed to the "Authorizations" screenshot relative to Ubuntu's use of PolicyKit: http://arstechnica.com/news.ars/post/20080202-first-look-ubuntu-8-04-hardy-heron-alpha-4.html Gosh, remember Viper/Seabreeze/AdminSuite3/SMC in one form or another since S7 ;-) Offline discussions with the power management group lead me to question the efficacy of the various stated default settings. It's my understanding that GPM (LSARC 2007/702) delivers the default settings. And that they are only for the logged in user. My original questions were about the "system" defaults, not the "user" defaults. If my understanding is correct when the user is not logged in, lid closure will do nothing, leaving a laptop up and running. This seems like it would discharge the battery far more quickly than desired. I can't say for sure how my MacBook came from the factory, but if I logout, and close the lid, it seems to "sleep". Perhaps I've misunderstood. And I'll ask again of all the related cases, what are the system defaults for power, especially lid? Out of the box, how does the user/admin modify them? How do they persist across logins and reboots? If committee (PSARC/LSARC) members believe I'm off in the ozone, I'll go back to my day other jobs and stand aside. Gary.. From sacadmin Mon Feb 4 12:29:04 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 m14KT34B022405 for ; Mon, 4 Feb 2008 12:29:03 -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 m14KSHfv015477; Mon, 4 Feb 2008 20:28:22 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 <0JVQ00703E789M00@nwk-avmta-2.sfbay.sun.com>; Mon, 04 Feb 2008 12:28:20 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVQ00K9WE77JBE0@nwk-avmta-2.sfbay.sun.com>; Mon, 04 Feb 2008 12:28:20 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m14KSJPG023654; Mon, 04 Feb 2008 12:28:19 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVQ00K01E22TP00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 04 Feb 2008 12:28:19 -0800 (PST) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVQ005CFE6PZL70@fe-sfbay-09.sun.com>; Mon, 04 Feb 2008 12:28:01 -0800 (PST) Date: Mon, 04 Feb 2008 12:27:59 -0800 From: John Plocher Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <200802041741.m14HfTRw014654@marduk.eng.sun.com> Sender: John.Plocher@sun.com To: Gary Winiger Cc: lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47A7754F.2070602@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 1182 [Internal-only comment] Gary Winiger wrote: > I'm still quite concerned that there is no coordinated big picture of how You seem to be assuming that there is a top-down picture/plan of "how Linux/Gnome's security/policy/admin model is intended to map to Solaris, and how it all will be integrated together" that could be produced and shown to y'all. Maybe there is no coordinated big picture. Maybe the entire plan is to port selected components as needed, and to address the model mismatch on a piece by piece basis thru shims and scaffolds like libpolkit that map to Solaris RBAC. In this alternative, there is no big plan to build and deploy a SMC/Viper integrated admin gui for all this stuff, and no overarching vision for how things should behave outside of the user- logged-in-on-desktop environment. MAYBE THAT IS OK because there is a business decision being made that impacts the architecture of the system. In it, we are choosing to NOT spend resources on a holistic admin model, but instead leverage whatever comes our way from GNOME. Like many diet foods, less calories really means costs more and tastes worse; this doesn't seem much different :-( -John From sacadmin Mon Feb 4 12:29:04 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 m14KT34D022405 for ; Mon, 4 Feb 2008 12:29:04 -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 m14KSHfv015477; Mon, 4 Feb 2008 20:28:22 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 <0JVQ00703E789M00@nwk-avmta-2.sfbay.sun.com>; Mon, 04 Feb 2008 12:28:20 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVQ00K9WE77JBE0@nwk-avmta-2.sfbay.sun.com>; Mon, 04 Feb 2008 12:28:20 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m14KSJPG023654; Mon, 04 Feb 2008 12:28:19 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVQ00K01E22TP00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 04 Feb 2008 12:28:19 -0800 (PST) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVQ005CFE6PZL70@fe-sfbay-09.sun.com>; Mon, 04 Feb 2008 12:28:01 -0800 (PST) Date: Mon, 04 Feb 2008 12:27:59 -0800 From: John Plocher Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <200802041741.m14HfTRw014654@marduk.eng.sun.com> Sender: John.Plocher@sun.com To: Gary Winiger Cc: lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47A7754F.2070602@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 1182 [Internal-only comment] Gary Winiger wrote: > I'm still quite concerned that there is no coordinated big picture of how You seem to be assuming that there is a top-down picture/plan of "how Linux/Gnome's security/policy/admin model is intended to map to Solaris, and how it all will be integrated together" that could be produced and shown to y'all. Maybe there is no coordinated big picture. Maybe the entire plan is to port selected components as needed, and to address the model mismatch on a piece by piece basis thru shims and scaffolds like libpolkit that map to Solaris RBAC. In this alternative, there is no big plan to build and deploy a SMC/Viper integrated admin gui for all this stuff, and no overarching vision for how things should behave outside of the user- logged-in-on-desktop environment. MAYBE THAT IS OK because there is a business decision being made that impacts the architecture of the system. In it, we are choosing to NOT spend resources on a holistic admin model, but instead leverage whatever comes our way from GNOME. Like many diet foods, less calories really means costs more and tastes worse; this doesn't seem much different :-( -John From John.Fischer@sun.com Wed Feb 6 10:42:11 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m16IgBQr019101; Wed, 6 Feb 2008 10:42:11 -0800 (PST) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m16IgB8E012887; Wed, 6 Feb 2008 10:42:11 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m16Ig87r007513; Wed, 6 Feb 2008 10:42:08 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVT00F01YGOTP00@fe-sfbay-09.sun.com> (original mail from John.Fischer@Sun.COM); Wed, 06 Feb 2008 10:42:07 -0800 (PST) Received: from [192.168.10.6] ([24.10.86.139]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVT00G0KYM4P4A0@fe-sfbay-09.sun.com>; Wed, 06 Feb 2008 10:42:05 -0800 (PST) Date: Wed, 06 Feb 2008 10:41:56 -0800 From: John Fischer Subject: Re: LSARC 2007/702 - GNOME Power Manager / PSARC 2008/021 - HAL Power Management Support Sender: John.Fischer@sun.com To: "Irene (Shi Ying) Huang" , PSARC-ext@sac.sfbay.sun.com, "phi.tran@sun.com >> Phi Tran" Cc: LSARC-ext@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Reply-to: John.Fischer@sun.com Message-id: <47A9FF74.8020407@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.4 (X11/20070622) Status: RO Content-Length: 243 Irene and Phi, At the PSARC meeting today this case and PSARC 2008/021 HAL Power Management Support were both placed in "waiting need spec". The committees would like to see what is called an umbrella case for these projects. Thanks, John From John.Fischer@sun.com Wed Feb 6 10:42:11 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m16IgBQr019101; Wed, 6 Feb 2008 10:42:11 -0800 (PST) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m16IgB8E012887; Wed, 6 Feb 2008 10:42:11 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m16Ig87r007513; Wed, 6 Feb 2008 10:42:08 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVT00F01YGOTP00@fe-sfbay-09.sun.com> (original mail from John.Fischer@Sun.COM); Wed, 06 Feb 2008 10:42:07 -0800 (PST) Received: from [192.168.10.6] ([24.10.86.139]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVT00G0KYM4P4A0@fe-sfbay-09.sun.com>; Wed, 06 Feb 2008 10:42:05 -0800 (PST) Date: Wed, 06 Feb 2008 10:41:56 -0800 From: John Fischer Subject: Re: LSARC 2007/702 - GNOME Power Manager / PSARC 2008/021 - HAL Power Management Support Sender: John.Fischer@sun.com To: "Irene (Shi Ying) Huang" , PSARC-ext@sac.sfbay.sun.com, "phi.tran@sun.com >> Phi Tran" Cc: LSARC-ext@sac.sfbay.sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Reply-to: John.Fischer@sun.com Message-id: <47A9FF74.8020407@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.4 (X11/20070622) Status: RO Content-Length: 243 Irene and Phi, At the PSARC meeting today this case and PSARC 2008/021 HAL Power Management Support were both placed in "waiting need spec". The committees would like to see what is called an umbrella case for these projects. Thanks, John From sacadmin Sun Feb 10 17:57:58 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 m1B1vvDA027717 for ; Sun, 10 Feb 2008 17:57:58 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1B1vSFx005169; Mon, 11 Feb 2008 01:57:35 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW100F01XFYPE00@nwk-avmta-1.sfbay.Sun.COM>; Sun, 10 Feb 2008 17:57:34 -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 <0JW1002A3XFX3E90@nwk-avmta-1.sfbay.Sun.COM>; Sun, 10 Feb 2008 17:57:33 -0800 (PST) Received: from domus.sfbay.sun.com (domus.SFBay.Sun.COM [10.6.64.11]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1B1vUVV045438; Sun, 10 Feb 2008 17:57:30 -0800 (PST) Received: from [10.7.251.213] (punchin-rotondo.SFBay.Sun.COM [10.7.251.213]) by domus.sfbay.sun.com (Trusted Solaris (8.11.7)/8.11.6) with ESMTP id m1B1vTr00729; Sun, 10 Feb 2008 17:57:29 -0800 (PST) Date: Sun, 10 Feb 2008 17:57:22 -0800 From: Scott Rotondo Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47A7754F.2070602@Sun.Com> To: John Plocher Cc: Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47AFAB82.3070808@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 2059 John Plocher wrote: > [Internal-only comment] > > Gary Winiger wrote: >> I'm still quite concerned that there is no coordinated big picture of how > > You seem to be assuming that there is a top-down picture/plan of "how > Linux/Gnome's security/policy/admin model is intended to map to Solaris, > and how it all will be integrated together" that could be produced and > shown to y'all. > > Maybe there is no coordinated big picture. Maybe the entire plan is to > port selected components as needed, and to address the model mismatch on > a piece by piece basis thru shims and scaffolds like libpolkit that map > to Solaris RBAC. In this alternative, there is no big plan to build and > deploy a SMC/Viper integrated admin gui for all this stuff, and no > overarching vision for how things should behave outside of the user- > logged-in-on-desktop environment. > > MAYBE THAT IS OK because there is a business decision being made > that impacts the architecture of the system. In it, we are choosing > to NOT spend resources on a holistic admin model, but instead leverage > whatever comes our way from GNOME. That's pretty much my understanding of the situation, and it probably is OK. We will continue to import huge amounts of code from Gnome and other open-source communities; most of it can and should be used as-is. However, some features in the OS (such as security administration) need to exist only once because multiple instances cannot coexist properly. [1] Code that duplicates features of that type will need some modification to merge with the existing feature. In this case, it seems clear that libpolkit should be implemented in terms of the existing RBAC authorization system. That way it can provide the API needed by various Gnome applications, while maintaining a single point of administrative control. Scott [1] As an example, what does it mean for an administrator to specify that only users A, B, and C have a given authorization if there is a parallel system that might grant equivalent powers to other users? From sacadmin Sun Feb 10 17:57:59 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 m1B1vvDC027717 for ; Sun, 10 Feb 2008 17:57:59 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1B1vSFx005169; Mon, 11 Feb 2008 01:57:35 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW100F01XFYPE00@nwk-avmta-1.sfbay.Sun.COM>; Sun, 10 Feb 2008 17:57:34 -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 <0JW1002A3XFX3E90@nwk-avmta-1.sfbay.Sun.COM>; Sun, 10 Feb 2008 17:57:33 -0800 (PST) Received: from domus.sfbay.sun.com (domus.SFBay.Sun.COM [10.6.64.11]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1B1vUVV045438; Sun, 10 Feb 2008 17:57:30 -0800 (PST) Received: from [10.7.251.213] (punchin-rotondo.SFBay.Sun.COM [10.7.251.213]) by domus.sfbay.sun.com (Trusted Solaris (8.11.7)/8.11.6) with ESMTP id m1B1vTr00729; Sun, 10 Feb 2008 17:57:29 -0800 (PST) Date: Sun, 10 Feb 2008 17:57:22 -0800 From: Scott Rotondo Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47A7754F.2070602@Sun.Com> To: John Plocher Cc: Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47AFAB82.3070808@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 2059 John Plocher wrote: > [Internal-only comment] > > Gary Winiger wrote: >> I'm still quite concerned that there is no coordinated big picture of how > > You seem to be assuming that there is a top-down picture/plan of "how > Linux/Gnome's security/policy/admin model is intended to map to Solaris, > and how it all will be integrated together" that could be produced and > shown to y'all. > > Maybe there is no coordinated big picture. Maybe the entire plan is to > port selected components as needed, and to address the model mismatch on > a piece by piece basis thru shims and scaffolds like libpolkit that map > to Solaris RBAC. In this alternative, there is no big plan to build and > deploy a SMC/Viper integrated admin gui for all this stuff, and no > overarching vision for how things should behave outside of the user- > logged-in-on-desktop environment. > > MAYBE THAT IS OK because there is a business decision being made > that impacts the architecture of the system. In it, we are choosing > to NOT spend resources on a holistic admin model, but instead leverage > whatever comes our way from GNOME. That's pretty much my understanding of the situation, and it probably is OK. We will continue to import huge amounts of code from Gnome and other open-source communities; most of it can and should be used as-is. However, some features in the OS (such as security administration) need to exist only once because multiple instances cannot coexist properly. [1] Code that duplicates features of that type will need some modification to merge with the existing feature. In this case, it seems clear that libpolkit should be implemented in terms of the existing RBAC authorization system. That way it can provide the API needed by various Gnome applications, while maintaining a single point of administrative control. Scott [1] As an example, what does it mean for an administrator to specify that only users A, B, and C have a given authorization if there is a parallel system that might grant equivalent powers to other users? From sacadmin Mon Feb 11 10:31:34 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 m1BIVX6j028087 for ; Mon, 11 Feb 2008 10:31:33 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1BIV3Zh018426; Tue, 12 Feb 2008 02:31:03 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW300J017FQAC00@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 11:31:02 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW3004557FPA2C0@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 11:31:01 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1BIV1P4005863; Mon, 11 Feb 2008 18:31:01 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300J015CQSX00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM); Mon, 11 Feb 2008 11:31:01 -0700 (MST) Received: from [192.168.1.64] ([189.137.195.67]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW3001QQ7FF5V60@mail-amer.sun.com>; Mon, 11 Feb 2008 11:30:57 -0700 (MST) Date: Mon, 11 Feb 2008 12:30:52 -0600 From: Brian Cameron Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47AFAB82.3070808@sun.com> Sender: Brian.Cameron@sun.com To: Scott Rotondo Cc: John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0945C.6090302@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080128) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 851 Scott: > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. That way it can provide > the API needed by various Gnome applications, while maintaining a single > point of administrative control. Does the usage of libpolkit add any additional configuration? For example, I imagine we map between libpolkit HAL keys and RBAC keys. If we can manage this without the need for end-users to further configure things, then this is probably not a problem. However, it would be annoying it users needed to configure both RBAC and PolicyKit to get the behavior they want. In other words, I don't think providing an API needed by various GNOME applications is necessarily a good thing if it overly complicates how end-users have to configure their systems in terms of security. Brian From sacadmin Mon Feb 11 10:31:35 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 m1BIVX6l028087 for ; Mon, 11 Feb 2008 10:31:34 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1BIV3Zh018426; Tue, 12 Feb 2008 02:31:03 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW300J017FQAC00@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 11:31:02 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW3004557FPA2C0@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 11:31:01 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1BIV1P4005863; Mon, 11 Feb 2008 18:31:01 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300J015CQSX00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM); Mon, 11 Feb 2008 11:31:01 -0700 (MST) Received: from [192.168.1.64] ([189.137.195.67]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW3001QQ7FF5V60@mail-amer.sun.com>; Mon, 11 Feb 2008 11:30:57 -0700 (MST) Date: Mon, 11 Feb 2008 12:30:52 -0600 From: Brian Cameron Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47AFAB82.3070808@sun.com> Sender: Brian.Cameron@sun.com To: Scott Rotondo Cc: John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0945C.6090302@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080128) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 851 Scott: > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. That way it can provide > the API needed by various Gnome applications, while maintaining a single > point of administrative control. Does the usage of libpolkit add any additional configuration? For example, I imagine we map between libpolkit HAL keys and RBAC keys. If we can manage this without the need for end-users to further configure things, then this is probably not a problem. However, it would be annoying it users needed to configure both RBAC and PolicyKit to get the behavior they want. In other words, I don't think providing an API needed by various GNOME applications is necessarily a good thing if it overly complicates how end-users have to configure their systems in terms of security. Brian From sacadmin Mon Feb 11 10:55:18 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BItIgb028785 for ; Mon, 11 Feb 2008 10:55:18 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BIt4RR020669; Mon, 11 Feb 2008 10:55:04 -0800 (PST) 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 <0JW3007038JQVF00@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 10:55:02 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW3000YD8JNK7A0@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 10:54:59 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BIswZl014097; Mon, 11 Feb 2008 10:54:58 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW30030188YZN00@fe-sfbay-09.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Mon, 11 Feb 2008 10:54:58 -0800 (PST) Received: from [192.168.1.100] ([75.6.231.214]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300CGE8JL0000@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 10:54:58 -0800 (PST) Date: Mon, 11 Feb 2008 10:53:47 -0800 From: Artem Kachitchkine Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47AFAB82.3070808@sun.com> Sender: Artem.Kachitchkin@sun.com To: Scott Rotondo Cc: John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B099BB.8010500@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 607 > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. At least to me, it is far from clear. PolicyKit evolved a lot since we reviewed Tamarack. libpolkit grew from a few to a few dozen functions, and in addition to libpolkit, there is now a DBus daemon, libpolkit-dbus, libpolkit-grant and PolicyKit-gnome. It gained new features that are not trivially mapped to RBAC (e.g. temporary authorizations and associating authorizations with sessions). It is a project-size effort to determine what's the right thing to do here. -Artem From sacadmin Mon Feb 11 10:55:18 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BItIgd028785 for ; Mon, 11 Feb 2008 10:55:18 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BIt4RR020669; Mon, 11 Feb 2008 10:55:04 -0800 (PST) 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 <0JW3007038JQVF00@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 10:55:02 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW3000YD8JNK7A0@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 10:54:59 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BIswZl014097; Mon, 11 Feb 2008 10:54:58 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW30030188YZN00@fe-sfbay-09.sun.com> (original mail from Artem.Kachitchkin@Sun.COM); Mon, 11 Feb 2008 10:54:58 -0800 (PST) Received: from [192.168.1.100] ([75.6.231.214]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300CGE8JL0000@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 10:54:58 -0800 (PST) Date: Mon, 11 Feb 2008 10:53:47 -0800 From: Artem Kachitchkine Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47AFAB82.3070808@sun.com> Sender: Artem.Kachitchkin@sun.com To: Scott Rotondo Cc: John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B099BB.8010500@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 607 > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. At least to me, it is far from clear. PolicyKit evolved a lot since we reviewed Tamarack. libpolkit grew from a few to a few dozen functions, and in addition to libpolkit, there is now a DBus daemon, libpolkit-dbus, libpolkit-grant and PolicyKit-gnome. It gained new features that are not trivially mapped to RBAC (e.g. temporary authorizations and associating authorizations with sessions). It is a project-size effort to determine what's the right thing to do here. -Artem From sacadmin Mon Feb 11 11:05:18 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 m1BJ5HTC029059 for ; Mon, 11 Feb 2008 11:05:17 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1BJ4bJj001804; Tue, 12 Feb 2008 03:04:47 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW300L018ZXNJ00@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 12:04:45 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30046N8ZW9XD0@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 12:04:44 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BJ4irx016389; Mon, 11 Feb 2008 11:04:44 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300C010AQKQ00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 11 Feb 2008 11:04:44 -0800 (PST) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300CNO8ZR0060@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 11:04:39 -0800 (PST) Date: Mon, 11 Feb 2008 11:04:35 -0800 From: John Plocher Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B0945C.6090302@sun.com> Sender: John.Plocher@sun.com To: Brian Cameron Cc: Scott Rotondo , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B09C43.4000308@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B0945C.6090302@sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1055 Brian Cameron wrote: > Does the usage of libpolkit add any additional configuration? The hole I see is that we are only solving part of the problem. The libpolkit/hal layer interfaces well with RBAC from a read-only perspective - GNOME PwrMgt presumes HAL "auth keys" exist and are assigned to the laptop user; we map them to RBAC auths, and the queries "just work". For "writing auths", things seem different. The existing GNOME and Linux tools don't "do" RBAC admin - they do libpolkit and HAL and whatever Linux infrastructure exists to support them. On Solaris, we don't provide a way to associate the RBAC auths with the current user of the laptop. In fact, we don't seem to do the security/admin piece very well at all. This leaves us with a system that theoretically could power save when the user closes the lid, but we aren't setting up the user to have the RBAC auths to actually have it work. One could argue that this isn't a polkit issue, but rather an install or admin one. Either way, the end result is a dead battery. -John From sacadmin Mon Feb 11 11:05:19 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 m1BJ5HTE029059 for ; Mon, 11 Feb 2008 11:05:18 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1BJ4bJj001804; Tue, 12 Feb 2008 03:04:47 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JW300L018ZXNJ00@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 12:04:45 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30046N8ZW9XD0@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 12:04:44 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BJ4irx016389; Mon, 11 Feb 2008 11:04:44 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300C010AQKQ00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 11 Feb 2008 11:04:44 -0800 (PST) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300CNO8ZR0060@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 11:04:39 -0800 (PST) Date: Mon, 11 Feb 2008 11:04:35 -0800 From: John Plocher Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B0945C.6090302@sun.com> Sender: John.Plocher@sun.com To: Brian Cameron Cc: Scott Rotondo , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B09C43.4000308@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B0945C.6090302@sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1055 Brian Cameron wrote: > Does the usage of libpolkit add any additional configuration? The hole I see is that we are only solving part of the problem. The libpolkit/hal layer interfaces well with RBAC from a read-only perspective - GNOME PwrMgt presumes HAL "auth keys" exist and are assigned to the laptop user; we map them to RBAC auths, and the queries "just work". For "writing auths", things seem different. The existing GNOME and Linux tools don't "do" RBAC admin - they do libpolkit and HAL and whatever Linux infrastructure exists to support them. On Solaris, we don't provide a way to associate the RBAC auths with the current user of the laptop. In fact, we don't seem to do the security/admin piece very well at all. This leaves us with a system that theoretically could power save when the user closes the lid, but we aren't setting up the user to have the RBAC auths to actually have it work. One could argue that this isn't a polkit issue, but rather an install or admin one. Either way, the end result is a dead battery. -John From sacadmin Mon Feb 11 11:47:06 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BJl6O8029607 for ; Mon, 11 Feb 2008 11:47:06 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BJkkfk045264; Mon, 11 Feb 2008 12:46:51 -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 <0JW30061BAY2PA00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 11 Feb 2008 11:46:50 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30018CAY1C0E0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BJknk8022374; Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300A01AKFQM00@fe-sfbay-09.sun.com> (original mail from Phi.Tran@Sun.COM); Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300BW6AXZH6C0@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 11:46:48 -0800 (PST) Date: Mon, 11 Feb 2008 11:56:25 -0800 From: Phi Tran Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B099BB.8010500@sun.com> Sender: Phi.Tran@sun.com To: Artem Kachitchkine Cc: Scott Rotondo , John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0A869.8050705@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B099BB.8010500@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 Status: RO Content-Length: 923 Artem Kachitchkine wrote: > >> In this case, it seems clear that libpolkit should be implemented in >> terms of the existing RBAC authorization system. > > > At least to me, it is far from clear. PolicyKit evolved a lot since we > reviewed Tamarack. libpolkit grew from a few to a few dozen functions, > and in addition to libpolkit, there is now a DBus daemon, > libpolkit-dbus, libpolkit-grant and PolicyKit-gnome. It gained new > features that are not trivially mapped to RBAC (e.g. temporary > authorizations and associating authorizations with sessions). > > It is a project-size effort to determine what's the right thing to do here. > > -Artem I agree there's a larger scope now for PolicyKit and it's new features may be needed for applications that make use of the new features such as session authorizations. GPM will care only if the user is root or console owner which can be handled by RBAC. Phi From sacadmin Mon Feb 11 11:47:06 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BJl6OA029607 for ; Mon, 11 Feb 2008 11:47:06 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BJkkfk045264; Mon, 11 Feb 2008 12:46:51 -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 <0JW30061BAY2PA00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 11 Feb 2008 11:46:50 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30018CAY1C0E0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BJknk8022374; Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300A01AKFQM00@fe-sfbay-09.sun.com> (original mail from Phi.Tran@Sun.COM); Mon, 11 Feb 2008 11:46:49 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW300BW6AXZH6C0@fe-sfbay-09.sun.com>; Mon, 11 Feb 2008 11:46:48 -0800 (PST) Date: Mon, 11 Feb 2008 11:56:25 -0800 From: Phi Tran Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B099BB.8010500@sun.com> Sender: Phi.Tran@sun.com To: Artem Kachitchkine Cc: Scott Rotondo , John Plocher , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0A869.8050705@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B099BB.8010500@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 Status: RO Content-Length: 923 Artem Kachitchkine wrote: > >> In this case, it seems clear that libpolkit should be implemented in >> terms of the existing RBAC authorization system. > > > At least to me, it is far from clear. PolicyKit evolved a lot since we > reviewed Tamarack. libpolkit grew from a few to a few dozen functions, > and in addition to libpolkit, there is now a DBus daemon, > libpolkit-dbus, libpolkit-grant and PolicyKit-gnome. It gained new > features that are not trivially mapped to RBAC (e.g. temporary > authorizations and associating authorizations with sessions). > > It is a project-size effort to determine what's the right thing to do here. > > -Artem I agree there's a larger scope now for PolicyKit and it's new features may be needed for applications that make use of the new features such as session authorizations. GPM will care only if the user is root or console owner which can be handled by RBAC. Phi From sacadmin Mon Feb 11 12:44:15 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BKiF0f002979 for ; Mon, 11 Feb 2008 12:44:15 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BKi08B005860; Mon, 11 Feb 2008 12:44:00 -0800 (PST) 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 <0JW300609DLC3600@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 13:44:00 -0700 (MST) Received: from jurassic.eng.sun.com ([129.146.228.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30002TDLBUZ50@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 13:43:59 -0700 (MST) Received: from grimmy.eng.sun.com (grimmy.SFBay.Sun.COM [129.146.108.114]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with SMTP id m1BKhw1p496727; Mon, 11 Feb 2008 12:43:58 -0800 (PST) Date: Mon, 11 Feb 2008 12:43:15 -0800 (PST) From: Randy Fishel Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends To: John.Plocher@sun.com, scott.rotondo@sun.com Cc: gww@eng.sun.com, lsarc@sun.com, psarc@sun.com, tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Reply-to: Randy Fishel Message-id: <200802112043.m1BKhw1p496727@jurassic.eng.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_48 SunOS 5.10 sun4u sparc Content-type: text/PLAIN Content-transfer-encoding: 7BIT X-Sun-Text-type: ascii X-PMX-Version: 5.2.0.264296 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 2698 This message seems to imply that the "spec" being requested by PSARC is *not* the spec that is being generated. PSARC (and particularly one of it's members) has requested that the project team (or a related project team) create a "Big Picture" spec. So the question for PSARC, is "what is the scope of the requested spec to satisfy the 'waiting need spec' requirements for these cases", as "what is the big picture" is way too broad (and discussions with several ARC contributors has come up with significantly different answers)? ---- Randy > > John Plocher wrote: > > [Internal-only comment] > > > > Gary Winiger wrote: > >> I'm still quite concerned that there is no coordinated big picture of how > > > > You seem to be assuming that there is a top-down picture/plan of "how > > Linux/Gnome's security/policy/admin model is intended to map to Solaris, > > and how it all will be integrated together" that could be produced and > > shown to y'all. > > > > Maybe there is no coordinated big picture. Maybe the entire plan is to > > port selected components as needed, and to address the model mismatch on > > a piece by piece basis thru shims and scaffolds like libpolkit that map > > to Solaris RBAC. In this alternative, there is no big plan to build and > > deploy a SMC/Viper integrated admin gui for all this stuff, and no > > overarching vision for how things should behave outside of the user- > > logged-in-on-desktop environment. > > > > MAYBE THAT IS OK because there is a business decision being made > > that impacts the architecture of the system. In it, we are choosing > > to NOT spend resources on a holistic admin model, but instead leverage > > whatever comes our way from GNOME. > > That's pretty much my understanding of the situation, and it probably is > OK. We will continue to import huge amounts of code from Gnome and other > open-source communities; most of it can and should be used as-is. > However, some features in the OS (such as security administration) need > to exist only once because multiple instances cannot coexist properly. > [1] Code that duplicates features of that type will need some > modification to merge with the existing feature. > > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. That way it can provide > the API needed by various Gnome applications, while maintaining a single > point of administrative control. > > Scott > > [1] As an example, what does it mean for an administrator to specify > that only users A, B, and C have a given authorization if there is a > parallel system that might grant equivalent powers to other users? From sacadmin Mon Feb 11 12:44:15 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1BKiF0h002979 for ; Mon, 11 Feb 2008 12:44:15 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1BKi08B005860; Mon, 11 Feb 2008 12:44:00 -0800 (PST) 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 <0JW300609DLC3600@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 13:44:00 -0700 (MST) Received: from jurassic.eng.sun.com ([129.146.228.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW30002TDLBUZ50@brm-avmta-1.central.sun.com>; Mon, 11 Feb 2008 13:43:59 -0700 (MST) Received: from grimmy.eng.sun.com (grimmy.SFBay.Sun.COM [129.146.108.114]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with SMTP id m1BKhw1p496727; Mon, 11 Feb 2008 12:43:58 -0800 (PST) Date: Mon, 11 Feb 2008 12:43:15 -0800 (PST) From: Randy Fishel Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends To: John.Plocher@sun.com, scott.rotondo@sun.com Cc: gww@eng.sun.com, lsarc@sun.com, psarc@sun.com, tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Phi.Tran@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Reply-to: Randy Fishel Message-id: <200802112043.m1BKhw1p496727@jurassic.eng.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_48 SunOS 5.10 sun4u sparc Content-type: text/PLAIN Content-transfer-encoding: 7BIT X-Sun-Text-type: ascii X-PMX-Version: 5.2.0.264296 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 2698 This message seems to imply that the "spec" being requested by PSARC is *not* the spec that is being generated. PSARC (and particularly one of it's members) has requested that the project team (or a related project team) create a "Big Picture" spec. So the question for PSARC, is "what is the scope of the requested spec to satisfy the 'waiting need spec' requirements for these cases", as "what is the big picture" is way too broad (and discussions with several ARC contributors has come up with significantly different answers)? ---- Randy > > John Plocher wrote: > > [Internal-only comment] > > > > Gary Winiger wrote: > >> I'm still quite concerned that there is no coordinated big picture of how > > > > You seem to be assuming that there is a top-down picture/plan of "how > > Linux/Gnome's security/policy/admin model is intended to map to Solaris, > > and how it all will be integrated together" that could be produced and > > shown to y'all. > > > > Maybe there is no coordinated big picture. Maybe the entire plan is to > > port selected components as needed, and to address the model mismatch on > > a piece by piece basis thru shims and scaffolds like libpolkit that map > > to Solaris RBAC. In this alternative, there is no big plan to build and > > deploy a SMC/Viper integrated admin gui for all this stuff, and no > > overarching vision for how things should behave outside of the user- > > logged-in-on-desktop environment. > > > > MAYBE THAT IS OK because there is a business decision being made > > that impacts the architecture of the system. In it, we are choosing > > to NOT spend resources on a holistic admin model, but instead leverage > > whatever comes our way from GNOME. > > That's pretty much my understanding of the situation, and it probably is > OK. We will continue to import huge amounts of code from Gnome and other > open-source communities; most of it can and should be used as-is. > However, some features in the OS (such as security administration) need > to exist only once because multiple instances cannot coexist properly. > [1] Code that duplicates features of that type will need some > modification to merge with the existing feature. > > In this case, it seems clear that libpolkit should be implemented in > terms of the existing RBAC authorization system. That way it can provide > the API needed by various Gnome applications, while maintaining a single > point of administrative control. > > Scott > > [1] As an example, what does it mean for an administrator to specify > that only users A, B, and C have a given authorization if there is a > parallel system that might grant equivalent powers to other users? From sacadmin Mon Feb 11 12:52:01 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 m1BKq0ux003070 for ; Mon, 11 Feb 2008 12:52:00 -0800 (PST) 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 m1BKpUUd013810; Tue, 12 Feb 2008 04:51:30 +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 <0JW300C0BDXRKA00@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 12:51:27 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW300BPGDXQNX10@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BKpQD8028667; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300C01DV1LB00@fe-sfbay-10.sun.com> (original mail from Phi.Tran@Sun.COM); Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW30026FDXP8950@fe-sfbay-10.sun.com>; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Date: Mon, 11 Feb 2008 13:01:02 -0800 From: Phi Tran Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B09C43.4000308@Sun.Com> Sender: Phi.Tran@sun.com To: John Plocher Cc: Brian Cameron , Scott Rotondo , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0B78E.3040204@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B0945C.6090302@sun.com> <47B09C43.4000308@Sun.Com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1483 John Plocher wrote: > Brian Cameron wrote: > >> Does the usage of libpolkit add any additional configuration? > > > The hole I see is that we are only solving part of the problem. > > The libpolkit/hal layer interfaces well with RBAC from a read-only > perspective - GNOME PwrMgt presumes HAL "auth keys" exist and are > assigned to the laptop user; we map them to RBAC auths, and the > queries "just work". > > For "writing auths", things seem different. The existing GNOME > and Linux tools don't "do" RBAC admin - they do libpolkit and > HAL and whatever Linux infrastructure exists to support them. Since we are replacing Gnome security policies with RBAC, we can use our admin tool to modify user privileges. > On Solaris, we don't provide a way to associate the RBAC auths with > the current user of the laptop. In fact, we don't seem to do the > security/admin piece very well at all. One can use the admin tool under "Users and Groups" or edit /etc/user_attr file by hand to change user auths from any defaults. > > This leaves us with a system that theoretically could power save > when the user closes the lid, but we aren't setting up the user to > have the RBAC auths to actually have it work. > > One could argue that this isn't a polkit issue, but rather an install > or admin one. Either way, the end result is a dead battery. For GPM, the expectations are that the root or console owner will have the RBAC auths to modify lid actions by default. Phi From sacadmin Mon Feb 11 12:52:02 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 m1BKq0v1003070 for ; Mon, 11 Feb 2008 12:52:02 -0800 (PST) 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 m1BKpUUd013810; Tue, 12 Feb 2008 04:51:30 +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 <0JW300C0BDXRKA00@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 12:51:27 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JW300BPGDXQNX10@nwk-avmta-2.sfbay.sun.com>; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1BKpQD8028667; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JW300C01DV1LB00@fe-sfbay-10.sun.com> (original mail from Phi.Tran@Sun.COM); Mon, 11 Feb 2008 12:51:26 -0800 (PST) Received: from [10.1.49.220] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JW30026FDXP8950@fe-sfbay-10.sun.com>; Mon, 11 Feb 2008 12:51:26 -0800 (PST) Date: Mon, 11 Feb 2008 13:01:02 -0800 From: Phi Tran Subject: Re: About 2008/021 HAL Power Management LSARC/2007/702 GPM and friends In-reply-to: <47B09C43.4000308@Sun.Com> Sender: Phi.Tran@sun.com To: John Plocher Cc: Brian Cameron , Scott Rotondo , Gary Winiger , lsarc@sun.com, "psarc@sun.com" , tpm@eng.sun.com, Artem.Kachitchkin@sun.com, David.Chieu@sun.com, Glenn.Faden@sun.com, Irene.Huang@sun.com, Jim.Li@sun.com, Randy.Fishel@sun.com, dchieu@sac.sfbay.sun.com, djb@eng.sun.com, James.Hughes@sun.com, solaris-battery-team@sun.com, tamarack-core@sun.com, x86power-iteam@sun.com Message-id: <47B0B78E.3040204@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200802041741.m14HfTRw014654@marduk.eng.sun.com> <47A7754F.2070602@Sun.Com> <47AFAB82.3070808@sun.com> <47B0945C.6090302@sun.com> <47B09C43.4000308@Sun.Com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20060417 x_sac_archived: PSARC/2008/021 Status: RO Content-Length: 1483 John Plocher wrote: > Brian Cameron wrote: > >> Does the usage of libpolkit add any additional configuration? > > > The hole I see is that we are only solving part of the problem. > > The libpolkit/hal layer interfaces well with RBAC from a read-only > perspective - GNOME PwrMgt presumes HAL "auth keys" exist and are > assigned to the laptop user; we map them to RBAC auths, and the > queries "just work". > > For "writing auths", things seem different. The existing GNOME > and Linux tools don't "do" RBAC admin - they do libpolkit and > HAL and whatever Linux infrastructure exists to support them. Since we are replacing Gnome security policies with RBAC, we can use our admin tool to modify user privileges. > On Solaris, we don't provide a way to associate the RBAC auths with > the current user of the laptop. In fact, we don't seem to do the > security/admin piece very well at all. One can use the admin tool under "Users and Groups" or edit /etc/user_attr file by hand to change user auths from any defaults. > > This leaves us with a system that theoretically could power save > when the user closes the lid, but we aren't setting up the user to > have the RBAC auths to actually have it work. > > One could argue that this isn't a polkit issue, but rather an install > or admin one. Either way, the end result is a dead battery. For GPM, the expectations are that the root or console owner will have the RBAC auths to modify lid actions by default. Phi From sacadmin Tue Mar 4 21:32:48 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m255WmA3012118; Tue, 4 Mar 2008 21:32:48 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m255Wlja037614; Tue, 4 Mar 2008 21:32:47 -0800 (PST) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m255Wlt5011062; Wed, 5 Mar 2008 05:32:47 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 <0JX800B01SCUVG00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Wed, 05 Mar 2008 13:32:41 +0800 (SGT) Received: from [129.158.219.209] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JX800B52SQ7MFJC@mail-apac.sun.com>; Wed, 05 Mar 2008 13:32:32 +0800 (SGT) Date: Wed, 05 Mar 2008 13:33:04 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <200801300215.m0U2FqYQ892766@jurassic.eng.sun.com> Sender: Irene.Huang@sun.com To: Randy Fishel Cc: gww@eng.sun.com, Simon.Zheng@sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <47CE3090.7000702@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200801300215.m0U2FqYQ892766@jurassic.eng.sun.com> User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) Status: RO Content-Length: 368 Hi, all Simon has come out with a new spec file for GNOME power manager available at http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt Here's the diff file between V2 and V3, for you convenience: http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.diff I am setting the new time out to be March 12th, 2008. Thanks in advance. --Irene From sacadmin Tue Mar 11 19:50:23 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2C2oNW8024376; Tue, 11 Mar 2008 19:50:23 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2C2oNrp039932; Tue, 11 Mar 2008 19:50:23 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m2C3oLN0020534; Tue, 11 Mar 2008 19:50:21 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m2C3oLPg020533; Tue, 11 Mar 2008 19:50:21 -0800 (PST) Date: Tue, 11 Mar 2008 19:50:21 -0800 (PST) From: Gary Winiger Message-Id: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> To: Irene.Huang@sun.com, randyf@jurassic.eng.sun.com Cc: LSARC@sac.sfbay.sun.com, Simon.Zheng@sun.com, gww@eng.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] Status: RO Content-Length: 1278 > Simon has come out with a new spec file for GNOME power manager > available at > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt > 4.10 Screen locking > By default, when system is resumed from suspend, hibernate or blanking screen, GPM > will automatically lock screen to requrie user passward. To be convient, we also > provide the user with a configurable GUI option, which is used to disable or enable > screen locking. I presumed the project is not doing its own screen locking since it imported xscreensaver. Is there some standard way to call whatever an authorized user/admin configures as the screen lock program for JDS's distribution of GNOME? I thought there was. If not, how do you ensure that the user/admin actually wanted xscreensaver? > xscreensaver-command CLI Committed LSARC/2001/121 Used to lock screen > XScreensaver Any option to disable a security feature that is required in many environments should have a way of either restricting the disabling to authorized user/admin, or to have the admin disable the feature all together. What does this project provide to support this customer need/requirement? Gary.. From sacadmin Wed Mar 12 21:03:54 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2D43rVt014834; Wed, 12 Mar 2008 21:03:53 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2D43qNH037008; Wed, 12 Mar 2008 21:03:53 -0700 (PDT) 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 m2D445J8002271; Thu, 13 Mar 2008 04:04:05 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 <0JXN00I01HEKF700@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 13 Mar 2008 12:03:45 +0800 (SGT) Received: from [129.158.217.134] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JXN00BE8HY3MHJJ@mail-apac.sun.com>; Thu, 13 Mar 2008 12:03:44 +0800 (SGT) Date: Thu, 13 Mar 2008 12:03:35 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: Irene.Huang@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1205381015.105311.48.camel@snowboard> MIME-version: 1.0 X-Mailer: Evolution 2.12.1 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> Status: RO Content-Length: 2704 On Tue, 2008-03-11 at 19:50 -0800, Gary Winiger wrote: > > Simon has come out with a new spec file for GNOME power manager > > available at > > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt > > > 4.10 Screen locking > > By default, when system is resumed from suspend, hibernate or blanking screen, GPM > > will automatically lock screen to requrie user passward. To be convient, we also > > provide the user with a configurable GUI option, which is used to disable or enable > > screen locking. > > I presumed the project is not doing its own screen locking since > it imported xscreensaver. Is there some standard way to call > whatever an authorized user/admin configures as the screen lock > program for JDS's distribution of GNOME? I thought there was. > If not, how do you ensure that the user/admin actually wanted > xscreensaver? Discussed with some guys, so far on Solaris there's not a unified interface to configure what screen lock program to use. Early "LSARC/2007/154/ xdisplaylock: the generic lock application for X display" ever tried to figure out this. But it's derailed. At present, most applications in GNOME have to decide how to do this properly by themselves. GPM also does in this way, seeking the hard-coding program name in following order and run. - gnome-screen-saver - xscreensaver If later Solaris has a better interface to configure screen lock program, we would like to change and keep consistent with other components of desktop. > > > xscreensaver-command CLI Committed LSARC/2001/121 Used to lock screen > > XScreensaver > Any option to disable a security feature that is required in > many environments should have a way of either restricting > the disabling to authorized user/admin, or to have the admin > disable the feature all together. What does this project > provide to support this customer need/requirement? GPM stores configuration whether or not lock screen in some gconf keys, e.g, /app/gnome-power-manager/lockscreen_on_resume This key can be restricted through gconf-related tool(LSARC/2002/146/). It's possible to have the key forced to a specific value by admin. In details, gconf mandatory setting can be used to enforced. There's a directory in /etc/gconf/gconf.xml.mandatory - where you can store a schema and have a specific value enforced. The easiest way to configure this, is to set the key using GUI gconf-editor and using a "Mandatory Window" - this option/key is grayed out when run as a normal user, but you can open this window if you're running as root. -Simon > > Gary.. From sacadmin Wed Mar 12 21:42:38 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2D4gcPr015098; Wed, 12 Mar 2008 21:42:38 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2D4gbN7053878; Wed, 12 Mar 2008 21:42:37 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m2D4gbxf018373; Thu, 13 Mar 2008 04:42:37 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXN00M01JJ9Y900@mail-amer.sun.com> (original mail from Alan.Coopersmith@Sun.COM); Wed, 12 Mar 2008 22:42:37 -0600 (MDT) Received: from [192.168.0.118] ([66.120.186.27]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXN00CFPJQVUK50@mail-amer.sun.com>; Wed, 12 Mar 2008 22:42:35 -0600 (MDT) Date: Wed, 12 Mar 2008 21:42:13 -0700 From: Alan Coopersmith Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <1205381015.105311.48.camel@snowboard> Sender: Alan.Coopersmith@sun.com To: "simon.zheng@sun.com" Cc: Gary Winiger , Irene.Huang@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren Kenny Message-id: <47D8B0A5.5070609@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> <1205381015.105311.48.camel@snowboard> User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) Status: RO Content-Length: 1225 simon.zheng@sun.com wrote: > On Tue, 2008-03-11 at 19:50 -0800, Gary Winiger wrote: >>> Simon has come out with a new spec file for GNOME power manager >>> available at >>> http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt >>> 4.10 Screen locking >>> By default, when system is resumed from suspend, hibernate or blanking screen, GPM >>> will automatically lock screen to requrie user passward. To be convient, we also >>> provide the user with a configurable GUI option, which is used to disable or enable >>> screen locking. >> I presumed the project is not doing its own screen locking since >> it imported xscreensaver. Is there some standard way to call >> whatever an authorized user/admin configures as the screen lock >> program for JDS's distribution of GNOME? I thought there was. >> If not, how do you ensure that the user/admin actually wanted >> xscreensaver? > > Discussed with some guys, so far on Solaris there's not a unified > interface to configure what screen lock program to use. Isn't that what xdg-screensaver (LSARC 2008/104) was supposed to do? -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From sacadmin Thu Mar 13 07:25:34 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2DEPY9O000439; Thu, 13 Mar 2008 07:25:34 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2DEPVkx005857; Thu, 13 Mar 2008 07:25:32 -0700 (PDT) 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 m2DEPXpn004226; Thu, 13 Mar 2008 14:25:33 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 <0JXO00501AKVBX00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Thu, 13 Mar 2008 22:25:25 +0800 (SGT) Received: from [192.168.0.133] ([125.33.142.11]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JXO00JQGAQ2E7MB@mail-apac.sun.com>; Thu, 13 Mar 2008 22:25:25 +0800 (SGT) Date: Thu, 13 Mar 2008 22:25:12 +0800 From: "simon.zheng" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <47D8B0A5.5070609@sun.com> Sender: Simon.Zheng@sun.com To: Alan Coopersmith Cc: Gary Winiger , Irene.Huang@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren Kenny Message-id: <47D93948.4030705@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> <1205381015.105311.48.camel@snowboard> <47D8B0A5.5070609@sun.com> User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) Status: RO Content-Length: 1539 Alan Coopersmith wrote: > simon.zheng@sun.com wrote: >> On Tue, 2008-03-11 at 19:50 -0800, Gary Winiger wrote: >>>> Simon has come out with a new spec file for GNOME power manager >>>> available at >>>> http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt >>>> 4.10 Screen locking >>>> By default, when system is resumed from suspend, hibernate or >>>> blanking screen, GPM will automatically lock screen to requrie user >>>> passward. To be convient, we also provide the user with a >>>> configurable GUI option, which is used to disable or enable screen >>>> locking. >>> I presumed the project is not doing its own screen locking since >>> it imported xscreensaver. Is there some standard way to call >>> whatever an authorized user/admin configures as the screen lock >>> program for JDS's distribution of GNOME? I thought there was. >>> If not, how do you ensure that the user/admin actually wanted >>> xscreensaver? >> >> Discussed with some guys, so far on Solaris there's not a unified >> interface to configure what screen lock program to use. > > Isn't that what xdg-screensaver (LSARC 2008/104) was supposed to do? Alan, Never notice that before. Script xdg-screensaver was just integrated into as Indiana project. xdg-screensaver is also hard-coding to search screen saver program. And it doesn't allow user to configure manually. Using it would be better to call xscreensaver directly. GPM will depend on that script xdg-screensaver instead of xscreensaver. Thanks, -Simon From sacadmin Thu Mar 13 23:25:51 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01 [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2E6PpA9029410; Thu, 13 Mar 2008 23:25:51 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2E6PoOO057060; Thu, 13 Mar 2008 23:25:50 -0700 (PDT) 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 m2E6Ppv6011477; Fri, 14 Mar 2008 06:25:51 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 <0JXP00301J4PQ000@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Fri, 14 Mar 2008 14:25:44 +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 <0JXP00J72J6VC7VE@mail-apac.sun.com>; Fri, 14 Mar 2008 14:25:44 +0800 (SGT) Date: Fri, 14 Mar 2008 14:26:07 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <47D93948.4030705@sun.com> Sender: Irene.Huang@sun.com To: "simon.zheng" Cc: Alan Coopersmith , Gary Winiger , randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren Kenny Message-id: <1205475967.1568.18.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.1 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200803120350.m2C3oLPg020533@marduk.eng.sun.com> <1205381015.105311.48.camel@snowboard> <47D8B0A5.5070609@sun.com> <47D93948.4030705@sun.com> Status: RO Content-Length: 1806 Hi, All If there's no more issues with this case, I'll close this case this weekend (Before Monday PST), as approved, thanks. --Irene On Thu, 2008-03-13 at 22:25 +0800, simon.zheng wrote: > Alan Coopersmith wrote: > > simon.zheng@sun.com wrote: > >> On Tue, 2008-03-11 at 19:50 -0800, Gary Winiger wrote: > >>>> Simon has come out with a new spec file for GNOME power manager > >>>> available at > >>>> http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt > >>>> 4.10 Screen locking > >>>> By default, when system is resumed from suspend, hibernate or > >>>> blanking screen, GPM will automatically lock screen to requrie user > >>>> passward. To be convient, we also provide the user with a > >>>> configurable GUI option, which is used to disable or enable screen > >>>> locking. > >>> I presumed the project is not doing its own screen locking since > >>> it imported xscreensaver. Is there some standard way to call > >>> whatever an authorized user/admin configures as the screen lock > >>> program for JDS's distribution of GNOME? I thought there was. > >>> If not, how do you ensure that the user/admin actually wanted > >>> xscreensaver? > >> > >> Discussed with some guys, so far on Solaris there's not a unified > >> interface to configure what screen lock program to use. > > > > Isn't that what xdg-screensaver (LSARC 2008/104) was supposed to do? > Alan, > > Never notice that before. Script xdg-screensaver was just integrated > into as > Indiana project. xdg-screensaver is also hard-coding to search screen saver > program. And it doesn't allow user to configure manually. Using it would be > better to call xscreensaver directly. > > GPM will depend on that script xdg-screensaver instead of xscreensaver. > > Thanks, > -Simon > > > From sacadmin Fri Mar 14 07:53:07 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2EEr7Oc012179; Fri, 14 Mar 2008 07:53:07 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2EEr6qD032030; Fri, 14 Mar 2008 07:53:06 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m2EFrB6E024784; Fri, 14 Mar 2008 07:53:11 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m2EFrBCr024783; Fri, 14 Mar 2008 07:53:11 -0800 (PST) Date: Fri, 14 Mar 2008 07:53:11 -0800 (PST) From: Gary Winiger Message-Id: <200803141553.m2EFrBCr024783@marduk.eng.sun.com> To: Simon.Zheng@sun.com, Irene.Huang@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] Cc: Alan.Coopersmith@sun.com, gww@eng.sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren.Kenny@sun.com X-Sun-Charset: US-ASCII Status: RO Content-Length: 257 > If there's no more issues with this case, I'll close this case this > weekend (Before Monday PST), as approved, thanks. Why not follow standard procedure? This case is still waiting need spec. Post the new spec and set the timer for a week. Gary.. From sacadmin Fri Mar 14 09:35:54 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2EGZsNs015358; Fri, 14 Mar 2008 09:35:54 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2EGZrhY044988; Fri, 14 Mar 2008 09:35:53 -0700 (PDT) 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 m2EGZt8u010790; Fri, 14 Mar 2008 16:35:55 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 <0JXQ00D01B735L00@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) ; Sat, 15 Mar 2008 00:35:47 +0800 (SGT) Received: from [192.168.1.100] ([123.121.213.132]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JXQ00JTOBFFE77G@mail-apac.sun.com>; Sat, 15 Mar 2008 00:35:47 +0800 (SGT) Date: Sat, 15 Mar 2008 00:35:36 +0800 From: Jeff Cai Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <200803141553.m2EFrBCr024783@marduk.eng.sun.com> Sender: Jeff.Cai@sun.com To: Gary Winiger Cc: Simon.Zheng@sun.com, Irene.Huang@sun.com, Alan.Coopersmith@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren.Kenny@sun.com Message-id: <47DAA958.6080106@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT References: <200803141553.m2EFrBCr024783@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) Status: RO Content-Length: 783 Gary Winiger 写道: >> If there's no more issues with this case, I'll close this case this >> weekend (Before Monday PST), as approved, thanks. >> > > Why not follow standard procedure? This case is still waiting > need spec. Post the new spec and set the timer for a week. > Gary, I think you may have missed the mail Irene sent on March 5 th. Attach the mail she has sent to lsarc. Hi, all Simon has come out with a new spec file for GNOME power manager available at http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt Here's the diff file between V2 and V3, for you convenience: http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.diff I am setting the new time out to be March 12th, 2008. Thanks in advance. --Irene > Gary.. > From sacadmin Fri Mar 14 09:59:07 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2EGx7RO016554; Fri, 14 Mar 2008 09:59:07 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2EGx6v2064262; Fri, 14 Mar 2008 09:59:06 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m2EHx8PY025089; Fri, 14 Mar 2008 09:59:08 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m2EHx8oR025088; Fri, 14 Mar 2008 09:59:08 -0800 (PST) Date: Fri, 14 Mar 2008 09:59:08 -0800 (PST) From: Gary Winiger Message-Id: <200803141759.m2EHx8oR025088@marduk.eng.sun.com> To: gww@eng.sun.com, Jeff.Cai@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] Cc: Simon.Zheng@sun.com, Irene.Huang@sun.com, Alan.Coopersmith@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren.Kenny@sun.com X-Sun-Charset: US-ASCII Status: RO Content-Length: 1287 > >> If there's no more issues with this case, I'll close this case this > >> weekend (Before Monday PST), as approved, thanks. > >> > > > > Why not follow standard procedure? This case is still waiting > > need spec. Post the new spec and set the timer for a week. > > > Gary, I think you may have missed the mail Irene sent on March 5 th. > Attach the mail she has sent to lsarc. > > Hi, all > > Simon has come out with a new spec file for GNOME power manager > available at > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt > Here's the diff file between V2 and V3, for you convenience: > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.diff > > I am setting the new time out to be March 12th, 2008. RTM the IAM file as of now: Name: GNOME Power Manager Submitter: Simon Zheng Owner: Irene Huang Interest: solaris-battery-team@sun.com, gww@sun.com Status: waiting need spec 01/06/2008 Comment: waiting fast-track 01/08/2008 Exposure: open Comment: Sending mail does not put this case on the agenda, nor does it set the timer. Updating the IAM file to be correct does this. Sending mail saying the case is restarted is a prerequisite for updating the IAM file. Follow along the astat listings. Gary.. From sacadmin Sun Mar 16 19:25:41 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2H2PfJL026389; Sun, 16 Mar 2008 19:25:41 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2H2Pdph026552; Sun, 16 Mar 2008 19:25:40 -0700 (PDT) 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 m2H2PsKp010893; Mon, 17 Mar 2008 02:25:54 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 <0JXU00A01S19KT00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Mon, 17 Mar 2008 10:25:34 +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 <0JXU00J47S2IC7AL@mail-apac.sun.com>; Mon, 17 Mar 2008 10:25:32 +0800 (SGT) Date: Mon, 17 Mar 2008 10:25:55 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/18/2008] In-reply-to: <200803141759.m2EHx8oR025088@marduk.eng.sun.com> Sender: Irene.Huang@sun.com To: Gary Winiger Cc: Jeff.Cai@sun.com, Simon.Zheng@sun.com, Alan.Coopersmith@sun.com, randyf@jurassic.eng.sun.com, LSARC@sac.sfbay.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com, Darren.Kenny@sun.com Message-id: <1205720755.909.0.camel@goalie> MIME-version: 1.0 X-Mailer: Evolution 2.12.1 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200803141759.m2EHx8oR025088@marduk.eng.sun.com> Status: RO Content-Length: 1470 resetting the time out to be March 18th. --Irene On Fri, 2008-03-14 at 09:59 -0800, Gary Winiger wrote: > > >> If there's no more issues with this case, I'll close this case this > > >> weekend (Before Monday PST), as approved, thanks. > > >> > > > > > > Why not follow standard procedure? This case is still waiting > > > need spec. Post the new spec and set the timer for a week. > > > > > Gary, I think you may have missed the mail Irene sent on March 5 th. > > Attach the mail she has sent to lsarc. > > > > Hi, all > > > > Simon has come out with a new spec file for GNOME power manager > > available at > > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.txt > > Here's the diff file between V2 and V3, for you convenience: > > http://sac.eng/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v3.diff > > > > I am setting the new time out to be March 12th, 2008. > > RTM the IAM file as of now: > Name: GNOME Power Manager > Submitter: Simon Zheng > Owner: Irene Huang > Interest: solaris-battery-team@sun.com, gww@sun.com > Status: waiting need spec 01/06/2008 > Comment: waiting fast-track 01/08/2008 > Exposure: open > Comment: > > Sending mail does not put this case on the agenda, nor > does it set the timer. Updating the IAM file to be correct > does this. Sending mail saying the case is restarted is > a prerequisite for updating the IAM file. > > Follow along the astat listings. > > Gary.. From sacadmin Mon Mar 17 15:46:03 2008 Received: from dm-eng-02.sfbay.sun.com (dm-eng-02 [129.146.11.32]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HMk3Rr002522; Mon, 17 Mar 2008 15:46:03 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2HMk3Ug054301; Mon, 17 Mar 2008 15:46:03 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m2HNkD4q028423; Mon, 17 Mar 2008 15:46:13 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m2HNkDk0028422; Mon, 17 Mar 2008 15:46:13 -0800 (PST) Date: Mon, 17 Mar 2008 15:46:13 -0800 (PST) From: Gary Winiger Message-Id: <200803172346.m2HNkDk0028422@marduk.eng.sun.com> To: Simon.Zheng@sun.com, gww@eng.sun.com Cc: Irene.Huang@sun.com, LSARC@sac.sfbay.sun.com, randyf@jurassic.eng.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] Status: RO Content-Length: 1499 Somehow this didn't seem to go when I tried to set it 15 Min ago. Sorry if it shows up twice. > > Any option to disable a security feature that is required in > > many environments should have a way of either restricting > > the disabling to authorized user/admin, or to have the admin > > disable the feature all together. What does this project > > provide to support this customer need/requirement? > > GPM stores configuration whether or not lock screen in some gconf keys, e.g, > > /app/gnome-power-manager/lockscreen_on_resume > > This key can be restricted through gconf-related tool(LSARC/2002/146/). > It's possible to have the key forced to a specific value by admin. > > In details, gconf mandatory setting can be used to enforced. There's a > directory in /etc/gconf/gconf.xml.mandatory - where you can store a schema > and have a specific value enforced. The easiest way to configure this, is to > set the key using GUI gconf-editor and using a "Mandatory Window" - this > option/key is grayed out when run as a normal user, but you can open this > window if you're running as root. That's not the question. The question is what this project does not what's possible. How will this project deliver? Will it deliver so only an authorized administrator can allow screen locking to be bypassed? And how is that administrator for this project authorized? Why is root involved anywhere? From S10 authority is not uid == 0 based. Gary.. From sacadmin Tue Mar 18 03:57:48 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2IAvlAH025250; Tue, 18 Mar 2008 03:57:47 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2IAvk1A002998; Tue, 18 Mar 2008 03:57:47 -0700 (PDT) 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 m2IAw1ks027762; Tue, 18 Mar 2008 10:58:01 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 <0JXX00B01A9WAX00@mail-apac.sun.com> (original mail from Simon.Zheng@Sun.COM); Tue, 18 Mar 2008 18:57:39 +0800 (SGT) Received: from [129.158.217.134] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JXX00JKNAG2C7EQ@mail-apac.sun.com>; Tue, 18 Mar 2008 18:57:39 +0800 (SGT) Date: Tue, 18 Mar 2008 18:57:28 +0800 From: "simon.zheng@sun.com" Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <200803172346.m2HNkDk0028422@marduk.eng.sun.com> Sender: Simon.Zheng@sun.com To: Gary Winiger Cc: Irene.Huang@sun.com, LSARC@sac.sfbay.sun.com, randyf@jurassic.eng.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1205837848.101502.41.camel@snowboard> MIME-version: 1.0 X-Mailer: Evolution 2.21.92 Content-type: text/plain Content-transfer-encoding: 8BIT References: <200803172346.m2HNkDk0028422@marduk.eng.sun.com> Status: RO Content-Length: 2389 On Mon, 2008-03-17 at 15:46 -0800, Gary Winiger wrote: > Somehow this didn't seem to go when I tried to set it 15 Min ago. > Sorry if it shows up twice. > > > > Any option to disable a security feature that is required in > > > many environments should have a way of either restricting > > > the disabling to authorized user/admin, or to have the admin > > > disable the feature all together. What does this project > > > provide to support this customer need/requirement? > > > > GPM stores configuration whether or not lock screen in some gconf keys, e.g, > > > > /app/gnome-power-manager/lockscreen_on_resume > > > > This key can be restricted through gconf-related tool(LSARC/2002/146/). > > It's possible to have the key forced to a specific value by admin. > > > > In details, gconf mandatory setting can be used to enforced. There's a > > directory in /etc/gconf/gconf.xml.mandatory - where you can store a schema > > and have a specific value enforced. The easiest way to configure this, is to > > set the key using GUI gconf-editor and using a "Mandatory Window" - this > > option/key is grayed out when run as a normal user, but you can open this > > window if you're running as root. > > That's not the question. The question is what this project does > not what's possible. How will this project deliver? Will it > deliver so only an authorized administrator can allow screen locking > to be bypassed? And how is that administrator for this project > authorized? As other GNOME-based desktop applications, this project will deliver setting/preference into gconf framework (LSARC/2002/146). The gconf keys imported by this project are managed via gconf-related tools. As I known, apart from gconf tools in LSARC/2002/146, user can use APOC (A point of control, see LSARC/2003/217, LSARC/2004/423, LSARC/2005/221) to manage gconf key. I think gconf key management belongs to gconf framework and APOC. It's out of this case scope. > > Why is root involved anywhere? From S10 authority is not uid == 0 > based. Make sense. I think it's Solaris-specific gconf issue. Already filed a bugster RFE for supporting more flexiable control for gconf management. Please see CR #6676590. http://bt2ws.central.sun.com/CrPrint?id=6676590 Hopefully gconf maintainer could figure out soon. Thanks, -Simon > > Gary.. From sacadmin Wed Mar 19 03:02:14 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2JA2EqG011810; Wed, 19 Mar 2008 03:02:14 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2JA2CDG033275; Wed, 19 Mar 2008 03:02:13 -0700 (PDT) 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 m2JA2T15001883; Wed, 19 Mar 2008 10:02:29 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 <0JXZ00G0120LIA00@mail-apac.sun.com> (original mail from Irene.Huang@Sun.COM); Wed, 19 Mar 2008 18:01:57 +0800 (SGT) Received: from [129.158.146.235] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JXZ00B6E2IOMF7X@mail-apac.sun.com>; Wed, 19 Mar 2008 18:01:38 +0800 (SGT) Date: Wed, 19 Mar 2008 18:02:23 +0800 From: Irene Huang Subject: Re: GNOME Power Manager [LSARC/2007/702 FastTrack NEW timeout 03/12/2008] In-reply-to: <1205837848.101502.41.camel@snowboard> Sender: Irene.Huang@sun.com To: "simon.zheng@sun.com" Cc: Gary Winiger , LSARC@sac.sfbay.sun.com, randyf@jurassic.eng.sun.com, sh162551@sac.sfbay.sun.com, solaris-battery-team@sun.com Message-id: <1205920943.1313.0.camel@crescent> MIME-version: 1.0 X-Mailer: Evolution 2.12.1 Content-type: text/plain Content-transfer-encoding: 8BIT References: <200803172346.m2HNkDk0028422@marduk.eng.sun.com> <1205837848.101502.41.camel@snowboard> Status: RO Content-Length: 2840 Case approved during the LSARC meeting on March 18th, 2008. The latest spec is available at http://sac.eng.sun.com/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v4.txt diff file at http://sac.eng.sun.com/Archives/CaseLog/arc/LSARC/2007/702/GPM-spec-v4.diff Thanks --Irene On Tue, 2008-03-18 at 18:57 +0800, simon.zheng@sun.com wrote: > On Mon, 2008-03-17 at 15:46 -0800, Gary Winiger wrote: > > Somehow this didn't seem to go when I tried to set it 15 Min ago. > > Sorry if it shows up twice. > > > > > > Any option to disable a security feature that is required in > > > > many environments should have a way of either restricting > > > > the disabling to authorized user/admin, or to have the admin > > > > disable the feature all together. What does this project > > > > provide to support this customer need/requirement? > > > > > > GPM stores configuration whether or not lock screen in some gconf keys, e.g, > > > > > > /app/gnome-power-manager/lockscreen_on_resume > > > > > > This key can be restricted through gconf-related tool(LSARC/2002/146/). > > > It's possible to have the key forced to a specific value by admin. > > > > > > In details, gconf mandatory setting can be used to enforced. There's a > > > directory in /etc/gconf/gconf.xml.mandatory - where you can store a schema > > > and have a specific value enforced. The easiest way to configure this, is to > > > set the key using GUI gconf-editor and using a "Mandatory Window" - this > > > option/key is grayed out when run as a normal user, but you can open this > > > window if you're running as root. > > > > That's not the question. The question is what this project does > > not what's possible. How will this project deliver? Will it > > deliver so only an authorized administrator can allow screen locking > > to be bypassed? And how is that administrator for this project > > authorized? > > As other GNOME-based desktop applications, this project will deliver > setting/preference into gconf framework (LSARC/2002/146). The gconf keys > imported by this project are managed via gconf-related tools. > > As I known, apart from gconf tools in LSARC/2002/146, user can use APOC > (A point of control, see LSARC/2003/217, LSARC/2004/423, LSARC/2005/221) > to manage gconf key. I think gconf key management belongs to gconf > framework and APOC. It's out of this case scope. > > > > > Why is root involved anywhere? From S10 authority is not uid == 0 > > based. > > Make sense. I think it's Solaris-specific gconf issue. Already filed a > bugster RFE for supporting more flexiable control for gconf management. > Please see CR #6676590. > http://bt2ws.central.sun.com/CrPrint?id=6676590 > > Hopefully gconf maintainer could figure out soon. > > Thanks, > -Simon > > > > > Gary.. >