FW: CPE Dictionary
|
|
Wolfkiel, Joseph
|
Some javascript/style in this post has been disabled (why?)
Drew,
List members,
To help with the expansion of the CPE dictionary, I'm submitting the CPEs for vendors in the US Army Asset Database. The list is in the CPE Dictionary XML format specified in the 2.1 specification. Please let me know if we need to make any changes in format. I would also like to know how I can track the progress of submitted CPEs as they are validated, added to the official CPE dictionary, then indexed with their respective CVEs. I'll also point out that the current namePattern format precludes us from just submitting a vendor name since the part-type component is mandatory. To get a vendor into the system, we have to create a cpe for each part-type that any given manufacturer may produce. In the attached list, each vendor is submitted as a producer of hardware, operating systems, and applications. I think we should discuss the role and requirement for the part-type component in the version 3.x CPE specification. - Joe Wolfkiel Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 <?xml version="1.0" encoding="utf-8" ?> <cpe-list xmlns="http://cpe.mitre.org/dictionary/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://cpe.mitre.org/dictionary/2.0 cpe-dictionary_2.0.xsd"> <cpe-item name="cpe:/o:3com"> <title xml:lang="en-us">3Com</title> </cpe-item> <cpe-item name="cpe:/a:3com"> <title xml:lang="en-us">3Com</title> </cpe-item> <cpe-item name="cpe:/h:3com"> <title xml:lang="en-us">3Com</title> </cpe-item> <cpe-item name="cpe:/o:3dconnexion"> <title xml:lang="en-us">3Dconnexion</title> </cpe-item> <cpe-item name="cpe:/a:3dconnexion"> <title xml:lang="en-us">3Dconnexion</title> </cpe-item> <cpe-item name="cpe:/h:3dconnexion"> <title xml:lang="en-us">3Dconnexion</title> </cpe-item> <cpe-item name="cpe:/o:3s_group"> <title xml:lang="en-us">3S Group</title> </cpe-item> <cpe-item name="cpe:/a:3s_group"> <title xml:lang="en-us">3S Group</title> </cpe-item> <cpe-item name="cpe:/h:3s_group"> <title xml:lang="en-us">3S Group</title> </cpe-item> <cpe-item name="cpe:/o:abaqus"> <title xml:lang="en-us">ABAQUS</title> </cpe-item> <cpe-item name="cpe:/a:abaqus"> <title xml:lang="en-us">ABAQUS</title> </cpe-item> <cpe-item name="cpe:/h:abaqus"> <title xml:lang="en-us">ABAQUS</title> </cpe-item> <cpe-item name="cpe:/o:abbyy"> <title xml:lang="en-us">ABBYY</title> </cpe-item> <cpe-item name="cpe:/a:abbyy"> <title xml:lang="en-us">ABBYY</title> </cpe-item> <cpe-item name="cpe:/h:abbyy"> <title xml:lang="en-us">ABBYY</title> </cpe-item> <cpe-item name="cpe:/o:act"> <title xml:lang="en-us">ACT</title> </cpe-item> <cpe-item name="cpe:/a:act"> <title xml:lang="en-us">ACT</title> </cpe-item> <cpe-item name="cpe:/h:act"> <title xml:lang="en-us">ACT</title> </cpe-item> <cpe-item name="cpe:/o:activcard"> <title xml:lang="en-us">ActivCard</title> </cpe-item> <cpe-item name="cpe:/a:activcard"> <title xml:lang="en-us">ActivCard</title> </cpe-item> <cpe-item name="cpe:/h:activcard"> <title xml:lang="en-us">ActivCard</title> </cpe-item> <cpe-item name="cpe:/o:activestate"> <title xml:lang="en-us">ActiveState</title> </cpe-item> <cpe-item name="cpe:/a:activestate"> <title xml:lang="en-us">ActiveState</title> </cpe-item> <cpe-item name="cpe:/h:activestate"> <title xml:lang="en-us">ActiveState</title> </cpe-item> <cpe-item name="cpe:/o:actividentity"> <title xml:lang="en-us">ActivIdentity</title> </cpe-item> <cpe-item name="cpe:/a:actividentity"> <title xml:lang="en-us">ActivIdentity</title> </cpe-item> <cpe-item name="cpe:/h:actividentity"> <title xml:lang="en-us">ActivIdentity</title> </cpe-item> <cpe-item name="cpe:/o:adobe"> <title xml:lang="en-us">Adobe</title> </cpe-item> <cpe-item name="cpe:/a:adobe"> <title xml:lang="en-us">Adobe</title> </cpe-item> <cpe-item name="cpe:/h:adobe"> <title xml:lang="en-us">Adobe</title> </cpe-item> <cpe-item name="cpe:/o:ahead"> <title xml:lang="en-us">Ahead</title> </cpe-item> <cpe-item name="cpe:/a:ahead"> <title xml:lang="en-us">Ahead</title> </cpe-item> <cpe-item name="cpe:/h:ahead"> <title xml:lang="en-us">Ahead</title> </cpe-item> <cpe-item name="cpe:/o:alcatel"> <title xml:lang="en-us">Alcatel</title> </cpe-item> <cpe-item name="cpe:/a:alcatel"> <title xml:lang="en-us">Alcatel</title> </cpe-item> <cpe-item name="cpe:/h:alcatel"> <title xml:lang="en-us">Alcatel</title> </cpe-item> <cpe-item name="cpe:/o:allied_telesis"> <title xml:lang="en-us">Allied Telesis</title> </cpe-item> <cpe-item name="cpe:/a:allied_telesis"> <title xml:lang="en-us">Allied Telesis</title> </cpe-item> <cpe-item name="cpe:/h:allied_telesis"> <title xml:lang="en-us">Allied Telesis</title> </cpe-item> <cpe-item name="cpe:/o:altiris"> <title xml:lang="en-us">Altiris</title> </cpe-item> <cpe-item name="cpe:/a:altiris"> <title xml:lang="en-us">Altiris</title> </cpe-item> <cpe-item name="cpe:/h:altiris"> <title xml:lang="en-us">Altiris</title> </cpe-item> <cpe-item name="cpe:/o:altium_ltd"> <title xml:lang="en-us">Altium Ltd.</title> </cpe-item> <cpe-item name="cpe:/a:altium_ltd"> <title xml:lang="en-us">Altium Ltd.</title> </cpe-item> <cpe-item name="cpe:/h:altium_ltd"> <title xml:lang="en-us">Altium Ltd.</title> </cpe-item> <cpe-item name="cpe:/o:analogx"> <title xml:lang="en-us">AnalogX</title> </cpe-item> <cpe-item name="cpe:/a:analogx"> <title xml:lang="en-us">AnalogX</title> </cpe-item> <cpe-item name="cpe:/h:analogx"> <title xml:lang="en-us">AnalogX</title> </cpe-item> <cpe-item name="cpe:/o:ansys"> <title xml:lang="en-us">ANSYS</title> </cpe-item> <cpe-item name="cpe:/a:ansys"> <title xml:lang="en-us">ANSYS</title> </cpe-item> <cpe-item name="cpe:/h:ansys"> <title xml:lang="en-us">ANSYS</title> </cpe-item> <cpe-item name="cpe:/o:apache_software_foundation"> <title xml:lang="en-us">Apache Software Foundation</title> </cpe-item> <cpe-item name="cpe:/a:apache_software_foundation"> <title xml:lang="en-us">Apache Software Foundation</title> </cpe-item> <cpe-item name="cpe:/h:apache_software_foundation"> <title xml:lang="en-us">Apache Software Foundation</title> </cpe-item> <cpe-item name="cpe:/o:apc"> <title xml:lang="en-us">APC</title> </cpe-item> <cpe-item name="cpe:/a:apc"> <title xml:lang="en-us">APC</title> </cpe-item> <cpe-item name="cpe:/h:apc"> <title xml:lang="en-us">APC</title> </cpe-item> <cpe-item name="cpe:/o:apple"> <title xml:lang="en-us">Apple</title> </cpe-item> <cpe-item name="cpe:/a:apple"> <title xml:lang="en-us">Apple</title> </cpe-item> <cpe-item name="cpe:/h:apple"> <title xml:lang="en-us">Apple</title> </cpe-item> <cpe-item name="cpe:/o:apteryx"> <title xml:lang="en-us">Apteryx</title> </cpe-item> <cpe-item name="cpe:/a:apteryx"> <title xml:lang="en-us">Apteryx</title> </cpe-item> <cpe-item name="cpe:/h:apteryx"> <title xml:lang="en-us">Apteryx</title> </cpe-item> <cpe-item name="cpe:/o:arcsight"> <title xml:lang="en-us">ArcSight</title> </cpe-item> <cpe-item name="cpe:/a:arcsight"> <title xml:lang="en-us">ArcSight</title> </cpe-item> <cpe-item name="cpe:/h:arcsight"> <title xml:lang="en-us">ArcSight</title> </cpe-item> <cpe-item name="cpe:/o:asus"> <title xml:lang="en-us">Asus</title> </cpe-item> <cpe-item name="cpe:/a:asus"> <title xml:lang="en-us">Asus</title> </cpe-item> <cpe-item name="cpe:/h:asus"> <title xml:lang="en-us">Asus</title> </cpe-item> <cpe-item name="cpe:/o:ati_technologies"> <title xml:lang="en-us">ATI Technologies</title> </cpe-item> <cpe-item name="cpe:/a:ati_technologies"> <title xml:lang="en-us">ATI Technologies</title> </cpe-item> <cpe-item name="cpe:/h:ati_technologies"> <title xml:lang="en-us">ATI Technologies</title> </cpe-item> <cpe-item name="cpe:/o:ats"> <title xml:lang="en-us">ATS</title> </cpe-item> <cpe-item name="cpe:/a:ats"> <title xml:lang="en-us">ATS</title> </cpe-item> <cpe-item name="cpe:/h:ats"> <title xml:lang="en-us">ATS</title> </cpe-item> <cpe-item name="cpe:/o:autodesk"> <title xml:lang="en-us">Autodesk</title> </cpe-item> <cpe-item name="cpe:/a:autodesk"> <title xml:lang="en-us">Autodesk</title> </cpe-item> <cpe-item name="cpe:/h:autodesk"> <title xml:lang="en-us">Autodesk</title> </cpe-item> <cpe-item name="cpe:/o:autonomy"> <title xml:lang="en-us">Autonomy</title> </cpe-item> <cpe-item name="cpe:/a:autonomy"> <title xml:lang="en-us">Autonomy</title> </cpe-item> <cpe-item name="cpe:/h:autonomy"> <title xml:lang="en-us">Autonomy</title> </cpe-item> <cpe-item name="cpe:/o:avaya"> <title xml:lang="en-us">Avaya</title> </cpe-item> <cpe-item name="cpe:/a:avaya"> <title xml:lang="en-us">Avaya</title> </cpe-item> <cpe-item name="cpe:/h:avaya"> <title xml:lang="en-us">Avaya</title> </cpe-item> <cpe-item name="cpe:/o:avery"> <title xml:lang="en-us">Avery</title> </cpe-item> <cpe-item name="cpe:/a:avery"> <title xml:lang="en-us">Avery</title> </cpe-item> <cpe-item name="cpe:/h:avery"> <title xml:lang="en-us">Avery</title> </cpe-item> <cpe-item name="cpe:/o:avocent_corporation"> <title xml:lang="en-us">Avocent Corporation</title> </cpe-item> <cpe-item name="cpe:/a:avocent_corporation"> <title xml:lang="en-us">Avocent Corporation</title> </cpe-item> <cpe-item name="cpe:/h:avocent_corporation"> <title xml:lang="en-us">Avocent Corporation</title> </cpe-item> <cpe-item name="cpe:/o:axis"> <title xml:lang="en-us">Axis</title> </cpe-item> <cpe-item name="cpe:/a:axis"> <title xml:lang="en-us">Axis</title> </cpe-item> <cpe-item name="cpe:/h:axis"> <title xml:lang="en-us">Axis</title> </cpe-item> <cpe-item name="cpe:/o:bea_systems"> <title xml:lang="en-us">BEA Systems</title> </cpe-item> <cpe-item name="cpe:/a:bea_systems"> <title xml:lang="en-us">BEA Systems</title> </cpe-item> <cpe-item name="cpe:/h:bea_systems"> <title xml:lang="en-us">BEA Systems</title> </cpe-item> <cpe-item name="cpe:/o:berbee"> <title xml:lang="en-us">Berbee</title> <references> <reference href="http://www.berbee.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:berbee"> <title xml:lang="en-us">Berbee</title> <references> <reference href="http://www.berbee.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:berbee"> <title xml:lang="en-us">Berbee</title> <references> <reference href="http://www.berbee.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:isc"> <title xml:lang="en-us">ISC</title> </cpe-item> <cpe-item name="cpe:/a:isc"> <title xml:lang="en-us">ISC</title> </cpe-item> <cpe-item name="cpe:/h:isc"> <title xml:lang="en-us">ISC</title> </cpe-item> <cpe-item name="cpe:/o:blackberry"> <title xml:lang="en-us">Blackberry</title> </cpe-item> <cpe-item name="cpe:/a:blackberry"> <title xml:lang="en-us">Blackberry</title> </cpe-item> <cpe-item name="cpe:/h:blackberry"> <title xml:lang="en-us">Blackberry</title> </cpe-item> <cpe-item name="cpe:/o:blue_coat_systems"> <title xml:lang="en-us">Blue Coat Systems</title> </cpe-item> <cpe-item name="cpe:/a:blue_coat_systems"> <title xml:lang="en-us">Blue Coat Systems</title> </cpe-item> <cpe-item name="cpe:/h:blue_coat_systems"> <title xml:lang="en-us">Blue Coat Systems</title> </cpe-item> <cpe-item name="cpe:/o:bmc_software"> <title xml:lang="en-us">BMC Software</title> </cpe-item> <cpe-item name="cpe:/a:bmc_software"> <title xml:lang="en-us">BMC Software</title> </cpe-item> <cpe-item name="cpe:/h:bmc_software"> <title xml:lang="en-us">BMC Software</title> </cpe-item> <cpe-item name="cpe:/o:broadcom"> <title xml:lang="en-us">Broadcom</title> </cpe-item> <cpe-item name="cpe:/a:broadcom"> <title xml:lang="en-us">Broadcom</title> </cpe-item> <cpe-item name="cpe:/h:broadcom"> <title xml:lang="en-us">Broadcom</title> </cpe-item> <cpe-item name="cpe:/o:brocade"> <title xml:lang="en-us">Brocade</title> </cpe-item> <cpe-item name="cpe:/a:brocade"> <title xml:lang="en-us">Brocade</title> </cpe-item> <cpe-item name="cpe:/h:brocade"> <title xml:lang="en-us">Brocade</title> </cpe-item> <cpe-item name="cpe:/o:broderbund"> <title xml:lang="en-us">Broderbund</title> </cpe-item> <cpe-item name="cpe:/a:broderbund"> <title xml:lang="en-us">Broderbund</title> </cpe-item> <cpe-item name="cpe:/h:broderbund"> <title xml:lang="en-us">Broderbund</title> </cpe-item> <cpe-item name="cpe:/o:brother"> <title xml:lang="en-us">Brother</title> </cpe-item> <cpe-item name="cpe:/a:brother"> <title xml:lang="en-us">Brother</title> </cpe-item> <cpe-item name="cpe:/h:brother"> <title xml:lang="en-us">Brother</title> </cpe-item> <cpe-item name="cpe:/o:business_objects"> <title xml:lang="en-us">Business Objects</title> </cpe-item> <cpe-item name="cpe:/a:business_objects"> <title xml:lang="en-us">Business Objects</title> </cpe-item> <cpe-item name="cpe:/h:business_objects"> <title xml:lang="en-us">Business Objects</title> </cpe-item> <cpe-item name="cpe:/o:cabletron"> <title xml:lang="en-us">Cabletron</title> </cpe-item> <cpe-item name="cpe:/a:cabletron"> <title xml:lang="en-us">Cabletron</title> </cpe-item> <cpe-item name="cpe:/h:cabletron"> <title xml:lang="en-us">Cabletron</title> </cpe-item> <cpe-item name="cpe:/o:canon"> <title xml:lang="en-us">Canon</title> </cpe-item> <cpe-item name="cpe:/a:canon"> <title xml:lang="en-us">Canon</title> </cpe-item> <cpe-item name="cpe:/h:canon"> <title xml:lang="en-us">Canon</title> </cpe-item> <cpe-item name="cpe:/o:caymas"> <title xml:lang="en-us">Caymas</title> </cpe-item> <cpe-item name="cpe:/a:caymas"> <title xml:lang="en-us">Caymas</title> </cpe-item> <cpe-item name="cpe:/h:caymas"> <title xml:lang="en-us">Caymas</title> </cpe-item> <cpe-item name="cpe:/o:celsian"> <title xml:lang="en-us">Celsian</title> </cpe-item> <cpe-item name="cpe:/a:celsian"> <title xml:lang="en-us">Celsian</title> </cpe-item> <cpe-item name="cpe:/h:celsian"> <title xml:lang="en-us">Celsian</title> </cpe-item> <cpe-item name="cpe:/o:centos"> <title xml:lang="en-us">CentOS</title> </cpe-item> <cpe-item name="cpe:/a:centos"> <title xml:lang="en-us">CentOS</title> </cpe-item> <cpe-item name="cpe:/h:centos"> <title xml:lang="en-us">CentOS</title> </cpe-item> <cpe-item name="cpe:/o:checkpoint"> <title xml:lang="en-us">Checkpoint</title> </cpe-item> <cpe-item name="cpe:/a:checkpoint"> <title xml:lang="en-us">Checkpoint</title> </cpe-item> <cpe-item name="cpe:/h:checkpoint"> <title xml:lang="en-us">Checkpoint</title> </cpe-item> <cpe-item name="cpe:/o:ciphertrust"> <title xml:lang="en-us">CipherTrust</title> </cpe-item> <cpe-item name="cpe:/a:ciphertrust"> <title xml:lang="en-us">CipherTrust</title> </cpe-item> <cpe-item name="cpe:/h:ciphertrust"> <title xml:lang="en-us">CipherTrust</title> </cpe-item> <cpe-item name="cpe:/o:cisco"> <title xml:lang="en-us">Cisco</title> </cpe-item> <cpe-item name="cpe:/a:cisco"> <title xml:lang="en-us">Cisco</title> </cpe-item> <cpe-item name="cpe:/h:cisco"> <title xml:lang="en-us">Cisco</title> </cpe-item> <cpe-item name="cpe:/o:citadel"> <title xml:lang="en-us">Citadel</title> </cpe-item> <cpe-item name="cpe:/a:citadel"> <title xml:lang="en-us">Citadel</title> </cpe-item> <cpe-item name="cpe:/h:citadel"> <title xml:lang="en-us">Citadel</title> </cpe-item> <cpe-item name="cpe:/o:citrix"> <title xml:lang="en-us">Citrix</title> </cpe-item> <cpe-item name="cpe:/a:citrix"> <title xml:lang="en-us">Citrix</title> </cpe-item> <cpe-item name="cpe:/h:citrix"> <title xml:lang="en-us">Citrix</title> </cpe-item> <cpe-item name="cpe:/o:clevereye"> <title xml:lang="en-us">CleverEye</title> </cpe-item> <cpe-item name="cpe:/a:clevereye"> <title xml:lang="en-us">CleverEye</title> </cpe-item> <cpe-item name="cpe:/h:clevereye"> <title xml:lang="en-us">CleverEye</title> </cpe-item> <cpe-item name="cpe:/o:cms"> <title xml:lang="en-us">CMS</title> </cpe-item> <cpe-item name="cpe:/a:cms"> <title xml:lang="en-us">CMS</title> </cpe-item> <cpe-item name="cpe:/h:cms"> <title xml:lang="en-us">CMS</title> </cpe-item> <cpe-item name="cpe:/o:cognos"> <title xml:lang="en-us">Cognos</title> </cpe-item> <cpe-item name="cpe:/a:cognos"> <title xml:lang="en-us">Cognos</title> </cpe-item> <cpe-item name="cpe:/h:cognos"> <title xml:lang="en-us">Cognos</title> </cpe-item> <cpe-item name="cpe:/o:commpower"> <title xml:lang="en-us">CommPower</title> </cpe-item> <cpe-item name="cpe:/a:commpower"> <title xml:lang="en-us">CommPower</title> </cpe-item> <cpe-item name="cpe:/h:commpower"> <title xml:lang="en-us">CommPower</title> </cpe-item> <cpe-item name="cpe:/o:commvault"> <title xml:lang="en-us">CommVault</title> </cpe-item> <cpe-item name="cpe:/a:commvault"> <title xml:lang="en-us">CommVault</title> </cpe-item> <cpe-item name="cpe:/h:commvault"> <title xml:lang="en-us">CommVault</title> </cpe-item> <cpe-item name="cpe:/o:compaq"> <title xml:lang="en-us">Compaq</title> </cpe-item> <cpe-item name="cpe:/a:compaq"> <title xml:lang="en-us">Compaq</title> </cpe-item> <cpe-item name="cpe:/h:compaq"> <title xml:lang="en-us">Compaq</title> </cpe-item> <cpe-item name="cpe:/o:compellent"> <title xml:lang="en-us">Compellent</title> </cpe-item> <cpe-item name="cpe:/a:compellent"> <title xml:lang="en-us">Compellent</title> </cpe-item> <cpe-item name="cpe:/h:compellent"> <title xml:lang="en-us">Compellent</title> </cpe-item> <cpe-item name="cpe:/o:componentone_llc"> <title xml:lang="en-us">ComponentOne LLC</title> </cpe-item> <cpe-item name="cpe:/a:componentone_llc"> <title xml:lang="en-us">ComponentOne LLC</title> </cpe-item> <cpe-item name="cpe:/h:componentone_llc"> <title xml:lang="en-us">ComponentOne LLC</title> </cpe-item> <cpe-item name="cpe:/o:computer_associates"> <title xml:lang="en-us">Computer Associates</title> </cpe-item> <cpe-item name="cpe:/a:computer_associates"> <title xml:lang="en-us">Computer Associates</title> </cpe-item> <cpe-item name="cpe:/h:computer_associates"> <title xml:lang="en-us">Computer Associates</title> </cpe-item> <cpe-item name="cpe:/o:concord_communications"> <title xml:lang="en-us">Concord Communications</title> </cpe-item> <cpe-item name="cpe:/a:concord_communications"> <title xml:lang="en-us">Concord Communications</title> </cpe-item> <cpe-item name="cpe:/h:concord_communications"> <title xml:lang="en-us">Concord Communications</title> </cpe-item> <cpe-item name="cpe:/o:conectiva"> <title xml:lang="en-us">Conectiva</title> </cpe-item> <cpe-item name="cpe:/a:conectiva"> <title xml:lang="en-us">Conectiva</title> </cpe-item> <cpe-item name="cpe:/h:conectiva"> <title xml:lang="en-us">Conectiva</title> </cpe-item> <cpe-item name="cpe:/o:conexant_ambit"> <title xml:lang="en-us">Conexant-Ambit</title> </cpe-item> <cpe-item name="cpe:/a:conexant_ambit"> <title xml:lang="en-us">Conexant-Ambit</title> </cpe-item> <cpe-item name="cpe:/h:conexant_ambit"> <title xml:lang="en-us">Conexant-Ambit</title> </cpe-item> <cpe-item name="cpe:/o:corel"> <title xml:lang="en-us">Corel</title> </cpe-item> <cpe-item name="cpe:/a:corel"> <title xml:lang="en-us">Corel</title> </cpe-item> <cpe-item name="cpe:/h:corel"> <title xml:lang="en-us">Corel</title> </cpe-item> <cpe-item name="cpe:/o:core_street"> <title xml:lang="en-us">Core-Street</title> </cpe-item> <cpe-item name="cpe:/a:core_street"> <title xml:lang="en-us">Core-Street</title> </cpe-item> <cpe-item name="cpe:/h:core_street"> <title xml:lang="en-us">Core-Street</title> </cpe-item> <cpe-item name="cpe:/o:cray"> <title xml:lang="en-us">Cray</title> </cpe-item> <cpe-item name="cpe:/a:cray"> <title xml:lang="en-us">Cray</title> </cpe-item> <cpe-item name="cpe:/h:cray"> <title xml:lang="en-us">Cray</title> </cpe-item> <cpe-item name="cpe:/o:crossbeam"> <title xml:lang="en-us">CrossBeam</title> </cpe-item> <cpe-item name="cpe:/a:crossbeam"> <title xml:lang="en-us">CrossBeam</title> </cpe-item> <cpe-item name="cpe:/h:crossbeam"> <title xml:lang="en-us">CrossBeam</title> </cpe-item> <cpe-item name="cpe:/o:ctb_mcgraw_hill"> <title xml:lang="en-us">CTB-McGraw Hill</title> </cpe-item> <cpe-item name="cpe:/a:ctb_mcgraw_hill"> <title xml:lang="en-us">CTB-McGraw Hill</title> </cpe-item> <cpe-item name="cpe:/h:ctb_mcgraw_hill"> <title xml:lang="en-us">CTB-McGraw Hill</title> </cpe-item> <cpe-item name="cpe:/o:cyberlink"> <title xml:lang="en-us">Cyberlink</title> </cpe-item> <cpe-item name="cpe:/a:cyberlink"> <title xml:lang="en-us">Cyberlink</title> </cpe-item> <cpe-item name="cpe:/h:cyberlink"> <title xml:lang="en-us">Cyberlink</title> </cpe-item> <cpe-item name="cpe:/o:data_dynamics"> <title xml:lang="en-us">Data Dynamics</title> </cpe-item> <cpe-item name="cpe:/a:data_dynamics"> <title xml:lang="en-us">Data Dynamics</title> </cpe-item> <cpe-item name="cpe:/h:data_dynamics"> <title xml:lang="en-us">Data Dynamics</title> </cpe-item> <cpe-item name="cpe:/o:datadirect_technologies"> <title xml:lang="en-us">DataDirect Technologies</title> </cpe-item> <cpe-item name="cpe:/a:datadirect_technologies"> <title xml:lang="en-us">DataDirect Technologies</title> </cpe-item> <cpe-item name="cpe:/h:datadirect_technologies"> <title xml:lang="en-us">DataDirect Technologies</title> </cpe-item> <cpe-item name="cpe:/o:datawatch"> <title xml:lang="en-us">DataWatch</title> </cpe-item> <cpe-item name="cpe:/a:datawatch"> <title xml:lang="en-us">DataWatch</title> </cpe-item> <cpe-item name="cpe:/h:datawatch"> <title xml:lang="en-us">DataWatch</title> </cpe-item> <cpe-item name="cpe:/o:debian"> <title xml:lang="en-us">Debian</title> <references> <reference href="http://debian.lcs.mit.edu/debian/"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:debian"> <title xml:lang="en-us">Debian</title> <references> <reference href="http://debian.lcs.mit.edu/debian/"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:debian"> <title xml:lang="en-us">Debian</title> <references> <reference href="http://debian.lcs.mit.edu/debian/"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:dell"> <title xml:lang="en-us">Dell</title> </cpe-item> <cpe-item name="cpe:/a:dell"> <title xml:lang="en-us">Dell</title> </cpe-item> <cpe-item name="cpe:/h:dell"> <title xml:lang="en-us">Dell</title> </cpe-item> <cpe-item name="cpe:/o:delrina"> <title xml:lang="en-us">Delrina</title> </cpe-item> <cpe-item name="cpe:/a:delrina"> <title xml:lang="en-us">Delrina</title> </cpe-item> <cpe-item name="cpe:/h:delrina"> <title xml:lang="en-us">Delrina</title> </cpe-item> <cpe-item name="cpe:/o:digi"> <title xml:lang="en-us">DiGi</title> </cpe-item> <cpe-item name="cpe:/a:digi"> <title xml:lang="en-us">DiGi</title> </cpe-item> <cpe-item name="cpe:/h:digi"> <title xml:lang="en-us">DiGi</title> </cpe-item> <cpe-item name="cpe:/o:digital_juice"> <title xml:lang="en-us">Digital Juice</title> </cpe-item> <cpe-item name="cpe:/a:digital_juice"> <title xml:lang="en-us">Digital Juice</title> </cpe-item> <cpe-item name="cpe:/h:digital_juice"> <title xml:lang="en-us">Digital Juice</title> </cpe-item> <cpe-item name="cpe:/o:distributive_management"> <title xml:lang="en-us">Distributive Management</title> </cpe-item> <cpe-item name="cpe:/a:distributive_management"> <title xml:lang="en-us">Distributive Management</title> </cpe-item> <cpe-item name="cpe:/h:distributive_management"> <title xml:lang="en-us">Distributive Management</title> </cpe-item> <cpe-item name="cpe:/o:dotpdn_llc"> <title xml:lang="en-us">dotPDN LLC</title> </cpe-item> <cpe-item name="cpe:/a:dotpdn_llc"> <title xml:lang="en-us">dotPDN LLC</title> </cpe-item> <cpe-item name="cpe:/h:dotpdn_llc"> <title xml:lang="en-us">dotPDN LLC</title> </cpe-item> <cpe-item name="cpe:/o:dtod"> <title xml:lang="en-us">DTOD</title> </cpe-item> <cpe-item name="cpe:/a:dtod"> <title xml:lang="en-us">DTOD</title> </cpe-item> <cpe-item name="cpe:/h:dtod"> <title xml:lang="en-us">DTOD</title> </cpe-item> <cpe-item name="cpe:/o:eip"> <title xml:lang="en-us">EIP</title> </cpe-item> <cpe-item name="cpe:/a:eip"> <title xml:lang="en-us">EIP</title> </cpe-item> <cpe-item name="cpe:/h:eip"> <title xml:lang="en-us">EIP</title> </cpe-item> <cpe-item name="cpe:/o:elan_software_systems"> <title xml:lang="en-us">Elan Software Systems</title> </cpe-item> <cpe-item name="cpe:/a:elan_software_systems"> <title xml:lang="en-us">Elan Software Systems</title> </cpe-item> <cpe-item name="cpe:/h:elan_software_systems"> <title xml:lang="en-us">Elan Software Systems</title> </cpe-item> <cpe-item name="cpe:/o:emc"> <title xml:lang="en-us">EMC</title> </cpe-item> <cpe-item name="cpe:/a:emc"> <title xml:lang="en-us">EMC</title> </cpe-item> <cpe-item name="cpe:/h:emc"> <title xml:lang="en-us">EMC</title> </cpe-item> <cpe-item name="cpe:/o:emulex"> <title xml:lang="en-us">Emulex</title> </cpe-item> <cpe-item name="cpe:/a:emulex"> <title xml:lang="en-us">Emulex</title> </cpe-item> <cpe-item name="cpe:/h:emulex"> <title xml:lang="en-us">Emulex</title> </cpe-item> <cpe-item name="cpe:/o:engarde"> <title xml:lang="en-us">Engarde</title> </cpe-item> <cpe-item name="cpe:/a:engarde"> <title xml:lang="en-us">Engarde</title> </cpe-item> <cpe-item name="cpe:/h:engarde"> <title xml:lang="en-us">Engarde</title> </cpe-item> <cpe-item name="cpe:/o:enterasys"> <title xml:lang="en-us">Enterasys</title> </cpe-item> <cpe-item name="cpe:/a:enterasys"> <title xml:lang="en-us">Enterasys</title> </cpe-item> <cpe-item name="cpe:/h:enterasys"> <title xml:lang="en-us">Enterasys</title> </cpe-item> <cpe-item name="cpe:/o:entercept_security_technologies"> <title xml:lang="en-us">Entercept Security Technologies</title> </cpe-item> <cpe-item name="cpe:/a:entercept_security_technologies"> <title xml:lang="en-us">Entercept Security Technologies</title> </cpe-item> <cpe-item name="cpe:/h:entercept_security_technologies"> <title xml:lang="en-us">Entercept Security Technologies</title> </cpe-item> <cpe-item name="cpe:/o:envisionit"> <title xml:lang="en-us">EnvisionIT</title> </cpe-item> <cpe-item name="cpe:/a:envisionit"> <title xml:lang="en-us">EnvisionIT</title> </cpe-item> <cpe-item name="cpe:/h:envisionit"> <title xml:lang="en-us">EnvisionIT</title> </cpe-item> <cpe-item name="cpe:/o:epson"> <title xml:lang="en-us">Epson</title> </cpe-item> <cpe-item name="cpe:/a:epson"> <title xml:lang="en-us">Epson</title> </cpe-item> <cpe-item name="cpe:/h:epson"> <title xml:lang="en-us">Epson</title> </cpe-item> <cpe-item name="cpe:/o:esri"> <title xml:lang="en-us">ESRI</title> </cpe-item> <cpe-item name="cpe:/a:esri"> <title xml:lang="en-us">ESRI</title> </cpe-item> <cpe-item name="cpe:/h:esri"> <title xml:lang="en-us">ESRI</title> </cpe-item> <cpe-item name="cpe:/o:e_watch"> <title xml:lang="en-us">E-Watch</title> </cpe-item> <cpe-item name="cpe:/a:e_watch"> <title xml:lang="en-us">E-Watch</title> </cpe-item> <cpe-item name="cpe:/h:e_watch"> <title xml:lang="en-us">E-Watch</title> </cpe-item> <cpe-item name="cpe:/o:extreme_networks"> <title xml:lang="en-us">Extreme Networks</title> </cpe-item> <cpe-item name="cpe:/a:extreme_networks"> <title xml:lang="en-us">Extreme Networks</title> </cpe-item> <cpe-item name="cpe:/h:extreme_networks"> <title xml:lang="en-us">Extreme Networks</title> </cpe-item> <cpe-item name="cpe:/o:f5_networks"> <title xml:lang="en-us">F5 Networks</title> </cpe-item> <cpe-item name="cpe:/a:f5_networks"> <title xml:lang="en-us">F5 Networks</title> </cpe-item> <cpe-item name="cpe:/h:f5_networks"> <title xml:lang="en-us">F5 Networks</title> </cpe-item> <cpe-item name="cpe:/o:famatech"> <title xml:lang="en-us">Famatech</title> </cpe-item> <cpe-item name="cpe:/a:famatech"> <title xml:lang="en-us">Famatech</title> </cpe-item> <cpe-item name="cpe:/h:famatech"> <title xml:lang="en-us">Famatech</title> </cpe-item> <cpe-item name="cpe:/o:filemaker_inc"> <title xml:lang="en-us">Filemaker Inc.</title> </cpe-item> <cpe-item name="cpe:/a:filemaker_inc"> <title xml:lang="en-us">Filemaker Inc.</title> </cpe-item> <cpe-item name="cpe:/h:filemaker_inc"> <title xml:lang="en-us">Filemaker Inc.</title> </cpe-item> <cpe-item name="cpe:/o:firaxis_games"> <title xml:lang="en-us">Firaxis Games</title> </cpe-item> <cpe-item name="cpe:/a:firaxis_games"> <title xml:lang="en-us">Firaxis Games</title> </cpe-item> <cpe-item name="cpe:/h:firaxis_games"> <title xml:lang="en-us">Firaxis Games</title> </cpe-item> <cpe-item name="cpe:/o:firebird_project"> <title xml:lang="en-us">Firebird Project</title> </cpe-item> <cpe-item name="cpe:/a:firebird_project"> <title xml:lang="en-us">Firebird Project</title> </cpe-item> <cpe-item name="cpe:/h:firebird_project"> <title xml:lang="en-us">Firebird Project</title> </cpe-item> <cpe-item name="cpe:/o:foundry"> <title xml:lang="en-us">Foundry</title> </cpe-item> <cpe-item name="cpe:/a:foundry"> <title xml:lang="en-us">Foundry</title> </cpe-item> <cpe-item name="cpe:/h:foundry"> <title xml:lang="en-us">Foundry</title> </cpe-item> <cpe-item name="cpe:/o:freebsd"> <title xml:lang="en-us">FreeBSD</title> </cpe-item> <cpe-item name="cpe:/a:freebsd"> <title xml:lang="en-us">FreeBSD</title> </cpe-item> <cpe-item name="cpe:/h:freebsd"> <title xml:lang="en-us">FreeBSD</title> </cpe-item> <cpe-item name="cpe:/o:frontrange"> <title xml:lang="en-us">FrontRange</title> </cpe-item> <cpe-item name="cpe:/a:frontrange"> <title xml:lang="en-us">FrontRange</title> </cpe-item> <cpe-item name="cpe:/h:frontrange"> <title xml:lang="en-us">FrontRange</title> </cpe-item> <cpe-item name="cpe:/o:ge_medical_systems"> <title xml:lang="en-us">GE Medical Systems</title> </cpe-item> <cpe-item name="cpe:/a:ge_medical_systems"> <title xml:lang="en-us">GE Medical Systems</title> </cpe-item> <cpe-item name="cpe:/h:ge_medical_systems"> <title xml:lang="en-us">GE Medical Systems</title> </cpe-item> <cpe-item name="cpe:/o:general_dynamics"> <title xml:lang="en-us">General Dynamics</title> </cpe-item> <cpe-item name="cpe:/a:general_dynamics"> <title xml:lang="en-us">General Dynamics</title> </cpe-item> <cpe-item name="cpe:/h:general_dynamics"> <title xml:lang="en-us">General Dynamics</title> </cpe-item> <cpe-item name="cpe:/o:gentoo"> <title xml:lang="en-us">Gentoo</title> </cpe-item> <cpe-item name="cpe:/a:gentoo"> <title xml:lang="en-us">Gentoo</title> </cpe-item> <cpe-item name="cpe:/h:gentoo"> <title xml:lang="en-us">Gentoo</title> </cpe-item> <cpe-item name="cpe:/o:gnu"> <title xml:lang="en-us">GNU</title> </cpe-item> <cpe-item name="cpe:/a:gnu"> <title xml:lang="en-us">GNU</title> </cpe-item> <cpe-item name="cpe:/h:gnu"> <title xml:lang="en-us">GNU</title> </cpe-item> <cpe-item name="cpe:/o:google"> <title xml:lang="en-us">Google</title> </cpe-item> <cpe-item name="cpe:/a:google"> <title xml:lang="en-us">Google</title> </cpe-item> <cpe-item name="cpe:/h:google"> <title xml:lang="en-us">Google</title> </cpe-item> <cpe-item name="cpe:/o:gradkell_systems"> <title xml:lang="en-us">Gradkell Systems</title> </cpe-item> <cpe-item name="cpe:/a:gradkell_systems"> <title xml:lang="en-us">Gradkell Systems</title> </cpe-item> <cpe-item name="cpe:/h:gradkell_systems"> <title xml:lang="en-us">Gradkell Systems</title> </cpe-item> <cpe-item name="cpe:/o:harris"> <title xml:lang="en-us">Harris</title> </cpe-item> <cpe-item name="cpe:/a:harris"> <title xml:lang="en-us">Harris</title> </cpe-item> <cpe-item name="cpe:/h:harris"> <title xml:lang="en-us">Harris</title> </cpe-item> <cpe-item name="cpe:/o:hp"> <title xml:lang="en-us">HP</title> </cpe-item> <cpe-item name="cpe:/a:hp"> <title xml:lang="en-us">HP</title> </cpe-item> <cpe-item name="cpe:/h:hp"> <title xml:lang="en-us">HP</title> </cpe-item> <cpe-item name="cpe:/o:hummingbird"> <title xml:lang="en-us">Hummingbird</title> </cpe-item> <cpe-item name="cpe:/a:hummingbird"> <title xml:lang="en-us">Hummingbird</title> </cpe-item> <cpe-item name="cpe:/h:hummingbird"> <title xml:lang="en-us">Hummingbird</title> </cpe-item> <cpe-item name="cpe:/o:ibm"> <title xml:lang="en-us">IBM</title> </cpe-item> <cpe-item name="cpe:/a:ibm"> <title xml:lang="en-us">IBM</title> </cpe-item> <cpe-item name="cpe:/h:ibm"> <title xml:lang="en-us">IBM</title> </cpe-item> <cpe-item name="cpe:/o:iiex_engineering"> <title xml:lang="en-us">Ilex Engineering</title> </cpe-item> <cpe-item name="cpe:/a:iiex_engineering"> <title xml:lang="en-us">Ilex Engineering</title> </cpe-item> <cpe-item name="cpe:/h:iiex_engineering"> <title xml:lang="en-us">Ilex Engineering</title> </cpe-item> <cpe-item name="cpe:/o:informatica"> <title xml:lang="en-us">Informatica</title> </cpe-item> <cpe-item name="cpe:/a:informatica"> <title xml:lang="en-us">Informatica</title> </cpe-item> <cpe-item name="cpe:/h:informatica"> <title xml:lang="en-us">Informatica</title> </cpe-item> <cpe-item name="cpe:/o:intel"> <title xml:lang="en-us">Intel</title> </cpe-item> <cpe-item name="cpe:/a:intel"> <title xml:lang="en-us">Intel</title> </cpe-item> <cpe-item name="cpe:/h:intel"> <title xml:lang="en-us">Intel</title> </cpe-item> <cpe-item name="cpe:/o:intergraph"> <title xml:lang="en-us">Intergraph</title> <references> <reference href="http://www.intergraph.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:intergraph"> <title xml:lang="en-us">Intergraph</title> <references> <reference href="http://www.intergraph.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:intergraph"> <title xml:lang="en-us">Intergraph</title> <references> <reference href="http://www.intergraph.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:internet_security_systems"> <title xml:lang="en-us">Internet Security Systems</title> </cpe-item> <cpe-item name="cpe:/a:internet_security_systems"> <title xml:lang="en-us">Internet Security Systems</title> </cpe-item> <cpe-item name="cpe:/h:internet_security_systems"> <title xml:lang="en-us">Internet Security Systems</title> </cpe-item> <cpe-item name="cpe:/o:intervideo"> <title xml:lang="en-us">InterVideo</title> </cpe-item> <cpe-item name="cpe:/a:intervideo"> <title xml:lang="en-us">InterVideo</title> </cpe-item> <cpe-item name="cpe:/h:intervideo"> <title xml:lang="en-us">InterVideo</title> </cpe-item> <cpe-item name="cpe:/o:jffnms"> <title xml:lang="en-us">JFFNMS</title> </cpe-item> <cpe-item name="cpe:/a:jffnms"> <title xml:lang="en-us">JFFNMS</title> </cpe-item> <cpe-item name="cpe:/h:jffnms"> <title xml:lang="en-us">JFFNMS</title> </cpe-item> <cpe-item name="cpe:/o:jolly_giant_software_inc"> <title xml:lang="en-us">Jolly Giant Software Inc.</title> </cpe-item> <cpe-item name="cpe:/a:jolly_giant_software_inc"> <title xml:lang="en-us">Jolly Giant Software Inc.</title> </cpe-item> <cpe-item name="cpe:/h:jolly_giant_software_inc"> <title xml:lang="en-us">Jolly Giant Software Inc.</title> </cpe-item> <cpe-item name="cpe:/o:juniper"> <title xml:lang="en-us">Juniper</title> </cpe-item> <cpe-item name="cpe:/a:juniper"> <title xml:lang="en-us">Juniper</title> </cpe-item> <cpe-item name="cpe:/h:juniper"> <title xml:lang="en-us">Juniper</title> </cpe-item> <cpe-item name="cpe:/o:kiosk_logix"> <title xml:lang="en-us">KIOSK LOGIX</title> </cpe-item> <cpe-item name="cpe:/a:kiosk_logix"> <title xml:lang="en-us">KIOSK LOGIX</title> </cpe-item> <cpe-item name="cpe:/h:kiosk_logix"> <title xml:lang="en-us">KIOSK LOGIX</title> </cpe-item> <cpe-item name="cpe:/o:k-lite"> <title xml:lang="en-us">K-Lite</title> </cpe-item> <cpe-item name="cpe:/a:k-lite"> <title xml:lang="en-us">K-Lite</title> </cpe-item> <cpe-item name="cpe:/h:k-lite"> <title xml:lang="en-us">K-Lite</title> </cpe-item> <cpe-item name="cpe:/o:kodak"> <title xml:lang="en-us">Kodak</title> </cpe-item> <cpe-item name="cpe:/a:kodak"> <title xml:lang="en-us">Kodak</title> </cpe-item> <cpe-item name="cpe:/h:kodak"> <title xml:lang="en-us">Kodak</title> </cpe-item> <cpe-item name="cpe:/o:konica_minolta"> <title xml:lang="en-us">Konica-Minolta</title> </cpe-item> <cpe-item name="cpe:/a:konica_minolta"> <title xml:lang="en-us">Konica-Minolta</title> </cpe-item> <cpe-item name="cpe:/h:konica_minolta"> <title xml:lang="en-us">Konica-Minolta</title> </cpe-item> <cpe-item name="cpe:/o:lancope"> <title xml:lang="en-us">Lancope</title> </cpe-item> <cpe-item name="cpe:/a:lancope"> <title xml:lang="en-us">Lancope</title> </cpe-item> <cpe-item name="cpe:/h:lancope"> <title xml:lang="en-us">Lancope</title> </cpe-item> <cpe-item name="cpe:/o:landesk_software"> <title xml:lang="en-us">LANDesk Software</title> </cpe-item> <cpe-item name="cpe:/a:landesk_software"> <title xml:lang="en-us">LANDesk Software</title> </cpe-item> <cpe-item name="cpe:/h:landesk_software"> <title xml:lang="en-us">LANDesk Software</title> </cpe-item> <cpe-item name="cpe:/o:lanier"> <title xml:lang="en-us">Lanier</title> </cpe-item> <cpe-item name="cpe:/a:lanier"> <title xml:lang="en-us">Lanier</title> </cpe-item> <cpe-item name="cpe:/h:lanier"> <title xml:lang="en-us">Lanier</title> </cpe-item> <cpe-item name="cpe:/o:lexmark"> <title xml:lang="en-us">Lexmark</title> </cpe-item> <cpe-item name="cpe:/a:lexmark"> <title xml:lang="en-us">Lexmark</title> </cpe-item> <cpe-item name="cpe:/h:lexmark"> <title xml:lang="en-us">Lexmark</title> </cpe-item> <cpe-item name="cpe:/o:linksys"> <title xml:lang="en-us">Linksys</title> </cpe-item> <cpe-item name="cpe:/a:linksys"> <title xml:lang="en-us">Linksys</title> </cpe-item> <cpe-item name="cpe:/h:linksys"> <title xml:lang="en-us">Linksys</title> </cpe-item> <cpe-item name="cpe:/o:linux"> <title xml:lang="en-us">Linux</title> </cpe-item> <cpe-item name="cpe:/a:linux"> <title xml:lang="en-us">Linux</title> </cpe-item> <cpe-item name="cpe:/h:linux"> <title xml:lang="en-us">Linux</title> </cpe-item> <cpe-item name="cpe:/o:litronic"> <title xml:lang="en-us">Litronic</title> </cpe-item> <cpe-item name="cpe:/a:litronic"> <title xml:lang="en-us">Litronic</title> </cpe-item> <cpe-item name="cpe:/h:litronic"> <title xml:lang="en-us">Litronic</title> </cpe-item> <cpe-item name="cpe:/o:logitech"> <title xml:lang="en-us">Logitech</title> </cpe-item> <cpe-item name="cpe:/a:logitech"> <title xml:lang="en-us">Logitech</title> </cpe-item> <cpe-item name="cpe:/h:logitech"> <title xml:lang="en-us">Logitech</title> </cpe-item> <cpe-item name="cpe:/o:storagetek"> <title xml:lang="en-us">Storagetek</title> </cpe-item> <cpe-item name="cpe:/a:storagetek"> <title xml:lang="en-us">Storagetek</title> </cpe-item> <cpe-item name="cpe:/h:storagetek"> <title xml:lang="en-us">Storagetek</title> </cpe-item> <cpe-item name="cpe:/o:l-soft"> <title xml:lang="en-us">L-Soft</title> </cpe-item> <cpe-item name="cpe:/a:l-soft"> <title xml:lang="en-us">L-Soft</title> </cpe-item> <cpe-item name="cpe:/h:l-soft"> <title xml:lang="en-us">L-Soft</title> </cpe-item> <cpe-item name="cpe:/o:lstc"> <title xml:lang="en-us">LSTC</title> </cpe-item> <cpe-item name="cpe:/a:lstc"> <title xml:lang="en-us">LSTC</title> </cpe-item> <cpe-item name="cpe:/h:lstc"> <title xml:lang="en-us">LSTC</title> </cpe-item> <cpe-item name="cpe:/o:lucent"> <title xml:lang="en-us">Lucent</title> </cpe-item> <cpe-item name="cpe:/a:lucent"> <title xml:lang="en-us">Lucent</title> </cpe-item> <cpe-item name="cpe:/h:lucent"> <title xml:lang="en-us">Lucent</title> </cpe-item> <cpe-item name="cpe:/o:lund_performance_solutions"> <title xml:lang="en-us">Lund Performance Solutions</title> </cpe-item> <cpe-item name="cpe:/a:lund_performance_solutions"> <title xml:lang="en-us">Lund Performance Solutions</title> </cpe-item> <cpe-item name="cpe:/h:lund_performance_solutions"> <title xml:lang="en-us">Lund Performance Solutions</title> </cpe-item> <cpe-item name="cpe:/o:macromedia"> <title xml:lang="en-us">Macromedia</title> </cpe-item> <cpe-item name="cpe:/a:macromedia"> <title xml:lang="en-us">Macromedia</title> </cpe-item> <cpe-item name="cpe:/h:macromedia"> <title xml:lang="en-us">Macromedia</title> </cpe-item> <cpe-item name="cpe:/o:mandrakesoft"> <title xml:lang="en-us">MandrakeSoft</title> </cpe-item> <cpe-item name="cpe:/a:mandrakesoft"> <title xml:lang="en-us">MandrakeSoft</title> </cpe-item> <cpe-item name="cpe:/h:mandrakesoft"> <title xml:lang="en-us">MandrakeSoft</title> </cpe-item> <cpe-item name="cpe:/o:marconi"> <title xml:lang="en-us">Marconi</title> </cpe-item> <cpe-item name="cpe:/a:marconi"> <title xml:lang="en-us">Marconi</title> </cpe-item> <cpe-item name="cpe:/h:marconi"> <title xml:lang="en-us">Marconi</title> </cpe-item> <cpe-item name="cpe:/o:maximus"> <title xml:lang="en-us">Maximus</title> </cpe-item> <cpe-item name="cpe:/a:maximus"> <title xml:lang="en-us">Maximus</title> </cpe-item> <cpe-item name="cpe:/h:maximus"> <title xml:lang="en-us">Maximus</title> </cpe-item> <cpe-item name="cpe:/o:mcafee"> <title xml:lang="en-us">McAfee</title> </cpe-item> <cpe-item name="cpe:/a:mcafee"> <title xml:lang="en-us">McAfee</title> </cpe-item> <cpe-item name="cpe:/h:mcafee"> <title xml:lang="en-us">McAfee</title> </cpe-item> <cpe-item name="cpe:/o:mcdata"> <title xml:lang="en-us">McDATA</title> </cpe-item> <cpe-item name="cpe:/a:mcdata"> <title xml:lang="en-us">McDATA</title> </cpe-item> <cpe-item name="cpe:/h:mcdata"> <title xml:lang="en-us">McDATA</title> </cpe-item> <cpe-item name="cpe:/o:mcgraw-hill"> <title xml:lang="en-us">McGraw-Hill</title> </cpe-item> <cpe-item name="cpe:/a:mcgraw-hill"> <title xml:lang="en-us">McGraw-Hill</title> </cpe-item> <cpe-item name="cpe:/h:mcgraw-hill"> <title xml:lang="en-us">McGraw-Hill</title> </cpe-item> <cpe-item name="cpe:/o:merant"> <title xml:lang="en-us">Merant</title> </cpe-item> <cpe-item name="cpe:/a:merant"> <title xml:lang="en-us">Merant</title> </cpe-item> <cpe-item name="cpe:/h:merant"> <title xml:lang="en-us">Merant</title> </cpe-item> <cpe-item name="cpe:/o:mercury"> <title xml:lang="en-us">Mercury</title> </cpe-item> <cpe-item name="cpe:/a:mercury"> <title xml:lang="en-us">Mercury</title> </cpe-item> <cpe-item name="cpe:/h:mercury"> <title xml:lang="en-us">Mercury</title> </cpe-item> <cpe-item name="cpe:/o:microsoft"> <title xml:lang="en-us">Microsoft</title> </cpe-item> <cpe-item name="cpe:/a:microsoft"> <title xml:lang="en-us">Microsoft</title> </cpe-item> <cpe-item name="cpe:/h:microsoft"> <title xml:lang="en-us">Microsoft</title> </cpe-item> <cpe-item name="cpe:/o:milan_technology"> <title xml:lang="en-us">Milan Technology</title> </cpe-item> <cpe-item name="cpe:/a:milan_technology"> <title xml:lang="en-us">Milan Technology</title> </cpe-item> <cpe-item name="cpe:/h:milan_technology"> <title xml:lang="en-us">Milan Technology</title> </cpe-item> <cpe-item name="cpe:/o:mit"> <title xml:lang="en-us">MIT</title> </cpe-item> <cpe-item name="cpe:/a:mit"> <title xml:lang="en-us">MIT</title> </cpe-item> <cpe-item name="cpe:/h:mit"> <title xml:lang="en-us">MIT</title> </cpe-item> <cpe-item name="cpe:/o:mozilla"> <title xml:lang="en-us">Mozilla</title> </cpe-item> <cpe-item name="cpe:/a:mozilla"> <title xml:lang="en-us">Mozilla</title> </cpe-item> <cpe-item name="cpe:/h:mozilla"> <title xml:lang="en-us">Mozilla</title> </cpe-item> <cpe-item name="cpe:/o:msc_software"> <title xml:lang="en-us">MSC Software</title> </cpe-item> <cpe-item name="cpe:/a:msc_software"> <title xml:lang="en-us">MSC Software</title> </cpe-item> <cpe-item name="cpe:/h:msc_software"> <title xml:lang="en-us">MSC Software</title> </cpe-item> <cpe-item name="cpe:/o:mysql"> <title xml:lang="en-us">MySQL</title> </cpe-item> <cpe-item name="cpe:/a:mysql"> <title xml:lang="en-us">MySQL</title> </cpe-item> <cpe-item name="cpe:/h:mysql"> <title xml:lang="en-us">MySQL</title> </cpe-item> <cpe-item name="cpe:/o:nec"> <title xml:lang="en-us">NEC</title> </cpe-item> <cpe-item name="cpe:/a:nec"> <title xml:lang="en-us">NEC</title> </cpe-item> <cpe-item name="cpe:/h:nec"> <title xml:lang="en-us">NEC</title> </cpe-item> <cpe-item name="cpe:/o:netapp"> <title xml:lang="en-us">Netapp</title> </cpe-item> <cpe-item name="cpe:/a:netapp"> <title xml:lang="en-us">Netapp</title> </cpe-item> <cpe-item name="cpe:/h:netapp"> <title xml:lang="en-us">Netapp</title> </cpe-item> <cpe-item name="cpe:/o:netbsd"> <title xml:lang="en-us">NetBSD</title> </cpe-item> <cpe-item name="cpe:/a:netbsd"> <title xml:lang="en-us">NetBSD</title> </cpe-item> <cpe-item name="cpe:/h:netbsd"> <title xml:lang="en-us">NetBSD</title> </cpe-item> <cpe-item name="cpe:/o:netgear"> <title xml:lang="en-us">NetGear</title> </cpe-item> <cpe-item name="cpe:/a:netgear"> <title xml:lang="en-us">NetGear</title> </cpe-item> <cpe-item name="cpe:/h:netgear"> <title xml:lang="en-us">NetGear</title> </cpe-item> <cpe-item name="cpe:/o:netopsystem"> <title xml:lang="en-us">Netopsystem</title> </cpe-item> <cpe-item name="cpe:/a:netopsystem"> <title xml:lang="en-us">Netopsystem</title> </cpe-item> <cpe-item name="cpe:/h:netopsystem"> <title xml:lang="en-us">Netopsystem</title> </cpe-item> <cpe-item name="cpe:/o:netscape"> <title xml:lang="en-us">Netscape</title> </cpe-item> <cpe-item name="cpe:/a:netscape"> <title xml:lang="en-us">Netscape</title> </cpe-item> <cpe-item name="cpe:/h:netscape"> <title xml:lang="en-us">Netscape</title> </cpe-item> <cpe-item name="cpe:/o:netscout"> <title xml:lang="en-us">NetScout</title> </cpe-item> <cpe-item name="cpe:/a:netscout"> <title xml:lang="en-us">NetScout</title> </cpe-item> <cpe-item name="cpe:/h:netscout"> <title xml:lang="en-us">NetScout</title> </cpe-item> <cpe-item name="cpe:/o:netstop_pro"> <title xml:lang="en-us">Netstop Pro</title> </cpe-item> <cpe-item name="cpe:/a:netstop_pro"> <title xml:lang="en-us">Netstop Pro</title> </cpe-item> <cpe-item name="cpe:/h:netstop_pro"> <title xml:lang="en-us">Netstop Pro</title> </cpe-item> <cpe-item name="cpe:/o:nfsen"> <title xml:lang="en-us">NFSen</title> </cpe-item> <cpe-item name="cpe:/a:nfsen"> <title xml:lang="en-us">NFSen</title> </cpe-item> <cpe-item name="cpe:/h:nfsen"> <title xml:lang="en-us">NFSen</title> </cpe-item> <cpe-item name="cpe:/o:nokia"> <title xml:lang="en-us">Nokia</title> </cpe-item> <cpe-item name="cpe:/a:nokia"> <title xml:lang="en-us">Nokia</title> </cpe-item> <cpe-item name="cpe:/h:nokia"> <title xml:lang="en-us">Nokia</title> </cpe-item> <cpe-item name="cpe:/o:nortel_alteon"> <title xml:lang="en-us">Nortel Alteon</title> </cpe-item> <cpe-item name="cpe:/a:nortel_alteon"> <title xml:lang="en-us">Nortel Alteon</title> </cpe-item> <cpe-item name="cpe:/h:nortel_alteon"> <title xml:lang="en-us">Nortel Alteon</title> </cpe-item> <cpe-item name="cpe:/o:nortel_networks"> <title xml:lang="en-us">Nortel Networks</title> </cpe-item> <cpe-item name="cpe:/a:nortel_networks"> <title xml:lang="en-us">Nortel Networks</title> </cpe-item> <cpe-item name="cpe:/h:nortel_networks"> <title xml:lang="en-us">Nortel Networks</title> </cpe-item> <cpe-item name="cpe:/o:novell"> <title xml:lang="en-us">Novell</title> </cpe-item> <cpe-item name="cpe:/a:novell"> <title xml:lang="en-us">Novell</title> </cpe-item> <cpe-item name="cpe:/h:novell"> <title xml:lang="en-us">Novell</title> </cpe-item> <cpe-item name="cpe:/o:nt_cadcam"> <title xml:lang="en-us">NT Cadcam</title> </cpe-item> <cpe-item name="cpe:/a:nt_cadcam"> <title xml:lang="en-us">NT Cadcam</title> </cpe-item> <cpe-item name="cpe:/h:nt_cadcam"> <title xml:lang="en-us">NT Cadcam</title> </cpe-item> <cpe-item name="cpe:/o:okidata"> <title xml:lang="en-us">Okidata</title> </cpe-item> <cpe-item name="cpe:/a:okidata"> <title xml:lang="en-us">Okidata</title> </cpe-item> <cpe-item name="cpe:/h:okidata"> <title xml:lang="en-us">Okidata</title> </cpe-item> <cpe-item name="cpe:/o:open_source"> <title xml:lang="en-us">OPEN SOURCE</title> </cpe-item> <cpe-item name="cpe:/a:open_source"> <title xml:lang="en-us">OPEN SOURCE</title> </cpe-item> <cpe-item name="cpe:/h:open_source"> <title xml:lang="en-us">OPEN SOURCE</title> </cpe-item> <cpe-item name="cpe:/o:openbsd"> <title xml:lang="en-us">OpenBSD</title> </cpe-item> <cpe-item name="cpe:/a:openbsd"> <title xml:lang="en-us">OpenBSD</title> </cpe-item> <cpe-item name="cpe:/h:openbsd"> <title xml:lang="en-us">OpenBSD</title> </cpe-item> <cpe-item name="cpe:/o:openpkg"> <title xml:lang="en-us">OpenPKG</title> </cpe-item> <cpe-item name="cpe:/a:openpkg"> <title xml:lang="en-us">OpenPKG</title> </cpe-item> <cpe-item name="cpe:/h:openpkg"> <title xml:lang="en-us">OpenPKG</title> </cpe-item> <cpe-item name="cpe:/o:openssh"> <title xml:lang="en-us">OpenSSH</title> </cpe-item> <cpe-item name="cpe:/a:openssh"> <title xml:lang="en-us">OpenSSH</title> </cpe-item> <cpe-item name="cpe:/h:openssh"> <title xml:lang="en-us">OpenSSH</title> </cpe-item> <cpe-item name="cpe:/o:openssl_project"> <title xml:lang="en-us">OpenSSL Project</title> </cpe-item> <cpe-item name="cpe:/a:openssl_project"> <title xml:lang="en-us">OpenSSL Project</title> </cpe-item> <cpe-item name="cpe:/h:openssl_project"> <title xml:lang="en-us">OpenSSL Project</title> </cpe-item> <cpe-item name="cpe:/o:oracle"> <title xml:lang="en-us">Oracle</title> </cpe-item> <cpe-item name="cpe:/a:oracle"> <title xml:lang="en-us">Oracle</title> </cpe-item> <cpe-item name="cpe:/h:oracle"> <title xml:lang="en-us">Oracle</title> </cpe-item> <cpe-item name="cpe:/o:panasonic"> <title xml:lang="en-us">Panasonic</title> </cpe-item> <cpe-item name="cpe:/a:panasonic"> <title xml:lang="en-us">Panasonic</title> </cpe-item> <cpe-item name="cpe:/h:panasonic"> <title xml:lang="en-us">Panasonic</title> </cpe-item> <cpe-item name="cpe:/o:patchlink_corporation"> <title xml:lang="en-us">PatchLink Corporation</title> </cpe-item> <cpe-item name="cpe:/a:patchlink_corporation"> <title xml:lang="en-us">PatchLink Corporation</title> </cpe-item> <cpe-item name="cpe:/h:patchlink_corporation"> <title xml:lang="en-us">PatchLink Corporation</title> </cpe-item> <cpe-item name="cpe:/o:peribit"> <title xml:lang="en-us">Peribit</title> </cpe-item> <cpe-item name="cpe:/a:peribit"> <title xml:lang="en-us">Peribit</title> </cpe-item> <cpe-item name="cpe:/h:peribit"> <title xml:lang="en-us">Peribit</title> </cpe-item> <cpe-item name="cpe:/o:perle_systems"> <title xml:lang="en-us">Perle Systems</title> </cpe-item> <cpe-item name="cpe:/a:perle_systems"> <title xml:lang="en-us">Perle Systems</title> </cpe-item> <cpe-item name="cpe:/h:perle_systems"> <title xml:lang="en-us">Perle Systems</title> </cpe-item> <cpe-item name="cpe:/o:persits_software"> <title xml:lang="en-us">Persits Software</title> </cpe-item> <cpe-item name="cpe:/a:persits_software"> <title xml:lang="en-us">Persits Software</title> </cpe-item> <cpe-item name="cpe:/h:persits_software"> <title xml:lang="en-us">Persits Software</title> </cpe-item> <cpe-item name="cpe:/o:pgp"> <title xml:lang="en-us">PGP</title> </cpe-item> <cpe-item name="cpe:/a:pgp"> <title xml:lang="en-us">PGP</title> </cpe-item> <cpe-item name="cpe:/h:pgp"> <title xml:lang="en-us">PGP</title> </cpe-item> <cpe-item name="cpe:/o:php"> <title xml:lang="en-us">PHP</title> </cpe-item> <cpe-item name="cpe:/a:php"> <title xml:lang="en-us">PHP</title> </cpe-item> <cpe-item name="cpe:/h:php"> <title xml:lang="en-us">PHP</title> </cpe-item> <cpe-item name="cpe:/o:pkware_inc"> <title xml:lang="en-us">PKWare Inc.</title> </cpe-item> <cpe-item name="cpe:/a:pkware_inc"> <title xml:lang="en-us">PKWare Inc.</title> </cpe-item> <cpe-item name="cpe:/h:pkware_inc"> <title xml:lang="en-us">PKWare Inc.</title> </cpe-item> <cpe-item name="cpe:/o:polycom"> <title xml:lang="en-us">Polycom</title> </cpe-item> <cpe-item name="cpe:/a:polycom"> <title xml:lang="en-us">Polycom</title> </cpe-item> <cpe-item name="cpe:/h:polycom"> <title xml:lang="en-us">Polycom</title> </cpe-item> <cpe-item name="cpe:/o:primopdf"> <title xml:lang="en-us">PrimoPDF</title> </cpe-item> <cpe-item name="cpe:/a:primopdf"> <title xml:lang="en-us">PrimoPDF</title> </cpe-item> <cpe-item name="cpe:/h:primopdf"> <title xml:lang="en-us">PrimoPDF</title> </cpe-item> <cpe-item name="cpe:/o:progress_software_corp"> <title xml:lang="en-us">Progress Software Corp</title> </cpe-item> <cpe-item name="cpe:/a:progress_software_corp"> <title xml:lang="en-us">Progress Software Corp</title> </cpe-item> <cpe-item name="cpe:/h:progress_software_corp"> <title xml:lang="en-us">Progress Software Corp</title> </cpe-item> <cpe-item name="cpe:/o:prohibited_software"> <title xml:lang="en-us">Prohibited Software</title> </cpe-item> <cpe-item name="cpe:/a:prohibited_software"> <title xml:lang="en-us">Prohibited Software</title> </cpe-item> <cpe-item name="cpe:/h:prohibited_software"> <title xml:lang="en-us">Prohibited Software</title> </cpe-item> <cpe-item name="cpe:/o:pureedge_solutions"> <title xml:lang="en-us">PureEdge Solutions</title> </cpe-item> <cpe-item name="cpe:/a:pureedge_solutions"> <title xml:lang="en-us">PureEdge Solutions</title> </cpe-item> <cpe-item name="cpe:/h:pureedge_solutions"> <title xml:lang="en-us">PureEdge Solutions</title> </cpe-item> <cpe-item name="cpe:/o:qlogic"> <title xml:lang="en-us">Qlogic</title> </cpe-item> <cpe-item name="cpe:/a:qlogic"> <title xml:lang="en-us">Qlogic</title> </cpe-item> <cpe-item name="cpe:/h:qlogic"> <title xml:lang="en-us">Qlogic</title> </cpe-item> <cpe-item name="cpe:/o:quantum"> <title xml:lang="en-us">Quantum</title> </cpe-item> <cpe-item name="cpe:/a:quantum"> <title xml:lang="en-us">Quantum</title> </cpe-item> <cpe-item name="cpe:/h:quantum"> <title xml:lang="en-us">Quantum</title> </cpe-item> <cpe-item name="cpe:/o:radvision"> <title xml:lang="en-us">RadVision</title> </cpe-item> <cpe-item name="cpe:/a:radvision"> <title xml:lang="en-us">RadVision</title> </cpe-item> <cpe-item name="cpe:/h:radvision"> <title xml:lang="en-us">RadVision</title> </cpe-item> <cpe-item name="cpe:/o:radware"> <title xml:lang="en-us">RadWare</title> </cpe-item> <cpe-item name="cpe:/a:radware"> <title xml:lang="en-us">RadWare</title> </cpe-item> <cpe-item name="cpe:/h:radware"> <title xml:lang="en-us">RadWare</title> </cpe-item> <cpe-item name="cpe:/o:real"> <title xml:lang="en-us">Real</title> </cpe-item> <cpe-item name="cpe:/a:real"> <title xml:lang="en-us">Real</title> </cpe-item> <cpe-item name="cpe:/h:real"> <title xml:lang="en-us">Real</title> </cpe-item> <cpe-item name="cpe:/o:redhat"> <title xml:lang="en-us">redhat</title> </cpe-item> <cpe-item name="cpe:/a:redhat"> <title xml:lang="en-us">redhat</title> </cpe-item> <cpe-item name="cpe:/h:redhat"> <title xml:lang="en-us">redhat</title> </cpe-item> <cpe-item name="cpe:/o:ricoh"> <title xml:lang="en-us">RICOH</title> </cpe-item> <cpe-item name="cpe:/a:ricoh"> <title xml:lang="en-us">RICOH</title> </cpe-item> <cpe-item name="cpe:/h:ricoh"> <title xml:lang="en-us">RICOH</title> </cpe-item> <cpe-item name="cpe:/o:roam_about"> <title xml:lang="en-us">Roam About</title> <references> <reference href="http://secure.enterasys.com/download/download.cgi?lib=roam"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:roam_about"> <title xml:lang="en-us">Roam About</title> <references> <reference href="http://secure.enterasys.com/download/download.cgi?lib=roam"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:roam_about"> <title xml:lang="en-us">Roam About</title> <references> <reference href="http://secure.enterasys.com/download/download.cgi?lib=roam"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:roxio"> <title xml:lang="en-us">Roxio</title> </cpe-item> <cpe-item name="cpe:/a:roxio"> <title xml:lang="en-us">Roxio</title> </cpe-item> <cpe-item name="cpe:/h:roxio"> <title xml:lang="en-us">Roxio</title> </cpe-item> <cpe-item name="cpe:/o:rsa"> <title xml:lang="en-us">RSA</title> </cpe-item> <cpe-item name="cpe:/a:rsa"> <title xml:lang="en-us">RSA</title> </cpe-item> <cpe-item name="cpe:/h:rsa"> <title xml:lang="en-us">RSA</title> </cpe-item> <cpe-item name="cpe:/o:safer_networking_limited"> <title xml:lang="en-us">Safer Networking Limited</title> </cpe-item> <cpe-item name="cpe:/a:safer_networking_limited"> <title xml:lang="en-us">Safer Networking Limited</title> </cpe-item> <cpe-item name="cpe:/h:safer_networking_limited"> <title xml:lang="en-us">Safer Networking Limited</title> </cpe-item> <cpe-item name="cpe:/o:samba"> <title xml:lang="en-us">Samba</title> </cpe-item> <cpe-item name="cpe:/a:samba"> <title xml:lang="en-us">Samba</title> </cpe-item> <cpe-item name="cpe:/h:samba"> <title xml:lang="en-us">Samba</title> </cpe-item> <cpe-item name="cpe:/o:scm_microsystems"> <title xml:lang="en-us">SCM Microsystems</title> </cpe-item> <cpe-item name="cpe:/a:scm_microsystems"> <title xml:lang="en-us">SCM Microsystems</title> </cpe-item> <cpe-item name="cpe:/h:scm_microsystems"> <title xml:lang="en-us">SCM Microsystems</title> </cpe-item> <cpe-item name="cpe:/o:screen_savers"> <title xml:lang="en-us">Screen Savers</title> </cpe-item> <cpe-item name="cpe:/a:screen_savers"> <title xml:lang="en-us">Screen Savers</title> </cpe-item> <cpe-item name="cpe:/h:screen_savers"> <title xml:lang="en-us">Screen Savers</title> </cpe-item> <cpe-item name="cpe:/o:secunia"> <title xml:lang="en-us">Secunia</title> </cpe-item> <cpe-item name="cpe:/a:secunia"> <title xml:lang="en-us">Secunia</title> </cpe-item> <cpe-item name="cpe:/h:secunia"> <title xml:lang="en-us">Secunia</title> </cpe-item> <cpe-item name="cpe:/o:secure_computing"> <title xml:lang="en-us">Secure Computing</title> </cpe-item> <cpe-item name="cpe:/a:secure_computing"> <title xml:lang="en-us">Secure Computing</title> </cpe-item> <cpe-item name="cpe:/h:secure_computing"> <title xml:lang="en-us">Secure Computing</title> </cpe-item> <cpe-item name="cpe:/o:sendmail"> <title xml:lang="en-us">Sendmail</title> </cpe-item> <cpe-item name="cpe:/a:sendmail"> <title xml:lang="en-us">Sendmail</title> </cpe-item> <cpe-item name="cpe:/h:sendmail"> <title xml:lang="en-us">Sendmail</title> </cpe-item> <cpe-item name="cpe:/o:sgi"> <title xml:lang="en-us">SGI</title> </cpe-item> <cpe-item name="cpe:/a:sgi"> <title xml:lang="en-us">SGI</title> </cpe-item> <cpe-item name="cpe:/h:sgi"> <title xml:lang="en-us">SGI</title> </cpe-item> <cpe-item name="cpe:/o:sharp"> <title xml:lang="en-us">Sharp</title> </cpe-item> <cpe-item name="cpe:/a:sharp"> <title xml:lang="en-us">Sharp</title> </cpe-item> <cpe-item name="cpe:/h:sharp"> <title xml:lang="en-us">Sharp</title> </cpe-item> <cpe-item name="cpe:/o:shoretel"> <title xml:lang="en-us">ShoreTel</title> <references> <reference href="http://www.shoretel.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:shoretel"> <title xml:lang="en-us">ShoreTel</title> <references> <reference href="http://www.shoretel.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:shoretel"> <title xml:lang="en-us">ShoreTel</title> <references> <reference href="http://www.shoretel.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:siemens"> <title xml:lang="en-us">Siemens</title> </cpe-item> <cpe-item name="cpe:/a:siemens"> <title xml:lang="en-us">Siemens</title> </cpe-item> <cpe-item name="cpe:/h:siemens"> <title xml:lang="en-us">Siemens</title> </cpe-item> <cpe-item name="cpe:/o:silanis_technology_incorporated"> <title xml:lang="en-us">Silanis Technology Incorporated</title> <references> <reference href="http://www.silanis.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:silanis_technology_incorporated"> <title xml:lang="en-us">Silanis Technology Incorporated</title> <references> <reference href="http://www.silanis.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:silanis_technology_incorporated"> <title xml:lang="en-us">Silanis Technology Incorporated</title> <references> <reference href="http://www.silanis.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:sitara"> <title xml:lang="en-us">Sitara</title> <references> <reference href="http://www.sitaranetworks.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:sitara"> <title xml:lang="en-us">Sitara</title> <references> <reference href="http://www.sitaranetworks.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:sitara"> <title xml:lang="en-us">Sitara</title> <references> <reference href="http://www.sitaranetworks.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:snapappliance"> <title xml:lang="en-us">SnapAppliance</title> <references> <reference href="http://www.snapappliance.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:snapappliance"> <title xml:lang="en-us">SnapAppliance</title> <references> <reference href="http://www.snapappliance.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:snapappliance"> <title xml:lang="en-us">SnapAppliance</title> <references> <reference href="http://www.snapappliance.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:snort"> <title xml:lang="en-us">Snort</title> </cpe-item> <cpe-item name="cpe:/a:snort"> <title xml:lang="en-us">Snort</title> </cpe-item> <cpe-item name="cpe:/h:snort"> <title xml:lang="en-us">Snort</title> </cpe-item> <cpe-item name="cpe:/o:solarwinds"> <title xml:lang="en-us">SolarWinds</title> </cpe-item> <cpe-item name="cpe:/a:solarwinds"> <title xml:lang="en-us">SolarWinds</title> </cpe-item> <cpe-item name="cpe:/h:solarwinds"> <title xml:lang="en-us">SolarWinds</title> </cpe-item> <cpe-item name="cpe:/o:sony"> <title xml:lang="en-us">Sony</title> </cpe-item> <cpe-item name="cpe:/a:sony"> <title xml:lang="en-us">Sony</title> </cpe-item> <cpe-item name="cpe:/h:sony"> <title xml:lang="en-us">Sony</title> </cpe-item> <cpe-item name="cpe:/o:spectra_logic"> <title xml:lang="en-us">Spectra Logic</title> <references> <reference href="http://www.spectralogic.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:spectra_logic"> <title xml:lang="en-us">Spectra Logic</title> <references> <reference href="http://www.spectralogic.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:spectra_logic"> <title xml:lang="en-us">Spectra Logic</title> <references> <reference href="http://www.spectralogic.com"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:splinterware_software_solutions"> <title xml:lang="en-us">Splinterware Software Solutions</title> <references> <reference href="http://www.splinterware.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/a:splinterware_software_solutions"> <title xml:lang="en-us">Splinterware Software Solutions</title> <references> <reference href="http://www.splinterware.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/h:splinterware_software_solutions"> <title xml:lang="en-us">Splinterware Software Solutions</title> <references> <reference href="http://www.splinterware.com/"></reference> </references> </cpe-item> <cpe-item name="cpe:/o:spss"> <title xml:lang="en-us">SPSS</title> </cpe-item> <cpe-item name="cpe:/a:spss"> <title xml:lang="en-us">SPSS</title> </cpe-item> <cpe-item name="cpe:/h:spss"> <title xml:lang="en-us">SPSS</title> </cpe-item> <cpe-item name="cpe:/o:ssh_communications_security"> <title xml:lang="en-us">SSH Communications Security</title> </cpe-item> <cpe-item name="cpe:/a:ssh_communications_security"> <title xml:lang="en-us">SSH Communications Security</title> </cpe-item> <cpe-item name="cpe:/h:ssh_communications_security"> <title xml:lang="en-us">SSH Communications Security</title> </cpe-item> <cpe-item name="cpe:/o:st_bernard"> <title xml:lang="en-us">St Bernard</title> </cpe-item> <cpe-item name="cpe:/a:st_bernard"> <title xml:lang="en-us">St Bernard</title> </cpe-item> <cpe-item name="cpe:/h:st_bernard"> <title xml:lang="en-us">St Bernard</title> </cpe-item> <cpe-item name="cpe:/o:starnet_communications"> <title xml:lang="en-us">StarNet Communications</title> </cpe-item> <cpe-item name="cpe:/a:starnet_communications"> <title xml:lang="en-us">StarNet Communications</title> </cpe-item> <cpe-item name="cpe:/h:starnet_communications"> <title xml:lang="en-us">StarNet Communications</title> </cpe-item> <cpe-item name="cpe:/o:storage_engine"> <title xml:lang="en-us">Storage Engine</title> </cpe-item> <cpe-item name="cpe:/a:storage_engine"> <title xml:lang="en-us">Storage Engine</title> </cpe-item> <cpe-item name="cpe:/h:storage_engine"> <title xml:lang="en-us">Storage Engine</title> </cpe-item> <cpe-item name="cpe:/o:sun"> <title xml:lang="en-us">Sun</title> </cpe-item> <cpe-item name="cpe:/a:sun"> <title xml:lang="en-us">Sun</title> </cpe-item> <cpe-item name="cpe:/h:sun"> <title xml:lang="en-us">Sun</title> </cpe-item> <cpe-item name="cpe:/o:surfcontrol"> <title xml:lang="en-us">SurfControl</title> </cpe-item> <cpe-item name="cpe:/a:surfcontrol"> <title xml:lang="en-us">SurfControl</title> </cpe-item> <cpe-item name="cpe:/h:surfcontrol"> <title xml:lang="en-us">SurfControl</title> </cpe-item> <cpe-item name="cpe:/o:suse"> <title xml:lang="en-us">SuSE</title> </cpe-item> <cpe-item name="cpe:/a:suse"> <title xml:lang="en-us">SuSE</title> </cpe-item> <cpe-item name="cpe:/h:suse"> <title xml:lang="en-us">SuSE</title> </cpe-item> <cpe-item name="cpe:/o:sybari_software"> <title xml:lang="en-us">Sybari Software</title> </cpe-item> <cpe-item name="cpe:/a:sybari_software"> <title xml:lang="en-us">Sybari Software</title> </cpe-item> <cpe-item name="cpe:/h:sybari_software"> <title xml:lang="en-us">Sybari Software</title> </cpe-item> <cpe-item name="cpe:/o:sybase"> <title xml:lang="en-us">Sybase</title> </cpe-item> <cpe-item name="cpe:/a:sybase"> <title xml:lang="en-us">Sybase</title> </cpe-item> <cpe-item name="cpe:/h:sybase"> <title xml:lang="en-us">Sybase</title> </cpe-item> <cpe-item name="cpe:/o:symantec"> <title xml:lang="en-us">Symantec</title> </cpe-item> <cpe-item name="cpe:/a:symantec"> <title xml:lang="en-us">Symantec</title> </cpe-item> <cpe-item name="cpe:/h:symantec"> <title xml:lang="en-us">Symantec</title> </cpe-item> <cpe-item name="cpe:/o:symmetricom"> <title xml:lang="en-us">Symmetricom</title> </cpe-item> <cpe-item name="cpe:/a:symmetricom"> <title xml:lang="en-us">Symmetricom</title> </cpe-item> <cpe-item name="cpe:/h:symmetricom"> <title xml:lang="en-us">Symmetricom</title> </cpe-item> <cpe-item name="cpe:/o:syncsort"> <title xml:lang="en-us">Syncsort</title> </cpe-item> <cpe-item name="cpe:/a:syncsort"> <title xml:lang="en-us">Syncsort</title> </cpe-item> <cpe-item name="cpe:/h:syncsort"> <title xml:lang="en-us">Syncsort</title> </cpe-item> <cpe-item name="cpe:/o:szaszvari_peter"> <title xml:lang="en-us">Szaszvari, Peter</title> </cpe-item> <cpe-item name="cpe:/a:szaszvari_peter"> <title xml:lang="en-us">Szaszvari, Peter</title> </cpe-item> <cpe-item name="cpe:/h:szaszvari_peter"> <title xml:lang="en-us">Szaszvari, Peter</title> </cpe-item> <cpe-item name="cpe:/o:tamosoft"> <title xml:lang="en-us">TamoSoft</title> </cpe-item> <cpe-item name="cpe:/a:tamosoft"> <title xml:lang="en-us">TamoSoft</title> </cpe-item> <cpe-item name="cpe:/h:tamosoft"> <title xml:lang="en-us">TamoSoft</title> </cpe-item> <cpe-item name="cpe:/o:tec-it"> <title xml:lang="en-us">TEC-IT</title> </cpe-item> <cpe-item name="cpe:/a:tec-it"> <title xml:lang="en-us">TEC-IT</title> </cpe-item> <cpe-item name="cpe:/h:tec-it"> <title xml:lang="en-us">TEC-IT</title> </cpe-item> <cpe-item name="cpe:/o:tektronix"> <title xml:lang="en-us">Tektronix</title> </cpe-item> <cpe-item name="cpe:/a:tektronix"> <title xml:lang="en-us">Tektronix</title> </cpe-item> <cpe-item name="cpe:/h:tektronix"> <title xml:lang="en-us">Tektronix</title> </cpe-item> <cpe-item name="cpe:/o:telelogic"> <title xml:lang="en-us">Telelogic</title> </cpe-item> <cpe-item name="cpe:/a:telelogic"> <title xml:lang="en-us">Telelogic</title> </cpe-item> <cpe-item name="cpe:/h:telelogic"> <title xml:lang="en-us">Telelogic</title> </cpe-item> <cpe-item name="cpe:/o:telos"> <title xml:lang="en-us">Telos</title> </cpe-item> <cpe-item name="cpe:/a:telos"> <title xml:lang="en-us">Telos</title> </cpe-item> <cpe-item name="cpe:/h:telos"> <title xml:lang="en-us">Telos</title> </cpe-item> <cpe-item name="cpe:/o:teltronics"> <title xml:lang="en-us">Teltronics</title> </cpe-item> <cpe-item name="cpe:/a:teltronics"> <title xml:lang="en-us">Teltronics</title> </cpe-item> <cpe-item name="cpe:/h:teltronics"> <title xml:lang="en-us">Teltronics</title> </cpe-item> <cpe-item name="cpe:/o:cis"> <title xml:lang="en-us">CIS</title> </cpe-item> <cpe-item name="cpe:/a:cis"> <title xml:lang="en-us">CIS</title> </cpe-item> <cpe-item name="cpe:/h:cis"> <title xml:lang="en-us">CIS</title> </cpe-item> <cpe-item name="cpe:/o:thompson_course_technology"> <title xml:lang="en-us">Thompson Course Technology</title> </cpe-item> <cpe-item name="cpe:/a:thompson_course_technology"> <title xml:lang="en-us">Thompson Course Technology</title> </cpe-item> <cpe-item name="cpe:/h:thompson_course_technology"> <title xml:lang="en-us">Thompson Course Technology</title> </cpe-item> <cpe-item name="cpe:/o:tipping_point"> <title xml:lang="en-us">Tipping Point</title> </cpe-item> <cpe-item name="cpe:/a:tipping_point"> <title xml:lang="en-us">Tipping Point</title> </cpe-item> <cpe-item name="cpe:/h:tipping_point"> <title xml:lang="en-us">Tipping Point</title> </cpe-item> <cpe-item name="cpe:/o:tivoli"> <title xml:lang="en-us">Tivoli</title> </cpe-item> <cpe-item name="cpe:/a:tivoli"> <title xml:lang="en-us">Tivoli</title> </cpe-item> <cpe-item name="cpe:/h:tivoli"> <title xml:lang="en-us">Tivoli</title> </cpe-item> <cpe-item name="cpe:/o:toshiba"> <title xml:lang="en-us">Toshiba</title> </cpe-item> <cpe-item name="cpe:/a:toshiba"> <title xml:lang="en-us">Toshiba</title> </cpe-item> <cpe-item name="cpe:/h:toshiba"> <title xml:lang="en-us">Toshiba</title> </cpe-item> <cpe-item name="cpe:/o:trustix"> <title xml:lang="en-us">Trustix</title> </cpe-item> <cpe-item name="cpe:/a:trustix"> <title xml:lang="en-us">Trustix</title> </cpe-item> <cpe-item name="cpe:/h:trustix"> <title xml:lang="en-us">Trustix</title> </cpe-item> <cpe-item name="cpe:/o:tumbleweed"> <title xml:lang="en-us">Tumbleweed</title> </cpe-item> <cpe-item name="cpe:/a:tumbleweed"> <title xml:lang="en-us">Tumbleweed</title> </cpe-item> <cpe-item name="cpe:/h:tumbleweed"> <title xml:lang="en-us">Tumbleweed</title> </cpe-item> <cpe-item name="cpe:/o:veritas"> <title xml:lang="en-us">Veritas</title> </cpe-item> <cpe-item name="cpe:/a:veritas"> <title xml:lang="en-us">Veritas</title> </cpe-item> <cpe-item name="cpe:/h:veritas"> <title xml:lang="en-us">Veritas</title> </cpe-item> <cpe-item name="cpe:/o:vermont_systems"> <title xml:lang="en-us">Vermont Systems</title> </cpe-item> <cpe-item name="cpe:/a:vermont_systems"> <title xml:lang="en-us">Vermont Systems</title> </cpe-item> <cpe-item name="cpe:/h:vermont_systems"> <title xml:lang="en-us">Vermont Systems</title> </cpe-item> <cpe-item name="cpe:/o:virtual_network_computing"> <title xml:lang="en-us">Virtual Network Computing</title> </cpe-item> <cpe-item name="cpe:/a:virtual_network_computing"> <title xml:lang="en-us">Virtual Network Computing</title> </cpe-item> <cpe-item name="cpe:/h:virtual_network_computing"> <title xml:lang="en-us">Virtual Network Computing</title> </cpe-item> <cpe-item name="cpe:/o:vms"> <title xml:lang="en-us">VMS</title> </cpe-item> <cpe-item name="cpe:/a:vms"> <title xml:lang="en-us">VMS</title> </cpe-item> <cpe-item name="cpe:/h:vms"> <title xml:lang="en-us">VMS</title> </cpe-item> <cpe-item name="cpe:/o:vmware"> <title xml:lang="en-us">VMWare</title> </cpe-item> <cpe-item name="cpe:/a:vmware"> <title xml:lang="en-us">VMWare</title> </cpe-item> <cpe-item name="cpe:/h:vmware"> <title xml:lang="en-us">VMWare</title> </cpe-item> <cpe-item name="cpe:/o:wallpaper"> <title xml:lang="en-us">Wallpaper</title> </cpe-item> <cpe-item name="cpe:/a:wallpaper"> <title xml:lang="en-us">Wallpaper</title> </cpe-item> <cpe-item name="cpe:/h:wallpaper"> <title xml:lang="en-us">Wallpaper</title> </cpe-item> <cpe-item name="cpe:/o:wind_river_systems"> <title xml:lang="en-us">Wind River Systems</title> </cpe-item> <cpe-item name="cpe:/a:wind_river_systems"> <title xml:lang="en-us">Wind River Systems</title> </cpe-item> <cpe-item name="cpe:/h:wind_river_systems"> <title xml:lang="en-us">Wind River Systems</title> </cpe-item> <cpe-item name="cpe:/o:winzip"> <title xml:lang="en-us">WinZip</title> </cpe-item> <cpe-item name="cpe:/a:winzip"> <title xml:lang="en-us">WinZip</title> </cpe-item> <cpe-item name="cpe:/h:winzip"> <title xml:lang="en-us">WinZip</title> </cpe-item> <cpe-item name="cpe:/o:xerox"> <title xml:lang="en-us">Xerox</title> </cpe-item> <cpe-item name="cpe:/a:xerox"> <title xml:lang="en-us">Xerox</title> </cpe-item> <cpe-item name="cpe:/h:xerox"> <title xml:lang="en-us">Xerox</title> </cpe-item> <cpe-item name="cpe:/o:xyplex"> <title xml:lang="en-us">Xyplex</title> </cpe-item> <cpe-item name="cpe:/a:xyplex"> <title xml:lang="en-us">Xyplex</title> </cpe-item> <cpe-item name="cpe:/h:xyplex"> <title xml:lang="en-us">Xyplex</title> </cpe-item> <cpe-item name="cpe:/o:yahoo"> <title xml:lang="en-us">Yahoo</title> </cpe-item> <cpe-item name="cpe:/a:yahoo"> <title xml:lang="en-us">Yahoo</title> </cpe-item> <cpe-item name="cpe:/h:yahoo"> <title xml:lang="en-us">Yahoo</title> </cpe-item> <cpe-item name="cpe:/o:ykoon"> <title xml:lang="en-us">Ykoon</title> </cpe-item> <cpe-item name="cpe:/a:ykoon"> <title xml:lang="en-us">Ykoon</title> </cpe-item> <cpe-item name="cpe:/h:ykoon"> <title xml:lang="en-us">Ykoon</title> </cpe-item> <cpe-item name="cpe:/o:zone_labs"> <title xml:lang="en-us">Zone Labs</title> </cpe-item> <cpe-item name="cpe:/a:zone_labs"> <title xml:lang="en-us">Zone Labs</title> </cpe-item> <cpe-item name="cpe:/h:zone_labs"> <title xml:lang="en-us">Zone Labs</title> </cpe-item> </cpe-list> |
||||||||||||||||
Andrew Buttner
|
>I think we should discuss the role and requirement for the
>part-type component in the version 3.x CPE specification. This would be a very beneficial discussion. What are the issues with the way CPE currently uses this type of information? What would you like to see changed? Thanks Drew |
||||||||||||||||
|
Andrew Buttner
|
In reply to this post
by Wolfkiel, Joseph
>To help with the expansion of the CPE dictionary, I'm
>submitting the CPEs for vendors in the US Army Asset Database. Thank you! I will make sure these get added to the Official Dictionary as soon as possible. I know we have updates to the dictionary that should be up on the site this week. >Please let me know if we need to make any changes in format. Format looks good. I have no comments associated with the CPE Names themselves. One point that I will bring up is that in general, it looks like the titles are all just copies of the text in the vendor component. This is fine for now for all the names that don't already exist (better to have something than nothing at all, right?), but for some of the names (Microsoft, Red Hat, etc.), titles already exist in the dictionary with different titles. I know the Red Hat entries were vetted by Red Hat and I would recommend that we stick with their version. Another note related to the titles ... they are meant to be a human readable representation of what platform type the CPE Name represents. For the names you have submitted (general vendor names) these platform types are representative of a family of applications or os's or hardware. So I would expect the titles to be modified in the future to something like: cpe:/o:redhat The Red Hat Family of Operating Systems If others agree with this, it would be pretty easy to script this change into this submission. If I hear demand for this, I can take care of it. thoughts? >I would also like to know how I can track the progress of >submitted CPEs as they are validated, added to the official >CPE dictionary, then indexed with their respective CVEs. Unfortunately, right now there is no way to track this. We would need to implement some form of a submission tool that stored all submissions along with a status flag. This capability currently does not exist. I do agree that this would be a very useful feature. >I'll also point out that the current namePattern format >precludes us from just submitting a vendor name since the >part-type component is mandatory. To get a vendor into the >system, we have to create a cpe for each part-type that any >given manufacturer may produce. In the attached list, each >vendor is submitted as a producer of hardware, operating >systems, and applications. The updated namePattern in Version 2.1 fixes this I think. This was an error in the 2.0 namePattern as all the components were supposed to be optional. Does this fix change your need relative to this submission? Would you rather see names like: cpe:/:redhat The Red Hat family of Platforms I will let everyone know when the Official CPE Dictionary gets updated. Thanks Drew |
||||||||||||||||
|
Wolfkiel, Joseph
|
In reply to this post
by Wolfkiel, Joseph
One point that I will bring up is that in general, it looks like the titles
are all just copies of the text in the vendor component. This is fine for now for all the names that don't already exist (better to have something than nothing at all, right?), but for some of the names (Microsoft, Red Hat, etc.), titles already exist in the dictionary with different titles. I know the Red Hat entries were vetted by Red Hat and I would recommend that we stick with their version. Another note related to the titles ... they are meant to be a human readable representation of what platform type the CPE Name represents. For the names you have submitted (general vendor names) these platform types are representative of a family of applications or os's or hardware. So I would expect the titles to be modified in the future to something like: cpe:/o:redhat The Red Hat Family of Operating Systems If others agree with this, it would be pretty easy to script this change into this submission. If I hear demand for this, I can take care of it. thoughts? ***** Response: If possible, I'd like to keep this field to a minimum length. We are planning to use the titles associated with each vendor as drop-down menus for our users to build CPE search strings. It is much more convenient and real-estate friendly if the display name for cpe:/:microsoft is "Microsoft Inc." or just "Microsoft" instead of "All products created and/or sold by the Microsoft Corporation." This is particularly true when you start concatenating the names together -- e.g. "All products produced or redistributed by the Red Hat Corporation" + "The Red Hat Linux Operating System" + "Version 1.02" Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Monday, February 04, 2008 4:52 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary >Please let me know if we need to make any changes in format. Format looks good. I have no comments associated with the CPE Names themselves. One point that I will bring up is that in general, it looks like the titles are all just copies of the text in the vendor component. This is fine for now for all the names that don't already exist (better to have something than nothing at all, right?), but for some of the names (Microsoft, Red Hat, etc.), titles already exist in the dictionary with different titles. I know the Red Hat entries were vetted by Red Hat and I would recommend that we stick with their version. Another note related to the titles ... they are meant to be a human readable representation of what platform type the CPE Name represents. For the names you have submitted (general vendor names) these platform types are representative of a family of applications or os's or hardware. So I would expect the titles to be modified in the future to something like: cpe:/o:redhat The Red Hat Family of Operating Systems If others agree with this, it would be pretty easy to script this change into this submission. If I hear demand for this, I can take care of it. thoughts? >I would also like to know how I can track the progress of >submitted CPEs as they are validated, added to the official >CPE dictionary, then indexed with their respective CVEs. Unfortunately, right now there is no way to track this. We would need to implement some form of a submission tool that stored all submissions along with a status flag. This capability currently does not exist. I do agree that this would be a very useful feature. >I'll also point out that the current namePattern format >precludes us from just submitting a vendor name since the >part-type component is mandatory. To get a vendor into the >system, we have to create a cpe for each part-type that any >given manufacturer may produce. In the attached list, each >vendor is submitted as a producer of hardware, operating >systems, and applications. The updated namePattern in Version 2.1 fixes this I think. This was an error in the 2.0 namePattern as all the components were supposed to be optional. Does this fix change your need relative to this submission? Would you rather see names like: cpe:/:redhat The Red Hat family of Platforms I will let everyone know when the Official CPE Dictionary gets updated. Thanks Drew |
Dick_Whitehurst
|
I second the conciseness suggestion. We, too, are planning to us the
title in drop-down selections. Dick Whitehurst -----Original Message----- From: Wolfkiel, Joseph [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 6:00 AM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary One point that I will bring up is that in general, it looks like the titles are all just copies of the text in the vendor component. This is fine for now for all the names that don't already exist (better to have something than nothing at all, right?), but for some of the names (Microsoft, Red Hat, etc.), titles already exist in the dictionary with different titles. I know the Red Hat entries were vetted by Red Hat and I would recommend that we stick with their version. Another note related to the titles ... they are meant to be a human readable representation of what platform type the CPE Name represents. For the names you have submitted (general vendor names) these platform types are representative of a family of applications or os's or hardware. So I would expect the titles to be modified in the future to something like: cpe:/o:redhat The Red Hat Family of Operating Systems If others agree with this, it would be pretty easy to script this change into this submission. If I hear demand for this, I can take care of it. thoughts? ***** Response: If possible, I'd like to keep this field to a minimum length. We are planning to use the titles associated with each vendor as drop-down menus for our users to build CPE search strings. It is much more convenient and real-estate friendly if the display name for cpe:/:microsoft is "Microsoft Inc." or just "Microsoft" instead of "All products created and/or sold by the Microsoft Corporation." This is particularly true when you start concatenating the names together -- e.g. "All products produced or redistributed by the Red Hat Corporation" + "The Red Hat Linux Operating System" + "Version 1.02" Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Monday, February 04, 2008 4:52 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary >Please let me know if we need to make any changes in format. Format looks good. I have no comments associated with the CPE Names themselves. One point that I will bring up is that in general, it looks like the titles are all just copies of the text in the vendor component. This is fine for now for all the names that don't already exist (better to have something than nothing at all, right?), but for some of the names (Microsoft, Red Hat, etc.), titles already exist in the dictionary with different titles. I know the Red Hat entries were vetted by Red Hat and I would recommend that we stick with their version. Another note related to the titles ... they are meant to be a human readable representation of what platform type the CPE Name represents. For the names you have submitted (general vendor names) these platform types are representative of a family of applications or os's or hardware. So I would expect the titles to be modified in the future to something like: cpe:/o:redhat The Red Hat Family of Operating Systems If others agree with this, it would be pretty easy to script this change into this submission. If I hear demand for this, I can take care of it. thoughts? >I would also like to know how I can track the progress of >submitted CPEs as they are validated, added to the official >CPE dictionary, then indexed with their respective CVEs. Unfortunately, right now there is no way to track this. We would need to implement some form of a submission tool that stored all submissions along with a status flag. This capability currently does not exist. I do agree that this would be a very useful feature. >I'll also point out that the current namePattern format >precludes us from just submitting a vendor name since the >part-type component is mandatory. To get a vendor into the >system, we have to create a cpe for each part-type that any >given manufacturer may produce. In the attached list, each >vendor is submitted as a producer of hardware, operating >systems, and applications. The updated namePattern in Version 2.1 fixes this I think. This was an error in the 2.0 namePattern as all the components were supposed to be optional. Does this fix change your need relative to this submission? Would you rather see names like: cpe:/:redhat The Red Hat family of Platforms I will let everyone know when the Official CPE Dictionary gets updated. Thanks Drew |
||||||||||||||||
|
Andrew Buttner
|
>I second the conciseness suggestion. We, too, are planning to us the
>title in drop-down selections. on a side note, regardless of how the titles come out, couldn't the drop downs be based off the components themselves. The CPE Spec tries to have each component readable but concise. These seems like the exact same goals that one would have for populating drop downs. Thanks Drew |
||||||||||||||||
|
Wolfkiel, Joseph
|
In reply to this post
by Wolfkiel, Joseph
The discussions on this list seem to uniformly go against making the cpe
name human friendly. Particularly the % encoding issue we just went through would make the cpe name less usable in human displays. However, even the previous limited character set, required underscores, and lack of support for capitalization bias against displaying the cpe-formatted names to the users. From the spec: "<title> The optional title element may appear as a child of a platform element, to provide a human readable title for it." I never considered it a realistic option to show users the cpe names. It would look unprofessional. Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 11:11 AM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary >I second the conciseness suggestion. We, too, are planning to us the >title in drop-down selections. on a side note, regardless of how the titles come out, couldn't the drop downs be based off the components themselves. The CPE Spec tries to have each component readable but concise. These seems like the exact same goals that one would have for populating drop downs. Thanks Drew |
||||||||||||||||
|
Andrew Buttner
|
All I was suggesting was an alternative that might enable support for
more than just the drop down list use case. There might be other cases that need a more descriptive title as they are presenting this information in a report instead of a drop down list. The suggestion is not to display the CPE Name, but rather to use the component name itself to generate the drop down lists. When displaying drop down lists, your implementation could chose to decode any percent encoding, or replace underscore characters with spaces, or to capitalize the first character. Would this work? If we don't think that there will ever be a need for different types of titles than we can ignore this. Obviously, another option for this would be to allow multiple <title> elements, but I don't think this is a good idea at this time. Thanks Drew >-----Original Message----- >From: Wolfkiel, Joseph [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 12:11 PM >To: cpe-discussion-list CPE Community Forum >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > >The discussions on this list seem to uniformly go against >making the cpe >name human friendly. Particularly the % encoding issue we >just went through >would make the cpe name less usable in human displays. >However, even the >previous limited character set, required underscores, and lack >of support >for capitalization bias against displaying the cpe-formatted >names to the >users. > >From the spec: "<title> The optional title element may appear >as a child of >a platform element, to provide a human readable >title for it." > >I never considered it a realistic option to show users the cpe >names. It >would look unprofessional. > >Lt Col Joseph L. Wolfkiel > >Director, Computer Network Defense Research & Technology (CND >R&T) Program >Management Office > >9800 Savage Rd Ste 6767 >Ft Meade, MD 20755-6767 >Commercial 410-854-5401 DSN 244-5401 >Fax 410-854-6700 > > >-----Original Message----- >From: Buttner, Drew [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 11:11 AM >To: [hidden email] >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > > >>I second the conciseness suggestion. We, too, are planning to us the >>title in drop-down selections. > >on a side note, regardless of how the titles come out, couldn't the >drop downs be based off the components themselves. The CPE Spec tries >to have each component readable but concise. These seems like the >exact same goals that one would have for populating drop downs. > >Thanks >Drew > |
||||||||||||||||
|
Wolfkiel, Joseph
|
In reply to this post
by Wolfkiel, Joseph
We could attempt to do some de- and re-ecoding of the cpe name to generate
something that is human readable, but I view many of the cpe conversion process steps and one-way transforms. It seems much more reasonable to keep a short, meaningful title than to attempt to reconstruct one by using some as-yet-to-be-defined heuristics from a fully encoded CPE name that has had capitalization, spaces, and special characters stripped. Keeping usable titles also saves me from having to build encoding and decoding capabilities into the interface. Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 IETF RFC 1925 2(3) (3) With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 12:33 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary All I was suggesting was an alternative that might enable support for more than just the drop down list use case. There might be other cases that need a more descriptive title as they are presenting this information in a report instead of a drop down list. The suggestion is not to display the CPE Name, but rather to use the component name itself to generate the drop down lists. When displaying drop down lists, your implementation could chose to decode any percent encoding, or replace underscore characters with spaces, or to capitalize the first character. Would this work? If we don't think that there will ever be a need for different types of titles than we can ignore this. Obviously, another option for this would be to allow multiple <title> elements, but I don't think this is a good idea at this time. Thanks Drew >-----Original Message----- >From: Wolfkiel, Joseph [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 12:11 PM >To: cpe-discussion-list CPE Community Forum >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > >The discussions on this list seem to uniformly go against >making the cpe >name human friendly. Particularly the % encoding issue we >just went through >would make the cpe name less usable in human displays. >However, even the >previous limited character set, required underscores, and lack >of support >for capitalization bias against displaying the cpe-formatted >names to the >users. > >From the spec: "<title> The optional title element may appear >as a child of >a platform element, to provide a human readable >title for it." > >I never considered it a realistic option to show users the cpe >names. It >would look unprofessional. > >Lt Col Joseph L. Wolfkiel > >Director, Computer Network Defense Research & Technology (CND >R&T) Program >Management Office > >9800 Savage Rd Ste 6767 >Ft Meade, MD 20755-6767 >Commercial 410-854-5401 DSN 244-5401 >Fax 410-854-6700 > > >-----Original Message----- >From: Buttner, Drew [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 11:11 AM >To: [hidden email] >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > > >>I second the conciseness suggestion. We, too, are planning to us the >>title in drop-down selections. > >on a side note, regardless of how the titles come out, couldn't the >drop downs be based off the components themselves. The CPE Spec tries >to have each component readable but concise. These seems like the >exact same goals that one would have for populating drop downs. > >Thanks >Drew > |
||||||||||||||||
Ken Lassesen-3
|
A while back we talking about CPE being two layered.
Top layer is CPE identifiers Next layer is XML which gives more information, including localized names for what is being identified, expression of the logic for composite CPE from 'atomic' CPE identifiers (not further decomposable - typically specific DLL and exe's) What is the status of that? It seems to address this issue. Ken Lassesen, Office 206-734-4718 Home: 360-724-3190 Cell: 360-509-2402 Skype: Ken.Lassesen IM: [hidden email] http://www.linkedin.com/in/lassesen CONFIDENTIALITY NOTICE The information contained in this electronic message may contain confidential and privileged information and is intended only for use by the individual(s) or entity(ies) to whom it was addressed. Any unauthorized review, use, disclosure, or distribution of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and permanently delete and destroy the original message. -----Original Message----- From: Wolfkiel, Joseph [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 10:33 AM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary We could attempt to do some de- and re-ecoding of the cpe name to generate something that is human readable, but I view many of the cpe conversion process steps and one-way transforms. It seems much more reasonable to keep a short, meaningful title than to attempt to reconstruct one by using some as-yet-to-be-defined heuristics from a fully encoded CPE name that has had capitalization, spaces, and special characters stripped. Keeping usable titles also saves me from having to build encoding and decoding capabilities into the interface. Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 IETF RFC 1925 2(3) (3) With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 12:33 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary All I was suggesting was an alternative that might enable support for more than just the drop down list use case. There might be other cases that need a more descriptive title as they are presenting this information in a report instead of a drop down list. The suggestion is not to display the CPE Name, but rather to use the component name itself to generate the drop down lists. When displaying drop down lists, your implementation could chose to decode any percent encoding, or replace underscore characters with spaces, or to capitalize the first character. Would this work? If we don't think that there will ever be a need for different types of titles than we can ignore this. Obviously, another option for this would be to allow multiple <title> elements, but I don't think this is a good idea at this time. Thanks Drew >-----Original Message----- >From: Wolfkiel, Joseph [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 12:11 PM >To: cpe-discussion-list CPE Community Forum >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > >The discussions on this list seem to uniformly go against making the >cpe name human friendly. Particularly the % encoding issue we just >went through would make the cpe name less usable in human displays. >However, even the >previous limited character set, required underscores, and lack of >support for capitalization bias against displaying the cpe-formatted >names to the users. > >From the spec: "<title> The optional title element may appear as a >child of a platform element, to provide a human readable title for it." > >I never considered it a realistic option to show users the cpe names. >It would look unprofessional. > >Lt Col Joseph L. Wolfkiel > >Director, Computer Network Defense Research & Technology (CND >R&T) Program >Management Office > >9800 Savage Rd Ste 6767 >Ft Meade, MD 20755-6767 >Commercial 410-854-5401 DSN 244-5401 >Fax 410-854-6700 > > >-----Original Message----- >From: Buttner, Drew [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 11:11 AM >To: [hidden email] >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > > >>I second the conciseness suggestion. We, too, are planning to us the >>title in drop-down selections. > >on a side note, regardless of how the titles come out, couldn't the >drop downs be based off the components themselves. The CPE Spec tries >to have each component readable but concise. These seems like the >exact same goals that one would have for populating drop downs. > >Thanks >Drew > |
||||||||||||||||
|
Andrew Buttner
|
>A while back we talking about CPE being two layered.
> Top layer is CPE identifiers > Next layer is XML which gives more information, including localized >names for what is being identified, expression of the logic for >composite CPE from 'atomic' CPE identifiers (not further decomposable - >typically specific DLL and exe's) > >What is the status of that? It seems to address this issue. I think this is what we are talking about. The <title> element in the XML. Thanks Drew |
||||||||||||||||
|
Ken Lassesen-3
|
In reply to this post
by Wolfkiel, Joseph
If we talking about XML, we could easily have
<title> <verbose lang="us-en"> Microsoft Windows XP Professional with SP2 applied <verbose> <verbose lang="ca-fr"> Découvrez Windows XP Professionnel avec SP2 <verbose> <terse> WinXPSp2 </terse> </title> This allows the both scenario... Ken Lassesen, Office 206-734-4718 Home: 360-724-3190 Cell: 360-509-2402 Skype: Ken.Lassesen IM: [hidden email] http://www.linkedin.com/in/lassesen CONFIDENTIALITY NOTICE The information contained in this electronic message may contain confidential and privileged information and is intended only for use by the individual(s) or entity(ies) to whom it was addressed. Any unauthorized review, use, disclosure, or distribution of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and permanently delete and destroy the original message. -----Original Message----- From: Wolfkiel, Joseph [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 10:33 AM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary We could attempt to do some de- and re-ecoding of the cpe name to generate something that is human readable, but I view many of the cpe conversion process steps and one-way transforms. It seems much more reasonable to keep a short, meaningful title than to attempt to reconstruct one by using some as-yet-to-be-defined heuristics from a fully encoded CPE name that has had capitalization, spaces, and special characters stripped. Keeping usable titles also saves me from having to build encoding and decoding capabilities into the interface. Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 IETF RFC 1925 2(3) (3) With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 12:33 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary All I was suggesting was an alternative that might enable support for more than just the drop down list use case. There might be other cases that need a more descriptive title as they are presenting this information in a report instead of a drop down list. The suggestion is not to display the CPE Name, but rather to use the component name itself to generate the drop down lists. When displaying drop down lists, your implementation could chose to decode any percent encoding, or replace underscore characters with spaces, or to capitalize the first character. Would this work? If we don't think that there will ever be a need for different types of titles than we can ignore this. Obviously, another option for this would be to allow multiple <title> elements, but I don't think this is a good idea at this time. Thanks Drew >-----Original Message----- >From: Wolfkiel, Joseph [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 12:11 PM >To: cpe-discussion-list CPE Community Forum >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > >The discussions on this list seem to uniformly go against making the >cpe name human friendly. Particularly the % encoding issue we just >went through would make the cpe name less usable in human displays. >However, even the >previous limited character set, required underscores, and lack of >support for capitalization bias against displaying the cpe-formatted >names to the users. > >From the spec: "<title> The optional title element may appear as a >child of a platform element, to provide a human readable title for it." > >I never considered it a realistic option to show users the cpe names. >It would look unprofessional. > >Lt Col Joseph L. Wolfkiel > >Director, Computer Network Defense Research & Technology (CND >R&T) Program >Management Office > >9800 Savage Rd Ste 6767 >Ft Meade, MD 20755-6767 >Commercial 410-854-5401 DSN 244-5401 >Fax 410-854-6700 > > >-----Original Message----- >From: Buttner, Drew [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 11:11 AM >To: [hidden email] >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > > >>I second the conciseness suggestion. We, too, are planning to us the >>title in drop-down selections. > >on a side note, regardless of how the titles come out, couldn't the >drop downs be based off the components themselves. The CPE Spec tries >to have each component readable but concise. These seems like the >exact same goals that one would have for populating drop downs. > >Thanks >Drew > |
||||||||||||||||
|
Wolfkiel, Joseph
|
In reply to this post
by Wolfkiel, Joseph
I'm actually hoping, in version 3.x that we can go to a per-component
metadata tagging environment. It would be helpful, for the case of a drop-down menu to have each CPE component have its own title and associated metadata. Under the 2.1 spec, if I want to be able to have a separate title for microsoft and for windows_xp and for sp2, I have to register the following: cpe:/:microsoft; title=Microsoft Corporation cpe:/::windows_xp; title=Windows XP cpe:/::::sp2; title=Service Pack 2 cpe:/o:microsoft:windows_xp::sp2; title=Microsoft Windows XP Service Pack 2 The first three allow me to associate titles with the specific component and the last cpe allows me to demonstrate how the names should be rolled up. Arguably, I need to also register cpe:/o:microsoft:windows_xp as well so I can have a title (Microsoft Windows XP) associated with that unique cpe string. Side Note: It's when I start doing this stuff that I question the need for the part type identifier. Is there really any danger of someone naming an OS the same as an application? If an OS [firmware] has the same cpe name as a printer [hardware] don't they pretty much always have the same vulnerabilities? Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 -----Original Message----- From: Ken Lassesen [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 2:39 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary If we talking about XML, we could easily have <title> <verbose lang="us-en"> Microsoft Windows XP Professional with SP2 applied <verbose> <verbose lang="ca-fr"> Découvrez Windows XP Professionnel avec SP2 <verbose> <terse> WinXPSp2 </terse> </title> This allows the both scenario... Ken Lassesen, Office 206-734-4718 Home: 360-724-3190 Cell: 360-509-2402 Skype: Ken.Lassesen IM: [hidden email] http://www.linkedin.com/in/lassesen CONFIDENTIALITY NOTICE The information contained in this electronic message may contain confidential and privileged information and is intended only for use by the individual(s) or entity(ies) to whom it was addressed. Any unauthorized review, use, disclosure, or distribution of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and permanently delete and destroy the original message. -----Original Message----- From: Wolfkiel, Joseph [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 10:33 AM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary We could attempt to do some de- and re-ecoding of the cpe name to generate something that is human readable, but I view many of the cpe conversion process steps and one-way transforms. It seems much more reasonable to keep a short, meaningful title than to attempt to reconstruct one by using some as-yet-to-be-defined heuristics from a fully encoded CPE name that has had capitalization, spaces, and special characters stripped. Keeping usable titles also saves me from having to build encoding and decoding capabilities into the interface. Lt Col Joseph L. Wolfkiel Director, Computer Network Defense Research & Technology (CND R&T) Program Management Office 9800 Savage Rd Ste 6767 Ft Meade, MD 20755-6767 Commercial 410-854-5401 DSN 244-5401 Fax 410-854-6700 IETF RFC 1925 2(3) (3) With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -----Original Message----- From: Buttner, Drew [mailto:[hidden email]] Sent: Tuesday, February 05, 2008 12:33 PM To: [hidden email] Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary All I was suggesting was an alternative that might enable support for more than just the drop down list use case. There might be other cases that need a more descriptive title as they are presenting this information in a report instead of a drop down list. The suggestion is not to display the CPE Name, but rather to use the component name itself to generate the drop down lists. When displaying drop down lists, your implementation could chose to decode any percent encoding, or replace underscore characters with spaces, or to capitalize the first character. Would this work? If we don't think that there will ever be a need for different types of titles than we can ignore this. Obviously, another option for this would be to allow multiple <title> elements, but I don't think this is a good idea at this time. Thanks Drew >-----Original Message----- >From: Wolfkiel, Joseph [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 12:11 PM >To: cpe-discussion-list CPE Community Forum >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > >The discussions on this list seem to uniformly go against making the >cpe name human friendly. Particularly the % encoding issue we just >went through would make the cpe name less usable in human displays. >However, even the >previous limited character set, required underscores, and lack of >support for capitalization bias against displaying the cpe-formatted >names to the users. > >From the spec: "<title> The optional title element may appear as a >child of a platform element, to provide a human readable title for it." > >I never considered it a realistic option to show users the cpe names. >It would look unprofessional. > >Lt Col Joseph L. Wolfkiel > >Director, Computer Network Defense Research & Technology (CND >R&T) Program >Management Office > >9800 Savage Rd Ste 6767 >Ft Meade, MD 20755-6767 >Commercial 410-854-5401 DSN 244-5401 >Fax 410-854-6700 > > >-----Original Message----- >From: Buttner, Drew [mailto:[hidden email]] >Sent: Tuesday, February 05, 2008 11:11 AM >To: [hidden email] >Subject: Re: [CPE-DISCUSSION-LIST] FW: CPE Dictionary > > >>I second the conciseness suggestion. We, too, are planning to us the >>title in drop-down selections. > >on a side note, regardless of how the titles come out, couldn't the >drop downs be based off the components themselves. The CPE Spec tries >to have each component readable but concise. These seems like the >exact same goals that one would have for populating drop downs. > >Thanks >Drew > |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
