StoneGate VPN Client User's Guide 4.3

StoneGate User's Guide

IPsec VPN Client 4.3

Legal Information

End-User License AgreementThe use of the products described in these materials is subject to the then current end-user license agreement, which can be found at the Stonesoft website:www.stonesoft.com/en/support/eula.html

General Terms and Conditions of Support and Maintenance ServicesThe support and maintenance services for the products described in these materials are provided pursuant to the general terms for support and maintenance services and the related service description, which can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/terms/

Replacement ServiceThe instructions for replacement service can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/return_material_authorization/

Hardware WarrantyThe appliances described in these materials have a limited hardware warranty. The terms of the hardware warranty can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/warranty_service/

Trademarks and PatentsThe products described in these materials are protected by one or more of the following European and US patents: European Patent Nos. 1065844, 1259028, 1271283, 1289183, 1289202, 1313290, 1326393, 1379046, 1330095, 131711, 1317937 and 1443729 and US Patent Nos. 6,650,621; 6 856 621; 6,885,633; 6,912,200; 6,996,573; 7,099,284; 7,127,739; 7,130,266; 7,130,305; 7,146,421; 7,162,737, 7,234,166, 7,260,843, 7,280,540 and 7,302,480 and may be protected by other EU, US, or other patents, or pending applications. Stonesoft, the Stonesoft logo and StoneGate, are all trademarks or registered trademarks of Stonesoft Corporation. All other trademarks or registered trademarks are property of their respective owners.

DisclaimerAlthough every precaution has been taken to prepare these materials, THESE MATERIALS ARE PROVIDED "AS-IS" and Stonesoft makes no warranty to the correctness of information and assumes no responsibility for errors, omissions, or resulting damages from the use of the information contained herein. All IP addresses in these materials were chosen at random and are used for illustrative purposes only.

Copyright © 2008 Stonesoft Corporation. All rights reserved. All specifications are subject to change.

Revision: SGVPNCUG_20080627

www.stonesoft.com/en/support/eula.html

www.stonesoft.com/en/support/view_support_offering/terms/

www.stonesoft.com/en/support/view_support_offering/return_material_authorization/

www.stonesoft.com/en/support/view_support_offering/warranty_service/

Table of Contents

CHAPTER 1 Introduction 5

How to Use This Guide 6

Typographical Conventions 6

Contact Information 6

Technical Support 6Your Comments and Queries 6

CHAPTER 2 Installing the StoneGate IPsec VPN Client 7

Installing the VPN Client 8

CHAPTER 3 Using the StoneGate IPsec VPN Client 11

Overview to Using the StoneGate IPsec VPN Client 12

Connecting to Gateways for the First Time 13

Adding New Gateways Manually 13Checking the Gateway’s Certificate Fingerprint 15Creating Certificate Requests for Internal

Certificates 15Importing Internal Certificates 19Using External Certificates 22Importing a PKCS # 12 File 22Importing Separate Certificate and Private Key

Files 25Connecting to Pre-Configured New Gateways 27

Authenticating to Gateways 29

Authenticating with a User Name and Password 29Authenticating with a Certificate 30

Connecting to Gateways and End-Points 31

Connecting to a Gateway 31Selecting the End-Point 32

CHAPTER 4 Managing VPN Connections 33

Overview to Managing VPN Connections 34

Viewing VPN Status 34

Managing VPNs 35

Viewing Details of a VPN Connection 35Disconnecting a VPN 36Disabling a VPN 36

Managing Gateways 36

Selecting the Authentication Method 37Removing a Gateway 37

CHAPTER 5 Managing Certificates 39

Overview to Managing Certificates 40

Changing the Key Passphrase 40

Viewing Details of User Certificates 41

Viewing Details of Issuer Certificate 42

Changing User ID Type of a Certificate 43

CHAPTER 6 Upgrading 45

Upgrading StoneGate IPsec VPN Client 46

CHAPTER 7 Troubleshooting VPN Connections 49

Using Logs and Diagnostics 50

Coping with Connectivity Problems 50

Authentication Failure 50Network Connectivity Problems 50

3

4

CHAPTER 1 Introduction

Welcome to the StoneGate IPsec VPN client. This chapter describes how to use this Guide. It also provides directions for obtaining technical support and giving feedback about the documentation.

The following sections are included:

How to Use This Guide, on page 6 Typographical Conventions, on page 6 Contact Information, on page 6

5

How to Use This GuideThis StoneGate IPsec VPN Client User’s Guide describes step-by-step the use of the StoneGate IPsec VPN client for the end-users. If you are a StoneGate administrator, see the Online Help of the Management Client and the StoneGate IPsec VPN Client Administrator’s Guide for information on setting up access for VPN clients and configuring the VPN client.

Typographical ConventionsThe following ways to highlight special text are used throughout the guide:

Note – Notes provide important information that may help you complete a task.

Contact InformationFor street addresses, phone numbers, and general information about StoneGate and Stonesoft Corporation, visit our Web site at http://www.stonesoft.com/.

Technical SupportIf you experience technical problems with the VPN Client, contact the network administrator responsible for the StoneGate system. Stonesoft technical support is available for the StoneGate administrators based on a valid support contract.

Your Comments and QueriesWe want to make our products suit your needs as best as possible. We are always pleased to receive any suggestions you may have for improvements.• To comment on software and hardware products, e-mail [email protected].• To comment on the documentation, e-mail [email protected].• For queries and comments regarding other matters, e-mail [email protected].

TABLE 1.1 Typographical Conventions

Formatting Informative Uses

VPN client text Interface elements (e.g., menu options) and any other interaction with the user interface are in bold-face.

References, terms Cross-references and first use of acronyms and terms are in italics.

Command line File names, directories, and text displayed on the screen are monospaced.

User input Text you need to type is monospaced bold-face.

6 Chapter 1: Introduction

mailto:[email protected]



http://www.stonesoft.com

CHAPTER 2 Installing the StoneGate IPsec VPN Client

This section explains how to install the StoneGate IPsec VPN client.


Installing the VPN Client, on page 8

7

