Hiroshi Inoue wrote:
>> Do you have a Win32 program that establishes a SSL connection and does NOT
>> crash?
>
>For example MS Access. Unfortunately we can't expect to add
> OPENSSL_Applink() code snippet to such generic applications.
Well, if SSL connections do work with MS Access, then the error must be
somewhere else.
How do you test the driver during developement? Are you using Access or a
handwritten program?
>> PS: psqlODBC only calls SSL_read(), SSL_write() and SSL_get_error(). As I
>> understand it all the real SSL handling happens in libpq. So maybe I am
>> looking at the wrong place to find the error?
>
>Psqlodbc uses libpq to establish SSL connections and gets the result
>communication path using PQsocket() and/or PQgetssl(). Then
>the driver communcates with the server via the commnication path
>and doesn't call libpq APIs until the end of the connection.
>The driver calls PQfinish() to terminate the connection.
>
>It would be a problem if libpq and psqlodbc link different openssl
>libraries.
What I did was installing Postgres 8.2.4 _without_ the psqlODBC driver.
Afterwards I downloaded the latest MSI package [8.2.0400] from the psqlODBC
page and installed that version. Any chance that there are some
incompatibilites introduced by that?
Rainer