Sophos Enterprise Console Startup Guide

Sophos Enterprise Console startup guide for Linux and

UNIX

Product version:

Document date:

5.4

April 2016

2

Contents

1 About this guide........................................................................................................................3

2 System requirements................................................................................................................4

3 Protecting Linux computers......................................................................................................5

3.1 Install Sophos Anti-Virus for the first time manually...................................................5

3.2 Create a deployment package....................................................................................6

3.3 Installing Sophos Anti-Virus using the deployment package......................................6

4 Protecting UNIX computers......................................................................................................8

4.1 Install Sophos Anti-Virus for the first time manually...................................................8

4.2 Create a deployment package....................................................................................9

4.3 Installing Sophos Anti-Virus using the deployment package......................................9

5 Check the health of your network...........................................................................................11

6 Appendix: Command-line options for mkinstpkg....................................................................12

7 Technical support....................................................................................................................14

8 Legal notices..........................................................................................................................15

startup guide for Linux and UNIX

1 About this guide

This guide describes the procedure for installing Sophos Anti-Virus on Linux and UNIX computers, so that it is managed by Sophos Enterprise Console. The guide assumes that you have installed the management tools, as explained in the Sophos Enterprise Console advanced startup guide.

Sophos documentation is published at http://www.sophos.com/en-us/support/documentation.aspx

.

3

4

Sophos Enterprise Console

2 System requirements

For system requirements, go to the system requirements page of the Sophos website

( www.sophos.com/en-us/products/all-system-requirements.aspx

).

For details of any additional requirements, for example for language support, see the "Additional information" section in the release notes.

You must have internet access in order to download the installation software from the Sophos website.

startup guide for Linux and UNIX

3 Protecting Linux computers

To protect Linux computers using a deployment package, you must:

■ Install Sophos Anti-Virus on a Linux server for the first time manually.

■

■

Create a deployment package.

Install Sophos Anti-Virus on the rest of the Linux computers.

3.1 Install Sophos Anti-Virus for the first time manually

This section assumes that you have downloaded Sophos Anti-Virus, as explained in the Sophos

Enterprise Console advanced startup guide.

1. To find out the path of the shared folder to which Sophos Anti-Virus has been downloaded, known as the bootstrap location: a) In Enterprise Console, on the View menu, click Bootstrap Locations.

In the Bootstrap Locations dialog box, the Location column displays the path of the bootstrap location for each platform.

b) Make a note of the relevant path.

2. Log on to your Linux server as root.

3. Mount the bootstrap location.

4. Change to the bootstrap location.

5. Run the install script:

./install.sh

When prompted, choose to enable remote management.

When installation has finished, in Enterprise Console the Linux server appears in the

Unassigned group.

6. If you have not done so already, in Enterprise Console create a new group where you want to put the Linux server.

7. Drag the server from the Unassigned group to this group.

8. By default, this group already has a default updating policy applied to it. If you need to edit the policy, see the Enterprise Console Help.

9. On the Linux server, trigger the first update:

/opt/sophos-av/bin/savupdate

Now create a deployment package.

5

6

Sophos Enterprise Console

3.2 Create a deployment package

You can use the mkinstpkg script to create a deployment package for your end-users. This script prompts you for information about how Sophos Anti-Virus will be installed on your Linux computers, and the answers gathered are inserted into the deployment package. When the end-user installs from this deployment package, it will not prompt for any information and will set up both the update location and credentials correctly. You can create a package in tar, RPM or deb format.

Note: The deb format is supported in Sophos Anti-Virus version 9.11 and later.

Note: The mkinstpkg script is for use within your organization only. Please read the license agreement and legal notice displayed by the mkinstpkg script.

Note: The instructions here show how to specify the package format. For details of other options you can use, see

Appendix: Command-line options for mkinstpkg (page 12)

To create a deployment package:

1. On the Linux server where you installed Sophos Anti-Virus, change to the directory

/opt/sophos-av/update/ .

2. To create a package in the current directory, do one of the following:

■ To create a tar format deployment package, called savinstpkg.tgz

, type:

./mkinstpkg

■ To create an RPM format deployment package, called savinstpkg-0.0-1.i586.rpm

, type:

./mkinstpkg -r

Note: The filename might be slightly different depending on the RPM setup.

■ To create a deb format deployment package called savinstpkg.deb

, type:

./mkinstpkg -D

Note: The deb format is supported in Sophos Anti-Virus version 9.11 and later.

3. When prompted, choose to have the computers managed by Enterprise Console.

4. When prompted for the location, enter the bootstrap location (as seen from the Linux computers).

Now you are ready to install Sophos Anti-Virus using this deployment package.

3.3 Installing Sophos Anti-Virus using the deployment package

