Both products must be either statically linked to OpenSSL or be rebuilt when OpenSSL changes.
Phil Howard wrote:
On Thu, Feb 20, 2003 at 12:23:40PM +0100, Richard Levitte - VMS Whacker wrote:
| phil-openssl-users> What I had to do to get around the problem was to
| phil-openssl-users> build critical programs like OpenSSH statically so
| phil-openssl-users> they had no dependency on the shared library.
| | That doesn't matter. OpenSSH detects a difference in the shared
| library, down to the patch level, so whenever you upgrade OpenSSL,
| even within the same "series", OpenSSH will stop working. That's
| their choice, and I can understand it.
If you understand it, could you explain that understanding? Is it
because of the API changes?
I guess I need to continue to build OpenSSH statically. And if their
choice persist even after OpenSSL 1.0.0, that may have to be forever.
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