Instal l ing the VPN ClientThe VPN client is available for computers running a modern version of the Windows operating system. If you are running some other operating system, ask your StoneGate administrator to recommend you a different VPN client.

Note – If you already have a Stonegate VPN client installed on your machine and the VPN client version is earlier than 4.2, uninstall the VPN client before installing StoneGate IPsec VPN 4.3.

To install the VPN client1. Double-click the executable file your network administrator has supplied. The Welcome page of the Installation Wizard opens.

Illustration 2.1 Welcome Page

You can click Back at any time to go back in the wizard.

You can click Cancel at any time to stop the installation.

2. Click Next to continue.

8 Chapter 2: Installing the StoneGate IPsec VPN Client

Illustration 2.2 License Agreement

Illustration 2.3 Installation Options

Note – You must allow the installation of all the drivers included in the installation package. You must also allow the installation of the Virtual Adapter if a message asking for permission to install it is displayed.

3. You must accept the License Agreement to continue. 4. Click Next.

6. Click Install.

5. (In Windows XP) Leave this option selected, if you do not want to manually confirm the installation of drivers that have not been signed by Microsoft.

Installing the VPN Client 9

Illustration 2.4 Installation Complete

Proceed to Using the StoneGate IPsec VPN Client, on page 11.

7. Click Finish to close the wizard.

10 Chapter 2: Installing the StoneGate IPsec VPN Client

CHAPTER 3 Using the StoneGate IPsec VPN Client

This chapter explains the basic use of the StoneGate IPsec VPN client.


Overview to Using the StoneGate IPsec VPN Client, on page 12 Connecting to Gateways for the First Time, on page 13 Authenticating to Gateways, on page 29 Connecting to Gateways and End-Points, on page 31

11

Overview to Using the StoneGate IPsec VPN Client

StoneGate IPsec VPN client is an application that allows you to access protected resources over a VPN. The VPN client establishes a connection between the VPN client machine and the gateway(s) that controls access to the resources. Each gateway can have one or several end-points, which are represented by IP addresses or host names. If a gateway has several end-points, you can selected which end-point you want to use.To connect to a gateway with the VPN client, you must have the following information from your network administrator:• The IP address or host name of one of the gateway’s end-points. The administrator

can also include the information for connecting to the gateway in the installation package or send you the required information in a file.

• The authentication method(s) for the gateway.• You user name and password, if they are used as the authentication method.• The certificate fingerprint of the gateway. It is used to authenticate the gateway to

which you connect. You do not need to know the certificate fingerprint if the gateway information is included in the installation package or you add the contact information for a new gateway to your VPN client from a file that the administrator provides.

You must authenticate yourself when you connect to a gateway. There are two possible authentication methods: authentication with a user name and a password or authentication with a certificate. The network administrator selects the required authentication method for each gateway. The administrator can also allow the use of both authentication methods with a gateway. In that case, you can select which authentication method you want to use with that gateway.

When you have installed the VPN client on your machine, it appears as an icon on the Windows taskbar. The most common commands for using the VPN client are available in the menu that opens when you right-click the icon. The available commands depend on the VPN status.

Illustration 3.1 IPsec VPN Client on Windows Taskbar

IPsec VPN icon

Access all the commands and actions for managing gateways and VPNs.

Select the gateway to which you want to connect.Close the current VPN

connection to a gateway. Select end-point for connecting to a gateway with several end-points.

Disable VPN connections.

Exit the VPN client.

12 Chapter 3: Using the StoneGate IPsec VPN Client

Connecting to Gateways for the First TimeAfter the installation, you cannot connect to gateways and end-points until they are on the list of available gateways and end-points in the VPN client.The administrator may inform you that the gateways and end-points are included in the installation package. In that case, the gateways and end-points are automatically available when you start using the VPN client. Alternatively, the administrator may provide you with a gateway contact information file for each gateway and instruct you how you can add the gateways and end-points by copying the file(s) to your VPN client. Once the gateways and end-points have been added to the VPN client by either method, the next step depends on the gateway’s authentication method:• If the gateway only allows authentication with a username and a password, proceed

to Connecting to Pre-Configured New Gateways, on page 27.• If the gateway requires or allows certificate authentication, you must have a signed

certificate to be able to authenticate yourself with a certificate. Proceed to Creating Certificate Requests for Internal Certificates, on page 15 if the administrator informs you that you must create a certificate request for an internal certificate. If the administrator instructs you to use an external certificate, proceed to Using External Certificates, on page 22.

If the gateways and end-points are not included in the installation package and you have not received gateway contact information files from the administrator, you must add the gateways and end-points manually. Proceed to one of the following:• If the gateway to which you want to you connect allows authentication with a user

name and password, proceed to Adding New Gateways Manually below.• If the gateway requires certificate authentication, you must have a signed certificate

for the gateway before adding the gateway. Proceed to Creating Certificate Requests for Internal Certificates, on page 15 if the administrator informs you that you must create a certificate request for an internal certificate. If the administrator instructs you to use an external certificate, proceed to Using External Certificates, on page 22.

Adding New Gateways ManuallyWhen you first start using the VPN client, you may have to add the gateways where you want to connect. You must add the gateways unless the administrator informs you that the gateway contact information was included in the installation or you copied the information from a file sent by the administrator.You can add the first gateway directly on the Status tab and the rest of the gateways on the Gateways tab in the StoneGate IPsec VPN Properties (see Illustration 3.2). Alternatively, you can add all the gateways on the Gateways tab. The process of adding a new gateway is the same on both tabs.


Note – If the gateway requires certificate authentication, you must get a certificate for the gateway before adding the gateway. See Creating Certificate Requests for Internal Certificates, on page 15, if the administrator has instructed you to create a request for an internal certificate.

To add a gateway manually1. Double-click the IPsec VPN icon in the Windows taskbar. The StoneGate IPsec VPN Properties dialog opens.

Illustration 3.2 StoneGate IPsec VPN Properties - Status Tab

Illustration 3.3 New Gateway Properties Dialog

If the authentication method is User Name, the New Gateway dialog opens. Proceed to Checking the Gateway’s Certificate Fingerprint, on page 15.

