setPrivateKeyFile Issues

[ezarowny]

Is there any reason the setPrivateKeyFile function in DcmTLSTransportLayer ( http://support.dcmtk.org/docs/classDcmT ... Layer.html ) would fail on Windows if the file path was correct?

Does this function work correctly in a thread?

For reference, I am using the latest public release (3.6.0) and appropriate matching Windows support libraries.

[Uli Schlachter]

Since that function just calls into OpenSSL, it should be just as thread-safe as OpenSSL is.

However, since that function just calls into OpenSSL, OpenSSL's error stack should contain details about the problem.

So what does

Code: Select all

COUT << ERR_reason_error_string(ERR_peek_error());

say about the problem?

[ezarowny]

Thanks for the response!

The error is reported as: unable to load ssl md5 routines

Google isn't bringing up anything particularly helpful unfortunately.

[ezarowny]

What's strange is that I am not getting this behavior with a previous version of DCMTK. I'll dig deeper.

[ezarowny]

Upgrading and downgrading openSSL hasn't seem to have made a difference. How odd.

[ezarowny]

Solved it. It was a conflicting framework in our application. The other framework wasn't handling openSSL in a thread-safe manner while our dcmtk integration was.

Upgrade your frameworks everyone!