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 ATC-NY

Table of Contents

1 Summary of Features .................................................................................................. 4

2 Requirements .............................................................................................................. 4
3 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

2
P2P Marshal User Guide ATC-NY

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.

3
P2P Marshal User Guide ATC-NY

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.

4
P2P Marshal User Guide ATC-NY

Figure 1: When P2P Marshal is first launched

4 Starting an acquisition
When P2P Marshal starts, the investigator can either create a new investigation or open
an existing one, using the File menu or the icons below the menu bar.

4.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. On the first page, Acquisition Information,
shown in Figure 2, the investigator enters information about the case, such as case
number, acquisition name (in case there are multiple acquisitions, i.e., disks to analyze,
associated with a case), and investigator’s name. The investigator also selects the
location where data will be stored. The location can be typed directly into the text box or
the “browse” button can be used to navigate directories (and create them), shown in
Figure 3. We recommend creating a new directory for each acquisition. Storing a new
acquisition in a directory that already contains an acquisition will first delete the contents
of the directory.
5
P2P Marshal User Guide ATC-NY

Figure 2: First page of the New Acquisition wizard

6
P2P Marshal User Guide ATC-NY

Figure 3: Selecting a location for the acquisition (the “Browse...” button)

On the second page, Location to be Analyzed, the investigator selects the target disk to be
analyzed. This can either be a logical drive (e.g., “D:” or “E:”), shown in Figure 4, or a
subdirectory where a disk image has been restored, shown in Figure 5. Note that the
logical drive can correspond to a physical disk, such as a USB disk, or a disk image
mounted by a third party program, such as Mount Image Pro or VMware-mount.

7
P2P Marshal User Guide ATC-NY

Figure 4: Selecting a logical drive for a new acquisition

8
P2P Marshal User Guide ATC-NY

Figure 5: Selecting a sub-directory for a new acquisition

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

9
P2P Marshal User Guide ATC-NY

Figure 6: Selecting target mount point

Once the location and mount point are specified, the investigator selects the “Finish”
button and P2P Marshal performs the analysis.

4.2 Opening an existing acquisition

Investigators can also open an existing acquisition. 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.

4.3 The Main P2P Marshal Window

The main P2P Marshal window consists of two parts: the case information, displayed at
the top, and the peer-to-peer application information, displayed as several tabs—one tab
for each peer-to-peer application found. Selecting a different tab selects a different peer-
to-peer client and displays information about it. The tab is labeled with the program
name and its icon and shows the version number and installation directory when the

10
P2P Marshal User Guide ATC-NY

mouse “hovers” over the tab. Figure 7 shows the main window with several tabs open
corresponding to six different clients.

Figure 7: After acquisition is finished

Each tab consists of two parts. The first part, Installation Information, describes
information about the client software, specifically the name, installation location, version,
and installation status. If P2P Marshal can determine the exact version, that value is
displayed (e.g., “4.14.8”), otherwise it displays the range of versions that match the
program, (e.g., “3.0.1.4-3.0.1.6a”). The installation status will be either “Partial” or
“Full”; the former indicates some components of the program (executable, libraries, etc.)
are missing, and the latter indicates all components were present. Clicking on the
installation status will open the Installation Artifacts window for that client (see Section
4.4, “Installation Artifacts”).

The second part of the window, Usage Information, describes how that client was used.
The first section allows the investigator to select which user’s information to report via a
pull-down menu. “All Users Combined” shows information for all users. If only one
user’s information exists, then the name will be listed and no selection box is displayed.
Figure 8 shows an example of a drop down menu showing three users for a client.

11
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.
The number of files displayed in the Shared/Downloaded Files section has been
significantly reduced. (Counts for each table are shown on the right-hand side of the
window.)

12
P2P Marshal User Guide ATC-NY

Figure 9: After selecting one user

Below the user selection is the Shared/Downloaded Files section. This window displays
files that were either downloaded or shared. Information fields include sharing status,
download status, file size, last modification time, directory in which the file is located,
and user associated with the file. Scroll bars are present as needed. Clicking on a
column heading will sort the list according to that column. Columns can be reordered
and resized, if desired, by clicking and dragging the column headings. A file can be
selected by clicking on its row. 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.g., .doc, .jpg, .wmv). Double-clicking on the file will also launch the appropriate
viewer.

The list of Peer Servers is next, and includes the name or IP address of any peer
computer found in the configuration, cache, or log files for that client. Note that no name
resolution is performed, 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, called supernodes,
trackers, etc. by the software), the last contact time, if available, and the user who
communicated with the peer server.

13
P2P Marshal User Guide ATC-NY

Below that is the Usage Log, if the client software maintained a log file. This includes
the log message and the date and time it was generated. If the client maintains no log,
this table is not present.

Finally, some programs (such as LimeWire) keep additional information, such as when
the last session ended, the Client’s ID, and total connection and run time. If present,
these are displayed at the bottom of the window. Figure 10 shows an example of a client
with extra information.

Figure 10: A tab showing additional client-specific information

4.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, shown in Figure 11. This window displays the directories, files, and
registry keys that P2P Marshal searched for to determine if a peer-to-peer client is present
on the examined system.

14
P2P Marshal User Guide ATC-NY

Figure 11: Installation Artifacts window