2. Select Add New Gateway.

3. Enter the IP address or the host name of one of the gateway’s end-points.

4. Select the authentication method.5. Click OK.


If the authentication method is Certificate, the User Authentication dialog opens. Proceed to Authenticating with a Certificate, on page 30.

Checking the Gateway’s Certificate Fingerprint

To check the Gateways Certificate Fingerprint

Caution – The Certificate Fingerprint identifies the gateway to which you connect. It is important to check that the fingerprint is correct.

Illustration 3.4 New Gateway Dialog

If the selected authentication method for the gateway is password authentication, you must next authenticate yourself. Proceed to Authenticating to Gateways, on page 29.If certificate authentication is used, the VPN client next opens a VPN connection to the gateway. See Managing VPN Connections, on page 33 for more information on managing the opened VPN connection.

Creating Certificate Requests for Internal CertificatesThe administrator may have defined that your VPN connections require a client certificate on your machine. If your VPN client does not have a certificate that can be used by the gateway you are contacting, you must obtain a certificate. If the administrator informs you that you must use an internal certificate, you must first generate a certificate request in the VPN client and send it for signing to your network administrator. Second, you must import the received certificate in the VPN client. If the client certificate on your machine has expired, repeat the same process.The following instructions describe how you can create a basic certificate request for an internal certificate in the VPN client. If the administrator informs you that you must create an advanced certificate request for an internal certificate, see the IPsec VPN Client Administrator’s Guide for instructions.

To create a basic certificate request for an internal certificate1. Double-click the IPsec VPN icon in the Windows taskbar to open the StoneGate IPsec VPN Properties.

1. Check the Subject Name and the Certificate Fingerprint.

2. Click OK.


Illustration 3.5 StoneGate IPsec VPN Properties - Certificates Tab

Illustration 3.6 Certificate Request Wizard

2. Switch to the Certificates tab.

3. Click Create Certificate Request.

4. Select Basic Mode.

5. Click Next.


Illustration 3.7 Create Certificate Request - Basic Mode

You must enter this passphrase whenever the VPN client requires you to authenticate yourself using this certificate.

Caution – Passphrases should be at least eight characters long and contain a combination of numbers, letters, and special characters. Secure passphrases are never based on personal information such as names, birthdays, ID numbers, phone numbers, street names, registration plate numbers, or any of the above written backwards.

Illustration 3.8 Save the Certificate Request

6. Enter the User Name.

7. Enter the Passphrase.

8. Click Create.

9. Click Save.


Illustration 3.9 Saving the Certificate Request

Make sure that Certificate Requests (*.csr) is selected as the file type in the Save as type field.

Illustration 3.10 Certificate Request Wizard Completed

10. Browse to the correct folder.

11. Enter a file name and click Save.

12. (Optional) Click Launch Default Windows E-Mail Application to open your default e-mail application.

13. Click Finish.


You must send the certificate request (the .csr file that you just saved) to your network administrator for signing. When you get the signed internal certificate back, you must import it as described in Importing Internal Certificates below.

Related Tasks

Managing Certificates, on page 39

Importing Internal CertificatesOnce the administrator has signed your certificate request for an internal certificate and sent it back to you, you must import the signed certificate in your VPN client.

To import an internal certificate1. Double-click the IPsec VPN icon in the Windows taskbar to open the StoneGate IPsec VPN Properties.

Illustration 3.11 IPsec VPN Properties - Certificates Tab


3. Click Import Certificate.


Illustration 3.12 Import Certificate Wizard - Importing an Internal Certificate

Illustration 3.13 Import Certificate Wizard - Continuing with the Import

4.Select Internal Certificate.

5. Click Next.

6.Click Select.


Illustration 3.14 Import Internal Certificate File Dialog

Illustration 3.15 Finishing Certificate Import

The signed internal certificate is now listed on the Certificates tab, which displays, among other information, the expiration date of the certificate. For more information on certificates, see Managing Certificates, on page 39.Proceed to one of the following:• If the gateway with which you will use the certificate has not yet been added to the

list of available gateways, proceed to Adding New Gateways Manually, on page 13.

7. Browse to the correct folder and select the signed certificate.

8. Click Open.

9. Click Finish.


• If the certificate has been created for a gateway that is already listed on the Gateways tab, you can now use the certificate to authenticate to the gateway. See Authenticating with a Certificate, on page 30.

Related Tasks


Using External CertificatesIf the administrator allows the use of external certificates as the authentication method, and you already have a suitable signed certificate and its private key, you can use the external certificate to authenticate yourself to a gateway. You must import the signed external certificate in the VPN client.There are two types of external certificates that you can import: you can either import the certificate and its private key as a single PKCS # 12 file or as two separate files. Proceed to Importing a PKCS # 12 File below or to Importing Separate Certificate and Private Key Files, on page 25 depending on which type of external certificate you have.

Importing a PKCS # 12 File

To import a PKCS # 12 file1. Double-click the IPsec VPN icon in the Windows taskbar to open the StoneGate IPsec VPN Properties.

Illustration 3.16 IPsec VPN Properties - Certificates tab




Illustration 3.17 Importing an External Certificate - a PKCS # 12 File

Illustration 3.18 Importing a PKCS # 12 File

You must enter this new passphrase whenever the VPN client requires you to authenticate yourself using this certificate.

4. Select External Certificate.

5. Select PKCS # 12 File.

6. Click Next.

7. Select the PKCS # File.

8. Enter the file’s password.

9. Enter the new passphrase for authenticating to the VPN client.

10. Click Next.


Caution – Passphrases should be at least eight characters long and contain a combination of numbers, letters, and special characters. Secure passphrases are never based on personal information such as names, birthdays, ID numbers, phone numbers, street names, registration plate numbers, or any of the above written backwards.

Illustration 3.19 Finishing PKCS # 12 File Import

The signed certificate is now listed on the Certificates tab, which displays, among other information, the expiration date of the certificate. For more information on certificates, see Managing Certificates, on page 39.Proceed to one of the following:• If the gateway with which you will use the external certificate has not yet been

