P2P Marshal User Guide

Version 1.1.0 July 15, 2008

ATC-NY 33 Thornwood Drive, Suite 500 Ithaca, NY 14850 phone: 607-257-1975 fax: 607-257-1972

P2P Marshal User Guide Table of Contents 1 2 3


Summary of Features .................................................................................................. 4 Requirements .............................................................................................................. 4 Getting Started ............................................................................................................ 4 3.1 Installing ............................................................................................................. 4 3.2 Uninstalling......................................................................................................... 4 3.3 Running............................................................................................................... 4 4 Starting an acquisition................................................................................................. 5 4.1 Creating a new acquisition.................................................................................. 5 4.2 Opening an existing acquisition........................................................................ 10 4.3 The Main P2P Marshal Window....................................................................... 10 4.4 Installation Artifacts.......................................................................................... 14 5 Searching................................................................................................................... 15 5.1 Performing a Search.......................................................................................... 16 5.2 Reviewing Searches .......................................................................................... 17 6 P2P Marshal Audit Log ............................................................................................ 20 7 Generating a Report .................................................................................................. 21 8 Supported Clients...................................................................................................... 23 8.1 Ares ................................................................................................................... 23 8.2 BitTorrent.......................................................................................................... 24 8.3 Google Hello..................................................................................................... 24 8.4 Kazaa................................................................................................................. 24 8.5 LimeWire .......................................................................................................... 25 8.6 uTorrent............................................................................................................. 25 8.7 Azureus Vuze (Azureus 3+) ............................................................................. 25 9 Version History......................................................................................................... 26 10 Known Issues ........................................................................................................ 26 11 License Agreement ............................................................................................... 26 12 Included software.................................................................................................. 31 12.1 Java License ...................................................................................................... 31 12.2 Eclipse License ................................................................................................. 35 12.3 JDOM License .................................................................................................. 38 12.4 BouncyCastle License....................................................................................... 39 12.5 iText License..................................................................................................... 39


P2P Marshal User Guide Abstract


P2P Marshal is a software tool, developed by ATC-NY, to aid in the automated analysis of disk images from systems that have used peer-to-peer (P2P) software. P2P Marshal automatically determines what P2P software is present on the image and analyzes and interprets relevant files, such as log files and configuration files. P2P Marshal allows the investigator to perform a variety of searches and presents the results of the investigation in a format that can easily be included in the investigation report. Because there are always new P2P clients emerging, P2P Marshal is extensible to support new clients.

Copyright ©2007, ATC-NY. All rights reserved.

This project was sponsored by Award No. 2006-DN-BX-K013 awarded by the National Institute of Justice, Office of Justice Programs, US Department of Justice. The opinions, findings, and conclusions or recommendations expressed in this publication/program are those of the authors and do not necessarily reflect the views of the Department of Justice.


P2P Marshal User Guide


1 Summary of Features
• • • • • • Analyzes peer-to-peer network usage on images of Windows 2000, 2003 and XP systems Extensible Forensically sound Provides full analysis for: BitTorrent, LimeWire, uTorrent, and Azereus Detects and shows default download locations for Ares, Google Hello, and Kazaa Future versions will include additional client and operating system support and capabilities

2 Requirements
P2P Marshal runs on a Windows 2000/XP/Vista system. Installation requires approximately 110 MB of disk space. In general, the target disk will be on a different logical drive, although it can be a directory, such as an extracted archive, within a logical drive (e.g., “C:”). Results from P2P Marshal are stored in a user-specified directory. While the space required will vary depending on the number of clients found, this is typically small, on the order of a few hundred KB.

3 Getting Started
3.1 Installing
To install, double-click on P2PMarshal_Setup.exe and follow the instructions in the install script. The default answers to installation questions are usually sufficient.

3.2 Uninstalling
Select “uninstall” from the P2P Marshal menu under the Windows “Start” button, or use the Windows “Add or Remove Programs” control panel.

3.3 Running
Double click on the P2P Marshal application to begin. Figure 1 shows the initial window that appears when P2P Marshal first starts running.


