From wyllys@borg.sfbay.sun.com Wed Oct 17 12:33:55 2007 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 l9HJXtcb018994 for ; Wed, 17 Oct 2007 12:33:55 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9HJUXOg007142 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.Com>; Wed, 17 Oct 2007 12:30:33 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQ20020LM6WC800@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Oct 2007 13:30:32 -0600 (MDT) Received: from borg.SFBay.Sun.COM ([10.6.50.138]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQ2009CQM6VPTD0@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Oct 2007 13:30:31 -0600 (MDT) Received: from borg.SFBay.Sun.COM (localhost [127.0.0.1]) by borg.SFBay.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id l9HJQ9B7007667; Wed, 17 Oct 2007 12:26:09 -0700 (PDT) Received: (from wyllys@localhost) by borg.SFBay.Sun.COM (8.14.1+Sun/8.14.1/Submit) id l9HJQ9h4007656; Wed, 17 Oct 2007 12:26:09 -0700 (PDT) Date: Wed, 17 Oct 2007 12:26:09 -0700 (PDT) From: Wyllys Ingersoll Subject: KMF Pluggability Enhancements [PSARC/2007/604 FastTrack timeout 10/24/2007] To: PSARC-ext@sun.com Cc: kmf-discuss@opensolaris.org Message-id: <200710171926.l9HJQ9h4007656@borg.SFBay.Sun.COM> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 5378 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: KMF Pluggability Enhancements 1.2. Name of Document Author/Supplier: Author: Huie Lee 1.3 Date of This Document: 17 October, 2007 4. Technical Description Proposal: KMF Dynamic Plugin Support Submitter: Huie-Ying Lee Sponsor: Wyllys Ingersoll Interface Taxonomy: libkmf - Committed kmfcfg CLI - Uncommitted /etc/crypto/kmf.conf - Private Release Binding: micro/patch ============================================================================= Background: ============================================================================= Currently, all three plugins in KMF (key management framework) are hard-coded in libkmf and KMF is unable to accomodate additional plugins automatically. This enhancement will provide capabilities for users to add/remove additional plugins dynamically. ======================================================= A New Private configuration file: /etc/crypto/kmf.conf Interface Taxonomy: Private ======================================================= The KMF configuration file is "/etc/crypto/kmf.conf" with permission "644". This file specifies only non-default keystore plugins with the following format: keystore:modulepath=xxx[;option=option_str] The "keystore" field specifies the keystore name. The "modulepath" field specifies the pathname to a KMF plugin shared library object. If the pathname is not absolute, shared library objects are assumed to be relative to /usr/lib/security/$ISA/. The ISA token is replaced by an implementation defined directory name which defines the path relative to the calling program's instruction set architecture. The option field specifies an option string which would only be processed by the plugin. ================================================== Changes to the kmfcfg command ================================================== 1) A new "install" subcommand will be added to the kmfcfg command. $kmfcfg install keystore=keystore_name modulepath=path [option=option_str] This command installs a new plugin into the Key Management framework. Internally, a new entry for this plugin will be added into the /etc/crypto/kmf.conf file. 2) A new "uninstall" subcommand will be added to the kmfcfg command. $kmfcfg uninstall keystore=keystore_name This command will uninstall the plugin with the kstype name. Intenally, the entry with the keystore name will be removed from /etc/crypto/kmf.conf file. 3) A new "plugin" parameter will be added to the list subcommand. $kmfcfg list plugin - This command displays all the plugins in the system, including 3 default plugins. For example, if there is an additional plugin in the system, the output will look like $kmfcfg list plugin pkcs11:kmf_pkcs11.so.1 (built-in) file:kmf_openssl.so.1 (built-in) nss:kmf_nss.so.1 (built-in) new_plugin:/opt/lib/new_plugin.so.1;option=debug Note that without the "plugin" keyword, "kmfcfg list" will show the policy stuff as before. 4) A new "modify plugin" subcommand will be added to the modify subcommand. $ kmfcfg modify plugin keystore=keystore_name option=option_str This subcommand allows an admininstrator to modify the plugin option. The plugin option is defined by the plugin and will be interpreted by the plugin specifically, therefore this command will accept any option string. ================================================== Changes to libkmf (Committed) ================================================== 1) A new kmf_get_plugin_info() API will be added. KMF_RETURN kmf_get_plugin_info(KMF_HANDLE_T handle, char *keystore_name, KMF_KEYSTORE_TYPE *kstype, char **option) kstype_name - input kstype - output option - output This function takes a keystore name as input and returns a new KMF_KEYSTORE_TYPE value. If the option argument is not NULL, then this function will return the plugin option if this is an option string specified for the plugin. Note that the returned "kstype" value should be used to access the new plugin's SPI. ========================================================= New plugin package requirement and class action scripts ====================================================== For a new plugin library, we would like it to be installed into the Key Management Framework during the pkgadd time and uninstalled during the pkgrm time automatically. To achieve this, two class action scripts will be added in the /usr/sadm/install/scripts directory. i.kmfconf -> the installation class action script r.kmfconf -> the removal class action script Accordingly, the new plugin package should do the following: 1. Add the "kmfconf" class into the CLASSES string of the pkginfo.tmpl file. 2. Create an input file "kmf.conf" in the "etc/crypto" directory and The syntax of the input file is same as the kmf.conf file keystore:modulepath=xxx[;option=xxx] 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From wyllys.ingersoll@sun.com Wed Oct 17 12:42:41 2007 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 l9HJgefk019189 for ; Wed, 17 Oct 2007 12:42:41 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l9HJdH4g010289 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 18 Oct 2007 03:39:18 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQ200I05MLGQZ00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Oct 2007 12:39:16 -0700 (PDT) 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 <0JQ200HYRMLGWS00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Oct 2007 12:39:16 -0700 (PDT) Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182]) by jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9HJdFWx751075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2007 12:39:15 -0700 (PDT) Date: Wed, 17 Oct 2007 15:38:44 -0400 From: Wyllys Ingersoll Subject: Re: KMF Pluggability Enhancements [PSARC/2007/604 FastTrack timeout 10/24/2007] In-reply-to: <200710171926.l9HJQ9h4007656@borg.SFBay.Sun.COM> To: Wyllys Ingersoll Cc: PSARC-ext@sun.com, kmf-discuss@opensolaris.org Message-id: <471664C4.9010601@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: <200710171926.l9HJQ9h4007656@borg.SFBay.Sun.COM> User-Agent: Thunderbird 2.0.0.4 (X11/20070827) Status: RO Content-Length: 5755 The updated man page for kmfcfg(1) is in the case directory (orig, diff, and new) -Wyllys Wyllys Ingersoll 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: > KMF Pluggability Enhancements > 1.2. Name of Document Author/Supplier: > Author: Huie Lee > 1.3 Date of This Document: > 17 October, 2007 > 4. Technical Description > Proposal: KMF Dynamic Plugin Support > Submitter: Huie-Ying Lee > Sponsor: Wyllys Ingersoll > > Interface Taxonomy: libkmf - Committed > kmfcfg CLI - Uncommitted > /etc/crypto/kmf.conf - Private > > Release Binding: micro/patch > > ============================================================================= > Background: > ============================================================================= > Currently, all three plugins in KMF (key management framework) are hard-coded > in libkmf and KMF is unable to accomodate additional plugins automatically. > This enhancement will provide capabilities for users to add/remove additional > plugins dynamically. > > ======================================================= > A New Private configuration file: /etc/crypto/kmf.conf > Interface Taxonomy: Private > ======================================================= > > The KMF configuration file is "/etc/crypto/kmf.conf" with permission > "644". This file specifies only non-default keystore plugins with the > following format: > > keystore:modulepath=xxx[;option=option_str] > > The "keystore" field specifies the keystore name. > > The "modulepath" field specifies the pathname to a KMF plugin shared > library object. If the pathname is not absolute, shared library > objects are assumed to be relative to /usr/lib/security/$ISA/. > The ISA token is replaced by an implementation defined directory name > which defines the path relative to the calling program's instruction > set architecture. > > The option field specifies an option string which would only > be processed by the plugin. > > > ================================================== > Changes to the kmfcfg command > ================================================== > 1) A new "install" subcommand will be added to the kmfcfg command. > > $kmfcfg install keystore=keystore_name modulepath=path [option=option_str] > > This command installs a new plugin into the Key Management framework. > Internally, a new entry for this plugin will be added into the > /etc/crypto/kmf.conf file. > > > 2) A new "uninstall" subcommand will be added to the kmfcfg command. > > $kmfcfg uninstall keystore=keystore_name > > This command will uninstall the plugin with the kstype name. > Intenally, the entry with the keystore name will be removed from > /etc/crypto/kmf.conf file. > > 3) A new "plugin" parameter will be added to the list subcommand. > > $kmfcfg list plugin > > - This command displays all the plugins in the system, including 3 default > plugins. For example, if there is an additional plugin in the system, > the output will look like > > $kmfcfg list plugin > pkcs11:kmf_pkcs11.so.1 (built-in) > file:kmf_openssl.so.1 (built-in) > nss:kmf_nss.so.1 (built-in) > new_plugin:/opt/lib/new_plugin.so.1;option=debug > > Note that without the "plugin" keyword, "kmfcfg list" will show the policy > stuff as before. > > 4) A new "modify plugin" subcommand will be added to the modify subcommand. > > $ kmfcfg modify plugin keystore=keystore_name option=option_str > > This subcommand allows an admininstrator to modify the plugin option. > The plugin option is defined by the plugin and will be interpreted by the > plugin specifically, therefore this command will accept any option string. > > ================================================== > Changes to libkmf (Committed) > ================================================== > 1) A new kmf_get_plugin_info() API will be added. > > KMF_RETURN > kmf_get_plugin_info(KMF_HANDLE_T handle, char *keystore_name, > KMF_KEYSTORE_TYPE *kstype, char **option) > > kstype_name - input > kstype - output > option - output > > This function takes a keystore name as input and returns a new > KMF_KEYSTORE_TYPE value. If the option argument is not NULL, then > this function will return the plugin option if this is an option > string specified for the plugin. > > Note that the returned "kstype" value should be used to access the new > plugin's SPI. > > ========================================================= > New plugin package requirement and class action scripts > ====================================================== > For a new plugin library, we would like it to be installed into the Key > Management Framework during the pkgadd time and uninstalled during the pkgrm > time automatically. To achieve this, two class action scripts will be added > in the /usr/sadm/install/scripts directory. > > i.kmfconf -> the installation class action script > r.kmfconf -> the removal class action script > > Accordingly, the new plugin package should do the following: > > 1. Add the "kmfconf" class into the CLASSES string of the pkginfo.tmpl > file. > > 2. Create an input file "kmf.conf" in the "etc/crypto" directory and > The syntax of the input file is same as the kmf.conf file > > keystore:modulepath=xxx[;option=xxx] > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From wyllys.ingersoll@sun.com Wed Oct 17 12:48:58 2007 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 l9HJmvZn019330 for ; Wed, 17 Oct 2007 12:48:57 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9HJjYX6011867 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 17 Oct 2007 12:45:35 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQ200311MVXAE00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Oct 2007 13:45:33 -0600 (MDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQ2009ZQMVWQ2E0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 17 Oct 2007 13:45:32 -0600 (MDT) Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182]) by jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9HJjVn7752139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2007 12:45:31 -0700 (PDT) Date: Wed, 17 Oct 2007 15:45:00 -0400 From: Wyllys Ingersoll Subject: Re: KMF Pluggability Enhancements [PSARC/2007/604 FastTrack timeout 10/24/2007] In-reply-to: <200710171926.l9HJQ9h4007656@borg.SFBay.Sun.COM> To: Wyllys Ingersoll Cc: PSARC-ext@sun.com, kmf-discuss@opensolaris.org Message-id: <4716663C.70809@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: <200710171926.l9HJQ9h4007656@borg.SFBay.Sun.COM> User-Agent: Thunderbird 2.0.0.4 (X11/20070827) Status: RO Content-Length: 5756 The updated man page for kmfcfg(1) is in the case directory (orig, diff, and new) -Wyllys Wyllys Ingersoll 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: > KMF Pluggability Enhancements > 1.2. Name of Document Author/Supplier: > Author: Huie Lee > 1.3 Date of This Document: > 17 October, 2007 > 4. Technical Description > Proposal: KMF Dynamic Plugin Support > Submitter: Huie-Ying Lee > Sponsor: Wyllys Ingersoll > > Interface Taxonomy: libkmf - Committed > kmfcfg CLI - Uncommitted > /etc/crypto/kmf.conf - Private > > Release Binding: micro/patch > > ============================================================================= > Background: > ============================================================================= > Currently, all three plugins in KMF (key management framework) are hard-coded > in libkmf and KMF is unable to accomodate additional plugins automatically. > This enhancement will provide capabilities for users to add/remove additional > plugins dynamically. > > ======================================================= > A New Private configuration file: /etc/crypto/kmf.conf > Interface Taxonomy: Private > ======================================================= > > The KMF configuration file is "/etc/crypto/kmf.conf" with permission > "644". This file specifies only non-default keystore plugins with the > following format: > > keystore:modulepath=xxx[;option=option_str] > > The "keystore" field specifies the keystore name. > > The "modulepath" field specifies the pathname to a KMF plugin shared > library object. If the pathname is not absolute, shared library > objects are assumed to be relative to /usr/lib/security/$ISA/. > The ISA token is replaced by an implementation defined directory name > which defines the path relative to the calling program's instruction > set architecture. > > The option field specifies an option string which would only > be processed by the plugin. > > > ================================================== > Changes to the kmfcfg command > ================================================== > 1) A new "install" subcommand will be added to the kmfcfg command. > > $kmfcfg install keystore=keystore_name modulepath=path [option=option_str] > > This command installs a new plugin into the Key Management framework. > Internally, a new entry for this plugin will be added into the > /etc/crypto/kmf.conf file. > > > 2) A new "uninstall" subcommand will be added to the kmfcfg command. > > $kmfcfg uninstall keystore=keystore_name > > This command will uninstall the plugin with the kstype name. > Intenally, the entry with the keystore name will be removed from > /etc/crypto/kmf.conf file. > > 3) A new "plugin" parameter will be added to the list subcommand. > > $kmfcfg list plugin > > - This command displays all the plugins in the system, including 3 default > plugins. For example, if there is an additional plugin in the system, > the output will look like > > $kmfcfg list plugin > pkcs11:kmf_pkcs11.so.1 (built-in) > file:kmf_openssl.so.1 (built-in) > nss:kmf_nss.so.1 (built-in) > new_plugin:/opt/lib/new_plugin.so.1;option=debug > > Note that without the "plugin" keyword, "kmfcfg list" will show the policy > stuff as before. > > 4) A new "modify plugin" subcommand will be added to the modify subcommand. > > $ kmfcfg modify plugin keystore=keystore_name option=option_str > > This subcommand allows an admininstrator to modify the plugin option. > The plugin option is defined by the plugin and will be interpreted by the > plugin specifically, therefore this command will accept any option string. > > ================================================== > Changes to libkmf (Committed) > ================================================== > 1) A new kmf_get_plugin_info() API will be added. > > KMF_RETURN > kmf_get_plugin_info(KMF_HANDLE_T handle, char *keystore_name, > KMF_KEYSTORE_TYPE *kstype, char **option) > > kstype_name - input > kstype - output > option - output > > This function takes a keystore name as input and returns a new > KMF_KEYSTORE_TYPE value. If the option argument is not NULL, then > this function will return the plugin option if this is an option > string specified for the plugin. > > Note that the returned "kstype" value should be used to access the new > plugin's SPI. > > ========================================================= > New plugin package requirement and class action scripts > ====================================================== > For a new plugin library, we would like it to be installed into the Key > Management Framework during the pkgadd time and uninstalled during the pkgrm > time automatically. To achieve this, two class action scripts will be added > in the /usr/sadm/install/scripts directory. > > i.kmfconf -> the installation class action script > r.kmfconf -> the removal class action script > > Accordingly, the new plugin package should do the following: > > 1. Add the "kmfconf" class into the CLASSES string of the pkginfo.tmpl > file. > > 2. Create an input file "kmf.conf" in the "etc/crypto" directory and > The syntax of the input file is same as the kmf.conf file > > keystore:modulepath=xxx[;option=xxx] > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From wyllys.ingersoll@sun.com Wed Oct 24 12:08:05 2007 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 l9OJ845I029532 for ; Wed, 24 Oct 2007 12:08:05 -0700 (PDT) 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 l9OJ4ZeP021647 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 24 Oct 2007 12:04:37 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQF00J03JNOAT00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 24 Oct 2007 12:04:36 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00CUZJNOSI80@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 24 Oct 2007 12:04:36 -0700 (PDT) Received: from [10.7.251.182] (punchin-wyllys.SFBay.Sun.COM [10.7.251.182]) by jurassic-x4600.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9OJ4Z3B947920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Oct 2007 12:04:35 -0700 (PDT) Date: Wed, 24 Oct 2007 15:04:34 -0400 From: Wyllys Ingersoll Subject: PSARC 2007/604 KMF Pluggability Enhancements To: PSARC-ext@sun.com, kmf-discuss@opensolaris.org Message-id: <471F9742.4040208@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 User-Agent: Thunderbird 2.0.0.4 (X11/20070827) Status: RO Content-Length: 53 This case was approved at today's meeting. -Wyllys