OpenSSH and OpenSSL snapshots

[Nicolas Williams]

On Tue, Jan 22, 2002 at 06:12:15PM -0800, Booker C. Bense wrote:
> On 23 Jan 2002, Damien Miller wrote:
> 
> > On Wed, 2002-01-23 at 03:27, Booker C. Bense wrote:
> >
> > > - The api hasn't changed that much, a simple query-replace
> > > with /des_/DES_/ should fix the src code tree once and for
> > > all.
> >
> > That won't work - we have to support currently deployed OpenSSL's as
> > well as the newest versions.
> >
> 
> - It will with this include file.
> 
> #ifdef OPENSSL_OLD_VERSION
> 
> #define DES_set_key          des_set_key
> #define DES_key_sched        des_key_sched
> #define DES_ncbc_encrypt     des_ncbc_encrypt
> #define DES_ede3_cbc_encrypt des_ede3_cbc_encrypt
> #define DES_cblock           des_cblock
> 
> #endif

So if the OpenSSH Team refuses to cater to this OpenSSL change or to
upgrade to the new version till, say, 1.0, one could ./configure
 --with-cppflags="-DDES_set_key=des_set_key ..." ...  or ./configure
 --with-cppflags="-Ddes_set_key=DES_set_key ..." ..., depending on what
version of OpenSSL the OpenSSH team decides to support and what version
you use. Kinda sucky, but livable.

> - I think people are making this into a bigger
> problem than it is. Yes it requires that openssl
> apps do a bit more work, but it isn't that much
> and it makes some things possible that just weren't
> before this change.

Yes. But not catering to this change in OpenSSL wouldn't be that bad if
the above ./configure --with-cppflags=... trick works...

> - Booker C. Bense


Cheers,

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.