No update in nine years, closing this.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
or not.
-Original Message-
From: Richard Levitte - VMS Whacker [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 2:10 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: Jim Sahaj
Subject: Re: [openssl.org #479] support version independent upgrade
In message [EMAIL PROTECTED] on Mon, 27 Jan 2003
In message [EMAIL PROTECTED] on Mon, 27 Jan 2003 23:33:24
+0100 (MET), [EMAIL PROTECTED] via RT [EMAIL PROTECTED] said:
rt Actually, I'd prefer that I wouldn't have to relink and
rt redistribute my application every time a security patch comes out
rt for OpenSSL. I haven't seen any issues in
In message [EMAIL PROTECTED] on Mon, 27 Jan 2003 23:33:24
+0100 (MET), [EMAIL PROTECTED] via RT [EMAIL PROTECTED] said:
rt Actually, I'd prefer that I wouldn't have to relink and
rt redistribute my application every time a security patch comes out
rt for OpenSSL. I haven't seen any issues in
Currently, on many Unix platforms I link my application against
libssl.so and libcrypto.so. Typically, these are links set to resolve
down to the versioned types of these files, like libssl.so.0.9.7 and
libcrypto.so.0.9.7. The internal names of these shared objects
include the major and
In message [EMAIL PROTECTED] on Mon, 27 Jan 2003 22:40:24
+0100 (MET), via RT [EMAIL PROTECTED] said:
rt Currently, on many Unix platforms I link my application against
rt libssl.so and libcrypto.so. Typically, these are links set to resolve
rt down to the versioned types of these files, like
In message [EMAIL PROTECTED] on Mon, 27 Jan 2003 22:40:24
+0100 (MET), via RT [EMAIL PROTECTED] said:
rt Currently, on many Unix platforms I link my application against
rt libssl.so and libcrypto.so. Typically, these are links set to resolve
rt down to the versioned types of these files,