added to the list of available gateways, proceed to Adding New Gateways Manually, on page 13.

• If the external certificate has been created for a gateway that is already listed on the Gateways tab, you can now use the external certificate to authenticate to the gateway. See Authenticating with a Certificate, on page 30.

Related Tasks


11. Click Finish.


Importing Separate Certificate and Private Key Files

To import separate certificate and private key files1. Double-click the IPsec VPN icon in the Windows taskbar to open the StoneGate IPsec VPN Properties.

Illustration 3.20 IPsec VPN Properties - Certificates Tab

Illustration 3.21 Importing an External Certificate - Separate Certificate and Private Key Files



4. Select External Certificate.

5. Select Separate Certificate and Private Key Files.

6. Click Next.


Illustration 3.22 Importing an External Certificate - Select Files

Illustration 3.23 Importing Separate Certificate and Private Key Files - Finish

The signed external certificate is now listed on the Certificates tab, which displays, among others, the expiration date of the certificate. For more information on certificates, see Managing Certificates, on page 39.

9. Click Next.

7. Select the Certificate File.

8. Select the Private Key File.

10. Click Finish.


Proceed to one of the following:• If the gateway with which you will use the external certificate has not yet been

added to the list of available gateways, proceed to Adding New Gateways Manually, on page 13.

• If the external certificate has been created for a gateway that is already listed on the Gateways tab, you can now use the certificate to authenticate to the gateway. See Authenticating with a Certificate, on page 30.

Related Tasks


Connecting to Pre-Configured New GatewaysIf the gateway to which you want to connect was included in the installation package or you copied the contact information for the gateway from a file provided by the administrator, the gateway is already available on the Gateways tab when you start the IPsec VPN client.If the administrator informs you that the gateway requires certificate authentication, you cannot connect to the gateway until you have a signed certificate with which you can authenticate yourself. Proceed to Creating Certificate Requests for Internal Certificates, on page 15 if the administrator instructs you to create a certificate request for an internal certificate. If the administrator instructs you to use an external certificate, proceed to Using External Certificates, on page 22.

To connect to a pre-configured new Gateway1. Double-click the IPsec VPN icon in the Windows taskbar. The StoneGate IPsec VPN Properties dialog opens.


Illustration 3.24 StoneGate IPsec VPN Properties - Status Tab with Active Gateway

Illustration 3.25 Connecting to a Pre-Configured Gateway on the Gateways Tab

2. Click Connect to to connect to the first gateway on the list of available gateways.

Switch to the Gateways tab to see the list of all gateways (see Illustration 3.25 below).

Right-click a gateway and select Connect to.


Illustration 3.26 New Gateway Properties Dialog

The User Authentication dialog opens. Proceed to Authenticating with a User Name and Password, on page 29 or Authenticating with a Certificate, on page 30 depending on the selected authentication method.

Authenticating to GatewaysYou must authenticate yourself whenever you connect to a gateway with the VPN client. The authentication method depends on how the administrator has configured the gateway to which you connect.If you authenticate yourself to a gateway with a user name and a password, the VPN client asks you to re-authenticate yourself periodically. If a certificate is used, re-authentication is performed automatically.Proceed to one of the following:• Authenticating with a User Name and Password, on page 29• Authenticating with a Certificate, on page 30

Authenticating with a User Name and Password

To authenticate with a user name and password

Illustration 3.27 Authentication with a User Name and Password

3. Select the IP address or the host name of one of the gateway’s end-points.

4. Select the authentication method.

5. Click OK.

1. Enter your User Name and Password.

2. Click OK.

Authenticating to Gateways 29

The network administrator provides your User Name and Password. If you are using a one-time password (for example, a password generated with a SecurID card), enter it in the Password field.The User Authentication dialog opens whenever you start a VPN. It also opens if the VPN client requires you to re-authenticate yourself while you are working over a VPN.

Note – You cannot change your password in the VPN client. If you want to change the password, you must ask your network administrator for a new password.

If the authentication is successful, you can now connect to resources through the gateway. See Managing VPN Connections, on page 33 for more information on managing the opened VPN connection.

Related Tasks

Selecting the Authentication Method, on page 37

Authenticating with a Certificate

To authenticate with a certificate

Illustration 3.28 Authentication with a Certificate

Note – The passphrase is the one that you entered as the passphrase in the Certificate Request Wizard.

If you are connecting to a new gateway that you are adding manually, the New Gateway dialog opens. Proceed to Checking the Gateway’s Certificate Fingerprint, on page 15.

1. Enter the Passphrase.2. Click OK.


Otherwise, if the authentication is successful, you can now connect to resources through the gateway. See Managing VPN Connections, on page 33 for more information on managing the opened VPN connection.

Related Tasks

Selecting the Authentication Method, on page 37

Connecting to Gateways and End-PointsThe gateways that have been added in the VPN client are listed on the Gateways tab. By default, the VPN connections are formed to the gateway that is shown as the Active Gateway on the Status tab. If you want to connect to another gateway, you can select it and open the VPN connection on the Gateways tab. If a gateway has several end-points, you can also select the end-point for connecting to the gateway on the Gateways tab.If you want to connect to a gateway that has not yet been added in the VPN client (the gateway is not listed on the Gateways tab), you must add the gateway as described in Adding New Gateways Manually, on page 13.

Connecting to a Gateway

To connect to a Gateway1. Double-click the IPsec VPN icon to open the StoneGate IPsec VPN properties.2. The Status tab shows the gateway to which you last connected as the Active

Gateway. Click Connect to to connect to this gateway.• If you want to connect to another gateway, switch to the Gateways tab, right-

click the gateway, and select Connect. The selected gateway becomes the Active Gateway.

3. Authenticate yourself according to the gateway’s authentication method. See Authenticating with a User Name and Password, on page 29 and Authenticating with a Certificate, on page 30 for more details.

4. The VPN client connects to the gateway. The Connection Steps show the progress of establishing the VPN.

When the VPN connection has been established, the Connection Status changes to VPN Connection Established. If you want to view more detailed information on the VPN connection, see Viewing Details of a VPN Connection, on page 35.If you want to select the end-point for connecting to the gateway, see Selecting the End-Point.