5 . and investigator’s name. The location can be typed directly into the text box or the “browse” button can be used to navigate directories (and create them). 4. using the File menu or the icons below the menu bar. the investigator enters information about the case. associated with a case). disks to analyze. Storing a new acquisition in a directory that already contains an acquisition will first delete the contents of the directory. Acquisition Information. shown in Figure 3. the investigator can either create a new investigation or open an existing one. such as case number. shown in Figure 2. The investigator also selects the location where data will be stored. On the first page..e. i.1 Creating a new acquisition P2P Marshal guides the investigator through the steps of creating a new investigation through a “wizard” that consists of 3 pages. acquisition name (in case there are multiple acquisitions.P2P Marshal User Guide ATC-NY Figure 1: When P2P Marshal is first launched 4 Starting an acquisition When P2P Marshal starts. We recommend creating a new directory for each acquisition.

P2P Marshal User Guide ATC-NY Figure 2: First page of the New Acquisition wizard 6 .

This can either be a logical drive (e. such as a USB disk. shown in Figure 4.. such as Mount Image Pro or VMware-mount. or a disk image mounted by a third party program. or a subdirectory where a disk image has been restored. “D:” or “E:”).P2P Marshal User Guide ATC-NY Figure 3: Selecting a location for the acquisition (the “Browse. Note that the logical drive can correspond to a physical disk. the investigator selects the target disk to be analyzed.g... 7 . Location to be Analyzed.” button) On the second page. shown in Figure 5.

P2P Marshal User Guide ATC-NY Figure 4: Selecting a logical drive for a new acquisition 8 .

is correct. Referenced files and directories that cannot be accessed are listed in the Shared/Downloaded Files section (see Section 4. 9 .3. The investigator can also select “unknown. the investigator selects the original logical drive label (mount point) of the target drive.P2P Marshal User Guide ATC-NY Figure 5: Selecting a sub-directory for a new acquisition On the third page. “C:”.” This significantly limits P2P Marshal’s capabilities. “The Main P2P Marshal Window”). P2P Marshal requires this information to find files on the target drive referred to by peer-to-peer clients’ configuration and log files. The “Directory” column in this table can help determine the correct mount point for reacquisition. Usually the default.

the investigator selects the “Finish” button and P2P Marshal performs the analysis. The tab is labeled with the program name and its icon and shows the version number and installation directory when the 10 .3 The Main P2P Marshal Window The main P2P Marshal window consists of two parts: the case information. and the peer-to-peer application information. This skips the initial steps described above. Note that the disk image must be present and mounted in the same location as it was when the acquisition was first created.P2P Marshal User Guide ATC-NY Figure 6: Selecting target mount point Once the location and mount point are specified. 4. displayed at the top. displayed as several tabs—one tab for each peer-to-peer application found.2 Opening an existing acquisition Investigators can also open an existing acquisition. 4. Selecting a different tab selects a different peerto-peer client and displays information about it.

“Installation Artifacts”). describes how that client was used.8”). Installation Information. version.14. If P2P Marshal can determine the exact version. “4.1. describes information about the client software. (e.4. “All Users Combined” shows information for all users.g. then the name will be listed and no selection box is displayed. The installation status will be either “Partial” or “Full”. Figure 7 shows the main window with several tabs open corresponding to six different clients.0.g.) are missing. that value is displayed (e. and the latter indicates all components were present.0. otherwise it displays the range of versions that match the program.. and installation status. the former indicates some components of the program (executable. specifically the name.P2P Marshal User Guide ATC-NY mouse “hovers” over the tab.1. The first part. Figure 8 shows an example of a drop down menu showing three users for a client. If only one user’s information exists. Usage Information. “3. Figure 7: After acquisition is finished Each tab consists of two parts. The first section allows the investigator to select which user’s information to report via a pull-down menu. installation location.. etc. libraries. Clicking on the installation status will open the Installation Artifacts window for that client (see Section 4.6a”). The second part of the window. 11 .4-3.

The number of files displayed in the Shared/Downloaded Files section has been significantly reduced.) 12 . (Counts for each table are shown on the right-hand side of the window.P2P Marshal User Guide ATC-NY Figure 8: Drop down menu of users for installations with multiple users Figure 9 shows the display after a single user has been selected from the pull-down menu.

jpg. Scroll bars are present as needed. .doc. last modification time. so the name or numeric address is selected solely based on what name was included in the log or configuration file. Additional information includes the type of the node (often there are normal peer nodes and special nodes. directory in which the file is located.P2P Marshal User Guide ATC-NY Figure 9: After selecting one user Below the user selection is the Shared/Downloaded Files section. trackers. A file can be selected by clicking on its row. . file size. Information fields include sharing status. etc. Columns can be reordered and resized. and user associated with the file. Clicking on a column heading will sort the list according to that column. cache. the last contact time. 13 . or log files for that client. by the software). This window displays files that were either downloaded or shared. and includes the name or IP address of any peer computer found in the configuration. Right clicking on a file brings up a menu that allows the investigator to open a Windows Explorer window of the directory where that file is located or to launch the appropriate Windows application for that file based on its file type (e.. called supernodes. download status. if desired.wmv). Note that no name resolution is performed. by clicking and dragging the column headings. if available. Double-clicking on the file will also launch the appropriate viewer. . and the user who communicated with the peer server.g. The list of Peer Servers is next.

Finally. 14 . This includes the log message and the date and time it was generated. and registry keys that P2P Marshal searched for to determine if a peer-to-peer client is present on the examined system. these are displayed at the bottom of the window. Figure 10 shows an example of a client with extra information. This window displays the directories.P2P Marshal User Guide ATC-NY Below that is the Usage Log. and total connection and run time. some programs (such as LimeWire) keep additional information. If the client maintains no log. If present. the Client’s ID. if the client software maintained a log file. this table is not present. files. shown in Figure 11.4 Installation Artifacts Clicking on the Installation Status text in the Installation Information section for a client or selecting “View installation artifacts” in the “Tools” menu displays the Installation Artifacts window. such as when the last session ended. Figure 10: A tab showing additional client-specific information 4.

Shared/Downloaded Files. the file is from a version of the software that P2P Marshal does not recognize. it is listed as invalid with a note. and Usage Log. the note is “not present. as well as the version or range of versions associated with that item. specifically. 15 .P2P Marshal User Guide ATC-NY Figure 11: Installation Artifacts window Positively-identified items are listed under the “Valid” section for a particular peer-topeer client. If a file is present but the MD5 checksum of that file does not match the specified value. Files can have a specified MD5 checksum that serves to identify different software versions. by using the search options under the Tools menu. (The primary purpose of this version of the Installation Artifacts window is to verify P2P Marshal’s determination of installed client software. The two other searches (Network Host in Acquired Data and Log Entry in Acquired Data) operate similarly.” Each valid file will likely have multiple invalid entries that are MD5 mismatches because P2P Marshal knows about multiple versions of each client. Peer Servers. “md5 mismatch.” If the file is not present at all. If there are many entries for a file that are MD5 mismatches and no corresponding valid entry. We will describe the File in Acquired Data search. and each typically has a different MD5 checksum.” Directories and registry entries are valid if they are present and invalid if they are not present.) 5 Searching The investigator can extract a subset of items from any of the three sections in the main window. Items that are not positively identified are listed under “Invalid.

Since there must always be at least one search term. P2P Marshal opens a search window. clicking on the minus sign (“-”) removes the corresponding search term.” In this case it is all MP3s greater than 6MB. MB. contains. does not begin with. The search terms consists of one or more items. coupled with "AND" Each search term has a pull-down menu that consists of the field name upon to search. For numeric fields. is not. size. The third input field is the term to match. Similarly. the menu consists of: file name. New terms can be created by clicking on the plus sign (“+”) button on the right side of the term. bytes(s). begins with. does not contain. it is any string. and directory. For example. two checkboxes allow the investigator to specify whether the search is to be case sensitive and whether to use a regular expression (both default to no). Figure 12 shows an example of two search terms linked by “AND.e. GB. download status. ends with. In the case of a file name or directory. the pulldown allows only the values that field can assume. there is no minus sign when there is only one search term. The next pull-down menu selects the type of matching to use.. i. like file name. The window consists of the search terms. the search scope. but there can be other text before 16 .1 Performing a Search When one of the Find items in the Tools menu is selected. file name allows the following search terms: is. sharing status. Also note that “is” is an exact match and “contains” means the searched string contains the term. and TB. In the case of the “File in Acquired Data” search. For fixed-value fields like download status. and does not end with. the control buttons. like size. modification time.P2P Marshal User Guide ATC-NY 5. the field accepts only numeric values. KB. and the results. For string searches. Figure 12: Two search terms. and a fourth field to the right contains the unit size.

“Generating a Report”). There are three control buttons. such as launching a shared file. as the search terms are evaluated in order from top-to-bottom.” indicating the peer-to-peer client the file. can be performed from the Search Results window.P2P Marshal User Guide ATC-NY or after the term. The investigator selects a search by clicking on a search listed in the top box. or log entry is associated with. Save for Report saves a copy of the current search results. The same operations that can be performed in the main window. such as Shared/Downloaded Files.2 Reviewing Searches All saved searches can be reviewed by selecting Review Searches under the Tools menu. peer. The Search Results table contains the same information present in the corresponding box in the main window. if the search has no name) of the each saved search.bmp AND size is at least 1 MB. 5. the results. based on the search terms. Most people will want to use “contains” for their searches. Search performs the specified search. (A or B and C generates different results from B and C or A. and an optional name. then the description is used. Each search has a description. “Reviewing Searches”) and included in the report (see Section 7.jpg OR file names ending with .) The search scope allows the Investigator to select whether the search should include just one client or all discovered clients. shown in Figure 13 17 . and whether it should include one user or all users. An example of a search would be file names ending with . The top box shows the name (or description. Note that order IS important. the date and time the search was saved. The bottom box shows the results from that search. a pull-down menu allows the terms to be linked by an “AND” or “OR” action. which can be reviewed later (see Section 4. “Installation. The middle box shows the description of the selected search. If no name is associated with the search. It has an additional column. If more than one search term has been created.

Selecting Delete will delete the selected search. 18 . shown in Figure 14. the user can associate a name with the search. Once the name is typed. shown in Figure 15. and then selecting Save. erasing the name in the text box. A text box will appear when Rename is selected. the investigator can then select Save to commit the change or Cancel to abort the name change. By selecting Rename.P2P Marshal User Guide ATC-NY Figure 13: Saved Search window (with a search selected) The investigator can rename or delete a selected search. The investigator can remove the associated name by selecting Rename.

P2P Marshal User Guide ATC-NY Figure 14: Renaming the saved search (via the "Rename" button) Figure 15: After renaming (via the "Save" button) 19 .

followed by a short description of the action in black. in gray. Figure 16 shows an example of the audit log showing the creation of a new acquisition. “Generating a Report”). followed by a detailed description of the action (and possibly the command line equivalent that was executed.P2P Marshal User Guide ATC-NY 6 P2P Marshal Audit Log P2P Marshal maintains an audit log of all significant activity performed by the Investigator. The log can be viewed by selecting View Log under the Tools menu. 20 . Figure 17 shows an example of an audit log showing the searches it performed. or copied/printed directly by right-clicking inside the window. Figure 16: Audit Log window. Each entry in the log consists of a timestamp in blue. if appropriate). Figure 17: Audit log showing searches that were performed The log can be included in the investigators report (see Section 7.

Similarly. 21 . In the first window. or group all users together within each discovered client. Report Data Selection. This will open a wizard window to guide the investigator through generating the report. If “Show data for selected users” is selected. there is a checkbox for each client. These will appear on the cover page of the report. and any optional comments. Figure 19 shows an example of selecting individual clients and users. Figure 18 shows an example of this. text and a logo image that will be included in the header on the report’s title page. the investigator can then select which users to include in the report (by clicking on the checkbox by each user’s name).P2P Marshal User Guide ATC-NY 7 Generating a Report The investigator selects Generate Report from the Tools menu to create a report. Report information. the investigator types in the name of the report. allowing the investigator to select which clients to include in the report. The investigator can also include. Figure 18: First page of Generate Report wizard In the second window. showing each client usage for each user. The Select all and Deselect all buttons are shortcuts to checking or un-checking all of the corresponding boxes. optionally. the investigator selects whether the report should be separated by user.

the list of downloaded and shared files. the investigator can select any saved searches to include.P2P Marshal User Guide ATC-NY Figure 19: Selecting individual users for the report Other checkbox options select whether the list of peers. the P2P Marshal audit log. and registry keys) that P2P Marshal found on the disk that allowed it to determine the presence of a particular client (see Section 4.4. Saved Searches. this page is skipped. This is shown in Figure 20. directories. and whether a list of all users. only valid installation artifacts are reported. If no searches were saved. “Installation Artifacts”). The installation artifacts represent the data (files. In the third window. and usage logs should be included. and installation artifacts should be included. Figure 20: Third page of Generate Report wizard 22 .

uTorrent.9 binary is present. Assumes user data is stored in “<User>/Local Settings/Application Data/Ares”.1 Ares • • • • Detects the presence of Ares if “Program Files/Ares/Ares.exe” is present*. P2P Marshal current supports PDF. Correctly identifies version if the 2. uTorrent. LimeWire. and Azereus. specifically Ares. HTML. either entering it in directly or by selecting the Browse button. we describe the support for each client in more detail. The investigator also specifies the file name and path to use for the report.0. 23 . P2P Marshal fully supports the analysis of BitTorrent. Below. Google Hello. Google Hello. and Kazaa.P2P Marshal User Guide ATC-NY In the fourth window. Displays files contained in “<User>/Local Settings/Application Data/Ares/My Shared Folder” as shared (default share location). the investigator selects the output format to use for the report. Finds peers from the CNodes. BitTorrent. Of these clients. LimeWire. Report Output.dat peer caches. shown in Figure 21. Kazaa. 8. P2P Marshal detects their presence and in some cases displays downloaded data if files are stored in the default location for that client. For the remaining clients.dat and SNodes. and RTF. Figure 21: Selecting the output format for the report 8 Supported Clients P2P Marshal supports the following clients: Ares. Azereus Vuze (Azereus 3+).

24 .5 binary is present.0-5. unless they are removed. All downloaded torrents have information cached in the “metadata” directory. complete files. Note that BitTorrent allows downloaded files to be saved to arbitrary locations on a per-download basis. The BitTorrent log file is also scanned for announcements that a connection to a tracker is established (these entries are by the torrent’s hash. BitTorrent 6 is identical to uTorrent. if it is on the active list). program-wide download directory are added as nonshared.4 Kazaa • Detects the presence of Kazaa if “Program Files/Kazaa/kazaa.2 BitTorrent • • • • • Detects the presence of BitTorrent if “Program Files/BitTorrent/bittorrent. • • • • 8.6).9 or 6. Downloads saved to a nondefault location will not be seen unless they are on the active-torrent list. These are added as non-bootstrap peers.exe” is present.0. except for installation and configuration paths. Files found in the default incomplete directory “<User>/Application Data/BitTorrent/incomplete” or the user-specified. Files associated with all “active” entries (items currently being downloaded or shared by BitTorrent) are added to the shared-file list as shared.5. 8.exe” is present*. not name) and for announcements that a torrent is initialized (occurs when the item is initially downloaded and each time BitTorrent launches. Correctly identifies version if the 6. program-wide incomplete directory are added as nonshared. incomplete files. Assumes user data is stored in “<User>/Local Settings/Application Data//Google/Hello”.0 binary is present.3 Google Hello • • • Detects the presence of Hello if “Program Files/Hello/Hello. It is handled by and has the same capabilities as the uTorrent module (See 8. Correctly identifies version if the 3. files found in the target directory are marked as complete. Correctly identifies version if 5.1 binary is present*. The BitTorrent log file is scanned for errors containing IP addresses (generated by other BitTorrent peers). which are added as bootstrap peers. this should be correct.exe” is present*. Generally. Files found in the working directory are marked as incomplete.2. These are scanned for BitTorrent tracker URLs. Any files found in the default download directory “<User>/My Documents/BitTorrent Downloads/” or the user-specified. Adds (as unshared) all files in the default storage directory “<User>/My Documents/My Pictures/Hello”. Assumes user data is stored in “<User>/Application Data/BitTorrent/”.0.P2P Marshal User Guide ATC-NY 8.

These are scanned for BitTorrent tracker URLs.10 binary is present.5 LimeWire • • • • Detects the presence of LimeWire if “Program Files/LimeWire/LimeWire. Files stored in the default download directory.12.exe” is present*. All downloaded torrents have information cached in the uTorrent directory. These are scanned for BitTorrent tracker URLs. Note that this client allows the user to save individual downloads to arbitrary locations. Incomplete entries are marked as such.7 Azureus Vuze (Azureus 3+) • • • • • • • Detects the presence of Azureus “Program Files/Azureus/Azureus. Files associated with all “active” entries (items currently being downloaded or shared by uTorrent) are added to the shared-file list as shared.14.2. Correctly identifies version if the 3. Assumes user data is stored in “<User>/Application Data/Azureus/”.0.12. complete files.exe” is present*. Correctly identifies version if a 4. Cached peers for active entries are added to the peer list as non-bootstrap peers. will be added as unshared. 8. The “shares” and “dht” information is currently ignored. (LimeWire 4.6a or 3.2 binaries are present.2 or 1. This client does not log events.) Assumes user data is stored in “<User>/Application Data/LimeWire/” or “<User>/.P2P Marshal User Guide ATC-NY 8. unless they are removed.5 binaries are present.6 uTorrent • • • • • • • Detects the presence of uTorrent if “Program Files/uTorrent/uTorrent. Correctly identifies version if the 1.0.exe” is present*.limewire” Lists cached peers stored in “gnutella. Information about downloaded and active entries stored by Azureus is used to add tracker peers and find downloaded files. 8. unless they are removed. The Azureus logs are scanned for log entries indicating the initiation of a download.0 . 25 . Files saved outside of the default directory that are not currently active will not be seen.7. We do not currently try to parse uTorrent’s stored data to look for DHT / PEX peers. Assumes user data is stored in “<User>/Application Data/uTorrent/”.0 released in June 2006.7. All downloaded torrents have information cached in the torrents directory. Uses LimeWire’s rules and users’ configurations to find and list shared and downloaded files. which are added as bootstrap peers.4. “<User>/My Documents/Downloads”.net”. which are added as bootstrap peers.1.

using this information. any files or directories found by examining peer-to-peer clients’ configuration data will be reported by P2P Marshal but inaccessible. an investigator can navigate manually to these files on the secondary drive. it does not contain the Windows. Running P2P Marshal on a drive that is not the root of a Windows installation – that is. If Windows and Documents and Settings are present. 11 License Agreement Important: Please read this License Agreement carefully before making the Program operable.1 • • • • Improved the registration process. even if all components of the peer-to-peer client are present. 26 . The full path of the file on the subject’s computer will be reported in the “Directory” column. If the Program Files directory is present. that accompanies this License. Updated uTorrent and BitTorrent 6 to handle the newer tracker list format. Fixed “Show in File Browser” to work properly on Windows Vista. ATC-NY 9 Version History 1. and this must be the root of the Windows installation. and Documents and Settings directories – will produce minimal results. No users will be found if the Documents and Settings directory is not present. CST and ATC are authorized to distribute the Program and to enter into a Software License Agreement with Licensees permitting the use of the Program. as well as associated documentation and help files (collectively called the "Program"). D:). P2P Marshal will detect the presence of installed peer-to-peer clients based on its contents.. This Software License Agreement is between CST. Program Files. P2P Marshal will also detect peer-to-peer clients based on registry keys. Changed the license terms. the installation status will be listed as “Partial”. Cyber Security Technologies Corporation (“CST” or “Licensor”) is the licensor from Architecture Technology Corporation (“ATC”) of the computer programs called P2P Marshal™ (P2P Marshal™).P2P Marshal User Guide * P2P Marshal also looks for other files in the same directory.g. 10 Known Issues If some components of an installed peer-to-peer client are of a version that P2P Marshal does not recognize. If files are stored on a secondary drive (e. ATC and you (“you” or “Licensee”). P2P Marshal can only examine one drive at a time. By making the Program operable you show your Agreement to the terms of this License.

non-sublicenseable license for Authorized Users to access and use the Program for Authorized Purposes only. the terms of the Modified License will govern. license. or allow any unauthorized users. to provide training to any third parties unless authorized in writing by CST. Licensee agrees to utilize and maintain all security. Licensee may not lease. access or other limitations on access as may be provided to assure only licensed access to the Program and will not distribute. sublicense or transfer any rights to use or access the Program other than as expressly provided herein. provided that Licensee reproduces all copyright and other proprietary notices that are on the original copy of the Program. or images or representations of the Program in any form or medium. In the event that Licensee is acquiring the Program pursuant to a master license. During the term of this License. No license terms granted by any reseller or distributor may vary the terms of this license. Terms: The following terms will have the definitions stated for all purposes of this License: Authorized Users: Licensee and its employees and agents are authorized to use the licensed Program. sell. Copy the Program once in machine-readable form for backup and archival purposes only in support of such use. Licensee may not use the Program. CST grants to Licensee a non-exclusive. 27 . CST grants the Licensee a non-exclusive License to use the Program as stated below. password. copy or allow non-licensed users to access or use the Program. Authorized Purposes: Licensee may use the Program for all lawful purposes and to analyze computer systems and images for which Licensee has lawful rights of access. Licensee may not use.P2P Marshal User Guide ATC-NY By clicking on the Accept button below. access. understands it. License Term/Termination: Licensee is granted a license to use the Program commencing on the date of the installation and registration of the Program on the Licensee’s computing platform. Subject to the terms and conditions of this License. on a single computer. redistribute. copy. and agrees to be bound by it. donate or in any other way transfer the Program to any other party. Licensee acknowledges that Licensee has read this agreement. corporate license or site license from CST (the “Modified License”). Licensee may not copy or transfer any portion of the Program to any other computer or storage device except for backup purposes as stated above. 1. to the extent that the terms of the Modified License differ from those in this License. The Licensee may: • • Install and use only one copy of the Program. 2. license. non-transferable.

title and interest to CST in such work. right or interest in the Program. enforceability. or assist others in contesting.) Licensee fails to comply with any provision of this License. or fraudulent manner. Licensee must promptly remove the Program from the computing platform upon which it is installed and destroy all copies of the Program and its documentation. (g) remove or attempt to remove any copyright notices or any other proprietary legends contained on or within the Program. No Additional Rights or Licenses: The Program is proprietary. The Program will remain the exclusive property of CST or its licensors or assigns. 6. Support and Maintenance: CST is under no obligation to provide maintenance. and other Limitations on License: Licensee will not: (a) decompile. defamatory. (e) permit access to the Program to anyone other than the Authorized Users. unless such use is expressly authorized by CST in writing. confidential and copyrighted. comprehend or copy the source code of the Program or otherwise reduce the Program to a human perceivable form. (b) copy the Program except as permitted in this License for backup purposes only.P2P Marshal User Guide ATC-NY This license continues in perpetuity unless terminated by the terms of this license agreement. (i) use CST’s name. 28 . Licensee may not use any trade or service marks or other proprietary or trade designation of CST without specific written authority. ownership or title of the program. Licensee has no claim. If you have acquired multiple licenses for the Program. All rights not otherwise granted herein are hereby reserved by CST and its licensors. This License may terminate early if a. (d) distribute the Program in any way or make the Program available on a service bureau or application service provider basis. upgrades and/or updates to the Program unless Licensee has entered into a Support and Maintenance Agreement with CST for this purpose and paid the thencurrent fees. the validity. 3. provide written certification to that effect upon CST’s request. or b. No Unauthorized Duplication/Modification or Reproduction of the Program. or in any illegal manner. (f) contest. Other than the rights granted in this License. or in any manner that infringes upon any third party intellectual property rights. if any. logo. decode. unless you have been authorized to do so in writing by CST. License Fees: Licensee is responsible for paying CST or the reseller from which Licensee purchased the Program the specified fees and applicable taxes for the license of the Program. disassemble. then at any time you may have only as many copies of the Program in use (plus backup copies as permitted by this License). 5. or other trademarks. translate or otherwise reverse engineer the Program. as you have valid and current licenses. (h) use the Program in any libelous. or make any attempt to discover.) Licensee terminates this License by destroying all copies of the Program and its documentation. (c) modify or create derivative works of the Program in whole or in part. and is protected internationally by copyright and other intellectual property law. CST shall own any derivative work created by Licensee or its agents or contractors and Licensee hereby assigns all right. contains trade secrets and other proprietary material of CST and its licensors. training. 4. and cease and desist from any further use of the Program. Upon termination. support.