Positively-identified items are listed under the “Valid” section for a particular peer-to-
peer client, as well as the version or range of versions associated with that item. Items
that are not positively identified are listed under “Invalid.” Directories and registry
entries are valid if they are present and invalid if they are not present. Files can have a
specified MD5 checksum that serves to identify different software versions. If a file is
present but the MD5 checksum of that file does not match the specified value, it is listed
as invalid with a note, “md5 mismatch.” If the file is not present at all, the note is “not
present.” Each valid file will likely have multiple invalid entries that are MD5
mismatches because P2P Marshal knows about multiple versions of each client, and each
typically has a different MD5 checksum. If there are many entries for a file that are MD5
mismatches and no corresponding valid entry, the file is from a version of the software
that P2P Marshal does not recognize. (The primary purpose of this version of the
Installation Artifacts window is to verify P2P Marshal’s determination of installed client
software.)

5 Searching
The investigator can extract a subset of items from any of the three sections in the main
window, specifically, Shared/Downloaded Files, Peer Servers, and Usage Log, by using
the search options under the Tools menu. We will describe the File in Acquired Data
search. The two other searches (Network Host in Acquired Data and Log Entry in
Acquired Data) operate similarly.

15
P2P Marshal User Guide ATC-NY

5.1 Performing a Search

When one of the Find items in the Tools menu is selected, P2P Marshal opens a search
window. The window consists of the search terms, the search scope, the control buttons,
and the results.

The search terms consists of one or more items. New terms can be created by clicking on
the plus sign (“+”) button on the right side of the term. Similarly, clicking on the minus
sign (“-”) removes the corresponding search term. Since there must always be at least
one search term, there is no minus sign when there is only one search term. Figure 12
shows an example of two search terms linked by “AND.” In this case it is all MP3s
greater than 6MB.

Figure 12: Two search terms, coupled with "AND"

Each search term has a pull-down menu that consists of the field name upon to search. In
the case of the “File in Acquired Data” search, the menu consists of: file name, sharing
status, download status, size, modification time, and directory. The next pull-down menu
selects the type of matching to use. For example, file name allows the following search
terms: is, contains, is not, does not contain, begins with, ends with, does not begin with,
and does not end with. The third input field is the term to match. In the case of a file
name or directory, it is any string. For fixed-value fields like download status, the pull-
down allows only the values that field can assume. For numeric fields, like size, the field
accepts only numeric values, and a fourth field to the right contains the unit size, i.e.,
bytes(s), KB, MB, GB, and TB. For string searches, like file name, 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). Also note that “is” is an exact match and
“contains” means the searched string contains the term, but there can be other text before
16
P2P Marshal User Guide ATC-NY

or after the term. Most people will want to use “contains” for their searches. If more
than one search term has been created, a pull-down menu allows the terms to be linked by
an “AND” or “OR” action. Note that order IS important, as the search terms are
evaluated in order from top-to-bottom. (A or B and C generates different results from B
and C or A.)

The search scope allows the Investigator to select whether the search should include just
one client or all discovered clients, and whether it should include one user or all users.

There are three control buttons. Search performs the specified search. Save for Report
saves a copy of the current search results, which can be reviewed later (see Section 4,
“Reviewing Searches”) and included in the report (see Section 7, “Generating a Report”).

The Search Results table contains the same information present in the corresponding box
in the main window, such as Shared/Downloaded Files. It has an additional column,
“Installation,” indicating the peer-to-peer client the file, peer, or log entry is associated
with. The same operations that can be performed in the main window, such as launching
a shared file, can be performed from the Search Results window.

An example of a search would be file names ending with .jpg OR file names ending with
.bmp AND size is at least 1 MB.

5.2 Reviewing Searches

All saved searches can be reviewed by selecting Review Searches under the Tools menu.
Each search has a description, based on the search terms, the results, the date and time the
search was saved, and an optional name. If no name is associated with the search, then
the description is used.

The top box shows the name (or description, if the search has no name) of the each saved
search. The middle box shows the description of the selected search. The bottom box
shows the results from that search. The investigator selects a search by clicking on a
search listed in the top box, shown in Figure 13

17
P2P Marshal User Guide ATC-NY

Figure 13: Saved Search window (with a search selected)

The investigator can rename or delete a selected search. By selecting Rename, the user
can associate a name with the search. A text box will appear when Rename is selected,
shown in Figure 14. Once the name is typed, the investigator can then select Save to
commit the change or Cancel to abort the name change. The investigator can remove the
associated name by selecting Rename, erasing the name in the text box, and then
selecting Save, shown in Figure 15. Selecting Delete will delete the selected search.

18
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
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. Each
entry in the log consists of a timestamp in blue, followed by a short description of the
action in black, followed by a detailed description of the action (and possibly the
command line equivalent that was executed, if appropriate), in gray. Figure 16 shows an
example of the audit log showing the creation of a new acquisition. Figure 17 shows an
example of an audit log showing the searches it performed.

Figure 16: Audit Log window.

Figure 17: Audit log showing searches that were performed

The log can be included in the investigators report (see Section 7, “Generating a
Report”), or copied/printed directly by right-clicking inside the window.

20
P2P Marshal User Guide ATC-NY

7 Generating a Report
The investigator selects Generate Report from the Tools menu to create a report. This
will open a wizard window to guide the investigator through generating the report.

In the first window, Report information, the investigator types in the name of the report,
and any optional comments. These will appear on the cover page of the report. The
investigator can also include, optionally, text and a logo image that will be included in
the header on the report’s title page. Figure 18 shows an example of this.

Figure 18: First page of Generate Report wizard

In the second window, Report Data Selection, the investigator selects whether the report
should be separated by user, showing each client usage for each user, or group all users
together within each discovered client. If “Show data for selected users” is selected, the
investigator can then select which users to include in the report (by clicking on the
checkbox by each user’s name). Similarly, there is a checkbox for each client, allowing
the investigator to select which clients to include in the report. The Select all and
Deselect all buttons are shortcuts to checking or un-checking all of the corresponding
boxes. Figure 19 shows an example of selecting individual clients and users.