Connecting to Gateways and End-Points 31

Selecting the End-PointSome gateways may be reached through several end-points. In that case, you can select which end-point is used to connect to the gateway. Selecting the end-point may be useful, for example, when one of the end-points is temporarily unavailable.

To select an end-point1. Switch to the Gateways tab in the StoneGate IPsec VPN properties.2. Right-click the gateway for which several end-points are available and select

Connect to End-Point and the name of the end-point from the menu that opens.3. The VPN client starts connecting to the end-point. The Connection Steps show

the progress of establishing the VPN.When the VPN connection has been established, the Connection Status changes to VPN Connection Established. If you want to view more detailed information on the VPN connection, see Viewing Details of a VPN Connection, on page 35.


CHAPTER 4 Managing VPN Connections

This chapter explains how you can manage VPN connections to gateways.


Overview to Managing VPN Connections, on page 34 Viewing VPN Status, on page 34 Managing VPNs, on page 35 Managing Gateways, on page 36

33

Overview to Managing VPN ConnectionsYou can manage and monitor VPN connections through the Status tab and the Gateways tab in the StoneGate IPsec VPN Properties. The Status tab shows the current VPN status. The Gateways tab shows the list of the gateways to which you can connect.

Viewing VPN StatusThe Status tab of the VPN client shows the status of VPN connections. The color of the IPsec VPN icon on the Windows taskbar also reflects the VPN status.• Gray: VPN is disabled.• Blue: No VPN connection.• Green: VPN established.• Red and green: Connectivity problems.• Red: Error situation.You can manage the VPN connections directly on the Status tab. You can enable and disable VPN connections, and connect to the Active Gateway and disconnect the VPN. You can also view details of the established VPN connection.

Illustration 4.1 Status Tab - Viewing Status Information

Proceed to one of the following:• If you want to connect to a gateway, proceed to Connecting to Gateways and End-

Points, on page 31.• If you want to view detailed information on the current VPN connection, see Viewing

Details of a VPN Connection, on page 35.

Name of the active gateway

Available actions

Details of established VPN

Progress of establishing a VPN

Status information

34 Chapter 4: Managing VPN Connections

• If you want to disconnect the current VPN, proceed to Disconnecting a VPN, on page 36.

• If you want to disable VPN connections, proceed to Disabling a VPN, on page 36.

Managing VPNsYou can manage the current VPN connection on the Status tab. You can view detailed information on the current VPN, disconnect the VPN, or disable VPN connections.

Viewing Details of a VPN Connection

To view details of a VPN connectionClick Details on the Status tab. The VPN Details dialog opens.

Illustration 4.2 VPN Details Dialog

The VPN dialog shows detailed information on how the VPN connection has been established. It shows, for example, the used authentication method and encryption algorithm, and how long the current authentication is valid. If the administrator has enabled virtual IP addressing for the VPN client, the dialog also shows the VPN client’s virtual IP address.

Expand or collapse all the VPN details

Click the plus or minus sign to expand or collapse details

Managing VPNs 35

Disconnecting a VPNThere is usually no need to disconnect a VPN when you stop using it. However, you can disconnect the VPN manually at any time.

To disconnect a VPNClick Disconnect on the Status tab or right-click the active gateway on the Gateways tab and select Disconnect from the menu that opens.

The status of the VPN changes to No VPN connection on the Status tab.

Disabling a VPNIf necessary, you can manually disable a VPN.

To disable a VPNClick Disable VPN on the Status tab.

The status of the VPN changes to No VPN connection (VPN Disabled).

Managing GatewaysYou can manage gateways on the Gateways tab. You can, for example, add and remove gateways. You can also disconnect the active VPN connection to a gateway. If several end-points are available for connecting to a gateway, you can also select which end-point you want to use. This may be useful, for example, when one of the end-points is temporarily unavailable. You can also select which authentication method is used for a gateway which allows the use of both certificates as well as user names and passwords.

Illustration 4.3 Gateways Tab Showing Gateway Status

A gateway to which the user has connected.

A new gateway to which the user has not yet connected.


Proceed to one of the following:• To add a gateway, see Adding New Gateways Manually, on page 13.• To connect to a gateway, see Connecting to a Gateway, on page 31.• To disconnect a VPN to the active gateway, see Disconnecting a VPN, on page 36.• To select which end-point is used to connect to a gateway, see Selecting the End-

Point, on page 32.• To select the authentication method for the gateway, see Selecting the

Authentication Method, on page 37.• To remove a gateway, see Removing a Gateway, on page 37.

Selecting the Authentication MethodThe network administrator can define that a gateway allows the users to authenticate themselves either by using a certificate or with a user name and password. In that case, you can select which authentication method is used to connect to the gateway.

To select the authentication methodOn the Gateways tab, right-click the gateway for which you want to select the authentication method and select Authentication→Username or Authentication→Certificate and the user name or subject name used in your certificate.

The selected authentication method is used the next time you must authenticate yourself.

Removing a Gateway

To remove a gateway1. Right-click the Gateway on the Gateways tab and select Remove Gateway from

the menu that opens.2. Click Yes in the confirmation dialog.The gateway is deleted from the list of gateways on the Gateways tab.

Managing Gateways 37


CHAPTER 5 Managing Certificates

This chapter explains how you can manage VPN client certificates.


Overview to Managing Certificates, on page 40 Changing the Key Passphrase, on page 40 Viewing Details of Issuer Certificate, on page 42 Changing User ID Type of a Certificate, on page 43

39

Overview to Managing CertificatesThe signed certificates that you have imported are listed on the Certificates tab. You can manage your certificate(s), for example, by changing their key passphrase. You can also view general information on the certificate(s) you use and on the Certificate Authority who signed the certificate(s). If you must create a new internal certificate request or import an internal certificate that an administrator has signed, see Creating Certificate Requests for Internal Certificates, on page 15, or Importing Internal Certificates, on page 19. If you want to import a certificate created and signed outside StoneGate, see Using External Certificates, on page 22.

