Release Notes for Trellix DAT Files Copyright (C) 2022 Musarubra US LLC. All Rights Reserved =============================================== Thank you for using our products. This file contains important information about the current virus definition (DAT) files. We recommend that you read the entire document. You must have a current Support agreement in order to be entitled to download product updates and upgrades, including engine and DAT updates. By downloading any of these files, you acknowledge that you currently have a valid Support agreement with Trellix. The DAT files supplied with this README file are compatible with our anti-virus products that use the version 5700 (or later) virus-scanning engine. We recommend that you upgrade to the latest version of the virus-scanning engine for optimal virus detection and cleaning. _______________________________________________ WHAT'S IN THIS FILE? - What are DAT files? - How we provide the DAT files - Which file to use - When to use the XDAT file - When to use the compressed DAT package (AVVDAT-nnnnn.zip or AVVDAT-nnnnn.tar) - Installation - Using the DAT Package Installer (XDAT file) - Using the DAT ZIP or DAT TAR file to update VirusScan Command Line and VirusScan for UNIX - Using the DAT ZIP or DAT TAR file to update other products - List of Virus Definition Files - Testing your installation - New Viruses Detected and Removed - Understanding Virus Names - Prefix - Prefix for Trojan horse classes - Infix - Suffix - Generic Detections - Heuristic Detections - Application Detections - Contacting Trellix - Copyright and Trademark Attributions - Trademarks - License Agreement _______________________________________________ WHAT ARE DAT FILES? Virus definition, or DAT files contain up-to-date virus signatures and other information that our anti-virus products use to protect your computer against millions of computer viruses and other potentially harmful software in circulation. Thousands of new threats appear each day. Every day, we release new DAT files. To ensure that your anti-virus software can protect your system or network against the latest threats, you must download and install the latest DAT files. _______________________________________________ HOW WE PROVIDE THE DAT FILES We store new DAT files on our website in several compressed formats to reduce transmission time: - DAT package installer, or "XDAT file". This file includes the DAT files in an executable package for install on Microsoft Windows Operating systems. The file name is of the format 10531XDAT.EXE, where 10531 is the five-digit DAT version number. The "XDAT file" cannot be directly checked into Trellix ePO and one must download and use the "DAT Package For Use with Trellix ePO" - Compressed DAT package - This file contains the DAT files compressed in a .zip or .tar file. You can extract and install them yourself to update most of our anti-virus software. The file name is of the format AVVDAT-10531.zip or AVVDAT-10531.tar, where 10531 is the five-digit DAT version number. _______________________________________________ WHICH FILE TO USE WHEN TO USE THE XDAT The XDAT makes DAT updating quick and simple on Microsoft Windows operating The XDAT installer does not update the virus-scanning engine for the anti-virus software. Hence, you can use this installer when your engine is up-to-date. The XDAT file is a standard application that you can double-click to start from within Microsoft Windows. It installs new DAT files to keep your anti-virus software up-to-date. It shuts down any active anti-virus scans, services, or other memory-resident software components that might interfere with your updates. It then copies the new files to their proper locations and enables your anti-virus software to use them immediately. WHEN TO USE THE COMPRESSED DAT PACKAGE (DAT) A compressed DAT package allows you to update the DAT files for any supported Trellix anti-virus product. The difference between this package and the XDAT installer is that you must manually stop any scans or virus-scanning services. You must then copy the new files to the program directory of your anti-virus software, then restart the services or background-scanning software that your application uses. Alternatively, if your anti-virus software has an AutoUpdate feature, you can configure that to download and install the package for you. Trellix anti-virus software can also use incremental DAT file updating. For more information, see your product documentation. To learn how to update these products, see "Installation". _______________________________________________ INSTALLATION We recommend customers use the auto update strategy of the respective Trellix products rather than manual DAT installation. In case of a manual update, one could use either the the DAT installer (XDAT file) to install new DAT files. This installer provide an straightforward method for correctly updating the DAT files. USING THE DAT PACKAGE INSTALLER (XDAT FILE) 1. Create a temporary directory on your hard disk. 2. Download the XDAT file to the temporary directory from our website. For the location, see the "Contacting Trellix" section in this readme. 3. Double-click the XDAT file to start the update. 4. Follow the instructions in the wizard panels. The installer then does the following: - Unloads Trellix memory-resident software or stops services that use your current DAT files. - Copies new DAT files to the appropriate program directories. - Restarts the software components needed to continue scans with your new DAT files. 5. When the installer has finished updating your DAT files, you may delete the file you downloaded, unless you want to keep a copy available for further updates. USING THE DAT ZIP OR DAT TAR FILE TO UPDATE VIRUSSCAN COMMAND LINE AND VIRUSSCAN FOR UNIX 1. Create a temporary directory on your hard disk. 2. Download the compressed DAT file to the temporary directory from our website. See the "Contacting Trellix" section in this readme. The name of the file is typically AVVDAT-10531.zip or AVVDAT-10531.tar, where 10531 is the DAT version number. 3. Back up or rename the existing DAT files, which are in the program directory for your anti-virus software. See "List of Virus Definition Files" in this readme for a complete DAT file list. 4. Using Winzip, PKUnzip, or a similar utility, open the zip file and extract the new DAT files. You can save the extracted files directly to the program directory for your anti-virus software. To extract DAT files stored in a tar file, use a compression utility that can read and extract the tar files, or follow these steps from a UNIX command prompt: 1. Change to the directory into which you want to extract the new DAT files. This is the program directory for your anti-virus software, or a temporary directory from which you intend to copy the new files. 2. Enter this command at the command prompt: tar xf /avvdat-10531.tar Here, is the path to the tar file you downloaded. The tar utility will extract the DAT files into your current working directory. NOTE: The syntax for the tar command might vary in different UNIX versions. Consult your manual pages or product documentation for more details. 5. Copy the new DAT files to the program directory for the software you want to update. Allow the new files to replace the existing files. NOTE: When you have finished using the compressed DAT file, you may delete it from your hard disk, unless you want to keep a copy for further updates. LIST OF VIRUS DEFINITION FILES The virus definition files (or DAT files) included in the packages are: AVVSCAN.DAT Data file for virus scanning AVVNAMES.DAT Data file for virus names AVVCLEAN.DAT Data file for virus cleaning TESTING YOUR INSTALLATION You can test the operation of the software by running the EICAR Standard AntiVirus Test File on any computer where you have installed the software. The EICAR Standard AntiVirus Test File is a combined effort by anti-virus vendors throughout the world to implement one standard by which customers can verify their anti-virus installations. To test your installation: 1. Copy the following line into its own file, then save the file with the name EICAR.COM. X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H* The file size will be 68 or 70 bytes. 2. Start your anti-virus software and allow it to scan the directory that contains EICAR.COM. When your software scans this file, it will report finding the EICAR test file. 3. Delete the file when you have finished testing your installation to avoid alarming unsuspected users. IMPORTANT: The EICAR test file is NOT A VIRUS. _______________________________________________ NEW VIRUSES DETECTED AND REMOVED Thousands of new viruses and variants appear each month. Those which are detected and cleaned by Trellix Advanced Research Center generic methods are added to the total virus count listed, but they are not listed separately here. Trellix software removes a virus either by deleting the infecting virus code from files or by deleting the file from your computer. For more information on the new viruses detected and removed by a specific DAT, please refer to the DAT Readme page on the Trellix website. https://www.trellix.com/en-us/advanced-research-center.html _______________________________________________ UNDERSTANDING VIRUS NAMES Our anti-virus software typically follows industry-wide naming conventions to identify the viruses that it detects and cleans. Occasionally, some virus names deviate from strict industry standards. The first virus with a given set of characteristics that mark it as a distinctly new entity receives a "family" name. Virus researchers draw the family name from some identifying quirk or notation in the virus, such as a text string, or a payload effect. A family name can also include a numeric string that designates the byte size of the virus. Researchers use this name as convenient shorthand to distinguish closely allied virus variants. Names for variants within a virus family consist of the family name and a suffix. For example, BadVirus.a. The suffix continues in alphabetical order until it reaches z. Then it begins again with aa and continues to az. Then the variants receive the suffix ba through bz and so on until the suffix reaches zz. If yet another variant appears after that, it will have the suffix aaa. As new virus strains appeared, industry naming conventions evolved to include more information. Some names, for instance, include parts that identify the platform on which the virus can run. Among anti-virus vendors, virus names can include a prefix, an infix, and a suffix. PREFIX The prefix designates the type of file that the virus infects or the platform on which the potentially harmful software can run. Viruses that infect DOS executables do not receive a prefix. Our naming convention includes the following prefixes: A97M/ Macro virus that infects Microsoft Access 97 files. APM/ Macro virus or Trojan horse program that infects Ami Pro document and template files. Bat/ Batch-file virus or Trojan horse program. These viruses usually run as batch or script files that affect a particular program that interprets the script or batch commands they include. They are very portable and can affect nearly any platform that can run batch or script files. The files themselves often have a .bat extension. CSC/ Corel Script virus or Trojan horse program that infects Corel Draw document files, template files, and scripts. IRC/ Internet Relay Chat script virus. This virus type can use early versions of the mIRC client software to distribute a virus or payload. JS/ Script virus or Trojan horse program written in JavaScript language. JV/ Potentially harmful Java application or applet. Linux/ Virus or Trojan horse program compiled for Linux operating system in ELF file format. LWP/ Potentially harmful software for Lotus WordPro. MacHC/ Virus or Trojan horse program for Apple Macintosh HyperCard scripting language. MacOS/ Virus or Trojan horse program for Apple Macintosh OS versions 6-9. MSIL/ Application written using Microsoft Intermediate Language framework, also known as .NET. P98M/ Macro virus or Trojan horse program that infects Microsoft Project documents and templates. PalmOS/ Virus or Trojan horse program for a Palm Pilot. PDF/ File-infector of Adobe PDF files. Perl/ Script virus or Trojan horse program written in Perl language. PHP/ Script virus or Trojan horse program written in PHP language. PP97M/ Macro virus. Infects Microsoft PowerPoint 97 files. RDN/ Denoting the malware signature was authored by Trellix Automation system. SunOS/ Potentially harmful software for Sun Solaris. SWF/ Potentially harmful software for Shockwave. Unix/ Program or a shell script for a version of UNIX. V5M/ Macro or script virus, or Trojan horse program that infects Visio VBA (Visual Basic for Applications) macros or scripts. VBS/ Script virus or Trojan horse program written in Visual Basic Script language. W16/ File-infector virus that runs in 16-bit Microsoft Windows environments (Windows 3.1x). W2K/ Potentially harmful software for 32-bit Microsoft Windows environments, specifically Windows NT, 2000, or XP. W32/ File-infector or boot-sector virus that runs in 32-bit Microsoft Windows environments (Windows 95, Windows 98, or Windows NT). W95/ File-infector virus that runs in Microsoft Windows 95, Windows 98, and Windows ME environments. W97M/ Macro virus that infects Microsoft Word 97 files. WHLP/ Potentially harmful software for 32-bit Microsoft Windows environments that target Windows HLP files. WM/ Macro virus that infects Microsoft Word 95 files. X97M/ Macro virus that infects Microsoft Excel 97 files. XF/ Macro virus that infects Microsoft Excel 95 or 97 via Excel formulas. XM/ Macro virus that infects Microsoft Excel 95 files. PREFIX FOR TROJAN HORSE CLASSES A name such as "BackDoor-" denotes A potentially harmful software that belongs to a class of similar Trojan horse programs. The class name is followed by extra characters to denote a family (such as BackDoor-JZ) or a name (such as BackDoor-Sub7). AdClicker - Repeatedly accesses websites that are funded by advertising. Adware - Installs advertising software but does not ask permission. BackDoor - Provides remote access or control through the Internet or network. Dialer - Dials a phone number without asking for permission. DDoS - Operates as a Distributed Denial of Service component. Del - Deletes files. Downloader - Downloads software from the Internet, usually to deliver backdoors, password stealers, and sometimes viruses. Exploit - Uses a vulnerability or a software defect. FDoS - Denotes a Flooding Denial of Service component. KeyLog - Logs keystrokes for immediate or future transmission to the attacker. Kit - Denotes a program designed for creating a virus or Trojan horse program. MultiDropper - Drops several Trojan horse programs or viruses (often several different 'backdoors'). Nuke - Uses defects in software installed on a remote computer to bring it down. ProcKill - Terminates the processes of anti-virus and security products. May also delete files associated with such applications. PWS - Steals a password. Reboot - Reboots the computer. Reg - Modifies the Registry in an undesirable fashion without asking questions. For example, reduces the security settings or creates abnormal associations or sets. Spam - Acts as a spamming tool. Spyware - Monitors browsing habits or other behavior and sends the information out, often for unsolicited advertising. Uploader - Sends files or other data from the computer. Vtool - Denotes a program used by virus writers or hackers for developing software. Zap - Wipes all or part of a hard disk. INFIX These designations usually appear in the middle of a virus name. Trellix Advanced Research Center assign these designations, which differ from industry conventions. .cmp. Companion file that the virus adds to an existing executable file. Our anti-virus software deletes the companion file to prevent later infections. .mp. Legacy multi-partite virus for DOS. .ow. Overwriting virus. This identifies a virus that overwrites data in a file, thereby irreparably corrupting it. This file must be deleted. SUFFIX These designations usually appear as the last part of a virus name. A virus name can have more than one suffix. One might designate a variant, for example, while others give additional information. @M Slow mailer. This virus uses an email system to spread. It usually replies to an incoming message once, or attaches itself to an outgoing message, or sends to just one email address. @MM Mass mailing distribution. This virus might use standard techniques to propagate itself, but also uses an email system to spread. .a - .zzz Virus variants. In accordance with the CARO (Computer Anti-virus Research Organization) naming convention, the vendor-specific suffixes can be preceded by a "!" character. Our software uses the following suffixes: apd Appended virus. A virus that appends its code to the file it infects, but fails to provide for correct replication. bat Software component in BAT language. cav Cavity virus. This designates a virus that copies itself into "cavities" (for example, areas of all zeroes) in a program file. cfg Configuration component of an Internet Trojan horse program (frequently of a 'BackDoor-'). cli Client-side component of an Internet Trojan horse program (frequently of a 'BackDoor-'). dam Damaged file. A file that is damaged or corrupted by an infection. demo Program that demonstrates potentially harmful action, such as an example of how an exploit works. dr Dropper file. This file introduces the virus into the host program. gen Generic detection. Native routines in our software detect this virus without using specific code strings. ini An mIRC or pIRCH script when it is a component of another virus. intd "Intended" virus. This virus has most of the usual virus characteristics but cannot replicate correctly. irc IRC component of potentially harmful software. js Potentially harmful software component in JavaScript. kit Virus or Trojan horse program created from a 'virus construction kit'. p2p Potentially harmful software that uses peer-to-peer communication to function. For example, Gnutella and Kazaa. sfx Self-extracting installation utility for Trojan horse programs. src Viral source code. This ordinarily cannot replicate or infect files, but some virus droppers add this to files as part of the infection cycle. Our products routinely flag files with additional code of this sort for deletion. sub Substitution virus. It substitutes the host file with itself, so that all infected hosts are of the same size and are a pure virus. (That is, a subclass of overwriting viruses.) svr Server-side component of an Internet Trojan horse program, often of a 'backdoor'. vbs Potentially harmful software component written in Visual Basic Script language. worm A non-parasitic virus that copies itself, or a virus that propagates through a network by copying to remote computers or by sending itself out via any means of file transmission such as remote shares, peer-to-peer, instant messaging, IRC file transfers, FTP, and SMTP. GENERIC DETECTIONS Our software detects a huge amount of potentially harmful software proactively and generically. In most cases, such objects are successfully cleaned even without Trellix Advanced Research Center ever receiving a sample. Such detection is denoted by "Generic" in the name or a "gen" suffix. To submit a sample to Trellix, visit the Trellix Advanced Research Center home page. See the "CONTACTING TRELLIX" section in this readme. HEURISTIC DETECTIONS Our software detects a huge amount of new potentially harmful software heuristically. Such detection is flagged using the "New" prefix to the name (For example, "New Worm" and "New Win32"). To submit any sample that was detected heuristically, visit the Trellix Advanced Research Center home page. See the "CONTACTING TRELLIX" section in this readme. APPLICATION DETECTIONS Our software detects potentially unwanted applications; they cannot be classified as viruses or Trojan horse programs. They include some adware, spyware, dialers, remote-access software that can hide itself, and other similar applications that many users do not want on their computers. Unwanted applications also include 'jokes' but these can be excluded from detection using scanning options. For more information, visit the Trellix Advanced Research Center home page. See the "CONTACTING TRELLIX" section in this readme. _________________________________________________________ CONTACTING TRELLIX Contact information for Trellix services and resources: Technical support, customer service, Trellix Advanced Research Center beta program, and training. It also includes a list of phone numbers, street addresses, web addresses, e-mail addresses, and fax numbers for Trellix offices in the United States and around the world. Technical Support Home Page https://www.trellix.com/en-us/support.html KnowledgeBase Search https://supportm.trellix.com/webcenter/portal/supportportal/pages_knowledgecenter Trellix Technical Support ServicePortal (Logon credentials required) https://supportm.trellix.com/ Login credentials required. Trellix Security Beta Program Beta website https://www.trellix.com/en-us/downloads/beta-programs.html Security Headquarters -- Trellix Advanced Research Center Home Page https://www.trellix.com/en-us/advanced-research-center.html Virus Information Library https://www.trellix.com/en-us/advanced-research-center.html Submit a Virus Sample https://kcm.trellix.com/corporate/index?page=content&id=KB68030 DAT Notification Service https://www.trellix.com/en-us/contact-us/sns-preferences.html Download Site Home Page https://www.trellix.com/en-us/downloads.html DAT File and Engine Updates For XDAT and ePO deployable packages: https://www.trellix.com/en-us/downloads/security-updates.html For Tar package: http://update.nai.com/products/datfiles/4.x/ For Zip package: https://update.nai.com/products/commonupdater/current/vscandat1000/dat/0000/ Product Upgrades https://www.trellix.com/en-us/downloads/my-products.html Valid grant number required - Contact Trellix Customer Service Trellix Customer Service Web: https://www.trellix.com/en-us/contact-us.html For additional information on contacting Trellix including toll-free numbers for other geographic areas -- see the CONTACT file that accompanied your original product release. __________________________________________________________ COPYRIGHT Copyright (C) 2022 Musarubra US LLC. Trellix, FireEye and Skyhigh Security are the trademarks or registered trademarks of Musarubra US LLC, FireEye Security Holdings US LLC and their affiliates in the US and /or other countries. McAfee is the trademark or registered trademark of McAfee LLC or its subsidiaries in the US and /or other countries. Other names and brands are the property of these companies or may be claimed as the property of others. __________________________________________________________ LICENSE INFORMATION LICENSE AGREEMENT NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEBSITE FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO TRELLIX (MUSARUBRA US LLC) OR THE PLACE OF PURCHASE FOR A FULL REFUND. LICENSE ATTRIBUTIONS This product includes or may include: * Software originally written by Philip Hazel, Copyright (c) 1997-2008 University of Cambridge. A copy of the license agreement for this software can be found at www.pcre.org/license.txt * This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). * Cryptographic software written by Eric A. Young and software written by Tim J. Hudson. * Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL, which is distributed to someone in an executable binary format, that the source code also be made available to those users. For any such software covered under the GPL, the source code is made available on this CD. If any Free Software licenses require that Trellix provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein. * Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer. * Software originally written by Robert Nordier, Copyright (C) 1996-7 Robert Nordier. * Software written by Douglas W. Sauder. * Software developed by the Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at www.apache.org/licenses/LICENSE-2.0.txt. * International Components for Unicode ("ICU") Copyright (C) 1995-2002 International Business Machines Corporation and others. * Software developed by CrystalClear Software, Inc., Copyright (C) 2000 CrystalClear Software, Inc. * FEAD(R) Optimizer(R) technology, Copyright Netopsystems AG, Berlin, Germany. * Outside In(R) Viewer Technology (C) 1992-2001 Stellent Chicago, Inc. and/or Outside In(R) HTML Export, (C) 2001 Stellent Chicago, Inc. * Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper, (C) 1998, 1999, 2000. * Software copyrighted by Expat maintainers. * Software copyrighted by The Regents of the University of California, (C) 1996, 1989, 1998-2000. * Software copyrighted by Gunnar Ritter. * Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A., (C) 2003. * Software copyrighted by Gisle Aas. (C) 1995-2003. * Software copyrighted by Michael A. Chase, (C) 1999-2000. * Software copyrighted by Neil Winton, (C) 1995-1996. * Software copyrighted by RSA Data Security, Inc., (C) 1990-1992. * Software copyrighted by Sean M. Burke, (C) 1999, 2000. * Software copyrighted by Martijn Koster, (C) 1995. * Software copyrighted by Brad Appleton, (C) 1996-1999. * Software copyrighted by Michael G. Schwern, (C) 2001. * Software copyrighted by Graham Barr, (C) 1998. * Software copyrighted by Larry Wall and Clark Cooper, (C) 1998-2000. * Software copyrighted by Frodo Looijaard, (C) 1997. * Software copyrighted by the Python Software Foundation, Copyright (C) 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. * Software copyrighted by Beman Dawes, (C) 1994-1999, 2002. * Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek (C) 1997-2000 University of Notre Dame. * Software copyrighted by Simone Bordet & Marco Cravero, (C) 2002. * Software copyrighted by Stephen Purcell, (C) 2001. * Software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). * Software copyrighted by International Business Machines Corporation and others, (C) 1995-2003. * Software developed by the University of California, Berkeley and its contributors. * Software developed by Ralf S. Engelschall for use in the mod_ssl project (http://www.modssl.org/). * Software copyrighted by Kevlin Henney, (C) 2000-2002. * Software copyrighted by Peter Dimov and Multi Media Ltd. (C) 2001, 2002. * Software copyrighted by David Abrahams, (C) 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. * Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, (C) 2000. * Software copyrighted by Boost.org, (C) 1999-2002. * Software copyrighted by Nicolai M. Josuttis, (C) 1999. * Software copyrighted by Jeremy Siek, (C) 1999-2001. * Software copyrighted by Daryle Walker, (C) 2001. * Software copyrighted by Chuck Allison and Jeremy Siek, (C) 2001, 2002. * Software copyrighted by Samuel Krempp, (C) 2001. See http://www.boost.org for updates, documentation, and revision history. * Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), (C) 2001, 2002. * Software copyrighted by Cadenza New Zealand Ltd., (C) 2000. * Software copyrighted by Jens Maurer, (C) 2000, 2001. * Software copyrighted by Jaakko Järvi (jaakko.jarvi@cs.utu.fi), (C) 1999, 2000. * Software copyrighted by Ronald Garcia, (C) 2002. * Software copyrighted by David Abrahams, Jeremy Siek, and Daryle Walker, (C) 1999-2001. * Software copyrighted by Stephen Cleary (shammah@voyager.net), (C) 2000. * Software copyrighted by Housemarque Oy , (C) 2001. * Software copyrighted by Paul Moore, (C) 1999. * Software copyrighted by Dr. John Maddock, (C) 1998-2002. * Software copyrighted by Greg Colvin and Beman Dawes, (C) 1998, 1999. * Software copyrighted by Peter Dimov, (C) 2001, 2002. * Software copyrighted by Jeremy Siek and John R. Bandela, (C) 2001. * Software copyrighted by Joerg Walter and Mathias Koch, (C) 2000-2002. * Software copyrighted by Carnegie Mellon University (C) 1989, 1991, 1992. * Software copyrighted by Cambridge Broadband Ltd., (C) 2001-2003. * Software copyrighted by Sparta, Inc., (C) 2003-2004. * Software copyrighted by Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, (C) 2004. * Software copyrighted by Simon Josefsson, (C) 2003. * Software copyrighted by Thomas Jacob, (C) 2003-2004. * Software copyrighted by Advanced Software Engineering Limited, (C) 2004. * Software copyrighted by Todd C. Miller, (C) 1998. * Software copyrighted by The Regents of the University of California, (C) 1990, 1993, with code derived from software contributed to Berkeley by Chris Torek. Copyright (c) 2017 Intel Corporation Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Deriv 2.3.1 DBN 146-EN