21
P2P Marshal User Guide ATC-NY

Figure 19: Selecting individual users for the report

Other checkbox options select whether the list of peers, the list of downloaded and shared
files, and usage logs should be included, and whether a list of all users, the P2P Marshal
audit log, and installation artifacts should be included. The installation artifacts represent
the data (files, directories, 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, “Installation
Artifacts”); only valid installation artifacts are reported.

In the third window, Saved Searches, the investigator can select any saved searches to
include. This is shown in Figure 20. If no searches were saved, this page is skipped.

Figure 20: Third page of Generate Report wizard

22
P2P Marshal User Guide ATC-NY

In the fourth window, Report Output, the investigator selects the output format to use for
the report, shown in Figure 21. P2P Marshal current supports PDF, HTML, and RTF.
The investigator also specifies the file name and path to use for the report, either entering
it in directly or by selecting the Browse button.

Figure 21: Selecting the output format for the report

8 Supported Clients
P2P Marshal supports the following clients: Ares, BitTorrent, Google Hello, Kazaa,
LimeWire, uTorrent, Azereus Vuze (Azereus 3+). Of these clients, P2P Marshal fully
supports the analysis of BitTorrent, LimeWire, uTorrent, and Azereus. For the remaining
clients, specifically Ares, Google Hello, and Kazaa, P2P Marshal detects their presence
and in some cases displays downloaded data if files are stored in the default location for
that client. Below, we describe the support for each client in more detail.

8.1 Ares

• Detects the presence of Ares if “Program Files/Ares/Ares.exe” is present*.

Correctly identifies version if the 2.0.9 binary is present.
• Assumes user data is stored in “<User>/Local Settings/Application Data/Ares”.
• Finds peers from the CNodes.dat and SNodes.dat peer caches.
• Displays files contained in “<User>/Local Settings/Application Data/Ares/My
Shared Folder” as shared (default share location).

23
P2P Marshal User Guide ATC-NY

8.2 BitTorrent

• Detects the presence of BitTorrent if “Program Files/BitTorrent/bittorrent.exe” is

present*. Correctly identifies version if 5.0.0-5.0.9 or 6.0 binary is present.
• Assumes user data is stored in “<User>/Application Data/BitTorrent/”.
• All downloaded torrents have information cached in the “metadata” directory,
unless they are removed. These are scanned for BitTorrent tracker URLs, which
are added as bootstrap peers.
• The BitTorrent log file is scanned for errors containing IP addresses (generated by
other BitTorrent peers). These are added as non-bootstrap peers.
• 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, not name) and for
announcements that a torrent is initialized (occurs when the item is initially
downloaded and each time BitTorrent launches, if it is on the active list).
• Files associated with all “active” entries (items currently being downloaded or
shared by BitTorrent) are added to the shared-file list as shared. Files found in the
working directory are marked as incomplete; files found in the target directory are
marked as complete. Generally, this should be correct.
• Any files found in the default download directory “<User>/My
Documents/BitTorrent Downloads/” or the user-specified, program-wide
download directory are added as nonshared, complete files. Files found in the
default incomplete directory “<User>/Application Data/BitTorrent/incomplete” or
the user-specified, program-wide incomplete directory are added as nonshared,
incomplete files.
• Note that BitTorrent allows downloaded files to be saved to arbitrary locations on
a per-download basis. Downloads saved to a nondefault location will not be seen
unless they are on the active-torrent list.
• BitTorrent 6 is identical to uTorrent, except for installation and configuration
paths. It is handled by and has the same capabilities as the uTorrent module (See
8.6).

8.3 Google Hello

• Detects the presence of Hello if “Program Files/Hello/Hello.exe” is present.

Correctly identifies version if the 6.5.1 binary is present*.
• Assumes user data is stored in “<User>/Local Settings/Application
Data//Google/Hello”.
• Adds (as unshared) all files in the default storage directory “<User>/My
Documents/My Pictures/Hello”.

8.4 Kazaa

• Detects the presence of Kazaa if “Program Files/Kazaa/kazaa.exe” is present*.

Correctly identifies version if the 3.2.5 binary is present.

24
P2P Marshal User Guide ATC-NY

8.5 LimeWire

• Detects the presence of LimeWire if “Program Files/LimeWire/LimeWire.exe” is

present*. Correctly identifies version if a 4.12.0 - 4.14.10 binary is present.
(LimeWire 4.12.0 released in June 2006.)
• Assumes user data is stored in “<User>/Application Data/LimeWire/” or
“<User>/.limewire”
• Lists cached peers stored in “gnutella.net”.
• Uses LimeWire’s rules and users’ configurations to find and list shared and
downloaded files.

8.6 uTorrent

• Detects the presence of uTorrent if “Program Files/uTorrent/uTorrent.exe” is

present*. Correctly identifies version if the 1.7.2 or 1.7.5 binaries are present.
• Assumes user data is stored in “<User>/Application Data/uTorrent/”.
• All downloaded torrents have information cached in the uTorrent directory, unless
they are removed. These are scanned for BitTorrent tracker URLs, which are
added as bootstrap peers.
• Files associated with all “active” entries (items currently being downloaded or
shared by uTorrent) are added to the shared-file list as shared. Incomplete entries
are marked as such.
• Files stored in the default download directory, “<User>/My
Documents/Downloads”, will be added as unshared, complete files.
• Note that this client allows the user to save individual downloads to arbitrary
locations. Files saved outside of the default directory that are not currently active
will not be seen.
• This client does not log events. We do not currently try to parse uTorrent’s stored
data to look for DHT / PEX peers.