9. CST does not warrant that the Program will meet your requirements or that the operation of the Program will be uninterrupted or that the Program will be error-free and expressly disclaims these and all other warranties for all versions of the Program. Independent Contractors: The parties to this License are independent contractors and are not agents or representatives of each other. title and interest in the Program. LOST DATA. INDIRECT. revisions. Waiver. EVEN IF CST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGES AND WHETHER OR NOT SUCH LOSS OR DAMAGES ARE FORESEEABLE. distributors.P2P Marshal User Guide ATC-NY 7. subject to the disclaimer of any failure of the Program due to the interaction with other software not owned or licensed by CST. such warranties are limited to an assurance that the Program will perform as specified for ninety (90) days. Ownership: Licensee acknowledges that the Program is a valuable asset and trade secret of CST. functionality. resellers. implied or statutory. or merchantability. its employees. and governed by and in accordance with the laws of the State of Minnesota. title. fitness for a particular purpose. Governing Law: This License shall be deemed to be made in the State of Minnesota and shall in all respects be interpreted. whether express. No oral or written information or advice given by CST. construed. its resellers. shall create a warranty or amend the scope of any warranty provided herein. and all modifications. fixes and other materials and the documentation delivered to Licensee shall be and remain the property of CST and/or its licensors. nor shall either party misstate or misrepresent its relationship hereunder. All rights. 12. IN NO EVENT SHALL THE LIABILITY OF CST EXCEED THE TOTAL AMOUNT RECEIVED BY CST FROM LICENSEE UNDER THIS AGREEMENT. OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM OR ANY DATA SUPPLIED THEREWITH. subject to the License granted hereunder. The Program is provided to Licensee “as is” and CST and its suppliers and licensors expressly disclaim any and all warranties and representations of any kind with regard to any subject matter of this Agreement. Entire Agreement. 8. 10. ITS DISTRIBUTORS OR ITS SUPPLIERS BE LIABLE TO LICENSEE OR TO ANY THIRD PARTY FOR ANY LOST PROFITS. Neither party shall have the power to bind the other. No oral or written information or advice of CST. INCIDENTAL. Warranty Disclaimer. agents or distributors. any warranty of non-infringement. including without limitation. This License contains the complete understanding between the parties with respect to the subject matter hereof. The parties agree that all disputes will be resolved by binding arbitration conducted according to the rules of the American Arbitration Association and venued in the State of Minnesota. dealers or agents shall increase the scope of the above warranties or create new warranties. OR OTHER SPECIAL. If any applicable law requires any warranties with respect to the Program. 11. INTERRUPTION OF BUSINESS. and supersedes all prior or 29 . Limitation of Remedies: IN NO EVENT WILL CST.

