From johnf@sr1-umpk-12.sfbay.sun.com Wed Feb 11 10:53:20 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1BIrKJ2010496 for ; Wed, 11 Feb 2009 10:53:20 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1BIrJeY022789 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 11 Feb 2009 10:53:20 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEX00H090GWCB00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 11 Feb 2009 10:53:20 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEX00KPX0GV1OE0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 11 Feb 2009 10:53:19 -0800 (PST) Received: from sr1-umpk-12.sfbay.sun.com (sr1-umpk-12.SFBay.Sun.COM [129.145.154.112]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1BIrIi6056164; Wed, 11 Feb 2009 10:53:18 -0800 (PST) Received: from sr1-umpk-12.sfbay.sun.com (localhost [127.0.0.1]) by sr1-umpk-12.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1BIrIWF061831; Wed, 11 Feb 2009 10:53:18 -0800 (PST) Received: (from johnf@localhost) by sr1-umpk-12.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1BIrIgG061820; Wed, 11 Feb 2009 10:53:18 -0800 (PST) Date: Wed, 11 Feb 2009 10:53:18 -0800 (PST) From: John Fischer Subject: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] To: LSARC-ext@sun.com Cc: Ke.Wang@sun.com Message-id: <200902111853.n1BIrIgG061820@sr1-umpk-12.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 8249 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: libproxy 1.2. Name of Document Author/Supplier: Author: Ke Wang 1.3 Date of This Document: 11 February, 2009 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: libproxy 1.2. Name of Document Author/Supplier: Author: Ke Wang Sponser: Irene Huang 1.3. Date of This Document: 02/04/2009 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert O'Dea 1.4.4. The name of your business unit: Software - OPG 1.5. Email Aliases: 1.5.1. Responsible Manager: harry.lu@sun.com 1.5.2. Responsible Engineer: ke.wang@sun.com 1.5.3. Marketing Manager: glynn.foster@sun.com 1.5.4. Interest List: jeff.cai@sun.com 2. Project Summary 2.1. Project Description: libproxy is a library that provides automatic proxy configuration management. 3. Technical Description: 3.1. Details: Proxy configuration is problematic for a number of reasons: 1. There are a variety of places to get configuration information 2. There are a variety of proxy types 3. Proxy auto-configuration (PAC) requires Javascript (which most applications don't have) 4. Automatically determining PAC location requires an implementation of the WPAD protocol Libproxy provides interfaces to get proxy that should be used to access a network resource. It use various plugins to get proxy configuration from different places e.g. environment variables, GConf, PAC. Libproxy offers the following features: * extremely small core footprint * no external dependencies within libproxy core (libproxy plugins may have dependencies) * only 3 functions in the stable external API * dynamic adjustment to changing network topology * a standard way of dealing with proxy settings across all scenarios Libproxy includes a core library and several plugins. What the core library does is only checking each plugin for an available proxy. Plugins list follows: PLUGIN | DEPS | COMMENT envar | None | Used to get proxy configured by environment variable "http_proxy" file | None | Used to get proxy configured in file $SYSCONFDIR/proxy.conf or $HOME/.proxy.conf gnome | x11, xmu, gconf | Used to get proxy configured by GConf mozjs | mozjs | Get proxy by PAC Every configuration plugin has a type. There are three configuration types: 1. SYSTEM - Defines configuration on a system-wide basis 2. USER - Defines configuration on a user-wide basis 3. SESSION - Defines configuration for this current login session only A plugin can also choose to have no configuration type. By default, plugins are attempted in the following order: SESSION, USER, SYSTEM, and finally plugins without a type. The order within the categories is undefined and could be random. If a plugins says it can't find the configuration, the next plugin is tried. So for instance, the KDE plugin will not be used unless you are actually logged into KDE. The same applies for GNOME. The plugin order can be manually specified through an environmental variable. For instance, the following will set libproxy to use the envvar plugin first, then USER, then SYSTEM, then SESSION (capitalization is important): export PX_CONFIG_ORDER=envvar,USER,SYSTEM,SESSION Libsoup 2.25.5 and above depends on libproxy. 3.2. Interfaces: Exported Interfaces Interface Classification Comments --------------- -------------- ----------------------- SUNWlibproxy Uncommitted Package name of base library SUNWlibproxy-devel Uncommitted Package name of library for development /usr/lib/libproxy.so.0 Volatile C library /usr/lib/amd64/libproxy.so.0 Volatile 64-bit library /usr/lib/python2.4/vendor-packages/libproxy.py Volatile Python binding /usr/lib/pkgconfig/libproxy-1.0.pc Uncommitted libproxy pc file /usr/lib/amd64/pkgconfig/libproxy-1.0.pc Uncommitted 64-bit pc file /usr/include/libproxy/proxy.h Volatile libproxy header file /usr/demo/jds/bin/proxy Volatile binary file used for testing /usr/demo/jds/bin/amd64/proxy Volatile 64-bit binary file for testing /usr/share/man/man3/libproxy.3 Volatile libproxy man page /usr/lib/libproxy/0.2.3/plugins/envvar.so Volatile plugins for environment variables /usr/lib/libproxy/0.2.3/plugins/file.so Volatile plugins for configration files /usr/lib/libproxy/0.2.3/plugins/gnome.so Volatile plugins for GConf /usr/lib/libproxy/0.2.3/plugins/mozjs.so Volatile plugins for PAC /usr/lib/amd64/libproxy/* Volatile 64-bit plugins Imported Interfaces Interface Classification Comments --------------- -------------- ----------------------- SUNWgnome-config Committed LSARC/2002/146 SUNWxwplt Stable X Window System platform software(PSARC/1998/299) http_proxy, no_proxy environment variable Stable PSARC/2001/540 [10] GConf keys: /system/proxy/mode, /system/proxy/autoconfig_url, /system/ http_proxy/host, /system/http_proxy/port, Volatile Gconf configuration keys /system/proxy/socks_host, /system/proxy/ socks_port, /system/http_proxy/ignore_hosts libmozjs.so Consolidation Shared with Firefox Private 3.3. Packaging & Delivery: SUNWlibproxy(base package) - base package SUNWlibproxy-devel (development package) - develoment package for header 3.4. Dependencies: Plugin of libproxy for GNOME depends on libX11 ,libXmu ,libgconf and libmozjs. 3.5. Security Impact: Libproxy supports the feature of WPAD, which exposes a security risk discussed in the following link: http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Security We shall apply a patch to disable WPAD by default and there is no other security impact. 4. Resources and Schedule: 4.1. Product Approval Committee requested information: 4.1.1. Consolidation Name: Desktop Cteam/GNOME 4.1.2. Contributing OpCo/BU/Division Name: Desktop 4.1.3. Type of PAC Review and Approval expected: FastTrack 5. References Project website: http://code.google.com/p/libproxy/ Applications that should use libproxy: http://code.google.com/p/libproxy/wiki/Applications 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: JDS - Gnome 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From John.Fischer@Sun.COM Thu Feb 12 11:48:00 2009 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 n1CJlxL2027546 for ; Thu, 12 Feb 2009 11:47:59 -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 n1CJlXRx021619 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 12 Feb 2009 19:47:58 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 <0KEY00A1HXNUNG00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 12 Feb 2009 11:47:54 -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 <0KEY004EYXNTNY90@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 12 Feb 2009 11:47:53 -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 n1CJlrgf002556 for ; Thu, 12 Feb 2009 11:47:53 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEY00900XAZ8400@fe-sfbay-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 12 Feb 2009 11:47:53 -0800 (PST) Received: from [192.168.10.10] ([unknown] [76.20.56.47]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEY00JC7XNPDL10@fe-sfbay-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 12 Feb 2009 11:47:50 -0800 (PST) Date: Thu, 12 Feb 2009 11:46:56 -0800 From: John Fischer Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] In-reply-to: <200902111853.n1BIrIgG061820@sr1-umpk-12.sfbay.sun.com> Sender: John.Fischer@Sun.COM To: LSARC-ext@Sun.COM Cc: Ke.Wang@Sun.COM Reply-to: John.Fischer@Sun.COM Message-id: <49947CB0.3050300@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_fwBkKnGGzWEyzH6FUogW5w)" X-PMX-Version: 5.4.1.325704 References: <200902111853.n1BIrIgG061820@sr1-umpk-12.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081216) Status: RO Content-Length: 17445 This is a multi-part message in MIME format. --Boundary_(ID_fwBkKnGGzWEyzH6FUogW5w) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT All, Attached please find an updated proposal for this project. The case directory has been updated as well. Most of the updates are for readability/clarification. The only interface change is an addition to the interface table for the PX_CONFIG_ORDER environment variable which was already described at the end of the Details section (3.1). Thanks, John John Fischer wrote: > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > libproxy > 1.2. Name of Document Author/Supplier: > Author: Ke Wang > 1.3 Date of This Document: > 11 February, 2009 > 4. Technical Description > 1. Introduction > 1.1. Project/Component Working Name: > > libproxy > > 1.2. Name of Document Author/Supplier: > > Author: Ke Wang > Sponser: Irene Huang > > 1.3. Date of This Document: > > 02/04/2009 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Robert O'Dea > > 1.4.4. The name of your business unit: > > Software - OPG > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: harry.lu@sun.com > 1.5.2. Responsible Engineer: ke.wang@sun.com > 1.5.3. Marketing Manager: glynn.foster@sun.com > 1.5.4. Interest List: jeff.cai@sun.com > > 2. Project Summary > 2.1. Project Description: > > libproxy is a library that provides automatic proxy configuration management. > > 3. Technical Description: > 3.1. Details: > Proxy configuration is problematic for a number of reasons: > 1. There are a variety of places to get configuration information > 2. There are a variety of proxy types > 3. Proxy auto-configuration (PAC) requires Javascript (which most applications don't have) > 4. Automatically determining PAC location requires an implementation of the WPAD protocol > > Libproxy provides interfaces to get proxy that should be used to access a network resource. > It use various plugins to get proxy configuration from different places e.g. environment > variables, GConf, PAC. > > Libproxy offers the following features: > * extremely small core footprint > * no external dependencies within libproxy core (libproxy plugins may have dependencies) > * only 3 functions in the stable external API > * dynamic adjustment to changing network topology > * a standard way of dealing with proxy settings across all scenarios > > Libproxy includes a core library and several plugins. What the core library does is > only checking each plugin for an available proxy. > > Plugins list follows: > > PLUGIN | DEPS | COMMENT > envar | None | Used to get proxy configured by environment variable "http_proxy" > file | None | Used to get proxy configured in file $SYSCONFDIR/proxy.conf or $HOME/.proxy.conf > gnome | x11, xmu, gconf | Used to get proxy configured by GConf > mozjs | mozjs | Get proxy by PAC > > Every configuration plugin has a type. There are three configuration types: > > 1. SYSTEM - Defines configuration on a system-wide basis > 2. USER - Defines configuration on a user-wide basis > 3. SESSION - Defines configuration for this current login session only > > A plugin can also choose to have no configuration type. > > By default, plugins are attempted in the following order: SESSION, USER, SYSTEM, and finally > plugins without a type. The order within the categories is undefined and could be random. If a > plugins says it can't find the configuration, the next plugin is tried. So for instance, the > KDE plugin will not be used unless you are actually logged into KDE. The same applies for GNOME. > > The plugin order can be manually specified through an environmental variable. > For instance, the following will set libproxy to use the envvar plugin first, then USER, > then SYSTEM, then SESSION (capitalization is important): > > export PX_CONFIG_ORDER=envvar,USER,SYSTEM,SESSION > > Libsoup 2.25.5 and above depends on libproxy. > > 3.2. Interfaces: > Exported Interfaces > Interface Classification Comments > --------------- -------------- ----------------------- > SUNWlibproxy Uncommitted Package name of base library > SUNWlibproxy-devel Uncommitted Package name of library for development > > /usr/lib/libproxy.so.0 Volatile C library > /usr/lib/amd64/libproxy.so.0 Volatile 64-bit library > /usr/lib/python2.4/vendor-packages/libproxy.py Volatile Python binding > > /usr/lib/pkgconfig/libproxy-1.0.pc Uncommitted libproxy pc file > /usr/lib/amd64/pkgconfig/libproxy-1.0.pc Uncommitted 64-bit pc file > /usr/include/libproxy/proxy.h Volatile libproxy header file > /usr/demo/jds/bin/proxy Volatile binary file used for testing > /usr/demo/jds/bin/amd64/proxy Volatile 64-bit binary file for testing > /usr/share/man/man3/libproxy.3 Volatile libproxy man page > /usr/lib/libproxy/0.2.3/plugins/envvar.so Volatile plugins for environment variables > /usr/lib/libproxy/0.2.3/plugins/file.so Volatile plugins for configration files > /usr/lib/libproxy/0.2.3/plugins/gnome.so Volatile plugins for GConf > /usr/lib/libproxy/0.2.3/plugins/mozjs.so Volatile plugins for PAC > /usr/lib/amd64/libproxy/* Volatile 64-bit plugins > > Imported Interfaces > Interface Classification Comments > --------------- -------------- ----------------------- > SUNWgnome-config Committed LSARC/2002/146 > SUNWxwplt Stable X Window System platform software(PSARC/1998/299) > http_proxy, no_proxy environment variable Stable PSARC/2001/540 [10] > > GConf keys: /system/proxy/mode, > /system/proxy/autoconfig_url, /system/ > http_proxy/host, /system/http_proxy/port, Volatile Gconf configuration keys > /system/proxy/socks_host, /system/proxy/ > socks_port, /system/http_proxy/ignore_hosts > > libmozjs.so Consolidation Shared with Firefox > Private > > 3.3. Packaging & Delivery: > SUNWlibproxy(base package) - base package > SUNWlibproxy-devel (development package) - develoment package for > header > > 3.4. Dependencies: > Plugin of libproxy for GNOME depends on libX11 ,libXmu ,libgconf and libmozjs. > > 3.5. Security Impact: > Libproxy supports the feature of WPAD, which exposes a security risk discussed > in the following link: > http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Security > > We shall apply a patch to disable WPAD by default and there is no other security impact. > > 4. Resources and Schedule: > > 4.1. Product Approval Committee requested information: > 4.1.1. Consolidation Name: > > Desktop Cteam/GNOME > > 4.1.2. Contributing OpCo/BU/Division Name: > > Desktop > > 4.1.3. Type of PAC Review and Approval expected: > > FastTrack > > 5. References > Project website: http://code.google.com/p/libproxy/ > Applications that should use libproxy: http://code.google.com/p/libproxy/wiki/Applications > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > JDS - Gnome > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > --Boundary_(ID_fwBkKnGGzWEyzH6FUogW5w) Content-type: text/plain; name=proposal.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=proposal.txt 1. Introduction 1.1. Project/Component Working Name: libproxy 1.2. Name of Document Author/Supplier: Author: Ke Wang Sponser: John Fischer 1.3. Date of This Document: 02/04/2009 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert O'Dea 1.4.4. The name of your business unit: Software - OPG 1.5. Email Aliases: 1.5.1. Responsible Manager: harry.lu@sun.com 1.5.2. Responsible Engineer: ke.wang@sun.com 1.5.3. Marketing Manager: glynn.foster@sun.com 1.5.4. Interest List: jeff.cai@sun.com 2. Project Summary 2.1. Project Description: libproxy is a library that provides automatic proxy configuration management. 3. Technical Description: 3.1. Details: Proxy configuration is problematic for a number of reasons: 1. There are a variety of places to get configuration information 2. There are a variety of proxy types 3. Proxy auto-configuration (PAC) requires Javascript (which most applications don't have) 4. Automatically determining PAC location requires an implementation of the WPAD protocol Libproxy provides interfaces to get proxy that should be used to access a network resource. It use various plugins to get proxy configuration from different places e.g. environment variables, GConf, PAC. Libproxy offers the following features: * extremely small core footprint * no external dependencies within libproxy core (libproxy plugins may have dependencies) * only 3 functions in the stable external API * dynamic adjustment to changing network topology * a standard way of dealing with proxy settings across all scenarios Libproxy includes a core library and several plugins. The core library checks each plugin for an available proxy. Plugins list follows: PLUGIN | DEPS | COMMENT envar | None | Used to get proxy configured by environment variable "http_proxy" file | None | Used to get proxy configured in file $SYSCONFDIR/proxy.conf or $HOME/.proxy.conf gnome | x11, xmu, gconf | Used to get proxy configured by GConf mozjs | mozjs | Get proxy by PAC Every configuration plugin has a type. There are three configuration types: 1. SYSTEM - Defines configuration on a system-wide basis 2. USER - Defines configuration on a user-wide basis 3. SESSION - Defines configuration for this current login session only A plugin can also choose to have no configuration type. By default, plugins are attempted in the following order: SESSION, USER, SYSTEM, and finally plugins without a type. The order within the categories is undefined and could be random. If a plugin responds that it can't find the configuration, the next plugin is tried. So for instance, the KDE plugin will not be used unless you are actually logged into KDE. The same applies for GNOME. The plugin order can be manually specified through an environmental variable. For instance, the following will set libproxy to use the envvar plugin first, then USER, then SYSTEM, then SESSION (capitalization is important): export PX_CONFIG_ORDER=envvar,USER,SYSTEM,SESSION Libsoup 2.25.5 and above depends on libproxy. 3.2. Interfaces: Exported Interfaces Interface Classification Comments --------------- -------------- ----------------------- SUNWlibproxy Uncommitted Package name of base library SUNWlibproxy-devel Uncommitted Package name of library for development /usr/lib/libproxy.so.0 Volatile C library /usr/lib/amd64/libproxy.so.0 Volatile 64-bit library /usr/lib/python2.4/vendor-packages/libproxy.py Volatile Python binding /usr/lib/pkgconfig/libproxy-1.0.pc Uncommitted libproxy pc file /usr/lib/amd64/pkgconfig/libproxy-1.0.pc Uncommitted 64-bit pc file /usr/include/libproxy/proxy.h Volatile libproxy header file /usr/demo/jds/bin/proxy Volatile binary file used for testing /usr/demo/jds/bin/amd64/proxy Volatile 64-bit binary file for testing /usr/share/man/man3/libproxy.3 Volatile libproxy man page /usr/lib/libproxy/0.2.3/plugins/envvar.so Volatile plugins for environment variables /usr/lib/libproxy/0.2.3/plugins/file.so Volatile plugins for configration files /usr/lib/libproxy/0.2.3/plugins/gnome.so Volatile plugins for GConf /usr/lib/libproxy/0.2.3/plugins/mozjs.so Volatile plugins for PAC /usr/lib/amd64/libproxy/* Volatile 64-bit plugins PX_CONFIG_ORDER environment variable Volatile environment variable to define plugins order Imported Interfaces Interface Classification Comments --------------- -------------- ----------------------- SUNWgnome-config Committed LSARC/2002/146 SUNWxwplt Stable X Window System platform software(PSARC/1998/299) http_proxy, no_proxy environment variable Stable PSARC/2001/540 [10] GConf keys: /system/proxy/mode, /system/proxy/autoconfig_url, /system/ http_proxy/host, /system/http_proxy/port, Volatile Gconf configuration keys /system/proxy/socks_host, /system/proxy/ socks_port, /system/http_proxy/ignore_hosts $SYSCONFDIR/proxy.conf, $HOME/.proxy.conf Volatile System proxy configuration files libmozjs.so Consolidation Shared with Firefox Private 3.3. Packaging & Delivery: SUNWlibproxy(base package) - base package SUNWlibproxy-devel (development package) - develoment package for header 3.4. Dependencies: Plugin of libproxy for GNOME depends on libX11 ,libXmu ,libgconf and libmozjs. 3.5. Security Impact: Libproxy supports the feature of WPAD, which exposes a security risk discussed in the following link: http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Security We shall apply a patch to disable WPAD by default so there is no other security impact. Administrators can enable WPAD by passing --with-wpad-fallback while configuring. 4. Resources and Schedule: 4.1. Product Approval Committee requested information: 4.1.1. Consolidation Name: Desktop Cteam/GNOME 4.1.2. Contributing OpCo/BU/Division Name: Desktop 4.1.3. Type of PAC Review and Approval expected: FastTrack 5. References Project website: http://code.google.com/p/libproxy/ Applications that should use libproxy: http://code.google.com/p/libproxy/wiki/Applications --Boundary_(ID_fwBkKnGGzWEyzH6FUogW5w)-- From johnf@sr1-umpk-12.sfbay.sun.com Fri Feb 20 06:13:13 2009 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 n1KEDCSd009371 for ; Fri, 20 Feb 2009 06:13:12 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1KECxHG022840 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 20 Feb 2009 14:13:11 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFD00M0DBHW7M00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 20 Feb 2009 07:13:08 -0700 (MST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFD00L4LBHW0V10@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 20 Feb 2009 07:13:08 -0700 (MST) Received: from sr1-umpk-12.sfbay.sun.com (sr1-umpk-12.SFBay.Sun.COM [129.145.154.112]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1KED6Lh003385; Fri, 20 Feb 2009 06:13:06 -0800 (PST) Received: from sr1-umpk-12.sfbay.sun.com (localhost [127.0.0.1]) by sr1-umpk-12.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1KED61d047898; Fri, 20 Feb 2009 06:13:06 -0800 (PST) Received: (from johnf@localhost) by sr1-umpk-12.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1KED6F2047897; Fri, 20 Feb 2009 06:13:06 -0800 (PST) Date: Fri, 20 Feb 2009 06:13:06 -0800 (PST) From: John Fischer Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] To: John.Fischer@sun.com, LSARC-ext@sun.com Cc: Ke.Wang@sun.com Message-id: <200902201413.n1KED6F2047897@sr1-umpk-12.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 129 all, The timer has expired on this fast track. However, no one did +1-ed it. Does anyone want to do that now? Thanks, John From margot.miller@sun.com Fri Feb 20 08:43:52 2009 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 n1KGhpu7021347 for ; Fri, 20 Feb 2009 08:43:52 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1KGhbe8041815; Fri, 20 Feb 2009 09:43:48 -0700 (MST) 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 <0KFD00JO7IGZEQ90@nwk-avmta-2.sfbay.sun.com>; Fri, 20 Feb 2009 08:43:47 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFD00L3LIE0JZ10@nwk-avmta-2.sfbay.sun.com>; Fri, 20 Feb 2009 08:42:00 -0800 (PST) Received: from [10.7.250.251] (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1KGfvTD972352; Fri, 20 Feb 2009 08:41:57 -0800 (PST) Date: Fri, 20 Feb 2009 08:38:22 -0800 From: Margot Miller Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] In-reply-to: <200902201413.n1KED6F2047897@sr1-umpk-12.sfbay.sun.com> To: John Fischer Cc: John.Fischer@sun.com, LSARC-ext@sun.com, Ke.Wang@sun.com Message-id: <499EDC7E.1090800@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902201413.n1KED6F2047897@sr1-umpk-12.sfbay.sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 432 +1 A few minor things: please move man page out of the interface table. Also, I didn't see the man page in the case materials. Could the team please put it there? Also, I would imagine that the man page would state the security risk of WPAD? Thanks Margot John Fischer wrote: > all, > > The timer has expired on this fast track. However, no one > did +1-ed it. Does anyone want to do that now? > > Thanks, > > John > > From Ke.Wang@sun.com Mon Feb 23 22:16:57 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1O6Gvv2025105 for ; Mon, 23 Feb 2009 22:16:57 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1O6Gui5015807 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 23 Feb 2009 22:16:57 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFK00703447O900@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 23 Feb 2009 22:16:55 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFK005O2446UR30@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 23 Feb 2009 22:16:55 -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 n1O6Gs7u006338 for ; Tue, 24 Feb 2009 06:16:54 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFK00A003ROZI00@mail-apac.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 14:16:54 +0800 (SGT) Received: from [129.158.217.112] ([unknown] [129.158.217.112]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFK00HHO445TF10@mail-apac.sun.com>; Tue, 24 Feb 2009 14:16:54 +0800 (SGT) Date: Tue, 24 Feb 2009 14:16:46 +0800 From: Ke Wang Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] In-reply-to: <499EDC7E.1090800@sun.com> Sender: Ke.Wang@sun.com To: Margot Miller Cc: John Fischer , John.Fischer@sun.com, LSARC-ext@sun.com Message-id: <1235456206.4459.9.camel@diving> MIME-version: 1.0 X-Mailer: Evolution 2.25.4 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902201413.n1KED6F2047897@sr1-umpk-12.sfbay.sun.com> <499EDC7E.1090800@sun.com> Status: RO Content-Length: 621 Hi Margot, Thanks for your advice! I've sent the man page to John. Regards, Ke On Fri, 2009-02-20 at 08:38 -0800, Margot Miller wrote: > +1 > > A few minor things: please move man page out of the interface table. > Also, I didn't see the man page in the case materials. Could the > team please put it there? Also, I would imagine that the > man page would state the security risk of WPAD? > > Thanks > Margot > > > > John Fischer wrote: > > all, > > > > The timer has expired on this fast track. However, no one > > did +1-ed it. Does anyone want to do that now? > > > > Thanks, > > > > John > > > > > From Ke.Wang@sun.com Mon Feb 23 22:48:35 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1O6mZfo025372 for ; Mon, 23 Feb 2009 22:48:35 -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 n1O6mSuk010022 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 23 Feb 2009 22:48:34 -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 <0KFK00K0H5KX6400@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Mon, 23 Feb 2009 23:48:33 -0700 (MST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFK0035E5KT4CA0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Mon, 23 Feb 2009 23:48:30 -0700 (MST) 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 n1O6mTvq009141 for ; Tue, 24 Feb 2009 06:48:29 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFK002005FV8100@mail-apac.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Tue, 24 Feb 2009 14:48:29 +0800 (SGT) Received: from [129.158.217.112] ([unknown] [129.158.217.112]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFK00HPH5KSTF30@mail-apac.sun.com>; Tue, 24 Feb 2009 14:48:29 +0800 (SGT) Date: Tue, 24 Feb 2009 14:48:21 +0800 From: Ke Wang Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] In-reply-to: <1235456206.4459.9.camel@diving> Sender: Ke.Wang@sun.com To: Margot Miller Cc: John Fischer , John.Fischer@sun.com, LSARC-ext@sun.com Message-id: <1235458101.4459.13.camel@diving> MIME-version: 1.0 X-Mailer: Evolution 2.25.4 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902201413.n1KED6F2047897@sr1-umpk-12.sfbay.sun.com> <499EDC7E.1090800@sun.com> <1235456206.4459.9.camel@diving> Status: RO Content-Length: 859 BTW, both the security risk of WPAD and how we deal with this risk are mentioned in the man page. Thanks Ke On Tue, 2009-02-24 at 14:16 +0800, Ke Wang wrote: > Hi Margot, > > Thanks for your advice! > I've sent the man page to John. > > Regards, > > Ke > > > On Fri, 2009-02-20 at 08:38 -0800, Margot Miller wrote: > > +1 > > > > A few minor things: please move man page out of the interface table. > > Also, I didn't see the man page in the case materials. Could the > > team please put it there? Also, I would imagine that the > > man page would state the security risk of WPAD? > > > > Thanks > > Margot > > > > > > > > John Fischer wrote: > > > all, > > > > > > The timer has expired on this fast track. However, no one > > > did +1-ed it. Does anyone want to do that now? > > > > > > Thanks, > > > > > > John > > > > > > > > > > From Lloyd.Chambers@Sun.COM Tue Feb 24 09:57:35 2009 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 n1OHvYfc029358 for ; Tue, 24 Feb 2009 09:57:35 -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 n1OHvTeZ023996 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 25 Feb 2009 01:57:33 +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 <0KFL009030JXUI00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 09:57:33 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFL009SZ0JX8L00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 09:57:33 -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 n1OHvW8t009526 for ; Tue, 24 Feb 2009 09:57:32 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFL00E0009OUK00@fe-sfbay-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 09:57:32 -0800 (PST) Received: from [192.168.1.8] ([unknown] [129.150.20.4]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFL00JR80I0Q8D0@fe-sfbay-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 09:57:21 -0800 (PST) Date: Tue, 24 Feb 2009 09:57:20 -0800 From: Lloyd Chambers Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] In-reply-to: <49947CB0.3050300@sun.com> Sender: Lloyd.Chambers@Sun.COM To: John.Fischer@Sun.COM Cc: LSARC-ext@Sun.COM, Ke.Wang@Sun.COM Message-id: <3C4A4394-8028-4229-9CD4-751650C87A65@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.930.3) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902111853.n1BIrIgG061820@sr1-umpk-12.sfbay.sun.com> <49947CB0.3050300@sun.com> Status: RO Content-Length: 17685 +1 .............................................. Lloyd Chambers GlassFish team, LSARC member On Feb 12, 2009, at 11:46 AM, John Fischer wrote: > All, > > Attached please find an updated proposal for this project. > The case directory has been updated as well. Most of the > updates are for readability/clarification. The only interface > change is an addition to the interface table for the > PX_CONFIG_ORDER environment variable which was already described > at the end of the Details section (3.1). > > Thanks, > > John > > > John Fischer wrote: >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> libproxy >> 1.2. Name of Document Author/Supplier: >> Author: Ke Wang >> 1.3 Date of This Document: >> 11 February, 2009 >> 4. Technical Description >> 1. Introduction >> 1.1. Project/Component Working Name: >> libproxy >> 1.2. Name of Document Author/Supplier: >> Author: Ke Wang >> Sponser: Irene Huang >> 1.3. Date of This Document: >> 02/04/2009 >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> Solaris PAC >> 1.4.2. The ARC(s) you expect to review your project: >> LSARC >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> Robert O'Dea >> 1.4.4. The name of your business unit: >> Software - OPG >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: harry.lu@sun.com >> 1.5.2. Responsible Engineer: ke.wang@sun.com >> 1.5.3. Marketing Manager: glynn.foster@sun.com >> 1.5.4. Interest List: jeff.cai@sun.com >> 2. Project Summary >> 2.1. Project Description: >> libproxy is a library that provides automatic proxy >> configuration management. >> 3. Technical Description: >> 3.1. Details: >> Proxy configuration is problematic for a number of reasons: >> 1. There are a variety of places to get configuration >> information >> 2. There are a variety of proxy types >> 3. Proxy auto-configuration (PAC) requires Javascript (which >> most applications don't have) >> 4. Automatically determining PAC location requires an >> implementation of the WPAD protocol >> Libproxy provides interfaces to get proxy that should be used >> to access a network resource. >> It use various plugins to get proxy configuration from >> different places e.g. environment >> variables, GConf, PAC. >> Libproxy offers the following features: >> * extremely small core footprint >> * no external dependencies within libproxy core (libproxy >> plugins may have dependencies) >> * only 3 functions in the stable external API >> * dynamic adjustment to changing network topology >> * a standard way of dealing with proxy settings across all >> scenarios >> Libproxy includes a core library and several plugins. What the >> core library does is >> only checking each plugin for an available proxy. >> Plugins list follows: >> PLUGIN | DEPS | COMMENT >> envar | None | Used to get proxy >> configured by environment variable "http_proxy" >> file | None | Used to get proxy >> configured in file $SYSCONFDIR/proxy.conf or $HOME/.proxy.conf >> gnome | x11, xmu, gconf | Used to get proxy >> configured by GConf >> mozjs | mozjs | Get proxy by PAC >> Every configuration plugin has a type. There are three >> configuration types: >> 1. SYSTEM - Defines configuration on a system-wide basis >> 2. USER - Defines configuration on a user-wide basis >> 3. SESSION - Defines configuration for this current login >> session only A plugin can also choose to have no >> configuration type. >> By default, plugins are attempted in the following order: >> SESSION, USER, SYSTEM, and finally >> plugins without a type. The order within the categories is >> undefined and could be random. If a >> plugins says it can't find the configuration, the next plugin >> is tried. So for instance, the >> KDE plugin will not be used unless you are actually logged >> into KDE. The same applies for GNOME. >> The plugin order can be manually specified through an >> environmental variable. >> For instance, the following will set libproxy to use the >> envvar plugin first, then USER, >> then SYSTEM, then SESSION (capitalization is important): >> export PX_CONFIG_ORDER=envvar,USER,SYSTEM,SESSION >> Libsoup 2.25.5 and above depends on libproxy. >> 3.2. Interfaces: >> Exported Interfaces >> Interface >> Classification Comments >> --------------- >> -------------- ----------------------- >> SUNWlibproxy >> Uncommitted Package name of base library >> SUNWlibproxy-devel >> Uncommitted Package name of library for development >> /usr/lib/libproxy.so.0 >> Volatile C library >> /usr/lib/amd64/libproxy.so.0 >> Volatile 64-bit library >> /usr/lib/python2.4/vendor-packages/libproxy.py >> Volatile Python binding >> /usr/lib/pkgconfig/libproxy-1.0.pc >> Uncommitted libproxy pc file >> /usr/lib/amd64/pkgconfig/libproxy-1.0.pc >> Uncommitted 64-bit pc file >> /usr/include/libproxy/proxy.h >> Volatile libproxy header file >> /usr/demo/jds/bin/proxy Volatile >> binary file used for testing >> /usr/demo/jds/bin/amd64/proxy >> Volatile 64-bit binary file for testing >> /usr/share/man/man3/libproxy.3 >> Volatile libproxy man page >> /usr/lib/libproxy/0.2.3/plugins/envvar.so >> Volatile plugins for environment variables >> /usr/lib/libproxy/0.2.3/plugins/file.so >> Volatile plugins for configration files >> /usr/lib/libproxy/0.2.3/plugins/gnome.so >> Volatile plugins for GConf >> /usr/lib/libproxy/0.2.3/plugins/mozjs.so >> Volatile plugins for PAC >> /usr/lib/amd64/libproxy/* >> Volatile 64-bit plugins >> Imported Interfaces >> Interface >> Classification Comments >> --------------- >> -------------- ----------------------- >> SUNWgnome-config >> Committed LSARC/2002/146 >> SUNWxwplt >> Stable X Window System platform software(PSARC/1998/299) >> http_proxy, no_proxy environment variable >> Stable PSARC/2001/540 [10] >> GConf keys: /system/proxy/mode, >> /system/proxy/autoconfig_url, /system/ >> http_proxy/host, /system/http_proxy/port, >> Volatile Gconf configuration keys >> /system/proxy/socks_host, /system/proxy/ >> socks_port, /system/http_proxy/ignore_hosts >> libmozjs.so >> Consolidation Shared with Firefox >> Private >> 3.3. Packaging & Delivery: >> SUNWlibproxy(base package) - base package >> SUNWlibproxy-devel (development package) - develoment >> package for >> header >> 3.4. Dependencies: >> Plugin of libproxy for GNOME depends on >> libX11 ,libXmu ,libgconf and libmozjs. >> 3.5. Security Impact: >> Libproxy supports the feature of WPAD, which exposes a >> security risk discussed >> in the following link: >> http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Security >> We shall apply a patch to disable WPAD by default and there >> is no other security impact. >> 4. Resources and Schedule: >> 4.1. Product Approval Committee requested information: >> 4.1.1. Consolidation Name: >> Desktop Cteam/GNOME >> 4.1.2. Contributing OpCo/BU/Division Name: >> Desktop >> 4.1.3. Type of PAC Review and Approval expected: >> FastTrack >> 5. References >> Project website: http://code.google.com/p/libproxy/ >> Applications that should use libproxy: http://code.google.com/p/libproxy/wiki/Applications >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> JDS - Gnome >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open > 1. Introduction > 1.1. Project/Component Working Name: > > libproxy > > 1.2. Name of Document Author/Supplier: > > Author: Ke Wang > Sponser: John Fischer > > 1.3. Date of This Document: > > 02/04/2009 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Robert O'Dea > > 1.4.4. The name of your business unit: > > Software - OPG > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: harry.lu@sun.com > 1.5.2. Responsible Engineer: ke.wang@sun.com > 1.5.3. Marketing Manager: glynn.foster@sun.com > 1.5.4. Interest List: jeff.cai@sun.com > > 2. Project Summary > 2.1. Project Description: > > libproxy is a library that provides automatic proxy > configuration management. > > 3. Technical Description: > 3.1. Details: > Proxy configuration is problematic for a number of reasons: > 1. There are a variety of places to get configuration > information > 2. There are a variety of proxy types > 3. Proxy auto-configuration (PAC) requires Javascript (which > most applications don't have) > 4. Automatically determining PAC location requires an > implementation of the WPAD protocol > > Libproxy provides interfaces to get proxy that should be used > to access a network resource. > It use various plugins to get proxy configuration from > different places e.g. environment > variables, GConf, PAC. > > Libproxy offers the following features: > * extremely small core footprint > * no external dependencies within libproxy core (libproxy > plugins may have dependencies) > * only 3 functions in the stable external API > * dynamic adjustment to changing network topology > * a standard way of dealing with proxy settings across all > scenarios > > Libproxy includes a core library and several plugins. The core > library checks each > plugin for an available proxy. > > Plugins list follows: > > PLUGIN | DEPS | COMMENT > envar | None | Used to get proxy > configured by environment variable "http_proxy" > file | None | Used to get proxy > configured in file $SYSCONFDIR/proxy.conf or $HOME/.proxy.conf > gnome | x11, xmu, gconf | Used to get proxy > configured by GConf > mozjs | mozjs | Get proxy by PAC > > Every configuration plugin has a type. There are three > configuration types: > > 1. SYSTEM - Defines configuration on a system-wide basis > 2. USER - Defines configuration on a user-wide basis > 3. SESSION - Defines configuration for this current login > session only > > A plugin can also choose to have no configuration type. > > By default, plugins are attempted in the following order: > SESSION, USER, SYSTEM, and finally > plugins without a type. The order within the categories is > undefined and could be random. If a > plugin responds that it can't find the configuration, the next > plugin is tried. So for instance, > the KDE plugin will not be used unless you are actually logged > into KDE. The same applies for GNOME. > > The plugin order can be manually specified through an > environmental variable. > For instance, the following will set libproxy to use the envvar > plugin first, then USER, > then SYSTEM, then SESSION (capitalization is important): > > export PX_CONFIG_ORDER=envvar,USER,SYSTEM,SESSION > > Libsoup 2.25.5 and above depends on libproxy. > > 3.2. Interfaces: > Exported Interfaces > Interface > Classification Comments > --------------- > -------------- ----------------------- > SUNWlibproxy > Uncommitted Package name of base library > SUNWlibproxy-devel > Uncommitted Package name of library for development > > /usr/lib/libproxy.so.0 > Volatile C library > /usr/lib/amd64/libproxy.so.0 > Volatile 64-bit library > /usr/lib/python2.4/vendor-packages/libproxy.py > Volatile Python binding > > /usr/lib/pkgconfig/libproxy-1.0.pc > Uncommitted libproxy pc file > /usr/lib/amd64/pkgconfig/libproxy-1.0.pc > Uncommitted 64-bit pc file > /usr/include/libproxy/proxy.h > Volatile libproxy header file > /usr/demo/jds/bin/proxy Volatile > binary file used for testing > /usr/demo/jds/bin/amd64/proxy > Volatile 64-bit binary file for testing > /usr/share/man/man3/libproxy.3 > Volatile libproxy man page > /usr/lib/libproxy/0.2.3/plugins/envvar.so > Volatile plugins for environment variables > /usr/lib/libproxy/0.2.3/plugins/file.so > Volatile plugins for configration files > /usr/lib/libproxy/0.2.3/plugins/gnome.so > Volatile plugins for GConf > /usr/lib/libproxy/0.2.3/plugins/mozjs.so > Volatile plugins for PAC > /usr/lib/amd64/libproxy/* > Volatile 64-bit plugins > > PX_CONFIG_ORDER environment variable > Volatile environment variable to define plugins order > > > Imported Interfaces > Interface > Classification Comments > --------------- > -------------- ----------------------- > SUNWgnome-config > Committed LSARC/2002/146 > SUNWxwplt > Stable X Window System platform software(PSARC/1998/299) > http_proxy, no_proxy environment variable > Stable PSARC/2001/540 [10] > > GConf keys: /system/proxy/mode, > /system/proxy/autoconfig_url, /system/ > http_proxy/host, /system/http_proxy/port, > Volatile Gconf configuration keys > /system/proxy/socks_host, /system/proxy/ > socks_port, /system/http_proxy/ignore_hosts > > $SYSCONFDIR/proxy.conf, $HOME/.proxy.conf > Volatile System proxy configuration files > > libmozjs.so > Consolidation Shared with Firefox > Private > > 3.3. Packaging & Delivery: > SUNWlibproxy(base package) - base package > SUNWlibproxy-devel (development package) - develoment > package for > header > > 3.4. Dependencies: > Plugin of libproxy for GNOME depends on > libX11 ,libXmu ,libgconf and libmozjs. > > 3.5. Security Impact: > Libproxy supports the feature of WPAD, which exposes a > security risk discussed > in the following link: > http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Security > > We shall apply a patch to disable WPAD by default so there > is no other security impact. > Administrators can enable WPAD by passing --with-wpad- > fallback while configuring. > > 4. Resources and Schedule: > > 4.1. Product Approval Committee requested information: > 4.1.1. Consolidation Name: > > Desktop Cteam/GNOME > > 4.1.2. Contributing OpCo/BU/Division Name: > > Desktop > > 4.1.3. Type of PAC Review and Approval expected: > > FastTrack > > 5. References > Project website: http://code.google.com/p/libproxy/ > Applications that should use libproxy: http://code.google.com/p/libproxy/wiki/Applications > From johnf@sac.sfbay.sun.com Thu Feb 26 10:25:17 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1QIPHPh003204 for ; Thu, 26 Feb 2009 10:25:17 -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 n1QIPBcX018482 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Thu, 26 Feb 2009 10:25:17 -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 <0KFO00117R64LK00@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Thu, 26 Feb 2009 11:25:16 -0700 (MST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFO00JBZR64JA50@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Thu, 26 Feb 2009 11:25:16 -0700 (MST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1QIPE9k006559; Thu, 26 Feb 2009 10:25:14 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1QIPELA003200; Thu, 26 Feb 2009 10:25:14 -0800 (PST) Received: (from johnf@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1QIPE06003199; Thu, 26 Feb 2009 10:25:14 -0800 (PST) Date: Thu, 26 Feb 2009 10:25:14 -0800 (PST) From: John Fischer Subject: Re: libproxy [LSARC/2009/088 FastTrack timeout 11/18/2009] To: John.Fischer@sun.com, Lloyd.Chambers@sun.com Cc: Ke.Wang@sun.com, lsarc-ext@sun.com Message-id: <200902261825.n1QIPE06003199@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 135 All, This case has received the needed +1, the timer has expired and it was approved at the LSARC meeting on Tuesday. Thanks, John