8.7 Azureus Vuze (Azureus 3+)

• Detects the presence of Azureus “Program Files/Azureus/Azureus.exe” is

present*. Correctly identifies version if the 3.0.1.6a or 3.0.2.2 binaries are present.
• Assumes user data is stored in “<User>/Application Data/Azureus/”.
• All downloaded torrents have information cached in the torrents directory, unless
they are removed. These are scanned for BitTorrent tracker URLs, which are
added as bootstrap peers.
• Information about downloaded and active entries stored by Azureus is used to add
tracker peers and find downloaded files.
• Cached peers for active entries are added to the peer list as non-bootstrap peers.
• The “shares” and “dht” information is currently ignored.
• The Azureus logs are scanned for log entries indicating the initiation of a
download.

25
P2P Marshal User Guide ATC-NY

* P2P Marshal also looks for other files in the same directory.

9 Version History
1.1

• Improved the registration process.

• Changed the license terms.
• Updated uTorrent and BitTorrent 6 to handle the newer tracker list format.
• Fixed “Show in File Browser” to work properly on Windows Vista.

10 Known Issues
If some components of an installed peer-to-peer client are of a version that P2P Marshal
does not recognize, the installation status will be listed as “Partial”, even if all
components of the peer-to-peer client are present.

Running P2P Marshal on a drive that is not the root of a Windows installation – that is, it
does not contain the Windows, Program Files, and Documents and Settings directories –
will produce minimal results. If the Program Files directory is present, P2P Marshal will
detect the presence of installed peer-to-peer clients based on its contents. If Windows and
Documents and Settings are present, P2P Marshal will also detect peer-to-peer clients
based on registry keys. No users will be found if the Documents and Settings directory is
not present.

P2P Marshal can only examine one drive at a time, and this must be the root of the
Windows installation. If files are stored on a secondary drive (e.g., D:), any files or
directories found by examining peer-to-peer clients’ configuration data will be reported
by P2P Marshal but inaccessible. The full path of the file on the subject’s computer will
be reported in the “Directory” column; using this information, an investigator can
navigate manually to these files on the secondary drive.

11 License Agreement
Important: Please read this License Agreement carefully before making the Program
operable. By making the Program operable you show your Agreement to the terms of
this License.

Cyber Security Technologies Corporation (“CST” or “Licensor”) is the licensor from

Architecture Technology Corporation (“ATC”) of the computer programs called P2P
Marshal™ (P2P Marshal™), as well as associated documentation and help files
(collectively called the "Program"), that accompanies this License. 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. This Software License Agreement is
between CST, ATC and you (“you” or “Licensee”).

26
P2P Marshal User Guide ATC-NY

By clicking on the Accept button below, Licensee acknowledges that Licensee has read
this agreement, understands it, and agrees to be bound by it.

During the term of this License, CST grants the Licensee a non-exclusive License to use
the Program as stated below.

The Licensee may:

• Install and use only one copy of the Program, on a single computer;
• Copy the Program once in machine-readable form for backup and archival
purposes only in support of such use; provided that Licensee reproduces all
copyright and other proprietary notices that are on the original copy of the
Program.

In the event that Licensee is acquiring the Program pursuant to a master license,
corporate license or site license from CST (the “Modified License”), to the extent that the
terms of the Modified License differ from those in this License, the terms of the Modified
License will govern. No license terms granted by any reseller or distributor may vary the
terms of this license.

1. 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. Licensee may not lease, license, sell, donate or in any other way
transfer the Program to any other party, or allow any unauthorized users.

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 copy or transfer any portion of the Program to any other computer or
storage device except for backup purposes as stated above. Licensee may not use the
Program, or images or representations of the Program in any form or medium, to provide
training to any third parties unless authorized in writing by CST.

2. 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, CST
grants to Licensee a non-exclusive, non-transferable, non-sublicenseable license for
Authorized Users to access and use the Program for Authorized Purposes only. Licensee
may not use, access, copy, redistribute, license, sublicense or transfer any rights to use or
access the Program other than as expressly provided herein. Licensee agrees to utilize
and maintain all security, password, access or other limitations on access as may be
provided to assure only licensed access to the Program and will not distribute, copy or
allow non-licensed users to access or use the Program.

27
P2P Marshal User Guide ATC-NY

This license continues in perpetuity unless terminated by the terms of this license
agreement. This License may terminate early if a.) Licensee terminates this License by
destroying all copies of the Program and its documentation; or b.) Licensee fails to
comply with any provision of this License. Upon termination, 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, provide written certification to that
effect upon CST’s request, and cease and desist from any further use of the Program.

3. No Additional Rights or Licenses: The Program is proprietary, confidential and

copyrighted, contains trade secrets and other proprietary material of CST and its
licensors, and is protected internationally by copyright and other intellectual property
law. Other than the rights granted in this License, Licensee has no claim, right or interest
in the Program. All rights not otherwise granted herein are hereby reserved by CST and
its licensors. The Program will remain the exclusive property of CST or its licensors or
assigns. Licensee may not use any trade or service marks or other proprietary or trade
designation of CST without specific written authority.

4. No Unauthorized Duplication/Modification or Reproduction of the Program, and

