Sybase now supports Secure Sockets Layer (SSL) Plus 3.1.5 + SBGSE on Solaris 32-bit and 64-bit and Microsoft Windows on the following products:
Software Developer’s Kit components:
Client-Library
ESQL/C
ESQL/COBOL
Open Server
As a result of Federal regulations, Sybase must use the FIPS-certified cipher suites. After you have upgraded to SDK 12.5.1 ESD #2 (which includes Open Client) and to Open Server 12.5.1 ESD #2 or later, for Microsoft Windows, you must initialize the Certicom libraries as described in the following procedure before you can do any SSL testing. For Solaris, you must make sure that the lib3p directory is in the dynamic load library path.
Initializing the Certicom libraries for Windows
To allow the ctlib and srvlib libraries to find the Certicom cipher suites in libsb.dll, add the following to the dynamic load library path:
%SYBASE%\%SYBASE_OCS%\lib3p
Run the following program:
%SYBASE%\%SYBASE_OCS%\bin\setsslreg.exe
This program adds an item to the system registry that is used by libsb.dll for a self-test. Once the value is in the registry for a particular machine, you do not need to rerun the setsslreg.exe program unless the value is deleted for some reason.
Run the following program:
%SYBASE%\%SYBASE_OCS%\bin\sbgtest.exe
This program verifies that the registry entry and libsb.dll are properly configured (be sure that lib3p is in the process path). The sbgtest.exe is used to confirm that libsb.dll can get to the registry entry and passes its self-test.
The situations when you might use sbgtest.exe more than once are as follows:
After running setsslreg, to confirm that the registry entry exists.
After experiencing a complete failure using SSL, to verify that libsb.dll is still functioning.
It is very important that when you run an application
that uses SSL, that the lib3p directory is
in its dynamic load library path.