development. You acknowledge that the Program licensed under this License is subject to the export control laws and regulations of various countries. the Export Administration Regulations ("EAR"). Export. indemnify. or use of missiles or support of missiles projects. Licensee shall pay any taxes due from it as a result of its possession or use of the Program 15. employees and agents) harmless from and against any and all claims. 16. Taxes. you agree that you shall not export. whether oral or written. (ii) the design. assessments. governmental authorization. production. fines. You shall not. Licensee will defend. or transfer any Program subject to this License either directly or indirectly. directors. Department of Commerce or the list of "Specifically Designated Nationals and Blocked Persons" maintained by the U.S. including those of the United States. Audit.S. expenses 30 . distributors. liabilities. Indemnification. but are not limited to activities related to: (i) the design. production. production. CST shall be responsible for the costs and expenses related to such audit unless the audit reveals Licensee is in violation of this Agreement in which case Licensee shall be responsible for all reasonable costs and expenses associated with such audit. Office of Foreign Asset Controls.S. development. Department of Treasury. or use of nuclear materials. deficiencies. Licensee shall comply with all applicable laws and regulations restricting the export and re-export of the Program and shall not export or re-export the Program or media in any form without the appropriate government approval. costs and other affiliates. nuclear facilities. reexport. only. and sanctions regimes of the U. You will comply with all trade regulations and laws both foreign and domestic. Such activities include. to any country subject to a U. or nuclear weapons. The failure or delay of CST to exercise any of its rights under this License or upon any breach of this License shall not be deemed a waiver of those rights or of the breach. Licensee shall be solely responsible for all fees and expenses related to a permitted export or re-export of the Program. without prior U. and not limitation. and hold CST and its licensors.S. download or otherwise export. In addition. and (iii) the design. re-export or transfer the Program subject to this License to any person engaged in activities related to weapons of mass destruction. You agree that any varying or additional terms contained in any purchase order or other written notification or document issued by you in relation to the Program licensed hereunder shall be of no effect.P2P Marshal User Guide ATC-NY contemporaneous agreements or understandings. Department of Treasury. such as. 14. If CST has a reasonable basis to believe that Licensee is using the Program in violation of this License. or to any person or entity listed on the "Entity List" or "Denied Persons List" maintained by the U. losses. trade embargo as defined by applicable law in effect or to any resident or national of any such country. by way of example. 13. CST shall have the right to audit Licensee’s use of the Program during normal business hours.S. or use of chemical or biological weapons. damages. resellers (and each of their respective officers. judgments. No provision hereof shall be deemed waived or modified except in writing. development.

California 95054. and other countries. Inc.S. delivering packages.P2P Marshal User Guide ATC-NY (including reasonable attorneys' fees) arising from or relating to your use of or reliance upon the Program. but not limited to. Survivorship: Sections 3. Jini. embargo or to entities identified on U. Privacy Policy. U. and shall not allow any party on Licensee's behalf to. sending postal mail and e-mail. including. are strictly prohibited. providing marketing assistance. Export or reexport to countries subject to U. and iText.S. Solaris and J2SE are trademarks or registered trademarks of Sun Microsystems. 15. 4150 Network Circle. 1991.S. You also understand that CST may employ other companies to perform functions on our behalf. Binary Code License Agreement 31 . These companies may have access to personal information needed to perform their functions.Commercial software. 14. Nuclear. 10. 1991.1 Java License Copyright © 2007 Sun Microsystems. Inc.S. Sun Microsystems. 9. address. 13. attempt to reverse engineer or decompile the Program into another computer language.. standard license agreement and applicable provisions of the FAR and its supplements. Government users are subject to the Sun Microsystems. U. Licensee agrees that within that jurisdiction it shall not. and may not use such information for other purposes. 16. 12 Included software P2P Marshal uses and includes. missile. Eclipse. 17. JDOM. Java. 7. Export Control laws and may be subject to the export or import laws in other countries. the Sun logo. 12. This product is covered and controlled by U. the denied persons and specially designated nationals lists is strictly prohibited.A. All Government Rights . 19. 18 and 19 shall survive termination of this License however effected.S. 4. chemical biological weapons or nuclear maritime end uses or end users. such as fulfilling orders. unless or until your consent is obtained or to comply with applicable law. Third Party Web Sites. and processing credit card payments. Use is subject to license terms. Santa Clara. Inc. rights reserved. whether direct or indirect. Inc. such as your name. 11. in the U. Data Collection. 18. Notwithstanding anything herein. Licensee acknowledges and agrees that CST may collect and retain information about you. unmodified: Java 6 JRE. except as expressly and specifically provided in the EEC Council Directive 91/250/EEC of May 14. if the Program is lawfully acquired outside of the United States within a jurisdiction which is a member of the European Union subject to the EEC Council Directive 91/250/EEC of May 14. This distribution may include materials developed by third parties. BouncyCastle. export exclusion lists. 12.S. The EEC Council Directive 91/250/EEC. and e-mail address. Sun. 8. 17. Sun Microsystems.

BY DOWNLOADING OR INSTALLING THIS SOFTWARE. ALL EXPRESS OR IMPLIED CONDITIONS. Software is provided "AS IS". the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. "Programs" mean Java applets and applications intended to run on the Java Platform. Sun warrants to you that for a period of ninety (90) days from the date of purchase. DEFINITIONS. so the above may not apply to you. Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. header files. libraries. INC. logo or trade name of Sun or its licensors is granted under this Agreement. source files. YOU ACCEPT THE TERMS OF THE AGREEMENT. No right. any other machine readable materials (including. disclaims any express or implied warranty of fitness for such uses. Software is confidential and copyrighted. decompile. RESTRICTIONS. You acknowledge that Licensed Software is not designed or intended for use in the design. 5. Standard Edition (Java SE) on Java-enabled general purpose desktop computers and servers. 3. 2. operation or maintenance of any nuclear facility. Except for the foregoing. Subject to the terms and conditions of this Agreement. non-transferable. Some states do not allow limitations on duration of an implied warranty. UNLESS SPECIFIED IN THIS AGREEMENT.P2P Marshal User Guide for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6 SUN MICROSYSTEMS. or reverse engineer Software. you may not modify. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. and any user manuals. Inc. SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE. EXCEPT TO THE ATC-NY 32 . IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS. but not limited to. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). Unless enforcement is prohibited by applicable law. programming guides and other documentation provided to you by Sun under this Agreement. service mark. including. INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY. 4. This limited warranty gives you specific legal rights. limited license without license fees to reproduce and use internally Software complete and unmodified for the sole purpose of running Programs. "Software" means the identified above in binary form. as evidenced by a copy of the receipt. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms. construction. REPRESENTATIONS AND WARRANTIES. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE AGREEMENT. any updates or error corrections provided by Sun. PLEASE READ THE AGREEMENT CAREFULLY. LICENSE TO USE. LIMITED WARRANTY. FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED. 1. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms. but not limited to the Java Technology Restrictions of the Supplemental License Terms. DISCLAIMER OF WARRANTY. Sun grants you a non-exclusive. You may have others. title or interest in or to any trademark. Sun Microsystems. and data files). Any implied warranties on the Software are limited to 90 days. which vary from state to state.

ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE. Any use you make of the Sun Marks inures to Sun's benefit. unless omission would frustrate the intent of the parties. Government or by a U. 13. 8. JAVA.101 and 12. 6. 9. SOLARIS. TERMINATION. TO THE EXTENT NOT PROHIBITED BY LAW. You acknowledge and agree as between you and Sun that Sun owns the SUN. This Agreement is effective until terminated.212 (for non-DOD acquisitions). in which case this Agreement will immediately terminate. tort (including negligence). EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. JAVA. This Agreement is the entire agreement ATC-NY 33 . All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. exceed the amount paid by you for Software under this Agreement. Any action related to this Agreement will be governed by California law and controlling U. INDIRECT. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE. 12. Either party may terminate this Agreement immediately should any Software become. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. re-export. 10. or import as may be required after delivery to you. TRADEMARKS AND LOGOS. INTEGRATION. and iPLANET trademarks and all SUN.S.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2. or otherwise. service marks. this Agreement will remain in effect with the provision omitted. INCIDENTAL OR PUNITIVE DAMAGES. U.com/policies/trademarks. PROFIT OR DATA. If any provision of this Agreement is held to be unenforceable. Some states do not allow the exclusion of incidental or consequential damages. and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.S. GOVERNING LAW.S. SEVERABILITY. 7. federal law. so some of the terms above may not be applicable to you. Government prime contractor or subcontractor (at any tier). whether in contract. then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement. FORTE. OR FOR SPECIAL. 11. SOLARIS. No choice of law rules of any jurisdiction will apply. CONSEQUENTIAL. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export. GOVERNMENT RESTRICTED RIGHTS.7201 through 227. Upon Termination. and iPLANET-related trademarks.P2P Marshal User Guide EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. JINI. EXPORT REGULATIONS. If Software is being acquired by or on behalf of the U. You may terminate this Agreement at any time by destroying all copies of Software. In no event will Sun's liability to you. HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY. JINI. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. or in either party's opinion be likely to become.S.sun. the subject of a claim of infringement of any intellectual property right. FORTE. you must destroy all copies of Software. this is in accordance with 48 CFR 227. logos and other brand designations ("Sun Marks"). LIMITATION OF LIABILITY.

non-transferable. or authorize your licensees to create. and (vi) you agree to defend and indemnify Sun and its licensors from and C.txt file. (ii) the Programs add significant and primary functionality to the Software. but not limited to the Java Technology Restrictions of these Supplemental Terms. (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement. "javax". No modification of this Agreement will be binding. your Programs. Source Code. Third Party Code. It supersedes all prior or contemporaneous oral or written communications.P2P Marshal User Guide between you and Sun relating to its subject matter. but not limited to the Java Technology Restrictions of these Supplemental Terms. order. limited license without fees to reproduce and distribute the Software. Source code may not be redistributed unless expressly provided for in this Agreement. unless expressly licensed for other purposes. or change the behavior of. Java Technology Restrictions. Sun grants you a non-exclusive. is provided solely for reference purposes pursuant to the terms of this Agreement. or change the behavior of. These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Binary Code License Agreement. the disclaimer of ATC-NY 34 . representations and warranties and prevails over any conflicting or additional terms of any quote. acknowledgment. modify. SUPPLEMENTAL LICENSE TERMS These Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. or other communication between the parties relating to its subject matter during the term of this Agreement. including. developing. including. proposals. non-transferable. You may not create. E. D. (iv) you do not remove or alter any proprietary legends or notices contained in the Software. Sun grants you a non-exclusive. In addition to any terms and conditions of any third party opensource/freeware license identified in the THIRDPARTYLICENSEREADME. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement . interfaces. or subpackages that are in any way identified as "java". modify. classes. and for the sole purpose of running. and testing your Programs. or in any license contained within the Software. License to Distribute Software. (iii) you do not distribute additional software intended to replace any component(s) of the Software. provided that (i) you distribute the Software complete and unmodified and only bundled as part of.txt file. B. "sun" or similar convention as specified by Sun in any naming convention designation. limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing. Software may contain source code that. Software Internal Use and Development License Grant. A. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file incorporated herein by reference. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME. unless in writing and signed by an authorized representative of each party.

Sun does not associate the data with personally identifiable information. in source code and object code form. or in either party's opinion be likely to become.S. You can find more information about the data Sun collects at http://java. "Recipient" means anyone who receives the Program under this Agreement. ATC-NY 12. worldwide. including all Contributors.A. and (ii) are not derivative works of the Program. 1. Inc. 35 .2 Eclipse License THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). The Software's installation and auto-update processes transmit a limited amount of data to Sun (or its service provider) about those specific processes to help Sun understand and optimize them. "Contributor" means any person or entity that distributes the Program.com/data/. the initial code and documentation distributed under this Agreement. G. and ii)additions to the Program. publicly display. the subject of a claim of infringement of any intellectual property right. if any. REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT’S ACCEPTANCE OF THIS AGREEMENT. 4150 Network Circle. Either party may terminate this Agreement immediately should any Software become. Santa Clara. Installation and Auto-Update. F. and such derivative works. and b) in the case of each subsequent Contributor: i)changes to the Program. Termination for Infringement.P2P Marshal User Guide warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution. 2. California 95054. GRANT OF RIGHTS a) Subject to the terms of this Agreement. For inquiries please contact: Sun Microsystems. prepare derivative works of. "Program" means the Contributions distributed in accordance with this Agreement. where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement. ANY USE.. distribute and sublicense the Contribution of such Contributor. each Contributor hereby grants Recipient a non-exclusive. U. DEFINITIONS "Contribution" means: a) in the case of the initial Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor’s behalf. "Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. publicly perform. royalty-free copyright license to reproduce.

