Installing HOBLink Secure Client/Server

Notes

The application for Client and Server is the same. The part that establishes a connection is called the "Server."

• HOBLink SSL Client / Server is available as an MS Windows application, as a Java application, or as a Java applet.

• HOBLink Secure is based on a standard that enables interaction with other software products using the SSL or TSL protocol.

Requirements

The following is required to establish a connection:

1. SSL implementation on both Server and Client

2. Both parts share a combination of encryption algorithms

3. According to the "Certificate Policy" both sides provide verified / valid certificates for authentication with matching keys

Configuration file, certificate database file(s) and password are stored in a HOBLink Secure specific format. Certificates and certificate requests generated by HOBLink Secure, however, can be imported and exported to standardized formats, such as DER, PEM, BASE 64.

If HOBLink Secure is intended to collaborate with applications, that do not support SSL encryption, the HOBLink Secure Proxy must be used  HOBLink Secure Proxy uses SSL encryption at one end and converts to unencrypted format at the other end. The HOBLink Secure Proxy may be used both on server side and on client side.

The HOBLink Secure Proxy is practical to attach a remote branch office or a mobile PC to an internal, confidential net by means of severs via the "insecure" Internet. Data that are not leaving the net can be exchanged without SSL encryption while communication to the outside of the net is subject to SSL encryption.

The HOBLink Secure Proxy is currently available for MS Windows only, written in C. A Java based version is in the planning. A Unix version written in C is currently also scheduled.

SSL Client / Server, HOBLink Secure Proxy and HOBLink Security Manager are bundled with SDK. Starting the installation you can decide which parts of the bundle are required to meet your specific demands (SSL Client / Server, HOBLink Security Manager, HOBLink SSL Redirector, Tools, source code and SDK description).

After the installation the user can download the SSL Client (and related files) from a server (as a Java applet)  without requiring a local installation of HOBLink Secure.

Overview and description of HOBLink Secure components

• HOBLink Security Manager

  Installs HOBLink Security Manager for configuration purposes and maintenance of the certificate database. It is a Java based application that will run on any computer with a JVM version 1.1.7 (or higher).

• SSL for Windows

  Installs the client / server component of HOBLink Secure on a computer with MS Windows

• SSL for Java

Installs the client / server component of HOBLink Secure on a computer with a JVM.

• HOBLink Security SDK (Software Development Kit)

  Installs the documentation and sample files you will need if you want to add HOBLink Secure to proprietary applications, which are to provide SSL encrypted connections.

• Tools for Windows

  Installs the HOBLink SSL Proxy as a service on a server with MS Windows. It is required only for a server with applications that cannot handle connections encrypted by SSL.

  Installs also some Windows programs for testing and analyzing the performance.

• Tools for Java (available with HOBLink J-Term)

  Is the proxy on a server with a JVM. It is required only for a server with applications that cannot handle connections encrypted by SSL

Using HOBLink Secure with HOB Connectivity software products

If you use HOBLink Secure with HOB Connectivity software products ensure you install the desired components to the appropriate installation path, e.g. C:\Program Files\HOBLink\JTerm.

SSL Client / Server classes are not independent applications. They work as add-ons to an existing  TCP/IP application. That is why it is necessary to ensure these classes are inserted to the installation path of the application, which is to be enhanced by SSL encryption (e.g. "C:\Program Files\HOBLink\Jterm\www" or "C:\Program Files\HOBLink\JDRDA"). During the installation you will also be reminded to consider this aspect. After selecting the desired installation path the installation program copies all the class files to the subdirectory "lib\hob\ssl".

Using HOBLink Secure with other software products

If you use HOBLink Secure with other software products ensure you install the desired components to the appropriate installation path of the software.

Using HOBLink Secure SDK with proprietary software products

If you intend to implement HOBLink Secure in proprietary software solutions refer to the documentation provided with the HOBLink SSL Software Development Kit, which after installation is available in the program folder "HOBLink Secure/HOBLink Security SDK"

webmaster@hobsoft.com, Last Updated: 03. Jul 07