From: Larry Rosenman <ler@lerctr.org>
ler> * Justin Clift <jclift@iprimus.com.au> [010325 07:34]:
ler> > Hi Peter,
ler> >
ler> > Can't this be at least worked around by ./configure detecting there will
ler> > be a conflict (i.e. being compiled with OpenSSL support on Solaris or
ler> > Unixware) then creating something like #define
ler> > OPENSSL_DES_ENCRYPT_NAMESPACE_CONFLICT in the Makefile, and then having
ler> > crypt.c (etc) check for this and not #include <crypt.h> ?
ler> >
ler> > Things compile fine without <crypt.h> being included, in the case of
ler> > OpenSSL support being needed. As the problem appears to be in
ler> > already-released versions of OpenSSL, wouldn't the best approach be to
ler> > notify the OpenSSL guys (they're decent people, and CC'ing this now to
ler> > their developer list) and also work around the problem ourselves?
ler> I've been in contact with an OpenSSL guy, and given him a shell
ler> account here. He's looking into it.
The problem is how to make it smoothe. I'm open for suggestions. And
it's not as simple as just skipping compilation of des_encrypt() in
OpenSSL, because it's needed internally. I've no idea if the bast way
is really to rename the function or something else. Just removing it
from the exported headers is *not* the solution, because there will
still be a name clash, the only difference being that ld won't make a
fuss about it, and the OpenSSL implementation will most probably win,
making those who call it thinking it's the libc ds_encrypt() loosers!
--
Richard Levitte \ Spannvägen 38, II \ LeViMS@stacken.kth.se
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- poei@bofh.se
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