and b) a copy of this Agreement must be included with each copy of the Program. Contributors may not remove or alter any copyright notices contained within the Program. no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. incidental and consequential damages. worldwide. provided that: a) it complies with the terms and conditions of this Agreement. d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution. in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. if any. and iv) states that source code for the Program is available from such Contributor. COMMERCIAL DISTRIBUTION 36 . iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party. if any. each Contributor hereby grants Recipient a non-exclusive. and b) its license agreement: i) effectively disclaims on behalf of all Contributors all warranties and conditions. royalty-free patent license under Licensed Patents to make. This patent license shall apply to the combination of the Contribution and the Program if. and implied warranties or conditions of merchantability and fitness for a particular purpose. including direct. ii) effectively excludes on behalf of all Contributors all liability for damages. express and implied. and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange. indirect. if any.P2P Marshal User Guide ATC-NY b) Subject to the terms of this Agreement. import and otherwise transfer the Contribution of such Contributor. When the Program is made available in source code form: a) it must be made available under this Agreement. offer to sell. 4. including warranties or conditions of title and non-infringement. in source code and object code form. use. if any. such as lost profits. it is Recipient’s responsibility to acquire that license before distributing the Program. to grant the copyright license set forth in this Agreement. if a third party patent license is required to allow Recipient to distribute the Program. at the time the Contribution is added by the Contributor. No hardware per se is licensed hereunder. For example. Each Contributor must identify itself as the originator of its Contribution. sell. As a condition to exercising the rights and licenses granted hereunder. such addition of the Contribution causes such combination to be covered by the Licensed Patents. c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein. each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed. REQUIREMENTS A Contributor may choose to distribute the Program in object code form under its own license agreement. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. special. The patent license shall not apply to any other combinations which include the Contribution. 3.

