final build.

[Jim Knoble]

Circa 2002-Jun-26 00:57:12 -0500 dixit Phil Howard:

: I don't need to have static executeables immediately.  But I do need
: to be on static executeables by the next time OpenSSL needs to be
: upgraded. I have a lot of remote servers to manage and I use SSH to
: access them.

Phil, another option is to patch the OpenSSL builds to use unique
SONAMEs for each new (and incompatible) version of the library.

For example, i generally install the OpenSSL libraries as:

  .../libcrypto-0.9.6d.so.0 -> libcrypto-0.9.6d.so.0.0.0
  .../libcrypto-0.9.6d.so.0.0.0
  .../libssl-0.9.6d.so.0 -> libssl-0.9.6d.so.0.0.0
  .../libssl-0.9.6d.so.0

This both keeps OpenSSL-0.9.6d from stomping on OpenSSL-0.9.6c and
allows packages which contain only the shared libraries to peacefully
coexist.  Thus, you can install new OpenSSL shared libs, upgrade the
development libs and headers, and compile OpenSSH against the new
libraries without danger that the old one will stop working in the
middle of the process.

I have a patch against OpenSSL-0.9.6d which accomplishes the above;
please mail me privately if you'd like it.

-- 
jim knoble  |  jmknoble at pobox.com  |  http://www.pobox.com/~jmknoble/
(GnuPG fingerprint: 31C4:8AAC:F24E:A70C:4000::BBF4:289F:EAA8:1381:1491)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 249 bytes
Desc: not available
Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20020626/aa9e2576/attachment.bin