RE: ssl_error(202): (GSKit) Key database file was not found.

[Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>]

In the README source member for LIBHTTP, there are instructions for building with SSL support. Did you recompile LIBHTTP on the production box? Did you compile with SSL support? To use, you will need *SYSTEM certificate in the DCM. If the production box has never had it setup, you will need to do that once.

In addition, there is new support for various versions of SSL and TLS both in the OS and in HTTPAPI. Depending on your release, you shouldn't have to do anything but you can change parameters in both to assist your SSL/TLS efforts. After following the setup instructions in the README, if you are still having problems, let us know.

Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Max Buda
Sent: Monday, April 27, 2015 10:12 AM
To: HTTPAPI and FTPAPI Projects
Subject: ssl_error(202): (GSKit) Key database file was not found.

I developed a program to consume a web service from our customer.
The program was promoted to production (separate system) this weekend and we ran into a problem.

Here is the error we are receiving:
SSL version 2 support disabled
SSL version 3 support disabled
Old interface to TLS version 1.0 support enabled TLS version 1.0 support enabled TLS version 1.1 support enabled TLS version 1.2 support enabled
(GSKit) Key database file was not found.
ssl_error(202): (GSKit) Key database file was not found.
SetError() #24: gsk_env_init: (GSKit) Key database file was not found.

I do not recall creating the database on the development system.
And now I am unfamiliar with the steps required to create such a database.

Any help would be greatly appreciated.


Max Buda
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------