business partners and the like. and if a court requires any other Contributor to pay any damages as a result. damage to or loss of data. If that Commercial Contributor then makes performance claims. programs or equipment. GENERAL If any provision of this Agreement is invalid or unenforceable under applicable law. a Contributor might include the Program in a commercial product offering. 5. For example. If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient’s patent(s). While this license is intended to facilitate the commercial use of the Program. SPECIAL. Therefore. Recipient agrees to cease use and 37 . those performance claims and warranties are such Commercial Contributor’s responsibility alone. If all Recipient’s rights under this Agreement terminate.P2P Marshal User Guide ATC-NY Commercial distributors of software may accept certain responsibilities with respect to end users. and b) allow the Commercial Contributor to control. NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT. including but not limited to the risks and costs of program errors. and without further action by the parties hereto. Product X. WHETHER IN CONTRACT. then such Recipient’s rights granted under Section 2(b) shall terminate as of the date such litigation is filed. the Commercial Contributor must pay those damages. All Recipient’s rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. That Contributor is then a Commercial Contributor. NON-INFRINGEMENT. and cooperate with the Commercial Contributor in. STRICT LIABILITY. EITHER EXPRESS OR IMPLIED INCLUDING. The Indemnified Contributor may participate in any such claim at its own expense. 7. INDIRECT. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. ANY WARRANTIES OR CONDITIONS OF TITLE. compliance with applicable laws. DISCLAIMER OF LIABILITY EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT. EXEMPLARY. or offers warranties related to Product X. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement . OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER. OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS). THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS. INCIDENTAL. In order to qualify. Under this section. the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties. WITHOUT LIMITATION. NO WARRANTY EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT. the defense and any related settlement negotiations. 6. the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim. and unavailability or interruption of operations. such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses. damages and costs (collectively "Losses") arising from claims. if a Contributor includes the Program in a commercial product offering. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. it shall not affect the validity or enforceability of the remainder of the terms of this Agreement. lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering.