other Limitations on License: Licensee will not: (a) decompile, disassemble, decode,
translate or otherwise reverse engineer the Program, or make any attempt to discover,
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; (c) modify or create derivative works of the Program in whole or
in part; (d) distribute the Program in any way or make the Program available on a service
bureau or application service provider basis, unless you have been authorized to do so in
writing by CST; (e) permit access to the Program to anyone other than the Authorized
Users; (f) contest, or assist others in contesting, the validity, enforceability, ownership or
title of the program; (g) remove or attempt to remove any copyright notices or any other
proprietary legends contained on or within the Program; (h) use the Program in any
libelous, defamatory, or fraudulent manner, or in any manner that infringes upon any
third party intellectual property rights, or in any illegal manner; (i) use CST’s name, logo,
or other trademarks, unless such use is expressly authorized by CST in writing. CST
shall own any derivative work created by Licensee or its agents or contractors and
Licensee hereby assigns all right, title and interest to CST in such work. If you have
acquired multiple licenses for the Program, then at any time you may have only as many
copies of the Program in use (plus backup copies as permitted by this License), as you
have valid and current licenses.

5. 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, if any.

6. Support and Maintenance: CST is under no obligation to provide maintenance,

support, training, 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 then-
current fees.

28
P2P Marshal User Guide ATC-NY

7. Warranty Disclaimer. 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, including without
limitation, any warranty of non-infringement, title, fitness for a particular purpose,
functionality, or merchantability, whether express, implied or statutory. No oral or
written information or advice given by CST, its employees, distributors, resellers, dealers
or agents shall increase the scope of the above warranties or create new warranties. 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. No oral or
written information or advice of CST, its resellers, agents or distributors, shall create a
warranty or amend the scope of any warranty provided herein. If any applicable law
requires any warranties with respect to the Program, such warranties are limited to an
assurance that the Program will perform as specified for ninety (90) days, subject to the
disclaimer of any failure of the Program due to the interaction with other software not
owned or licensed by CST.

8. Limitation of Remedies: IN NO EVENT WILL CST, ITS DISTRIBUTORS OR ITS

SUPPLIERS BE LIABLE TO LICENSEE OR TO ANY THIRD PARTY FOR ANY
LOST PROFITS, LOST DATA, INTERRUPTION OF BUSINESS, OR OTHER
SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
KIND ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM OR
ANY DATA SUPPLIED THEREWITH, EVEN IF CST HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH LOSS OR DAMAGES AND WHETHER OR NOT
SUCH LOSS OR DAMAGES ARE FORESEEABLE. IN NO EVENT SHALL THE
LIABILITY OF CST EXCEED THE TOTAL AMOUNT RECEIVED BY CST FROM
LICENSEE UNDER THIS AGREEMENT.

9. Ownership: Licensee acknowledges that the Program is a valuable asset and trade
secret of CST. All rights, title and interest in the Program, and all modifications,
revisions, fixes and other materials and the documentation delivered to Licensee shall be
and remain the property of CST and/or its licensors, subject to the License granted
hereunder.

10. Governing Law: This License shall be deemed to be made in the State of Minnesota
and shall in all respects be interpreted, construed, and governed by and in accordance with
the laws of the State of Minnesota. 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.

11. Independent Contractors: The parties to this License are independent contractors
and are not agents or representatives of each other. Neither party shall have the power to
bind the other, nor shall either party misstate or misrepresent its relationship hereunder.

12. Entire Agreement; Waiver. This License contains the complete understanding
between the parties with respect to the subject matter hereof, and supersedes all prior or

29
P2P Marshal User Guide ATC-NY

contemporaneous agreements or understandings, whether oral or written. 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. 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. No provision hereof shall be deemed waived or modified except in
writing.

13. Export. 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. You will comply with
all trade regulations and laws both foreign and domestic. You acknowledge that the
Program licensed under this License is subject to the export control laws and regulations
of various countries, including those of the United States, such as, by way of example,
only, and not limitation, the Export Administration Regulations ("EAR"), and sanctions
regimes of the U.S. Department of Treasury, Office of Foreign Asset Controls. You shall
not, without prior U.S. governmental authorization, download or otherwise export, re-
export, or transfer any Program subject to this License either directly or indirectly, to any
country subject to a U.S. trade embargo as defined by applicable law in effect or to any
resident or national of any such country, or to any person or entity listed on the "Entity
List" or "Denied Persons List" maintained by the U.S. Department of Commerce or the
list of "Specifically Designated Nationals and Blocked Persons" maintained by the U.S.
Department of Treasury. In addition, you agree that you shall not export, re-export or
transfer the Program subject to this License to any person engaged in activities related to
weapons of mass destruction. Such activities include, but are not limited to activities
related to: (i) the design, development, production, or use of nuclear materials, nuclear
facilities, or nuclear weapons; (ii) the design, development, production, or use of missiles
or support of missiles projects; and (iii) the design, development, production, or use of
chemical or biological weapons. Licensee shall be solely responsible for all fees and
expenses related to a permitted export or re-export of the Program.

14. Taxes. Licensee shall pay any taxes due from it as a result of its possession or use of
the Program

15. Audit. If CST has a reasonable basis to believe that Licensee is using the Program in
violation of this License, CST shall have the right to audit Licensee’s use of the Program
during normal business hours. 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.

16. Indemnification. Licensee will defend, indemnify, and hold CST and its affiliates,
licensors, distributors, resellers (and each of their respective officers, directors,
employees and agents) harmless from and against any and all claims, losses, damages,
liabilities, deficiencies, judgments, assessments, fines, costs and other expenses

30
P2P Marshal User Guide ATC-NY