Changing the Key PassphraseYou can change the passphrase that protects the private key of your certificate.

To change the key passphrase1. Double-click the IPsec VPN icon in the Windows taskbar. The StoneGate IPsec VPN Properties dialog opens.

Illustration 5.1 Certificates Tab

3. Right-click the certificate whose passphrase you want to change and select Change Key Passphrase from the menu. The Change Key Passphrase dialog opens.


40 Chapter 5: Managing Certificates

Illustration 5.2 Change Key Passphrase

Caution – If you leave the New Passphrase field empty, the private key of the certificate will not be encrypted. For security reasons, it is highly recommended that you enter a passphrase.

You must enter the new passphrase the next time the VPN client asks you to authenticate yourself using this certificate.

Viewing Details of User Certificates

To view details of a user certificate1. Right-click a certificate on the Certificates tab and select Details of User Certificate from the menu. The Certificate dialog opens.

Illustration 5.3 User Certificate Details

4. Enter the old passphrase.

5. Enter the new passphrase.

6. Click OK.

2. Switch between the General, Details, and Certification Path tabs to view detailed information on the user certificate.

Changing the Key Passphrase 41

You can optionally install the user certificate in the Microsoft Certificates Store on your computer. However, installing the user certificates is not necessary for the operation of the VPN client. The VPN client certificates are only used in user authentication between the VPN client and the gateways for which they have been signed. If you want to install the certificate in the Microsoft Certificates Store, click Install Certificate in the Certificate dialog and proceed as instructed in the dialogs that follow.

Viewing Detai ls of Issuer CertificateTo view details of issuer certificate

1. Right-click a certificate on the Certificates tab and select Details of Issuer Certificate from the menu that opens. The Certificate dialog opens.

Illustration 5.4 Issuer Certificate Details

You can optionally install the issuer certificate in the Trusted Root Certification Store. This is not necessary for the operation of the VPN client. The VPN client certificates are only used in user authentication between the VPN client and the gateways for which they have been signed. If you want to install the issuer certificate in the Trusted Root Certification Store, click Install Certificate in the Certificate dialog and proceed as instructed in the dialogs that follow.

2. Switch between the General, Details and Certification Path tabs to view detailed information on the issuer of the certificate.


Changing User ID Type of a CertificateSeveral user IDs may be available for a certificate that you use for authenticating yourself to a gateway. The administrator may ask you to change the user ID type for the certificate.

Caution – The network administrator has defined your user ID and its type. Do not change the user ID type unless the network administrator specifically instructs you to do so.

To change a certificate’s user ID typeRight-click the certificate for which you want to change the user ID type and select Certificate ID to Use→E-mail, Certificate ID to Use→Subject Name, or Certificate ID to Use→IP Address from the menu.

Changing User ID Type of a Certificate 43


CHAPTER 6 Upgrading

This section explains how you can upgrade your VPN client.


Upgrading StoneGate IPsec VPN Client, on page 46

45

Upgrading StoneGate IPsec VPN ClientUpgrade your VPN client as soon as possible when the administrator informs you that a new version is available.

To upgrade StoneGate IPsec VPN client1. Double-click the executable file your network administrator has supplied. A dialog opens.

Illustration 6.1 StoneGate IPsec VPN 4.3.0 Dialog

Illustration 6.2 InstallShield Wizard - Welcome

2. Click Yes to start the Upgrade Wizard.

3. Click Next to continue.

46 Chapter 6: Upgrading

Illustration 6.3 InstallShield Wizard - Upgrade Completed

4. Click Finish when the upgrade is ready.

Upgrading StoneGate IPsec VPN Client 47

48 Chapter 6: Upgrading

CHAPTER 7 Troubleshooting VPN Connections

This chapter explains what you can do if you have problems with your VPN connections.


Using Logs and Diagnostics, on page 50 Coping with Connectivity Problems, on page 50

49

Using Logs and DiagnosticsYou can view information on how the VPN client functions on the Diagnostics tab in the IPsec VPN client properties. Logs and diagnostics are seldom needed in everyday use of the VPN client. They can, however, provide important information, for example, for administrators. For more information on logs and diagnostics, see the StoneGate IPsec VPN Client Administrator’s Guide.

Coping with Connectivity ProblemsThere may sometimes be problems with connecting to a gateway. Network connectivity problems may also occasionally occur when you are using a VPN.

Authentication FailureContact the administrator if you cannot authenticate to a gateway and you see the following message: “Failed to authenticate the gateway. The identity of the gateway has changed.”This message usually means that the administrator has changed the VPN configuration in such a way that the VPN client can no longer connect to the gateway. Ask the administrator for more information and instructions.

Network Connectivity ProblemsIf network connectivity problems occur when the VPN client has already established a VPN to a gateway, the Connectivity Problems dialog may be displayed.

Illustration 7.1 Connectivity Problems Dialog

To troubleshoot network connectivity problems1. Select one of the available options:

• Switch to the next end-point of the gateway: If the gateway has several end-points, the VPN client tries to establish a VPN by switching to the next end-point.

• Reconnect to the end-point: The VPN client tries to establish a new connection to the currently selected end-point.

50 Chapter 7: Troubleshooting VPN Connections

• Continue with the current end-point as usual: The VPN client waits for the already established connection to the current end-point to become available.

2. Click OK.If the VPN client fails to establish a connection according to the selected option, wait until network connections become available again and then try to connect to the gateway manually as described in Connecting to Gateways and End-Points, on page 31.

Coping with Connectivity Problems 51

52 Chapter 7: Troubleshooting VPN Connections

Legal Information

LicensesStonesoft products are sold pursuant to their relevant End-User License Agreements. By installing or otherwise using Stonesoft products in any way, end-users agree to be bound by such agreement(s). See Stonesoft's website, www.stonesoft.com for further details.If Licensee is acquiring the Software, including accompanying documentation on behalf of the U.S. Government, the following provisions apply. If the Software is supplied to the Department of Defense (“DoD”), the Software is subject to “Restricted Rights”, as that term is defined in the DOD Supplement to the Federal Acquisition Regulations (“DFAR”) in paragraph 252.227-7013(c) (1). If the Software is supplied to any unit or agency of the United States Government other than DOD, the Government’s rights in the Software will be as defined in paragraph 52.227-19(c) (2) of the Federal Acquisition Regulations (“FAR”). Use, duplication, reproduction or disclosure by the Government is subject to such restrictions or successor provisions.

