Sophos Anti-Virus for VMware vShield Virtual Machine Security Software Startup Guide

Sophos Anti-Virus for
VMware vShield
startup guide
Product version: 2.0
Document date: February 2015
Contents
1 About this guide........................................................................................................................4
2 About Sophos Anti-Virus..........................................................................................................4
3 Key steps in installation............................................................................................................6
4 Check the system requirements...............................................................................................6
4.1 VMware requirements.................................................................................................7
4.2 Sophos requirements................................................................................................10
5 Uninstall other anti-virus products..........................................................................................10
6 Install Sophos requirements...................................................................................................11
6.1 Install Enterprise Console.........................................................................................11
6.2 Create a Sophos Anti-Virus update share................................................................12
6.3 Check access to the Sophos Anti-Virus update share..............................................12
7 Install Sophos security VMs...................................................................................................13
7.1 Check that you have the passwords you need.........................................................13
7.2 Check that systems are synchronized......................................................................14
7.3 Download the installer..............................................................................................14
7.4 Install the security VMs.............................................................................................14
7.5 Check that security VMs are installed.......................................................................16
7.6 Set up Enterprise Console to manage the security VMs..........................................17
8 Install the VMware Guest Introspection Agent........................................................................18
8.1 Check whether the agent is already installed...........................................................18
8.2 Prepare to install the agent.......................................................................................19
8.3 Install the agent........................................................................................................19
9 Install the Sophos Guest VM Agent........................................................................................21
10 Check that security VMs are working...................................................................................22
10.1 Check the status in vSphere Client.........................................................................22
10.2 Check that on-access scanning is working.............................................................23
10.3 Troubleshoot on-access scanning...........................................................................24
11 Maintain the security VMs....................................................................................................24
12 View the protected guest VMs..............................................................................................24
13 Scan guest VMs...................................................................................................................25
14 What happens when a threat is detected.............................................................................26
15 Find out about a threat.........................................................................................................27
2
16 Clean up a threat..................................................................................................................27
16.1 Automatic cleanup..................................................................................................27
16.2 Manual cleanup......................................................................................................28
17 Upgrade security VMs..........................................................................................................29
18 Uninstall security VMs..........................................................................................................29
19 Appendix: vCenter administrator account.............................................................................29
20 Appendix: Set the CPU configuration...................................................................................30
21 Technical support..................................................................................................................30
22 Legal notices........................................................................................................................31
3
Sophos Anti-Virus for VMware vShield
1 About this guide
This guide is for administrators who want to protect a network of virtual machines (VMs) against
viruses and other threats.
The guide describes how to install Sophos Anti-Virus for VMware vShield on VMware ESXi hosts
to provide central anti-virus scanning for guest VMs.
Below are links to other documents you might find useful.
Need help setting up the VMware and vShield environment?
See the Sophos guide VMware and vShield: an overview of setup.
See also these articles from VMware:
■
Installing vCloud Networking and Security 5.5.x best practices
■
Guest operating systems that are supported for vShield Endpoint Thin Agent
Note: The vShield Endpoint Thin Agent is called VMware Guest Introspection Agent in recent
releases.
Need information on alternative ways to protect VMs?
Go to www.sophos.com/en-us/support/knowledgebase/110507.aspx.
Need to upgrade Sophos Anti-Virus for VMware vShield?
See the Sophos Anti-Virus for VMware vShield upgrade guide.
2 About Sophos Anti-Virus
Sophos Anti-Virus for VMware vShield is a security virtual machine (VM) that protects your VMs.
It works like this:
4
■
You put a Sophos security VM on each VMware ESXi host. This can detect and block threats
on the guest VMs that are running on the host.
■
You put a Sophos Guest VM Agent on each guest VM. This can attempt automatic cleanup
of any threats detected on the guest VM. This component is optional but is required if you want
automatic cleanup.
■
You use Sophos Enterprise Console on another computer to manage the security VMs and
keep them up to date.
startup guide
Which guest VMs can be protected?
The Sophos security VM can protect guest VMs that run Windows operating systems. For full
details, see Guest VMs (page 8).
How does scanning work?
When a guest VM tries to access a file:
■
The VMware Guest Introspection Agent running on the VM notifies the Sophos security VM.
■
The security VM scans the file.
■
If the security VM detects a threat, access to the file is blocked, and the security VM sends an
alert to Enterprise Console.
5
Sophos Anti-Virus for VMware vShield
The security VM can also perform a full scan of all the guest VMs. You can run this scan
immediately or schedule it.
How is the security VM managed?
Enterprise Console displays the status of the security VM, including how up to date it is and
whether it has detected any threats.
Enterprise Console also enables you to configure scanning by means of a policy.
How do you deal with threats?
The security VM can clean up many threats automatically, provided you have installed the Sophos
Guest VM Agent on your VMs.
You can also clean up threats manually.
How is the security VM updated?
Enterprise Console keeps the security VM updated.
Enterprise Console downloads the latest threat data, maintenance updates and even new versions
of the product from Sophos and puts them in a network share. The security VM automatically
fetches updates from there.
3 Key steps in installation
Installation involves these key steps, which are described in the sections that follow:
■
Check the system requirements.
■
Uninstall other anti-virus products.
■
Install the Sophos requirements.
■
Install Sophos security VMs.
■
Install the VMware Guest Introspection Agent on guest VMs (if not already installed).
■
Install the Sophos Guest VM Agent on guest VMs.
■
Check that security VMs are working.
4 Check the system requirements
This section tells you the requirements and how to check that you comply with them.
It also tells you about any information (such as computer details) that you should gather now so
that you will have it available when you install the security VMs.
6
startup guide
It covers:
■
VMware requirements.
■
Guest VM requirements.
■
Sophos requirements (Sophos software you need before you install the Sophos security VMs).
4.1 VMware requirements
This section shows you the VMware software you need.
For help with setting up VMware software, see the Sophos guide VMware and vShield: an overview
of setup. You can also read these VMware knowledgebase articles:
■
Installing vCloud Networking and Security 5.5.x best practices
■
Guest operating systems that are supported for vShield Endpoint Thin Agent
4.1.1 ESXi host
You should install the following on each host that will run a Sophos security VM:
■
VMware ESXi host 5.1 or 5.5.
Hardware requirements
The ESXi host must be able to allocate the following resources for the Sophos security VM:
■
2 CPUs.
■
20 Gb disk space.
■
2 Gb RAM.
Notes
By default, 2 CPUs are allocated. If you have many guest VMs to protect, you can configure more
CPUs after you install the security VM. This guide tells you how.
The Sophos security VM reserves memory. High-availability and load-balancing systems make
automatic choices based on resource reservations for the VMs in your VMware environment, so
these choices could be different after you install the security VM. You should not remove the
security VM memory reservation.
4.1.2 vCenter and vSphere
You require the following vCenter and vSphere software.
Software
Version
Notes
vCenter
Version 5.1 or 5.5.
You will also need:
The network address.
7
Sophos Anti-Virus for VMware vShield
Software
Version
Notes
An administrator account. For permissions needed,
see Appendix: vCenter administrator account
(page 29).
A read-only account. This may be a local or
domain user. Local user names are case-sensitive.
vSphere Client
Version 5.1 or 5.5.
4.1.3 Guest VMs
The Sophos security VM can protect guest VMs that meet these requirements.
Virtual hardware
The VMware virtual hardware must be version 7 or later.
Tip: If you have virtual hardware that came as default with ESXi version 4.x or later, you already
meet this requirement.
Note: For information on upgrading virtual hardware versions, see VMware Knowledge Base
article 1010675.
Operating system
Guest VMs should run one of the following operating systems:
■
Windows 8 (64-bit). Only with vSphere 5.5. ReFS file system not supported.
■
Windows 7 (32- and 64-bit).
■
Windows Vista (32-bit) SP 2.
■
Windows XP (32-bit) SP 3 and later. The Sophos security VM cannot clean up threats
automatically on this operating system.
■
Windows Server 2012 (64-bit). Only with vSphere 5.5. ReFS file system not supported.
■
Windows Server 2008 R2 (64-bit).
■
Windows Server 2008 (64-bit).
■
Windows Server 2003 R2 (32- and 64-bit) SP 2. The Sophos security VM cannot clean up
threats automatically on this operating system.
■
Windows Server 2003 (32- and 64-bit) SP 2 and later. The Sophos security VM cannot clean
up threats automatically on this operating system.
Some platforms, for example Vista 32-bit or Server 2003 32- and 64-bit, require the latest service
packs so that the vShield drivers (also called VMware Guest Introspection Agent) can be installed.
Tip: The Guest Introspection Agent was formerly called the vShield Endpoint Thin Agent.
8
startup guide
4.1.4 vShield
You require the following vShield software.
Software
Version
Notes
vShield Manager
Version 5.1 or 5.5.
You will also need:
To check that it's installed:
The network address.
1. Restart vSphere Client.
2. In vSphere Client, click the ESXi host on
which you want to install the security VM.
3. Check that the vShield tab is visible.
A vShield Administrator or
Enterprise Administrator
account.
vShield Endpoint
Version 5.1 or 5.5.
Must be installed on each ESXi host that will run
the Sophos security VM.
To check that it's installed:
1. In vSphere Client, click the ESXi host on
which you want to install the security VM.
2. On the vShield tab, General page, if the
vShield Endpoint row is listed with version
5.1.0 or later in the Installed column, then
the appropriate version of vShield Endpoint
is installed. Otherwise, click Install.
VMware Guest
Must be installed on each guest VM that needs
Introspection Agent (also protection.
called "vShield drivers")
Note: You can install the agent after you install
the Sophos security VM. This guide tells you
how.
Supports Windows operating
systems only.
This is part of VMware Tools
and can be automatically
upgraded.
To check whether it's installed:
1. In vSphere Client, click the ESXi host on
which you want to install the security VM.
2. Ensure that the guest VMs that you want to
check are turned on.
3. On the vShield tab, Endpoint page, look for
the guest VMs in the computer list, displayed
as “vm”.
4. Check that the Description shows that the
agent is enabled.
9
Sophos Anti-Virus for VMware vShield
4.1.5 vMotion
Sophos security VMs are automatically excluded from vMotion. This ensures that a security VM
always remains on its ESXi host to protect guest VMs.
You do not need to make any changes to your settings.
Note: If vMotion migrates guest VMs to a different server during the cleanup of threats, the
cleanup and the cleanup reports sent to Enterprise Console can be affected. For details, see the
Sophos Anti-Virus for VMware vShield configuration guide.
4.2 Sophos requirements
You need the following Sophos software before you can install and use the Sophos security VM.
If you don’t have this software, follow the instructions in Install Sophos requirements (page 11).
Warning: Ensure that Sophos Anti-Virus for Windows (which is included in Sophos Endpoint
Security and Control) is not installed on guest VMs that you intend to protect with the Sophos
security VM. This avoids the conflicts that can arise between any two anti-virus products on the
same VM.
Turning off the on-access scanning in Sophos Anti-Virus for Windows is not sufficient to avoid
conflicts.
Software
Version
Sophos Enterprise
Console
Version 5.1 or later.
Sophos Anti-Virus for
No minimum version.
VMware vShield network
share
Notes
You must set up a network share
where Enterprise Console makes
the latest updates available for
your security VM. This guide tells
you how to set up the share.
5 Uninstall other anti-virus products
You should uninstall any anti-virus products that are already installed on your guest VMs.
You cannot use Sophos Anti-Virus for VMware vShield to protect guest VMs that run other anti-virus
products. This is because files might be scanned multiple times (due to the design of VMware
vShield).
10
startup guide
This limitation applies to VMs that run products from other vendors or other anti-virus products
from Sophos. It also applies to VMs with Sophos gateway or server products that include or require
anti-virus components. So you cannot protect guest VMs that run:
■
Sophos Endpoint Security and Control for Windows (includes Sophos Anti-Virus).
■
PureMessage for Microsoft Exchange.
■
PureMessage for Lotus Domino.
■
Sophos for Sharepoint.
■
Sophos Anti-Virus for NetApp.
■
Any third-party software that integrates SAV Interface.
6 Install Sophos requirements
Before you install Sophos security VMs, you should:
■
Install Sophos Enterprise Console (if you do not already have it). You use this to download
protection software and to manage the VMs you protect.
■
Create a Sophos Anti-Virus for VMware vShield network share. The share is used to keep
security VMs up to date.
The following sections describe how to do this.
Already using Enterprise Console?
Warning: If you already use Enterprise Console to manage other Sophos products and now
want to add Sophos Anti-Virus for VMware vShield, your customer credentials might not let you
set up the Sophos network share. If this happens, check that your license includes this product.
You can send license queries to [email protected]
6.1 Install Enterprise Console
If you already have Enterprise Console installed, go to Create a Sophos Anti-Virus update share
(page 12).
You should install Enterprise Console on a Windows computer that will be on the same network
as the security VMs.
Follow the instructions in the Enterprise Console quick startup guide. When you are prompted to
select the platforms you want to protect, include VMware vShield. This creates the Sophos
Anti-Virus for VMware vShield network share.
Caution: This gives you the Recommended version. If you want the Preview version, which
gives you early access to new features, create or edit the network share manually (page 12).
Note: Whether you have Recommended or Preview, you must use the same version when you
install the security VMs later.
11
Sophos Anti-Virus for VMware vShield
After installation, see Check access to the Sophos Anti-Virus update share (page 12).
6.2 Create a Sophos Anti-Virus update share
If you have just made a new installation of Enterprise Console and included protection for VMware
vShield, you can skip this section.
1. In Enterprise Console, on the View menu, click Update Managers.
2. Set up a "subscription" to Sophos Anti-Virus for VMware vShield :
a) In the Software Subscriptions pane, click Add at the top of the pane.
b) In the Software Subscription dialog box, type a name in the Subscription name text
box.
c) In the platform list, select VMware vShield.
Note: If you cannot see VMware vShield in the list, your customer credentials need
updating. Contact Sophos Technical Support.
d) In the version box, select Recommended or Preview.
Note: Preview gives you early access to new features. Read more about Recommended
and Preview.
Note: You must use the same version when you install the security VMs later.
3. Configure the update manager to use this subscription:
a) In the Update Managers pane, select the update manager that is installed on this server.
Right-click it and click View/Edit configuration.
b) In the Configure update manager dialog box, on the Subscriptions tab, ensure that the
new subscription is in the Subscribed to list.
c) Click OK.
Now continue to the next section.
6.3 Check access to the Sophos Anti-Virus update share
You need to locate the Sophos Anti-Virus update share and ensure that it can be accessed using
either valid credentials or a guest account.
Note: Unless you specified otherwise, the Sophos Anti-Virus share is accessed by the user
account set up during installation of Enterprise Console. It is described there as the "Update
Manager" account and most customers give it the username SophosUpdateMgr.
1. In Enterprise Console, on the View menu, click Bootstrap Locations.
A list of locations is displayed.
2. Find the location for Sophos Anti-Virus for VMware vShield, the "savvshield" share, and make
a note of it. You will need this when you install the Sophos security VMs.
You will need the Fully Qualified Domain Name for this location.
12
startup guide
3. If the share is on Windows Server 2008 or 2012, you might need to change Windows Firewall
settings on the server temporarily to enable the Sophos security VM installer to access it.
The following Inbound rules must be set to On (which is the default):
■
■
■
File and Printer Sharing (NB-Datagram-In)
File and Printer Sharing (NB-Name-In)
File and Printer Sharing (NB-Session-In)
You can set these rules to Off again after you have installed your security VMs.
Notes:
If you have a customised installation of Enterprise Console or you created an additional network
share for updating the security VM, note that:
■
If credentials are required, they will need to be stored on security VMs after they are installed,
so we recommend that you use read-only credentials.
■
If the network share is on a different computer to Enterprise Console (or the Update Manager
component of Enterprise Console), ensure that it can also be accessed using an account that
has write-access.
7 Install Sophos security VMs
You install a Sophos security VM on each ESXi host where you want to protect guest VMs.
Installation involves these steps, which are described in the sections that follow:
■
Check that you have the passwords you need.
■
Check that systems are synchronized.
■
Download the installer.
■
Install security VMs.
■
Set up Enterprise Console to manage security VMs.
7.1 Check that you have the passwords you need
When you run the security VM installer, you need to enter certain passwords. You should make
sure that you have the passwords for the following accounts:
■
The vCenter Administrator account.
■
The vCenter read-only user account, used to query information from vCenter during security
VM operation.
■
The vShield Administrator account.
■
The account used to access the Sophos Anti-Virus for VMware vShield network share (or
"Sophos Update folder").
Note: The vCenter user account is stored on the security VMs. Therefore we recommend that
the account is read-only.
13
Sophos Anti-Virus for VMware vShield
7.2 Check that systems are synchronized
You must ensure that the time is synchronized on the Enterprise Console server and on each
ESXi host where you install the security VM.
You can use NTP (Network Time Protocol) synchronization for each vCenter server or each host.
Warning: If the time is not synchronized, you can install security VMs but you cannot manage
them from Enterprise Console.
7.3 Download the installer
You download the installer from the Sophos website (if you have not already done this).
The following steps assume that you have a MySophos account and that you have associated
your license credentials with it. If you need help, go to
www.sophos.com/en-us/support/knowledgebase/111195.aspx.
Notes:
■
You can download the installer at any computer and then copy it to the computer where you
will use it.
■
You cannot use the installer on a Windows XP or Windows Server 2003 computer.
To download the installer:
1. Go to www.sophos.com/en-us/support/downloads/.
2. Type your MySophos username and password.
You see a webpage that shows your license or licenses.
3. Select a license. Under Standalone installers, click Anti-Virus for VMware vShield.
4. On the Anti-Virus for VMware vShield web page, download the Recommended or Preview
installer. The web page explains the differences between these two options.
Note: You must select the same option here and in your Enterprise Console subscription for
Sophos Anti-Virus for VMware vShield.
Ensure that the installer download is on a Windows computer that has access to vCenter and
vShield Manager over the network. The installer does not currently support the use of a proxy,
so installation or uninstallation of the security VM must be done on the local network.
Note: This computer is not used for management or protection of your security VM or guest VMs
after installation.
7.4 Install the security VMs
To install security VMs, do as follows.
Note: You cannot use the installer on a Windows XP or Windows Server 2003 computer.
14
startup guide
Tip: You might want to install a single security VM as a test and then install more on other hosts
later. We make this easy with an option to re-run the installer with your previous settings, as
explained at the end of this section.
1. Ensure that the installer you downloaded is on a Windows computer that has access to vCenter
and vShield Manager over the network.
The installer does not currently support the use of a proxy, so installation or uninstallation of
the security VM must be done on the local network.
Note: This computer is not used for management or protection of your security VM or guest
VMs after installation.
2. Double-click the installer.
A wizard runs to guide you through the installation.
3. Accept the license agreement.
4.
5.
6.
7.
Click Install to extract the installation files to a folder on your computer.
Select Install new security VMs.
Check that you have installed all the Prerequisites for installation.
Enter your vCenter details.
When you enter the administrator usernames, they should be in exactly the same form that
you would use to log in to vCenter using vSphere Client, that is, with or without the domain
prefix as required and using the same capitalization.
a) Enter your vCenter address.
b) Enter your vCenter administrator username and password.
c) Enter the vCenter read-only username and password. This is used to query information
from vCenter during security VM operation. You can use a domain or a local (to vCenter)
username.
8. Enter your vShield Manager address and administrator credentials.
The administrator name should be in exactly the same form that you would use to log in to
vShield Manager web interface, that is, with or without the domain prefix as required and using
the same capitalization.
9. The wizard displays your hosts. Select the host or hosts on which you want to install the security
VM.
Note: The installer will give security VMs names based on the host name or IP address, as
you will see later.
10. Enter your Sophos Update folder details. This is the Sophos Anti-Virus for VMware vShield
network share that you created earlier.
a) Enter the location. Use a UNC path including the fully qualified domain name, or a web
address (if the share is on a web server).
For example:
\\<Your server name.domain name>\sophosupdate\CIDs\Sxxx\savvshield
15
Sophos Anti-Virus for VMware vShield
Tip: To check the location, go to Enterprise Console. On the View menu, click Bootstrap
Locations and look for the "savvshield" share.
b) Enter the username and password. You (or another administrator) set up this user account
during Enterprise Console installation. It is described there as the "Update Manager" account
and most customers give it the username SophosUpdateMgr.
Note that:
■
If you specify a domain user, you must include the domain name.
■
The credentials are securely stored on the security VM.
11. Create a Support password.
You need this password in order to view your protected guest VMs. You also need it if you
want Sophos Technical Support to troubleshoot your installation remotely. They will use it to
collect logs, which you can review and send to Sophos if required.
You can use special characters and spaces in your password.
12. Select the time zone that the security VM will use to schedule scans.
13. Configure the IP settings for security VMs.
By default, IP addresses are assigned dynamically by DHCP. If your network policy requires
you to use static addresses, select that option and enter the details.
14. Select the type of datastore on which you want to install the security VM.
If you select Select from list of visible datastores for each host, a list is displayed.
The security VM protects all guest VMs on an ESXi host that have VMware Guest Introspection
Agent installed, even if their templates are stored in different datastores.
15. Select a VM network. This enables the security VM to communicate with Enterprise Console.
The default is VM network.
16. At the Summary of installation page, you can see full installation details, including your
security VM names. Click Install.
17. At the Installation complete page, you can see whether installation of any security VMs
failed. If it did, check the log for details.
Tip: If you want to install more security VMs, leave the installer open and click Start Over
when you are ready to start again. The installer will use your previous settings as defaults.
The security VMs are installed.
Follow the instructions in the next two sections to:
■
Check that you can see the security VMs in vSphere Client and Enterprise Console.
■
Set up Enterprise Console to manage the security VMs.
7.5 Check that security VMs are installed
This section tells you how to check that security VMs are installed and have the resources they
need.
16
startup guide
Check that you can see security VMs
When the security VMs have been installed, you should see the following:
In vSphere Client
The security VMs should be shown within twenty minutes, in the Endpoints list on the vShield
tab for each host.
Note: If you do not yet have the VMware Guest Introspection Agent installed on any guest VMs,
this does not happen.
In Enterprise Console
The security VMs are registered and placed in the Unassigned group of computers.
The security VM names are based on the host name or, if it does not have a name, IP address.
This helps you match security VMs with hosts (if you have multiple security VMs). Here are some
examples.
Host name or address
Sophos security VM name
MyESXhost
MyESXhost-SSVM
192.0.2.0
192.0.2.0-SSVM
If you change the name of a security VM after installation, it is still shown in Enterprise Console
with the name assigned during installation.
Check whether you need to configure resources
Usually you do not need to configure resources for the security VM. Note that:
■
The installer reserves memory for the Sophos security VMs. High-availability and
load-balancing systems make automatic choices based on resource reservations for the VMs
in your VMware environment, so these choices could be different after you install the security
VMs. You should not remove the security VM memory reservation.
■
If you have a large number of guest VMs on a single host, ensure that the security VM has
enough processing power for scanning. See Appendix: Set the CPU configuration (page 30).
■
Sophos security VMs are automatically excluded from vMotion. This ensures that a
security VM always remains on its ESXi host to protect guest VMs.
You are ready to set up Enterprise Console to manage the security VMs.
7.6 Set up Enterprise Console to manage the security VMs
1. In Sophos Enterprise Console, create an updating policy and an anti-virus and HIPS policy.
Right-click each policy and select Reset Policy to Factory Defaults.
2. Double-click the new updating policy to open it.
17
Sophos Anti-Virus for VMware vShield
3. In the Updating policy dialog box:
a) Click the Subscription tab and select the subscription for VMware vShield.
b) Click the Primary Server tab and ensure that the location of the update folder includes the
fully qualified domain name. Save the policy.
4. Create a new computer group to contain the security VMs.
5. Apply the new policies to the new group.
6. Drag the security VMs from the Unassigned group to the new group.
Now install the VMware Guest Introspection Agent (if not already installed), as described in the
next section.
To check that security VMs are working, see Check that security VMs are working (page 22).
For general advice on post-installation and maintenance tasks, see Maintain the security VMs
(page 24)
8 Install the VMware Guest Introspection
Agent
If you do not have the VMware Guest Introspection Agent installed on the guest VMs, you should
install it now.
Tip: The Guest Introspection Agent was formerly called the vShield Endpoint Thin Agent and is
also known as the "vShield driver".
This section tells you how to:
■
Check whether the agent is already installed (if you are not sure).
■
Prepare to install the agent.
■
Install the agent.
8.1 Check whether the agent is already installed
To check whether the VMware Guest Introspection Agent is already installed:
1. In vSphere Client, click the ESXi host on which you installed a security VM.
2. Ensure that the guest VMs that you want to check are turned on.
3. On the vShield tab, Endpoint page, look for the guest VMs in the computer list, displayed as
“vm”.
4. Check whether the Description shows “Thin Agent enabled”.
If the agent is not installed, continue to Prepare to install the agent (page 19).
18
startup guide
8.2 Prepare to install the agent
Before you install the agent, you should prepare as follows. The steps depend on whether you
already have anti-virus software on guest VMs.
If you already have anti-virus software on guest VMs
If you already have anti-virus software (whether Sophos software or another vendor's software)
installed on your guest VMs, you should do as follows:
1. Ensure the guest VMs are turned on.
2. Uninstall the anti-virus software.
3. Restart the guest VMs if you are prompted to. This completes the uninstallation.
You are now ready to install the agent.
If you do not have anti-virus software on guest VMs
If you do not have anti-virus software protecting your guest VMs, make sure that none of them
are connected to the live network.
You are now ready to install the agent.
8.3 Install the agent
You install the VMware Guest Introspection Agent as one of the components of VMware Tools.
The agent is not included in a standard VMware Tools installation, so you must do one of
the following:
■
Install VMware Tools with the Custom option and include the agent (shown as "VMCI driver")
in your selected components.
■
Upgrade VMware Tools in order to add the Guest Introspection component.
The following sections tell you how to do this manually (interactively) or automatically
(non-interactively).
Note: This guide assumes that you use vSphere Client to install the agent. If you have vSphere
5.1, you can use other VMware management software, as described in Installing and Configuring
VMware Tools.
8.3.1 Install the agent manually
To install the agent interactively on a guest VM:
1. Power on the VM and check that the guest operating system is running.
2. Log in to the VM as an administrator.
19
Sophos Anti-Virus for VMware vShield
3. In vSphere Client, select the menu command to mount the VMware Tools virtual disk on the
guest operating system. The command depends on the version of vSphere Client you use.
Version
Command
vSphere Client
Select Inventory > Virtual Machine > Guest > Install/Upgrade
VMware Tools.
Note: To locate a virtual machine:
Select a datacenter or cluster.
Click the Virtual Machines tab.
vSphere Web Client
Right-click the virtual machine and select All vCenter Actions >
Guest OS > Install/Upgrade VMware Tools.
Note: To locate a virtual machine:
Select a datacenter, folder, cluster, resource pool, host, or vApp.
Click the Related Objects tab and click Virtual Machines.
4. Now start the installation procedure. The command depends on whether you are
upgrading/reinstalling VMware Tools or installing it for the first time.
Installation type
Command
Upgrade
In the Install/Upgrade VMware Tools dialog box, select Interactive
Tools Upgrade and click OK.
First time installation
In the Install VMware Tools information screen, click OK.
5. When prompted, confirm that you want to run the setup program.
If autorun is enabled for the CD-ROM drive in the guest operating system, the VMware Tools
installation wizard is started.
Note: If autorun is not enabled, you can launch the wizard manually. Click Start > Run and
enter D:\setup.exe, where D: is your first virtual CD-ROM drive.
6. The installation wizard guides you through the installation. You should:
■
■
20
Select Modify if you are upgrading. Select a Custom installation if you are installing for
the first time.
On the Custom setup page, select VMCI driver > vShield Drivers.
startup guide
7. If the Windows New Hardware wizard is run, complete the wizard.You can accept the defaults
at each page.
Windows may run this wizard because you have installed drivers that simulate a change to
the hardware installed on the machine.
8. When prompted, restart the virtual machine.
8.3.2 Install the agent automatically
You can automate installation of the VMware Guest Introspection Agent.
See the sample instructions in the VMware vSphere Documentation Center.
After installation, restart the guest VM.
9 Install the Sophos Guest VM Agent
The Sophos Guest VM Agent runs on each guest VM and enables automatic cleanup of threats.
Installing it is optional.
Notes:
This agent is only available with Sophos Anti-Virus for VMware vShield 2.0 and later.
This agent can only be installed on guest VMs running Windows Vista and later.
Before you install this agent, you must have the VMware Guest Introspection Agent installed on
the guest VMs.
1. Go to the Sophos Update folder. This is the Sophos Anti-Virus for VMware vShield network
share that you created earlier.
Tip: To check the location, go to Sophos Enterprise Console. On the View menu, click
Bootstrap Locations and look for the "savvshield" share.
2. Find the "sgvma" folder within the Sophos Update folder. Copy it to the guest VM where you
want to install the agent.
3. Open the new "sgvma" folder, find the SophosGvmAgentInstaller.msi file and run it. Follow
the on-screen instructions. Alternatively you can:
■
■
Use the command line. Enter: msiexec /i <path to
SophosGvmAgentInstaller.msi>
Use Group Policy deployment. For details, see this Microsoft article:
http://support.microsoft.com/kb/816102
4. Go to Sophos Enterprise Console. Make sure that your anti-virus and HIPS policy has automatic
cleanup selected (this is the default setting). This enables the Sophos Guest VM Agent to
provide cleanup.
We recommend that you snapshot the guest VM after installing the agent. This means that you
can safely revert the guest VM later if you need to (for example, to remove a threat manually).
21
Sophos Anti-Virus for VMware vShield
10 Check that security VMs are working
This section tells you how to check that:
■
A Sophos security VM is working.
■
The guest VMs are protected with on-access scanning.
Note: Guest VMs are shown as UNPROTECTED on the vShield tab in the vSphere Client console.
This refers only to vShield App protection, not to Sophos protection provided by vShield Endpoint.
You should ignore this and follow the instructions in this section to check that VMs are protected.
10.1 Check the status in vSphere Client
You check the status of a security VM in vSphere Client as follows.
Important:
There can be a delay of up to 20 minutes between activating a security VM and seeing its status
in vSphere Client change.
1. In vSphere Client, on the vShield tab, Endpoint page, look for the security VM in the computer
list.
The Description should show “vShield Endpoint Solution, Sophos Anti-Virus for VMware
vShield, enabled” and there should be no critical errors under Endpoint Status.
2. If the Description does not show “enabled” and there is a critical error, perform the relevant
action according to this table:
Description
Action
There is a protocol version mismatch with the
vShield Endpoint module.
Ensure that the vShield Endpoint module and the
security VM have protocols that are compatible with
each other.
vShield Endpoint could not establish a connection Ensure that the security VM is powered on and that
to the security VM.
the network is configured properly.
The security VM is not reporting its status even
though guests are connected.
Internal error. Contact your VMware support
representative.
3. Look for the guest VMs in the computer list, displayed as “vm.”
The Description should show “Thin agent enabled”.
22
startup guide
4. If the Description does not show “enabled”, turn on a guest VM that is turned off, or restart a
guest VM.
This should trigger the status to update.
10.2 Check that on-access scanning is working
On-access scanning is your main method of protection against threats. Whenever you copy,
move, or open a file, or start a program, the security VM scans the file or program and grants
access to it only if it does not pose a threat to your computer.
Important: Ensure that Sophos Anti-Virus for Windows is not installed on any guest VMs that
are protected with a security VM.
To check that a security VM is scanning files on access:
1. Go to eicar.org/86-0-Intended-use.html. Copy the EICAR test string to a new file. Give the file
a name with a .com extension and save it to one of the guest VMs.
2. Try to access the file from the guest VM.
3. In Sophos Enterprise Console, in the computer list in the lower right part of the window, click
the Status tab.
4. In the list of computers, look for the security VM.
■
■
If you have automatic cleanup on, double-click the security VM to open the Computer
Details dialog box. In the "History" section, you should see that EICAR has been detected
and cleaned up.
If you don't have automatic cleanup on, you should see an alert in the Alerts and errors
column. Right-click the security VM. In the Resolve alerts and errors dialog, you should
see that EICAR has been detected but not cleaned up.
If EICAR needs to be cleaned up, see the next section.
10.2.1 Clean up EICAR
To clean up the EICAR test virus, do as follows:
1. Stop the VMware Guest Introspection Agent on the affected guest VM.
As an Administrator, in a Command Prompt window, type:
net stop vsepflt
2. Delete EICAR.
3. Restart the Guest Introspection Agent. Type:
net start vsepflt
4. In Enterprise Console, clear the threat alert.
a) In the computer list, right-click the security VM and select Resolve Alerts and Errors.
b) In the Resolve Alerts and Errors dialog box, on the Alerts tab, select the alert and click
Acknowledge.
23
Sophos Anti-Virus for VMware vShield
10.3 Troubleshoot on-access scanning
If on-access scanning is not working:
1. Ensure that the security VM is in a group whose anti-virus policy specifies that on-access
scanning should be turned on:
a) In Enterprise Console, in the Groups pane, right-click the group that contains the security
VM and select View/Edit Group Policy Details. Check which anti-virus and HIPS policy
is used.
b) In the Policies pane, double-click Anti-virus and HIPS.
c) Double-click the policy that is used by the group that contains the security VM.
d) In the On-access scanning panel, ensure that the Enable on-access scanning check
box is selected. Click OK.
e) In the computer list, right-click the security VM and select Comply with. Then select Group
anti-virus and HIPS policy.
f) Check that the security VM is shown as compliant with the policy.
2. Ensure that each guest VM has the VMware Guest Introspection Agent installed:
a) On each guest VM, run the VMware Tools setup wizard.
b) On the Custom Setup page, ensure that VMware Device Drivers > VMCI Driver > vShield
Drivers is selected for installation.
3. If on-access scanning is still not working, contact Sophos Technical Support.
11 Maintain the security VMs
This section gives advice on post-installation and maintenance tasks.
■
You must power on a security VM manually whenever the ESXi host is taken out of
maintenance or standby mode. Do this before you power on the guest VMs, so that the
guest VMs are protected immediately.
■
If you want to change settings after installation, you must uninstall and re-install the security
VM.
■
If you want to uninstall security VMs, run the installer again and select removal, as described
in the uninstallation section of this guide. You cannot uninstall a security VM by deleting it in
vCenter.
12 View the protected guest VMs
You can view all guest VMs that are protected by your security VMs.
24
startup guide
You view protected guest VMs by using a feature included in the Sophos Anti-Virus for VMware
vShield installer.
1. In the same directory to which you extracted the installer, double-click ssvmtool.exe.
Tip: If you used default settings, the installer will be in the C:\SSVM_2_x_x directory, where
2.x.x is the version number.
A wizard runs.
2.
3.
4.
5.
6.
Select View protected guest VMs.
Enter your vCenter address and credentials.
Enter your vShield Manager address and credentials.
Select the host or hosts where you want to view guest VMs.
Enter your Support password. This is the password you created when you installed your
security VMs.
7. On the Ready to find guest VMs page, click Find.
The wizard begins the search for guest VMs.
8. When the search is finished, click View.
9. A list of Protected guest VMs found is displayed.
The list is also available as a file on your hard disk. To find it, click Show file location.
13 Scan guest VMs
Sophos Anti-Virus for VMware vShield always scans files on access, that is, when they are opened
and closed.
A security VM can also perform a full scan of all guest VMs.You can either run a scan immediately
or at set times.
The full system scan detects but doesn't clean up threats.
Note: The security VM cannot run a scan if it is still in the Enterprise Console Unassigned group.
It must be in a group to which you have applied policies.
Note: The security VM staggers scans so that the ESXi host is not placed under a high load. By
default, two guest VMs are scanned at a time. Therefore, it may take longer for the scanning of
all guest VMs managed by the security VM to complete.
Scan guest VMs now
To run a full scan of all the guest VMs immediately:
1. Go to Enterprise Console and find the security VM in the computer list.
2. Right-click the security VM and select Full System Scan.
Note: Alternatively, on the Actions menu, select Full System Scan.
25
Sophos Anti-Virus for VMware vShield
Scan guest VMs at set times
To run a full scan of all the guest VMs at set times:
1. Go to Enterprise Console.
2. Create a scheduled scan, as explained in the Enterprise Console Help, in the section about
configuring the anti-virus and HIPS policy.
To view details of the scan after it has been run:
In Enterprise Console, in the computer list in the lower right part of the window, double-click the
security VM to display the Computer details dialog box.
14 What happens when a threat is detected
If the security VM detects a threat on one of the guest VMs, it will:
■
Send an alert to Enterprise Console.
■
Clean up the threat automatically or block it, depending on your settings.
Note: The security VM does not automatically clean up threats detected during a full scan of all
guest VMs.
Alerts
In Enterprise Console:
■
An alert is displayed on the dashboard.
■
A red warning icon is displayed in the computer list, on the Status tab, next to the security VM
in the Alerts and errors column.
To find out which guest VM the threat is on, and to learn more about it, see Find out about a threat
(page 27).
If the security VM detects a threat when a user tries to access a file, a message may also be
displayed on the guest VM informing the user that the file cannot be accessed. This depends on
the application used to access the file.
Automatic cleanup
If you have the Sophos Guest VM Agent installed on the guest VM, it will attempt to clean up the
threat automatically.
Note: This applies for guest VMs running Windows Vista and later. On earlier versions of Windows,
you must clean up manually.
26
startup guide
Even if the agent cannot clean up a threat, it will always block it.
For more details of automatic and manual cleanup, see Clean up a threat (page 27).
15 Find out about a threat
To find out more about a threat and how to deal with it:
1. In Enterprise Console, in the computer list in the lower right part of the window, double-click
the security VM to display the Computer details dialog box.
In the History section, Items detected are listed.The name of the threat is shown in the Name
column and the affected guest VM and file are shown in the Details column.
2. Click the name of the threat.
This connects you to the Sophos website, where you can read a description of the item and
advice on what actions to take against it.
16 Clean up a threat
This section describes both automatic and manual cleanup of threats.
If you need more detailed instructions for manual cleanup, see Sophos Anti-Virus for VMware
vShield configuration guide.
16.1 Automatic cleanup
The security VM can automatically clean up threats that it detects, provided that automatic cleanup
is supported on the guest VM's system, and you have the Sophos Guest VM Agent installed on
the guest VM.
Automatic cleanup is supported on:
■
Windows Vista and later.
■
NTFS file systems.
Automatic cleanup is not supported on:
■
Versions of Windows that are earlier than Windows Vista, such as Windows XP and Windows
Server 2003. On those systems, clean up the threats manually, as described in the following
sections.
■
ReFS, CDFS, UDF, or FAT file systems.
■
CDs or read-only file systems and media.
■
Remote file systems.
27
Sophos Anti-Virus for VMware vShield
What happens when there is an automatic cleanup?
When a threat is detected and cleaned up automatically, Enterprise Console:
■
Shows that the threat has been blocked (see the "History" section of the Computer Details
dialog box).
■
Displays an alert that shows what the threat is and whether it is cleanable.
■
Removes the alert if cleanup is successful.
Occasionally a guest VM needs to be restarted to complete the cleanup. In this case, a "Restart
required" alert is displayed for the security VM. To find out which guest VM the alert applies to,
double-click the security VM to open the Computer details dialog box and look in the description
of the alert in the Outstanding alerts and errors section.
Note: If a guest VM is moved from one physical server to another using VMware vSphere vMotion,
or is moved from one security VM to another when cleanup is in progress, the final cleanup status
won't be reported back to Enterprise Console and the alert won't disappear from the console even
if cleanup was successful. In this case, you will need to clear the alert manually. If cleanup fails,
your guest VM will still remain protected - cleanup will be attempted again the next time the threat
is detected.
16.2 Manual cleanup
To clean up a guest VM manually, you can:
■
Restore the guest VM.
■
Use Sophos tools to remove threats.
Restore the guest VM
If you can accept the loss of your data, just restore the VM. Use one of these methods:
■
Delete the affected guest VM and reclone it from the template image.
■
Revert the affected guest VM to the previous known clean snapshot.
Whichever method you use, run a full scan of the guest VM afterwards to ensure that it is clean.
Use Sophos tools
You can use Sophos software to remove threats. This method can be used on guest VMs running
Windows XP or Windows Server 2003, where automatic cleanup is not available.
On the affected guest VM, do as follows:
28
■
Stop the VMware Guest Introspection Agent.
■
Install and run the free Sophos Virus Removal Tool to remove the threat. You can download
the tool from www.sophos.com/en-us/products/free-tools/virus-removal-tool.aspx.
■
Restart the VMware Guest Introspection Agent.
startup guide
17 Upgrade security VMs
Your security VMs are upgraded automatically.
If you need to do any post-upgrade configuration, instructions will be in the Sophos Anti-Virus for
VMware vShield upgrade guide.
18 Uninstall security VMs
To uninstall security VMs, you run the Sophos Anti-Virus for VMware vShield installer again.
You will need your administrator credentials for vCenter and vShield Manager. Remember to
enter them exactly as you would when you log in to vCenter or vShield Manager.
1. In the same directory to which you extracted the installer, double-click ssvmtool.exe.
Tip: If you used default settings, the installer will be in the C:\SSVM_2_x_x directory, where
2.x.x is the version number.
2. A wizard guides you through uninstallation. You should:
■
■
■
■
■
■
Accept the license agreement and extract the installer files.
Select Remove existing security VMs.
Enter your vCenter address and credentials.
Enter your vShield Manager address and credentials.
Select the hosts from which you want to remove Sophos security VMs.
At the summary page, click Uninstall.
The installer uninstalls the security VMs.
19 Appendix: vCenter administrator account
Your vCenter administrator account must have the following permissions:
■
Datastore > Allocate space
■
Network > Assign network
■
vApp > Import
■
vApp > vApp instance configuration
■
Virtual machine > Configuration > Add new disk
■
Virtual machine > Guest Operation > Guest Operation Modifications
■
Virtual machine > Guest Operation > Guest Operation Program Execution
29
Sophos Anti-Virus for VMware vShield
■
Virtual machine > Guest Operation > Guest Operation Queries
■
Virtual machine > Interaction > Power Off
■
Virtual machine > Interaction > Power On
■
Virtual machine > Inventory > Remove
20 Appendix: Set the CPU configuration
If you have a large number of guest VMs on a host, you should ensure that the security VM has
enough processing power to scan the files they use when they all start up.
To do this, you edit the CPU configuration for the security VM.
Note:
You can edit the CPU configuration at any time. However, if you do it after you have added the
security VM to a computer group in Enterprise Console, you should wait until the security VM
complies with the group policy.
1. Power off the security VM.
2. In vSphere Client, select the security VM.
3. Select Edit Settings > Hardware > CPUs. Then specify the number of CPUs.
Adding CPUs increases the number of guest VMs the security VM can handle, as shown in
the table.
CPUs
Performance
2
This is the default.
4
Large increase compared with 2 CPUs.
6
Small increase compared with 4 CPUs.
8
Minimal increase compared with 6 CPUs.
21 Technical support
You can find technical support for Sophos products in any of these ways:
30
■
Visit the SophosTalk community at community.sophos.com/ and search for other users who
are experiencing the same problem.
■
Visit the Sophos support knowledgebase at www.sophos.com/en-us/support.aspx.
startup guide
■
Download the product documentation at www.sophos.com/en-us/support/documentation.aspx.
■
Open a ticket with our support team at
https://secure2.sophos.com/support/contact-support/support-query.aspx.
22 Legal notices
Copyright © 2015 Sophos Limited. All rights reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording or otherwise unless you are either a valid licensee where
the documentation can be reproduced in accordance with the license terms or you otherwise have
the prior permission in writing of the copyright owner.
Sophos, Sophos Anti-Virus and SafeGuard are registered trademarks of Sophos Limited, Sophos
Group and Utimaco Safeware AG, as applicable. All other product and company names mentioned
are trademarks or registered trademarks of their respective owners.
ACE™, TAO™, CIAO™, DAnCE™, and CoSMIC™
ACE™, TAO™, CIAO™, DAnCE™, and CoSMIC™ (henceforth referred to as "DOC software") are
copyrighted by Douglas C. Schmidt and his research group at Washington University, University
of California, Irvine, and Vanderbilt University, Copyright (c) 1993-2014, all rights reserved. Since
DOC software is open-source, freely available software, you are free to use, modify, copy, and
distribute—perpetually and irrevocably—the DOC software source code and object code produced
from the source, as well as copy and distribute modified versions of this software. You must,
however, include this copyright statement along with any code built using DOC software that you
release. No copyright statement needs to be provided if you just ship binary executables of your
software products.
You can use DOC software in commercial and/or binary software releases and are under no
obligation to redistribute any of your source code that is built using DOC software. Note, however,
that you may not misappropriate the DOC software code, such as copyrighting it yourself or
claiming authorship of the DOC software code, in a way that will prevent DOC software from being
distributed freely using an open-source development model. You needn't inform anyone that
you're using DOC software in your software, though we encourage you to let us know so we can
promote your project in the DOC software success stories.
The ACE, TAO, CIAO, DAnCE, and CoSMIC web sites are maintained by the DOC Group at the
Institute for Software Integrated Systems (ISIS) and the Center for Distributed Object Computing
of Washington University, St. Louis for the development of open-source software as part of the
open-source software community. Submissions are provided by the submitter "as is" with no
warranties whatsoever, including any warranty of merchantability, noninfringement of third party
intellectual property, or fitness for any particular purpose. In no event shall the submitter be liable
for any direct, indirect, special, exemplary, punitive, or consequential damages, including without
limitation, lost profits, even if advised of the possibility of such damages. Likewise, DOC software
is provided as is with no warranties of any kind, including the warranties of design, merchantability,
and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage
or trade practice. Washington University, UC Irvine, Vanderbilt University, their employees, and
students shall have no liability with respect to the infringement of copyrights, trade secrets or any
patents by DOC software or any part thereof. Moreover, in no event will Washington University,
31
Sophos Anti-Virus for VMware vShield
UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or
profits or other special, indirect and consequential damages.
DOC software is provided with no support and without any obligation on the part of Washington
University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use,
correction, modification, or enhancement. A number of companies around the world provide
commercial support for DOC software, however. DOC software is Y2K-compliant, as long as the
underlying OS platform is Y2K-compliant. Likewise, DOC software is compliant with the new US
daylight savings rule passed by Congress as "The Energy Policy Act of 2005," which established
new daylight savings times (DST) rules for the United States that expand DST as of March 2007.
Since DOC software obtains time/date and calendaring information from operating systems users
will not be affected by the new DST rules as long as they upgrade their operating systems
accordingly.
The names ACE™, TAO™, CIAO™, DAnCE™, CoSMIC™, Washington University, UC Irvine, and
Vanderbilt University, may not be used to endorse or promote products or services derived from
this source without express written permission from Washington University, UC Irvine, or Vanderbilt
University. This license grants no permission to call products or services derived from this source
ACE™, TAO™, CIAO™, DAnCE™, or CoSMIC™, nor does it grant permission for the name
Washington University, UC Irvine, or Vanderbilt University to appear in their names.
If you have any suggestions, additions, comments, or questions, please let me know.
Douglas C. Schmidt
Bzip2
This program, "bzip2", the associated library "libbzip2", and all documentation, are copyright ©
1996-2010 Julian R Seward. 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. The origin of this software must not be misrepresented; you must not claim that you wrote the
original software. If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
3. Altered source versions must be plainly marked as such, and must not be misrepresented as
being the original software.
4. The name of the author may not be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS'' AND ANY EXPRESS 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 AUTHOR 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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Julian Seward, [email protected]
32
startup guide
bzip2/libbzip2 version 1.0.6 of 6 September 2010
curl
Copyright (c) 1996 - 2014, Daniel Stenberg, <[email protected]>.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee
is hereby granted, provided that the above copyright notice and this permission notice appear in
all copies.
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 OF THIRD PARTY
RIGHTS. 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.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising
or otherwise to promote the sale, use or other dealings in this Software without prior written
authorization of the copyright holder.
file
Copyright (c) Ian F. Darwin 1986, 1987, 1989, 1990, 1991, 1992, 1994, 1995.
Software written by Ian F. Darwin and others; maintained 1994- Christos Zoulas.
This software is not subject to any export provision of the United States Department of Commerce,
and may be exported to any country or planet.
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 immediately at the
beginning of the file, without modification, 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS 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 AUTHOR OR 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
33
Sophos Anti-Virus for VMware vShield
GNU General Public License
Some software programs are licensed (or sublicensed) to the user under the GNU General Public
License (GPL) or similar Free Software licenses which, among other rights, permit the user to
copy, modify, and redistribute certain programs, or portions thereof, and have access to the source
code. The GPL requires for any software licensed under the GPL, which is distributed to a user
in an executable binary format, that the source code also be made available to those users. For
any such software which is distributed along with this Sophos product, the source code is available
by submitting a request to Sophos via email to [email protected]. A copy of the GPL
terms can be found at www.gnu.org/copyleft/gpl.html
Info-ZIP
Copyright © 1990–2007 Info-ZIP. All rights reserved.
For the purposes of this copyright and license, “Info-ZIP” is defined as the following set of
individuals:
Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter
Goatley, Ed Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath,
Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor
Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai
Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda, Christian Spieler, Cosmin Truta,
Antoine Verheijen, Paul von Behren, Rich Wales, Mike White
This software is provided “as is,” without warranty of any kind, express or implied. In no event
shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or
consequential damages arising out of the use of or inability to use this software.
Permission is granted to anyone to use this software for any purpose, including commercial
applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. Redistributions of source code must retain the above copyright notice, definition, disclaimer,
and this list of conditions.
2. Redistributions in binary form (compiled executables and libraries) must reproduce the above
copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other
materials provided with the distribution. The sole exception to this condition is redistribution
of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is
permitted without inclusion of this license, as long as the normal SFX banner has not been
removed from the binary or disabled.
3. Altered versions—including, but not limited to, ports to new operating systems, existing ports
with new graphical interfaces, versions with modified or added functionality, and dynamic,
shared, or static library versions not from Info-ZIP—must be plainly marked as such and must
not be misrepresented as being the original source or, if binaries, compiled from the original
source. Such altered versions also must not be misrepresented as being Info-ZIP
releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP"
(or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip,"
"WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further
prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or the
Info-ZIP URL(s), such as to imply Info-ZIP will provide support for the altered versions.
4. Info-ZIP retains the right to use the names “Info-ZIP,” “Zip,” “UnZip,” “UnZipSFX,” “WiZ,” “Pocket
UnZip,” “Pocket Zip,” and “MacZip” for its own source and binary releases.
34
startup guide
libcap
Unless otherwise *explicitly* stated, the following text describes the licensed conditions under
which the contents of this libcap release may be used and distributed:
Redistribution and use in source and binary forms of libcap, with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain any existing copyright notice, and this entire
permission notice in its entirety, including the disclaimer of warranties.
2. Redistributions in binary form must reproduce all prior and current copyright notices, this list
of conditions, and the following disclaimer in the documentation and/or other materials provided
with the distribution.
3. The name of any author may not be used to endorse or promote products derived from this
software without their specific prior written permission.
ALTERNATIVELY, this product may be distributed under the terms of the GNU General Public
License (v2.0 - see below), in which case the provisions of the GNU GPL are required INSTEAD
OF the above restrictions. (This clause is necessary due to a potential conflict between the GNU
GPL and the restrictions contained in a BSD-style copyright.)
THIS SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESS 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
AUTHOR(S) 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
libdnet
Copyright (c) 2000-2006 Dug Song <[email protected]> All rights reserved, all wrongs
reversed.
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The names of the authors and copyright holders may not be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS 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
AUTHOR 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
35
Sophos Anti-Virus for VMware vShield
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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
libmagic – file type detection
Copyright © Ian F. Darwin 1986, 1987, 1989, 1990, 1991, 1992, 1994, 1995.
Software written by Ian F. Darwin and others; maintained 1994–2004 Christos Zoulas.
This software is not subject to any export provision of the United States Department of Commerce,
and may be exported to any country or planet.
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 immediately at the
beginning of the file, without modification, 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS “AS IS” AND ANY
EXPRESS 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 AUTHOR OR 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
libtirpc
Copyright (c) Copyright (c) Bull S.A. 2005 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The name of the author may not be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS 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 AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
36
startup guide
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
lockfile
Copyright © 2007 Skip Montanaro.
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.
log4cplus
Copyright (C) 2010, Vaclav Haisman. 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
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
APACHE SOFTWARE FOUNDATION OR ITS 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 OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
37
Sophos Anti-Virus for VMware vShield
Medusa web server
Medusa was once distributed under a ‘free for non-commercial use’ license, but in May of 2000
Sam Rushing changed the license to be identical to the standard Python license at the time. The
standard Python license has always applied to the core components of Medusa, this change just
frees up the rest of the system, including the http server, ftp server, utilities, etc. Medusa is
therefore under the following license:
Permission to use, copy, modify, and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appear in all copies
and that both that copyright notice and this permission notice appear in supporting documentation,
and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution
of the software without specific, written prior permission.
SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Sam would like to take this opportunity to thank all of the folks who supported Medusa over the
years by purchasing commercial licenses.
mock
Copyright (c) 2003-2012, Michael Foord 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS
IS AND ANY EXPRESS 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 COPYRIGHT OWNER OR 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
ncurses
Copyright (c) 1998-2004,2006 Free Software Foundation, Inc.
38
startup guide
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, distribute with
modifications, 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 ABOVE 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.
Except as contained in this notice, the name(s) of the above copyright holders shall not be used
in advertising or otherwise to promote the sale, use or other dealings in this Software without prior
written authorization.
netaddr
Copyright © 2008-2011, David P. D. Moss. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
■
Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
■
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
■
Neither the name of David P. D. Moss nor the names of contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS 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 COPYRIGHT OWNER OR
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
License for incorporated software:
intset.py - Immutable integer set type
Copyright © 2006, Heiko Wundram.
39
Sophos Anti-Virus for VMware vShield
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.
Network Time Protocol
Copyright (c) University of Delaware 1992-2011
Permission to use, copy, modify, and distribute this software and its documentation for any purpose
with or without fee is hereby granted, provided that the above copyright notice appears in all
copies and that both the copyright notice and this permission notice appear in supporting
documentation, and that the name University of Delaware not be used in advertising or publicity
pertaining to distribution of the software without specific, written prior permission. The University
of Delaware makes no representations about the suitability this software for any purpose. It is
provided "as is" without express or implied warranty.
OpenSSH
This file is part of the OpenSSH software.
The licences which components of this software fall under are as follows. First, we will summarize
and say that all components are under a BSD licence, or a licence more free than that.
OpenSSH contains no GPL code.
1)
Copyright (c) 1995 Tatu Ylonen <[email protected]>, Espoo, Finland All rights reserved
As far as I am concerned, the code I have written for this software can be used freely for any
purpose. Any derived versions of this software must be clearly marked as such, and if the derived
work is incompatible with the protocol description in the RFC file, it must be called by a name
other than "ssh" or "Secure Shell".
[Tatu continues]
However, I am not implying to give any licenses to any patents or copyrights held by third parties,
and the software includes parts that are not under my direct control. As far as I know, all included
source code is used in accordance with the relevant license agreements and can be used freely
for any purpose (the GNU license being the most restrictive); see below for details.
40
startup guide
[However, none of that term is relevant at this point in time. All of these restrictively licenced
software components which he talks about have been removed from OpenSSH, i.e.,
■
RSA is no longer included, found in the OpenSSL library
■
IDEA is no longer included, its use is deprecated
■
DES is now external, in the OpenSSL library
■
GMP is no longer used, and instead we call BN code from OpenSSL
■
Zlib is now external, in a library
■
The make-ssh-known-hosts script is no longer included
■
TSS has been removed
■
MD5 is now external, in the OpenSSL library
■
RC4 support has been replaced with ARC4 support from OpenSSL
■
Blowfish is now external, in the OpenSSL library
[The licence continues]
Note that any information and cryptographic algorithms used in this software are publicly available
on the Internet and at any major bookstore, scientific library, and patent office worldwide. More
information can be found e.g. at "http://www.cs.hut.fi/crypto".
The legal status of this program is some combination of all these permissions and restrictions.
Use only at your own responsibility. You will be responsible for any legal consequences yourself;
I am not making any claims whether possessing or using this is legal or not in your country, and
I am not taking any responsibility on your behalf.
NO WARRANTY
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
2)
The 32-bit CRC compensation attack detector in deattack.c was contributed by CORE SDI S.A.
under a BSD-style license.
41
Sophos Anti-Virus for VMware vShield
Cryptographic attack detector for ssh - source code
Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina.
All rights reserved. Redistribution and use in source and binary forms, with or without modification,
are permitted provided that this copyright notice is retained.
THIS SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES
ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES
RESULTING FROM THE USE OR MISUSE OF THIS SOFTWARE.
Ariel Futoransky <[email protected]>
<http://www.core-sdi.com>
3)
ssh-keyscan was contributed by David Mazieres under a BSD-style license.
Copyright 1995, 1996 by David Mazieres <[email protected]>.
Modification and redistribution in source and binary forms is permitted provided that due credit is
given to the author and the OpenBSD project by leaving this copyright notice intact.
4)
The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers and Paulo Barreto is in the
public domain and distributed with the following license:
@version 3.0 (December 2000)
Optimised ANSI C code for the Rijndael cipher (now AES)
@author Vincent Rijmen <[email protected]>
@author Antoon Bosselaers <[email protected]>
@author Paulo Barreto <[email protected]
This code is hereby placed in the public domain.
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS 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 AUTHORS OR 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 OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
5)
One component of the ssh source code is under a 3-clause BSD license, held by the University
of California, since we pulled these parts from original Berkeley code.
Copyright (c) 1983, 1990, 1992, 1993, 1995 The Regents of the University of California. All rights
reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
42
startup guide
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS'' AND ANY
EXPRESS 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 REGENTS OR 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
6)
Remaining components of the software are provided under a standard 2-term BSD licence with
the following names as copyright holders:
Markus Friedl
Theo de Raadt
Niels Provos
Dug Song
Aaron Campbell
Damien Miller
Kevin Steves
Daniel Kouril
Wesley Griffin
Per Allansson
Nils Nordman
Simon Wilkinson
Portable OpenSSH additionally includes code from the following copyright holders, also under
the 2-term BSD license:
Ben Lindstrom
Tim Rice
Andre Lucas
Chris Adams
Corinna Vinschen
Cray Inc.
Denis Parker
Gert Doering
Jakob Schlyter
Jason Downs
Juha Yrjölä
Michael Stone
Networks Associates Technology, Inc.
43
Sophos Anti-Virus for VMware vShield
Solar Designer
Todd C. Miller
Wayne Schroeder
William Jones
Darren Tucker
Sun Microsystems
The SCO Group
Daniel Walsh
Red Hat, Inc
Simon Vallet / Genoscope
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS'' AND ANY EXPRESS 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 AUTHOR 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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
8)
Portable OpenSSH contains the following additional licenses:
a) md5crypt.c, md5crypt.h
"THE BEER-WARE LICENSE" (Revision 42): <[email protected]> wrote this file. As long as
you retain this notice you can do whatever you want with this stuff. If we meet some day, and you
think this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
b) snprintf replacement
Copyright Patrick Powell 1995 This code is based on code written by Patrick Powell
([email protected]) It may be used for any purpose as long as this notice remains intact on
all source code distributions
c) Compatibility code (openbsd-compat)
Apart from the previously mentioned licenses, various pieces of code in the openbsd-compat/
subdirectory are licensed as follows:
Some code is licensed under a 3-term BSD license, to the following copyright holders:
Todd C. Miller
Theo de Raadt
Damien Miller
Eric P. Allman
44
startup guide
The Regents of the University of California
Constantin S. Svintsoff
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS'' AND ANY
EXPRESS 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 REGENTS OR 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 OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
Some code is licensed under an ISC-style license, to the following copyright holders:
Internet Software Consortium.
Todd C. Miller
Reyk Floeter
Chad Mynhier
Permission to use, copy, modify, and distribute this software for any purpose with or without fee
is hereby granted, provided that the above copyright notice and this permission notice appear in
all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C. MILLER BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Some code is licensed under a MIT-style license to the following copyright holders:
Free Software Foundation, Inc.
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, distribute with
modifications, 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.
45
Sophos Anti-Virus for VMware vShield
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 ABOVE 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.
Except as contained in this notice, the name(s) of the above copyright holders shall not be used
in advertising or otherwise to promote the sale, use or other dealings in this Software without prior
written authorization.
OpenSSL Cryptography and SSL/TLS Toolkit
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License
and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually
both licenses are BSD-style Open Source licenses. In case of any license issues related to
OpenSSL please contact [email protected].
OpenSSL license
Copyright © 1998–2011 The OpenSSL Project. 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/)”
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote
products derived from this software without prior written permission. For written permission,
please contact [email protected].
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear
in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “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 OpenSSL PROJECT OR ITS 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
46
startup guide
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
This product includes cryptographic software written by Eric Young ([email protected]). This
product includes software written by Tim Hudson ([email protected]).
Original SSLeay license
Copyright © 1995–1998 Eric Young ([email protected]) All rights reserved.
This package is an SSL implementation written by Eric Young ([email protected]). The
implementation was written so as to conform with Netscape’s SSL.
This library is free for commercial and non-commercial use as long as the following conditions
are adhered to. The following conditions apply to all code found in this distribution, be it the RC4,
RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this
distribution is covered by the same copyright terms except that the holder is Tim Hudson
([email protected]).
Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be
removed. If this package is used in a product, Eric Young should be given attribution as the author
of the parts of the library used. This can be in the form of a textual message at program startup
or in documentation (online or textual) provided with the package.
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 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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement:
“This product includes cryptographic software written by Eric Young ([email protected])”
The word “cryptographic” can be left out if the routines from the library being used are not
cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory
(application code) you must include an acknowledgement:
“This product includes software written by Tim Hudson ([email protected])”
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS 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 AUTHOR OR 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 OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
47
Sophos Anti-Virus for VMware vShield
The license and distribution terms for any publically available version or derivative of this code
cannot be changed. i.e. this code cannot simply be copied and put under another distribution
license [including the GNU Public License.]
Protocol Buffers (libprotobuf)
Copyright 2008, Google Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
■
Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
■
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
■
Neither the name of Google Inc. nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS 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 COPYRIGHT OWNER OR
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Code generated by the Protocol Buffer compiler is owned by the owner of the input file used when
generating it. This code is not standalone and requires a support library to be linked with it. This
support library is itself covered by the above license.
pyasn1
Copyright (c) 2005-2013, Ilya Etingof <[email protected]> All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS 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 COPYRIGHT HOLDERS AND
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
48
startup guide
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
pycrypto
Distribute and use freely; there are no restrictions on further dissemination and usage except
those imposed by the laws of your country of residence. This software is provided “as is” without
warranty of fitness for use or suitability for any purpose, express or implied. Use at your own risk
or not at all.
Incorporating the code into commercial products is permitted; you do not have to make source
available or contribute your changes back (though that would be nice).
– –amk (www.amk.ca)
pysmb
Copyright (C) 2001-2013 Michael Teo <miketeo (a) miketeo.net>
This software is provided 'as-is', without any express or implied warranty. In no event will the
author be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial
applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the
original software. If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as
being the original software.
3. This notice cannot be removed or altered from any source distribution.
pysphere
Copyright (c) 2011, Sebastian Tello
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
■
Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
■
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
■
Neither the name of copyright holders nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
49
Sophos Anti-Virus for VMware vShield
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS 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 COPYRIGHT HOLDER OR
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Python
PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
1. This LICENSE AGREEMENT is between the Python Software Foundation (“PSF”), and the
Individual or Organization (“Licensee”) accessing and otherwise using this software (“Python”)
in source or binary form and its associated documentation.
2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee
a nonexclusive, royalty-free, worldwide license to reproduce, analyze, test, perform and/or
display publicly, prepare derivative works, distribute, and otherwise use Python alone or in
any derivative version, provided, however, that PSF’s License Agreement and PSF’s notice
of copyright, i.e., “Copyright © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Python
Software Foundation; All Rights Reserved” are retained in Python alone or in any derivative
version prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on or incorporates Python or
any part thereof, and wants to make the derivative work available to others as provided herein,
then Licensee hereby agrees to include in any such work a brief summary of the changes
made to Python.
4. PSF is making Python available to Licensee on an “AS IS” basis. PSF MAKES NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE,
BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR
WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE
OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR
ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT
OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE
THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material breach of its terms and
conditions.
7. Nothing in this License Agreement shall be deemed to create any relationship of agency,
partnership, or joint venture between PSF and Licensee. This License Agreement does not
grant permission to use PSF trademarks or trade name in a trademark sense to endorse or
promote products or services of Licensee, or any third party.
8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms
and conditions of this License Agreement.
50
startup guide
strace
Copyright (c) 1991, 1992 Paul Kranenburg <[email protected]>
Copyright (c) 1993 Branko Lankester <[email protected]>
Copyright (c) 1993 Ulrich Pegelow <[email protected]>
Copyright (c) 1995, 1996 Michael Elizabeth Chastain <[email protected]>
Copyright (c) 1993, 1994, 1995, 1996 Rick Sladkey <[email protected]>
Copyright (C) 1998-2001 Wichert Akkerman <[email protected]>
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The name of the author may not be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS'' AND ANY EXPRESS 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 AUTHOR 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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
sudo
Copyright (c) 1994-1996, 1998-2013 Todd C. Miller <[email protected]>
Permission to use, copy, modify, and distribute this software for any purpose with or without fee
is hereby granted, provided that the above copyright notice and this permission notice appear in
all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
51
Sophos Anti-Virus for VMware vShield
Sponsored in part by the Defense Advanced Research Projects Agency (DARPA) and Air Force
Research Laboratory, Air Force Materiel Command, USAF, under agreement number
F39502-99-1-0512.
tcl
This software is copyrighted by the Regents of the University of California, Sun Microsystems,
Inc., Scriptics Corporation, ActiveState Corporation and other parties. The following terms apply
to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software
and its documentation for any purpose, provided that existing copyright notices are retained in
all copies and that this notice is included verbatim in any distributions. No written agreement,
license, or royalty fee is required for any of the authorized uses. Modifications to this software
may be copyrighted by their authors and need not follow the licensing terms described here,
provided that the new terms are clearly indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT
OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF,
EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS
PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO
OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the
Government shall have only "Restricted Rights" in the software and related documentation as
defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are
acquiring the software on behalf of the Department of Defense, the software shall be classified
as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as
defined in Clause 252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the authors
grant the U.S. Government and others acting in its behalf permission to use and distribute the
software in accordance with the terms specified in this license.
TinyXML XML parser
www.sourceforge.net/projects/tinyxml
Original code by Lee Thomason (www.grinninglizard.com)
This software is provided ‘as-is’, without any express or implied warranty. In no event will the
authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial
applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the
original software. If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as
being the original software.
52
startup guide
3. This notice may not be removed or altered from any source distribution.
Vim
1. There are no restrictions on distributing unmodified copies of Vim except that they must include
this license text. You can also distribute unmodified parts of Vim, likewise unrestricted except
that they must include this license text. You are also allowed to include executables that you
made from the unmodified Vim sources, plus your own usage examples and Vim scripts.
2. It is allowed to distribute a modified (or extended) version of Vim, including executables and/or
source code, when the following four conditions are met:
a. This license text must be included unmodified.
b. The modified Vim must be distributed in one of the following five ways:
a. If you make changes to Vim yourself, you must clearly describe in the distribution how
to contact you. When the maintainer asks you (in any way) for a copy of the modified
Vim you distributed, you must make your changes, including source code, available to
the maintainer without fee. The maintainer reserves the right to include your changes
in the official version of Vim. What the maintainer will do with your changes and under
what license they will be distributed is negotiable. If there has been no negotiation then
this license, or a later version, also applies to your changes. The current maintainer is
Bram Moolenaar <[email protected]>. If this changes it will be announced in appropriate
places (most likely vim.sf.net, www.vim.org and/or comp.editors). When it is completely
impossible to contact the maintainer, the obligation to send him your changes ceases.
Once the maintainer has confirmed that he has received your changes they will not
have to be sent again.
b. If you have received a modified Vim that was distributed as mentioned under 2.2.1 you
are allowed to further distribute it unmodified, as mentioned at 1). If you make additional
changes the text under 2.2.1 applies to those changes.
c. Provide all the changes, including source code, with every copy of the modified Vim
you distribute. This may be done in the form of a context diff. You can choose what
license to use for new code you add. The changes and their license must not restrict
others from making their own changes to the official version of Vim.
d. When you have a modified Vim which includes changes as mentioned under 2.2.3, you
can distribute it without the source code for the changes if the following three conditions
are met:
■
The license that applies to the changes permits you to distribute the changes to the
Vim maintainer without fee or restriction, and permits the Vim maintainer to include
the changes in the official version of Vim without fee or restriction.
■
You keep the changes for at least three years after last distributing the corresponding
modified Vim. When the maintainer or someone who you distributed the modified
Vim to asks you (in any way) for the changes within this period, you must make them
available to him.
■
You clearly describe in the distribution how to contact you. This contact information
must remain valid for at least three years after last distributing the corresponding
modified Vim, or as long as possible.
e. When the GNU General Public License (GPL) applies to the changes, you can distribute
the modified Vim under the GNU GPL version 2 or any later version.
53
Sophos Anti-Virus for VMware vShield
c. A message must be added, at least in the output of the ":version" command and in the intro
screen, such that the user of the modified Vim is able to see that it was modified. When
distributing as mentioned under 2.2.5 adding the message is only required for as far as
this does not conflict with the license used for the changes.
d. The contact information as required under 2.2.1 and 2.2.4 must not be removed or changed,
except that the person himself can make corrections.
3. If you distribute a modified version of Vim, you are encouraged to use the Vim license for your
changes and make them available to the maintainer, including the source code. The preferred
way to do this is by e-mail or by uploading the files to a server and e-mailing the URL. If the
number of changes is small (e.g., a modified Makefile) e-mailing a context diff will do. The
e-mail address to be used is <[email protected]>
4. It is not allowed to remove this license from the distribution of the Vim sources, parts of it or
from a modified version. You may use this license for previous Vim releases instead of the
license that they came with, at your option.
zlib data compression library
©
1995–2013 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the
authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial
applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the
original software. If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as
being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly [email protected]
Mark Adler [email protected]
ZSI
Copyright (c) 2003, The Regents of the University of California, through Lawrence Berkeley
National Laboratory (subject to receipt of any required approvals from the U.S. Dept. of Energy).
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
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 following disclaimer in the documentation and/or other materials provided with the
distribution.
54
startup guide
3. Neither the name of the University of California, Lawrence Berkeley National Laboratory, U.S.
Dept. of Energy nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS 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 COPYRIGHT OWNER OR
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 OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
You are under no obligation whatsoever to provide any bug fixes, patches, or upgrades to the
features, functionality or performance of the source code ("Enhancements") to anyone; however,
if you choose to make your Enhancements available either publicly, or directly to Lawrence
Berkeley National Laboratory, without imposing a separate written license agreement for such
Enhancements, then you hereby grant the following license: a non-exclusive, royalty-free perpetual
license to install, use, modify, prepare derivative works, incorporate into other computer software,
distribute, and sublicense such Enhancements or derivative works thereof, in binary and source
code form.
55
">