(including reasonable attorneys' fees) arising from or relating to your use of or reliance
upon the Program.

17. Data Collection; Privacy Policy; Third Party Web Sites. Licensee acknowledges
and agrees that CST may collect and retain information about you, such as your name,
address, and e-mail address. You also understand that CST may employ other companies
to perform functions on our behalf, such as fulfilling orders, delivering packages, sending
postal mail and e-mail, providing marketing assistance, and processing credit card
payments. These companies may have access to personal information needed to perform
their functions, and may not use such information for other purposes, unless or until your
consent is obtained or to comply with applicable law.

18. The EEC Council Directive 91/250/EEC. Notwithstanding anything herein, 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, 1991, Licensee agrees that within that jurisdiction it shall not, and shall not
allow any party on Licensee's behalf to, attempt to reverse engineer or decompile the
Program into another computer language, except as expressly and specifically provided in
the EEC Council Directive 91/250/EEC of May 14, 1991.

19. Survivorship: Sections 3, 4, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18 and 19 shall
survive termination of this License however effected.

12 Included software
P2P Marshal uses and includes, unmodified: Java 6 JRE, Eclipse, JDOM, BouncyCastle,
and iText.

12.1 Java License

Copyright © 2007 Sun Microsystems, Inc., 4150
Network Circle, Santa Clara, California 95054, U.S.A. All
rights reserved. U.S.

Government Rights - Commercial software. Government users

are subject to the Sun Microsystems, Inc. standard license
agreement and applicable provisions of the FAR and its
supplements. Use is subject to license terms. This
distribution may include materials developed by third
parties. Sun, Sun Microsystems, the Sun logo, Java, Jini,
Solaris and J2SE are trademarks or registered trademarks of
Sun Microsystems, Inc. in the U.S. and other
countries. This product is covered and controlled by U.S.
Export Control laws and may be subject to the export or
import laws in other countries. Nuclear, missile, chemical
biological weapons or nuclear maritime end uses or end
users, whether direct or indirect, are strictly prohibited.

Export or reexport to countries subject to U.S.

embargo or to entities identified on U.S. export exclusion
lists, including, but not limited to, the denied persons and
specially designated nationals lists is strictly prohibited.
Sun Microsystems, Inc. Binary Code License Agreement

31
P2P Marshal User Guide ATC-NY

for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6

SUN MICROSYSTEMS, INC. ("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"). PLEASE READ THE AGREEMENT
CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU
ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY
SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE
AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE
TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE
AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT
CONTINUE.

1. DEFINITIONS. "Software" means the identified above in

binary form, any other machine readable materials
(including, but not limited to, libraries, source files,
header files, and data files), any updates or error
corrections provided by Sun, and any user manuals,
programming guides and other documentation provided to you
by Sun under this Agreement. "Programs" mean Java applets
and applications intended to run on the Java Platform,
Standard Edition (Java SE) on Java-enabled general purpose
desktop computers and servers.

2. LICENSE TO USE. Subject to the terms and conditions of

this Agreement, including, but not limited to the Java
Technology Restrictions of the Supplemental License Terms,
Sun grants you a non-exclusive, non-transferable, limited
license without license fees to reproduce and use
internally Software complete and unmodified for the sole
purpose of running Programs. Additional licenses for
developers and/or publishers are granted in the
Supplemental License Terms.

3. RESTRICTIONS. Software is confidential and copyrighted.

Title to Software and all associated intellectual property
rights is retained by Sun and/or its licensors. Unless
enforcement is prohibited by applicable law, you may not
modify, decompile, or reverse engineer Software. You
acknowledge that Licensed Software is not designed or
intended for use in the design, construction, operation or
maintenance of any nuclear facility. Sun Microsystems, Inc.
disclaims any express or implied warranty of fitness for
such uses. No right, title or interest in or to any
trademark, service mark, logo or trade name of Sun or its
licensors is granted under this Agreement. Additional
restrictions for developers and/or publishers licenses are
set forth in the Supplemental License Terms.

4. LIMITED WARRANTY. Sun warrants to you that for a period

of ninety (90) days from the date of purchase, as evidenced
by a copy of the receipt, the media on which Software is
furnished (if any) will be free of defects in materials and
workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". 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. Any implied warranties on the Software
are limited to 90 days. Some states do not allow
limitations on duration of an implied warranty, so the
above may not apply to you. This limited warranty gives you
specific legal rights. You may have others, which vary from
state to state.

5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS

AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE

32
P2P Marshal User Guide ATC-NY

EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY

INVALID.

6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY

LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR
ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER
CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT
OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE,
EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. In no event will Sun's liability to you, whether
in contract, tort (including negligence), or otherwise,
exceed the amount paid by you for Software under this
Agreement. The foregoing limitations will apply even if the
above stated warranty fails of its essential purpose. Some
states do not allow the exclusion of incidental or
consequential damages, so some of the terms above may not
be applicable to you.

7. TERMINATION. This Agreement is effective until

terminated. You may terminate this Agreement at any time by
destroying all copies of Software. This Agreement will
terminate immediately without notice from Sun if you fail
to comply with any provision of this Agreement. Either
party may terminate this Agreement immediately should any
Software become, or in either party's opinion be likely to
become, the subject of a claim of infringement of any
intellectual property right. Upon Termination, you must
destroy all copies of Software.

8. EXPORT REGULATIONS. 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. You agree to comply
strictly with all such laws and regulations and acknowledge
that you have the responsibility to obtain such licenses to
export, re-export, or import as may be required after
delivery to you.

9. TRADEMARKS AND LOGOS. You acknowledge and agree as

between you and Sun that Sun owns the SUN, SOLARIS, JAVA,
JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS,
JAVA, JINI, FORTE, and iPLANET-related trademarks, service
marks, logos and other brand designations ("Sun Marks"),
and you agree to comply with the Sun Trademark and Logo
Usage Requirements currently located at
http://www.sun.com/policies/trademarks. Any use you make of
the Sun Marks inures to Sun's benefit.

10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being

acquired by or on behalf of the U.S. Government or by a
U.S. Government prime contractor or subcontractor (at any
tier), then the Government's rights in Software and
accompanying documentation will be only as set forth in
this Agreement; this is in accordance with 48 CFR 227.7201
through 227.7202-4 (for Department of Defense (DOD)
acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
acquisitions).

11. GOVERNING LAW. Any action related to this Agreement

will be governed by California law and controlling U.S.
federal law. No choice of law rules of any jurisdiction
will apply.

12. SEVERABILITY. If any provision of this Agreement is

held to be unenforceable, this Agreement will remain in
effect with the provision omitted, unless omission would
frustrate the intent of the parties, in which case this
Agreement will immediately terminate.

13. INTEGRATION. This Agreement is the entire agreement

33
P2P Marshal User Guide ATC-NY

between you and Sun relating to its subject matter. It

supersedes all prior or contemporaneous oral or written
communications, proposals, representations and warranties
and prevails over any conflicting or additional terms of
any quote, order, acknowledgment, or other communication
between the parties relating to its subject matter during
the term of this Agreement. No modification of this
Agreement will be binding, unless in writing and signed by
an authorized representative of each party.

SUPPLEMENTAL LICENSE TERMS

These Supplemental License Terms add to or modify the terms

of the Binary Code License Agreement. Capitalized terms not
defined in these Supplemental Terms shall have the same
meanings ascribed to them in the Binary Code License
Agreement . These Supplemental Terms shall supersede any
inconsistent or conflicting terms in the Binary Code
License Agreement, or in any license contained within the
Software.

A. Software Internal Use and Development License Grant.

Subject to the terms and conditions of this Agreement and
restrictions and exceptions set forth in the Software
"README" file incorporated herein by reference, including,
but not limited to the Java Technology Restrictions of
these Supplemental Terms, Sun grants you a non-exclusive,
non-transferable, limited license without fees to reproduce
internally and use internally the Software complete and
unmodified for the purpose of designing, developing, and
testing your Programs.

B. License to Distribute Software. Subject to the terms and

conditions of this Agreement and restrictions and
exceptions set forth in the Software README file,
including, but not limited to the Java Technology
Restrictions of these Supplemental Terms, Sun grants you a
non-exclusive, non-transferable, limited license without
fees to reproduce and distribute the Software, provided
that (i) you distribute the Software complete and
unmodified and only bundled as part of, and for the sole
purpose of running, your Programs, (ii) the Programs add
significant and primary functionality to the Software,
(iii) you do not distribute additional software intended to
replace any component(s) of the Software, (iv) you do not
remove or alter any proprietary legends or notices
contained in the Software, (v) you only distribute the
Software subject to a license agreement that protects Sun's
interests consistent with the terms contained in this
Agreement, and (vi) you agree to defend and indemnify Sun
and its licensors from and

C. Java Technology Restrictions. You may not create,

modify, or change the behavior of, or authorize your
licensees to create, modify, or change the behavior of,
classes, interfaces, or subpackages that are in any way
identified as "java", "javax", "sun" or similar convention
as specified by Sun in any naming convention designation.

D. Source Code. Software may contain source code that,

unless expressly licensed for other purposes, is provided
solely for reference purposes pursuant to the terms of this
Agreement. Source code may not be redistributed unless
expressly provided for in this Agreement.

E. Third Party Code. Additional copyright notices and

license terms applicable to portions of the Software are
set forth in the THIRDPARTYLICENSEREADME.txt file. In
addition to any terms and conditions of any third party
opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of

34
P2P Marshal User Guide ATC-NY

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.

F. Termination for Infringement. Either party may terminate

this Agreement immediately should any Software become, or
in either party's opinion be likely to become, the subject
of a claim of infringement of any intellectual property
right.

G. Installation and Auto-Update. 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. Sun does not associate the data with personally
identifiable information. You can find more information
about the data Sun collects at http://java.com/data/.

For inquiries please contact: Sun Microsystems, Inc., 4150

Network Circle, Santa Clara, California 95054, U.S.A.

12.2 Eclipse License

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
RECIPIENT’S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation distributed
under this Agreement, and
b) in the case of each subsequent Contributor:

i)changes to the Program, and

ii)additions to the Program;

where such changes and/or additions to the Program originate from and are distributed by
that particular 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. 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, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"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.

"Program" means the Contributions distributed in accordance with this Agreement.

"Recipient" means anyone who receives the Program under this Agreement, including all
Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative
works of, publicly display, publicly perform, distribute and sublicense the Contribution
of such Contributor, if any, and such derivative works, in source code and object code
form.

35
P2P Marshal User Guide ATC-NY

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
use, sell, offer to sell, import and otherwise transfer the Contribution of such
Contributor, if any, in source code and object code form. This patent license shall apply
to the combination of the Contribution and the Program if, at the time the Contribution
is added by the Contributor, such addition of the Contribution causes such combination to
be covered by the Licensed Patents. The patent license shall not apply to any other
combinations which include the Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its
Contributions set forth herein, no assurances are provided by any Contributor that the
Program does not infringe the patent or other intellectual property rights of any other
entity. Each Contributor disclaims any liability to Recipient for claims brought by any
other entity based on infringement of intellectual property rights or otherwise. As a
condition to exercising the rights and licenses granted hereunder, each Recipient hereby
assumes sole responsibility to secure any other intellectual property rights needed, if
any. For example, if a third party patent license is required to allow Recipient to
distribute the Program, it is Recipient’s responsibility to acquire that license before
distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights
in its Contribution, if any, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own
license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions,