Product Export RestrictionsThe products described in this document are subject to export control under the laws of Finland and the European Council Regulation (EC) N:o 1334/2000 of 22 June 2000 setting up a Community regime for the control of exports of dual-use items and technology (as amended). Thus, the export of this Stonesoft software in any manner is restricted and requires a license by the relevant authorities.

Licenses 53

http://www.stonesoft.com/

Patent NoticeMulti-Link, Multi-Link VPN, and the StoneGate clustering technology—as well as other technologies included in StoneGate—are protected by pending patent applications in the U.S. and other countries.

End-User Licence AgreementThe use of the Stonegate products is subject to the then current end-user license agreement, which can be found at the Stonesoft website: www.stonesoft.com/en/support/eula.html.

Software Licensing InformationThe StoneGate software includes several open source or third-party software packages to support certain features. This section provides the appropriate software licensing information for those products.

GNU General Public LicenseVersion 2, June 1991Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USAEveryone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.PreambleThe licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.The precise terms and conditions for copying, distribution and modification follow.

54 Legal Information



GNU GENERAL PUBLIC LICENSETERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION1. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may

be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided

that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your

Software Licensing Information 55

rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY11. 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.

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

END OF TERMS AND CONDITIONSHow to Apply These Terms to Your New ProgramsIf you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.


To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.>Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USAAlso add information on how to contact you by electronic and paper mail.If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of authorGnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program‘Gnomovision’ (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of ViceThis General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

GNU LESSER GENERAL PUBLIC LICENSEVersion 2.1, February 1999Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USAEveryone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]PreambleThe licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.


To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.GNU LESSER GENERAL PUBLIC LICENSETERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you".A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:a) The modified work must itself be a software library.b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.


c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.This option is useful when you wish to copy part of the code of the Library into a program that is not a library.4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that workunder terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified


Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy.For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version


or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OROTHER PARTIES PROVIDE THE LIBRARY "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 LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFYAND/OR REDISTRIBUTE THE LIBRARY 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 LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONSHow to Apply These Terms to Your New LibrariesIf you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.<one line to give the library's name and a brief idea of what it does.>Copyright (C) <year> <name of author>This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USAAlso add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker.<signature of Ty Coon>, 1 April 1990Ty Coon, President of ViceThat's all there is to it!

OpenSSL ToolkitThis software includes the OpenSSL toolkit.LICENSE ISSUES==============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] License---------------Copyright (c) 1998-2000 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: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.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/)”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] derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.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 (C) 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 aheared 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:Redistributions of source code must retain the 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.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 rouines from the library being used are not cryptographic related:-).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 licence 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 licence [including the GNU Public Licence.]

OpenLDAPThis software includes the OpenLDAP client developed by The OpenLDAPFoundation. Original version of the OpenLDAP client can be downloaded from http://www.openldap.org This software includes the OpenLDAP server. The OpenLDAP Public License Version 2.7, 7 September 2001Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:1. Redistributions of source code must retain copyright statements and notices,


2. Redistributions in binary form must reproduce applicable copyright statements and notices, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution, and3. Redistributions must contain a verbatim copy of this document.The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished by a version number. You may use the Software under terms of this license revision or under the terms of any subsequent revision of the license.THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND CONTRIBUTORS “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 OPENLDAP 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.OpenLDAP is a trademark of the OpenLDAP Foundation.Copyright 1999-2001 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission to copy and distributed verbatim copies of this document is granted.

libradius1This software includes the libradius1 package.Copyright (C) 1995,1996,1997,1998 Lars Fenneberg <[email protected]>Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that this copy ight and permission notice appear on all copies and supporting documentation, the name of Lars Fenneberg not be used in advertising or publicity pertaining to distribution of the program without specific prior permission, and notice be given in supporting documentation that copying and distribution is by permission of Lars Fenneberg.Lars Fenneberg makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.------------------------------------------------------------------------------Copyright 1992 Livingston Enterprises, Inc.Livingston Enterprises, Inc. 6920 Koll Center Parkway Pleasanton, CA 94566Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that this copyright and permission notice appear on all copies and supporting documentation, the name of Livingston Enterprises, Inc. not be used in advertising or publicity pertaining to distribution of the program without specific prior permission, and notice be given in supporting documentation that copying and distribution is by permission of Livingston Enterprises, Inc.Livingston Enterprises, Inc. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.------------------------------------------------------------------------------[C] The Regents of the University of Michigan and Merit Network, Inc. 1992, 1993, 1994, 1995 All Rights Reserved.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 and this permission notice appear in all copies of the software and derivative works or modified versions thereof, and that both the copyright notice and this permission and disclaimer notice appear in supporting documentation.THIS SOFTWARE IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE REGENTS OF THE UNIVERSITY OF MICHIGAN AND MERIT NETWORK, INC. DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET LICENSEE'S REQUIREMENTS OR THAT OPERATION WILL BE UNINTERRUPTED OR ERROR FREE. The Regents of the University of Michigan and Merit Network, Inc. shall not be liable for any special, indirect, incidental or consequential damages with respect to any claim by Licensee or any third party arising from use of the software.------------------------------------------------------------------------------Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.License to copy and use this software is granted provided that it is identified as the “RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing this software or this function.License is also granted to make and use derivative works provided that such works are identified as “derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided “as is” without express or implied warranty of any kind.These notices must be retained in any copies of any part of this documentation and/or software.