You use the package to install Sophos Anti-Virus in one of two ways:

■ Manually on each computer. This approach can be used with a package in RPM or tar format.

■ Automatically across the network. This approach can be used only with a package in RPM format.

startup guide for Linux and UNIX

3.3.1 Install Sophos Anti-Virus manually

1. Use your own tools to copy the deployment package to the computers where you want to install Sophos Anti-Virus.

2. Go to each computer and log in as root.

3. Place the deployment package in a temporary directory and change to that directory.

4. Do one of the following:

■ To install from the tar package, type: tar -zxvf savinstpkg.tgz

./sophos-av/install.sh

■ To install from the RPM package, type:

rpm -i RPM package

■ To install from the deb package, type:

dpkg -i deb package

The necessary files are copied from the server and Sophos Anti-Virus is installed. From now on,

Sophos Anti-Virus will be updated automatically whenever the bootstrap location is updated.

Sophos Anti-Virus also sends product and platform information to Sophos to help us with product development. See Sophos Knowledgebase Article 121214 .

3.3.2 Install Sophos Anti-Virus automatically

■ To install Sophos Anti-Virus automatically from the deployment package, use one of the operating system administration tools that support remote deployment.

For more information, see the documentation for that tool.

Once Sophos Anti-Virus is installed, it will be started and will be updated automatically whenever the bootstrap location is updated.

Sophos Anti-Virus also sends product and platform information to Sophos to help us with product development. See Sophos Knowledgebase Article 121214 .

7

Sophos Enterprise Console

8

4 Protecting UNIX computers

To protect UNIX computers, you must use a deployment package. To do this:

■ Install Sophos Anti-Virus on a UNIX server for the first time manually.

■

■

Create a deployment package.

Install Sophos Anti-Virus on the rest of the UNIX computers.

Note: In the Japanese AIX environment, please specify "LANG=C" during installation.

4.1 Install Sophos Anti-Virus for the first time manually

This section assumes that you have downloaded Sophos Anti-Virus, as explained in the Sophos

Enterprise Console advanced startup guide.

Note: If Sophos Anti-Virus version 4 is installed on your UNIX server, you must uninstall it before you install version 9. For information, see the Sophos Anti-Virus for UNIX and Linux startup guide for version 4.

1. To find out the path of the shared folder to which Sophos Anti-Virus has been downloaded, known as the bootstrap location: a) In Enterprise Console, on the View menu, click Bootstrap Locations.

In the Bootstrap Locations dialog box, the Location column displays the path of the bootstrap location for each platform.

b) Make a note of the relevant path.

2. Log on to your UNIX server as root.

3. Mount the bootstrap location.

4. Change to the bootstrap location.

5. Run the install script:

./install.sh

When prompted, choose to enable remote management.

When installation has finished, in Enterprise Console the UNIX server appears in the

Unassigned group.

6. If you have not done so already, in Enterprise Console create a new group where you want to put the UNIX server.

7. Drag the server from the Unassigned group to this group.

8. By default, this group already has a default updating policy applied to it. If you need to edit the policy, see the Enterprise Console Help.

9. On the UNIX server, trigger the first update:

/opt/sophos-av/bin/savupdate

Now create a deployment package.

startup guide for Linux and UNIX

4.2 Create a deployment package

You can use the mkinstpkg script to create a deployment package for your end-users. This script prompts you for information about how Sophos Anti-Virus will be installed on your UNIX computers, and the answers gathered are inserted into the deployment package. When the end-user installs from this deployment package, it will not prompt for any information and will set up both the update location and credentials correctly. You can create a package in tar format.

Note: The mkinstpkg script is for use within your organization only. Please read the license agreement and legal notice displayed by the mkinstpkg script.

To create a deployment package:

1. On the UNIX server where you installed Sophos Anti-Virus, change to the directory

/opt/sophos-av/update/ .

2. To create a deployment package in tar format, called savinstpkg.tar

, type:

./mkinstpkg

3. When prompted, choose to have the computers managed by Enterprise Console.

4. When prompted for the location, enter the bootstrap location (as seen from the UNIX computers).

Now you are ready to install Sophos Anti-Virus using this deployment package.

4.3 Installing Sophos Anti-Virus using the deployment package

You use the package to install Sophos Anti-Virus in one of two ways:

■ Manually on each computer.

■ Automatically across the network.

4.3.1 Install Sophos Anti-Virus manually

1. Use your own tools to copy the deployment package to the computers where you want to install Sophos Anti-Virus.

2. Go to each computer and log in as root.

3. Place the deployment package in a temporary directory and change to that directory.

4. To install from the tar package, type: tar -xvf savinstpkg.tar

./sophos-av/install.sh