No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. with or without modification. Except as expressly stated in Sections 2(a) and 2(b) above. 3. All rights reserved. STRICT LIABILITY. Redistributions of source code must retain the above copyright notice. nor may "JDOM" appear in their name. OR CONSEQUENTIAL DAMAGES (INCLUDING. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. by implication. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. INCLUDING. whether expressly. In addition. Each party waives its rights to a jury trial in any resulting litigation. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT.P2P Marshal User Guide ATC-NY distribution of the Program as soon as reasonably practicable. we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following: "This product includes software developed by the JDOM Project (http://www. the acknowledgment may be graphical using the logos available at http://www.org/images/logos. after a new version of the Agreement is published. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. WHETHER IN CONTRACT. without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>. Redistribution and use in source and binary forms. Products derived from this software may not be called "JDOM". OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT 38 . The Eclipse Foundation is the initial Agreement Steward. Redistributions in binary form must reproduce the above copyright notice. and the following disclaimer. DATA. 2. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.3 JDOM License Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.jdom." Alternatively.jdom. INCIDENTAL. BUT NOT LIMITED TO. In addition. OR PROFITS. this list of conditions. INDIRECT. please contact <request_AT_jdom_DOT_org>. All rights in the Program not expressly granted under this Agreement are reserved. 12. this list of conditions. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES. Everyone is permitted to copy and distribute copies of this Agreement. SPECIAL. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. However. BUT NOT LIMITED TO. but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. 4. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. LOSS OF USE. and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution. EXEMPLARY.org/). estoppel or otherwise. Contributor may elect to distribute the Program (including its Contributions) under the new version. Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement. For written permission. are permitted provided that the following conditions are met: 1. Recipient’s obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.