express and implied, including warranties or conditions of title and non-infringement,
and implied warranties or conditions of merchantability and fitness for a particular
purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages,
including direct, indirect, special, incidental and consequential damages, such as lost
profits;

iii) states that any provisions which differ from this Agreement are offered by that
Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor, and
informs licensees how to obtain it in a reasonable manner on or through a medium
customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; 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.

Each Contributor must identify itself as the originator of its Contribution, if any, in a
manner that reasonably allows subsequent Recipients to identify the originator of the
Contribution.

4. COMMERCIAL DISTRIBUTION

36
P2P Marshal User Guide ATC-NY

Commercial distributors of software may accept certain responsibilities with respect to

end users, business partners and the like. While this license is intended to facilitate
the commercial use of the Program, 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. Therefore, if a Contributor includes the Program in a
commercial product offering, 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, 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. The obligations in this
section do not apply to any claims or Losses relating to any actual or alleged
intellectual property infringement. In order to qualify, an Indemnified Contributor must:
a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the
Commercial Contributor to control, and cooperate with the Commercial Contributor in, the
defense and any related settlement negotiations. The Indemnified Contributor may
participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering,
Product X. That Contributor is then a Commercial Contributor. If that Commercial
Contributor then makes performance claims, or offers warranties related to Product X,
those performance claims and warranties are such Commercial Contributor’s responsibility
alone. Under this section, the Commercial Contributor would have to defend claims against
the other Contributors related to those performance claims and warranties, and if a court
requires any other Contributor to pay any damages as a result, the Commercial Contributor
must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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 , including but not
limited to the risks and costs of program errors, compliance with applicable laws, damage
to or loss of data, programs or equipment, and unavailability or interruption of
operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS
SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 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, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it

shall not affect the validity or enforceability of the remainder of the terms of this
Agreement, and without further action by the parties hereto, such provision shall be
reformed to the minimum extent necessary to make such provision valid and enforceable.

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), then
such Recipient’s rights granted under Section 2(b) shall terminate as of the date such
litigation is filed.

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. If all
Recipient’s rights under this Agreement terminate, Recipient agrees to cease use and

37
P2P Marshal User Guide ATC-NY

distribution of the Program as soon as reasonably practicable. However, Recipient’s

obligations under this Agreement and any licenses granted by Recipient relating to the
Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but in order to
avoid inconsistency the Agreement is copyrighted and may only be modified in the
following manner. The Agreement Steward reserves the right to publish new versions
(including revisions) of this Agreement from time to time. No one other than the
Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the
initial Agreement Steward. 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. The Program (including Contributions) may
always be distributed subject to the version of the Agreement under which it was
received. In addition, after a new version of the Agreement is published, Contributor may
elect to distribute the Program (including its Contributions) under the new version.
Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights
or licenses to the intellectual property of any Contributor under this Agreement, whether
expressly, by implication, estoppel or otherwise. All rights in the Program not expressly
granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual
property laws of the United States of America. No party to this Agreement will bring a
legal action under this Agreement more than one year after the cause of action arose.
Each party waives its rights to a jury trial in any resulting litigation.

12.3 JDOM License

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright

notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright

notice, this list of conditions, and the disclaimer that follows
these conditions in the documentation and/or other materials
provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products

derived from this software without prior written permission. For
written permission, please contact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor
may "JDOM" appear in their name, without prior written permission
from the JDOM Project Management <request_AT_jdom_DOT_org>.

In addition, 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.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos
available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT

38
P2P Marshal User Guide ATC-NY

OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.

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>. For more information
on the JDOM Project, please see <http://www.jdom.org/>.

12.4 BouncyCastle License

Copyright (c) 2000 - 2006 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)

Permission is hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the "Software"), to deal in the Software
without restriction, including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, 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.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

12.5 iText License

The iText library is included, unmodified, under the Mozilla Public License (MPL 1.1).
Copyright 1999, 2000, 2001, 2002 by Bruno Lowagie.

The contents of this file are subject to the Mozilla Public License Version 1.1
(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.mozilla.org/MPL/

Software distributed under the License is distributed on an "AS IS" basis,

WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License
for the specific language governing rights and limitations under the License.

The Original Code is 'iText, a free JAVA-PDF library'.

The Initial Developer of the Original Code is Bruno Lowagie. Portions created by
the Initial Developer are Copyright (C) 1999, 2000, 2001, 2002 by Bruno Lowagie.
All Rights Reserved.
Co-Developer of the code is Paulo Soares. Portions created by the Co-Developer
are Copyright (C) 2000, 2001, 2002 by Paulo Soares. All Rights Reserved.

Contributor(s): all the names of the contributors are added in the source code
where applicable.

Alternatively, the contents of this file may be used under the terms of the
LGPL license (the "GNU LIBRARY GENERAL PUBLIC LICENSE"), in which case the
provisions of LGPL are applicable instead of those above. 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, indicate your decision by deleting the provisions above and
replace them with the notice and other provisions required by the LGPL.
If you do not delete the provisions above, a recipient may use your version
of this file under either the MPL or the GNU LIBRARY GENERAL PUBLIC LICENSE.

This library is free software; you can redistribute it and/or modify it

39
P2P Marshal User Guide ATC-NY

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;
either version 2 of the License, or any later version.

This library is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the GNU Library general Public License for more
details.

40