The necessary files are copied from the server and Sophos Anti-Virus is installed. From now on,

Sophos Anti-Virus will be updated automatically whenever the bootstrap location is updated.

Sophos Anti-Virus also sends product and platform information to Sophos to help us with product development. See Sophos Knowledgebase Article 121214 .

9

Sophos Enterprise Console

4.3.2 Install Sophos Anti-Virus automatically

■ To install Sophos Anti-Virus automatically from the deployment package, use one of the operating system administration tools that support remote deployment.

For more information, see the documentation for that tool.

Once Sophos Anti-Virus is installed, it will be started and will be updated automatically whenever the bootstrap location is updated.

Sophos Anti-Virus also sends product and platform information to Sophos to help us with product development. See Sophos Knowledgebase Article 121214 .

10

startup guide for Linux and UNIX

5 Check the health of your network

To check the health of your network from Enterprise Console:

■ View the Dashboard.

If it is not already displayed, on the View menu, click Dashboard.

The Dashboard shows you how many computers:

■

Have detected threats.

■

Are out of date.

■

Do not comply with policies.

11

Sophos Enterprise Console

6 Appendix: Command-line options for mkinstpkg

The mkinstpkg tool creates a deployment package that end users can use to install Sophos

Anti-Virus.

Here is a full list of the command-line options you can use with mkinstpkg. "=" at the end of the option means it takes an argument.

Option

-d,--debug

-h,--help

-o=,--output=

-r,--rpm

-D,--deb

--tar

--update-proxy-address=

--update-proxy-username=

--update-proxy-password=

--extra-options=

-v,--verbose

--rpm-version=

--rpm-release=

--sophos

Description

Use the --debug option when the Sophos Anti-Virus installer is run.

Output help text

Destination for the package

Build an RPM package

Build a DEB package

Build a tar file (default)

Proxy address to use when installing Sophos Anti-Virus over HTTP

Proxy username to use when installing Sophos Anti-Virus over

HTTP

Proxy password to use when installing Sophos Anti-Virus over

HTTP

Extra installer options to use when installing Sophos Anti-Virus, for example: --extra-options="--preferFanotify"

Use the --verbose option when the Sophos Anti-Virus installer is run.

RPM version if building an RPM package

RPM release version if building an RPM package

Update from Sophos rather than your own server

12

Option

--update-type=

--sec-group= startup guide for Linux and UNIX

Description

Specify where Sophos Anti-Virus will update from. Use "s" for updates from Sophos, or anything other than "s" for updates from your own server.

The Enterprise Console group that computers will be added to when Sophos Anti-Virus is installed

13

Sophos Enterprise Console

7 Technical support

You can find technical support for Sophos products in any of these ways:

■ Visit the Sophos 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

.

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

.

14

startup guide for Linux and UNIX

8 Legal notices

Copyright © 2015–2016 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 and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sophos Group.

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,

UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages.

15

Sophos Enterprise Console

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

Apache

The Sophos software that is described in this document may include some software programs that are licensed (or sublicensed) to the user under the Apache License. A copy of the license agreement for any such included software can be found at http://www.apache.org/licenses/LICENSE-2.0

Boost C++ Libraries

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the “Software”) to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

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, TITLE AND NON-INFRINGEMENT. IN NO EVENT

SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE

FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR

OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

16

startup guide for Linux and UNIX

Common Public License

The Sophos software that is referenced in this document includes or may include some software programs that are licensed (or sublicensed) to the user under the Common Public License (CPL), which, among other rights, permits the user to have access to the source code. The CPL requires for any software licensed under the terms of the CPL, which is distributed in object code form, that the source code for such software also be made available to the users of the object code form. For any such software covered under the CPL, the source code is available via mail order by submitting a request to Sophos; via email to [email protected]

or via the web at https://www.sophos.com/en-us/support/contact-support.aspx

. A copy of the license agreement for any such included software can be found at http://opensource.org/licenses/cpl1.0.php

ConvertUTF

Copyright 2001–2004 Unicode, Inc.

This source code is provided as is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. If this file has been purchased on magnetic or optical media from Unicode, Inc., the sole remedy for any claim will be exchange of defective media within 90 days of receipt.

Unicode, Inc. hereby grants the right to freely use the information supplied in this file in the creation of products supporting the Unicode Standard, and to make copies of this file in any form for internal or external distribution as long as this notice remains attached.

Loki

The MIT License (MIT)

Copyright © 2001 by Andrei Alexandrescu

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.

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

17

Sophos Enterprise Console 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

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

18

startup guide for Linux and UNIX 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.

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

WilsonORMapper

Copyright © 2007, Paul Wilson

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.

19

Sophos Enterprise Console

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

zlib data compression library

Copyright © 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]

20