unmodified. You may obtain a copy of the License at http://www. a free JAVA-PDF library'. in which case the provisions of LGPL are applicable instead of those above. The Original Code is 'iText. 2001. DAMAGES OR OTHER LIABILITY. merge. 2000. and/or sell copies of the Software. All Rights Reserved. either express or implied.bouncycastle. free of charge. 2002 by Bruno Lowagie. subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Co-Developer of the code is Paulo Soares. sublicense.2006 The Legion Of The Bouncy Castle (http://www. EXPRESS OR IMPLIED. Contributor(s): all the names of the contributors are added in the source code where applicable. 12. Portions created by the Initial Developer are Copyright (C) 1999. Portions created by the Co-Developer are Copyright (C) 2000.org) Permission is hereby granted. For more information ATC-NY on the JDOM Project.4 BouncyCastle License Copyright (c) 2000 .org/>. 2002 by Bruno Lowagie. you may not use this file except in compliance with the License. This library is free software. If you wish to allow use of your version of this file only under the terms of the LGPL License and not to allow others to use your version of this file under the MPL. distribute. WHETHER IN AN ACTION OF CONTRACT. Copyright 1999.jdom. All Rights Reserved. Alternatively. a recipient may use your version of this file under either the MPL or the GNU LIBRARY GENERAL PUBLIC LICENSE. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. WITHOUT WARRANTY OF ANY KIND. This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. 2000. See the License for the specific language governing rights and limitations under the License. ARISING FROM. THE SOFTWARE IS PROVIDED "AS IS". The Initial Developer of the Original Code is Bruno Lowagie. publish. 2001. and to permit persons to whom the Software is furnished to do so. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.1).mozilla. please see <http://www. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM.5 iText License The iText library is included. copy. under the Mozilla Public License (MPL 1. WITHOUT WARRANTY OF ANY KIND.P2P Marshal User Guide OF THE USE OF THIS SOFTWARE. TORT OR OTHERWISE. to any person obtaining a copy of this software and associated documentation files (the "Software"). 2001. you can redistribute it and/or modify it 39 . If you do not delete the provisions above. indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the LGPL. The contents of this file are subject to the Mozilla Public License Version 1. 2002 by Paulo Soares. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY. the contents of this file may be used under the terms of the LGPL license (the "GNU LIBRARY GENERAL PUBLIC LICENSE"). including without limitation the rights to use.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis. 12. modify. to deal in the Software without restriction.1 (the "License").

See the GNU Library general Public License for more details. without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. or any later version. This library is distributed in the hope that it will be useful. either version 2 of the License. ATC-NY 40 . but WITHOUT ANY WARRANTY.P2P Marshal User Guide under the terms of the MPL as stated above or under the terms of the GNU Library General Public License as published by the Free Software Foundation.

Sign up to vote on this title
UsefulNot useful