TACACS+ ClientThis software contains TACACS+ client.Copyright (c) 1995-1998 by Cisco systems, Inc.Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that this copyright and permission notice appear on all copies of the software and supporting documentation, the name of Cisco Systems, Inc. not be used in advertising or publicity pertaining to distribution of the program without specific prior permission, and notice be given in supporting documentation that modification, copying and distribution is by permission of Cisco Systems, Inc.Cisco Systems, Inc. makes no representations about the suitability of this software for any purpose. THIS SOFTWARE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.MD5C.C - RSA Data Security, Inc., MD5 message-digest algorithmCopyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.License to copy and use this software is granted provided that it is identified as the “RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing this software or this function.License is also granted to make and use derivative works provided that such works are identified as “derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing the derived work.RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided “as is” without express or implied warranty of any kind.These notices must be retained in any copies of any part of this documentation and/or software.

libwwwThis software contains libwww software.Copyright © 1995-1998 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.This program is distributed under the W3C's Intellectual Property License. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See W3C License http://www.w3.org/Consortium/Legal/ for more details.------------------------------------------------------------------------------Copyright © 1995 CERN. "This product includes computer software created and made available by CERN. This acknowledgment shall be mentioned in full in any product which includes the CERN computer software included herein or parts thereof."

W3C® SOFTWARE NOTICE AND LICENSEhttp://www.w3.org/Consortium/Legal/2002/copyright-software-20021231This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications: 1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative work. 2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code. 3. Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.____________________________________This formulation of W3C's notice and license became active on December 31 2002. This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous


grant of "use". Otherwise, this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to [email protected] Reagle <[email protected]>Last revised by Reagle $Date: 2003/01/16 15:01:10 $Last revised by Reagle $Date: 2003/01/16 15:01:10 $

XML-RPC C Library LicenseThis software contains software covered by the XML-RPC C Library License.Copyright (C) 2001 by First Peer, Inc. All rights reserved.Copyright (C) 2001 by Eric Kidd. 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 AND CONTRIBUTORS `ÀS 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.

Expat LicenseThis software contains software covered by the Expat License.Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center LtdPermission 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.

ABYSS Web Server LicenseThis software contains software covered by the ABYSS Web Server LicenseCopyright (C) 2000 by Moez Mahfoudh <[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 AND CONTRIBUTORS `ÀS 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.

Python 1.5.2 LicenseThis software contains software covered by the Python 1.5.2 License.Copyright 1991, 1992, 1993, 1994 by Stichting Mathematisch Centrum, Amsterdam, The Netherlands.All Rights ReservedPermission 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 names of Stichting Mathematisch Centrum or CWI or Corporation for National Research Initiatives or CNRI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.While CWI is the initial source for this software, a modified version is made available by the Corporation for National Research Initiatives (CNRI) at the Internet address ftp://ftp.python.org.STICHTING MATHEMATISCH CENTRUM AND CNRI DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM OR CNRI 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.

The Apache Software License, Version 1.1This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."Copyright (C) 1999 The Apache Software Foundation. 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 end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names "log4j" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]. Products derived from this software may not be called “Apache”, nor may “Apache” appear in their name, without prior written permission of the Apache Software Foundation.THIS SOFTWARE IS PROVIDED `ÀS 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.This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.

Bouncy Castle notice and license.Copyright (c) 2000 The Legion Of The Bouncy Castle (http://www.bouncycastle.org) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Package: discover-dataDebian package author: Branden RobinsonThe contents of this package that are not in the debian/ subdirectory are simple compilations of data and are therefore not copyrightable in the United States (c.f. _Feist Publications, Inc., v. Rural Telephone Service Company, Inc., 499 U.S. 340 (1991)_)._Feist_ holds that: Article I, s 8, cl. 8, of the Constitution mandates originality as a prerequisite for copyright protection. The constitutional requirement necessitates independent creation plus a modicum of creativity. Since facts do not owe their origin to an act of authorship, they are not original and, thus, are not copyrightable. Although a compilation of facts may possess the requisite originality because the author typically chooses which facts to include, in what order to place them, and how to arrange the data so that readers may use them effectively, copyright protection extends only to those components of the work that are original to the author, not to the facts themselves. This fact/expression dichotomy severely limits the scope of protection in fact-based works. Therefore, the hardware information lists that comprise the "meat" of this package enjoy no copyright protection and are thus in the public domain. Note, however, that a number of trademarks may be referenced in the hardware lists (names of vendors and products). Their usage does not imply a challenge to any such status, and all trademarks, service marks, etc. are the property of their respective owners.The remainder of this package is copyrighted and licensed as follows: Package infrastructure: Copyright 2001,2002 Progeny Linux Systems, Inc. Copyright 2002 Hewlett-Packard Company Written by Branden Robinson for Progeny Linux Systems, Inc.lst2xml conversion script: Copyright 2002 Progeny Linux Systems, Inc. Copyright 2002 Hewlett-Packard Company Written by Eric Gillespie, John R. Daily, and Josh Bressers for Progeny Linux Systems, 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, 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 COPYRIGHT HOLDER(S) 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.Copyright (c) 1999, 2004 Tanuki SoftwarePermission is hereby granted, free of charge, to any person obtaining a copy of the Java Service Wrapper and associated documentation files (the "Software"), to deal in the Softwarewithout restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sub-license, and/or sell copies of the Software, and to permit persons towhom 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 NON-INFRINGEMENT. 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.Portions of the Software have been derived from source code developed by Silver Egg Technology under the following license:Copyright (c) 2001 Silver Egg TechnologyPermission 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, sub-license, 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.



Available StoneGate Guides:

Administrator Documentation• Administrator’s Guide• Installation Guides• Reference Guides• IPsec VPN Client Administrator’s Guide

End-User Documentation• Monitoring Client User’s Guide• IPsec VPN Client User’s Guide

For PDF versions of the guides and the StoneGate technical knowledge base, visitwww.stonesoft.com/support

Stonesoft CorporationItälahdenkatu 22 AFI-00210 HelsinkiFinlandTel. +358 9 476 711Fax +358 9 4767 1234

Stonesoft Inc.1050 Crown Pointe ParkwaySuite 900Atlanta, GA 30338USATel. +1 770 668 1125Fax +1 770 668 1131

Copyright 2008 Stonesoft Corporation. All rights reserved. All specifications are subject to change.

http://www.stonesoft.com/support/

StoneGate VPN Client User's Guide 4.3

Documents