On Thu, Jun 06, 2002 at 02:57:28PM -0500, Steve Romero wrote: > Didn't see a bug list, but wanted to let everyone know that I had problems > with this beta release under the following conditions: > > + gcc > + Solaris 8 (patched) > + rsaref-2.0 > + openssl-0.9.7-beta1 > > When compiling openssl I get: > > evp_test.c: In function `main': > evp_test.c:361: warning: implicit declaration of function `strsep' > evp_test.c:361: warning: passing arg 1 of `atoi' makes pointer from integer > without a cast > gcc -o evp_test -I.. -I../include -DOPENSSL_SYSNAME_ULTRASPARC -fPIC > -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 > -fPIC -m32 -mcpu=ultrasparc -O3 -fomit-frame-pointer -Wall -DB_ENDIAN > -DBN_DIV2W -DMD5_ASM evp_test.o -L.. -lcrypto > -L/home/sromero/openssl-0.9.7-beta1/../rsaref-2.0/local/rsaref -lsocket > -lnsl -ldl > evp_test.o: In function `main': > evp_test.o(.text+0x11bc): undefined reference to `strsep' > collect2: ld returned 1 exit status > make[1]: *** [evp_test] Error 1 > make[1]: Leaving directory `/LOG/home/sromero/openssl-0.9.7-beta1/test' > make: *** [sub_all] Error 1
This bug has been fixed since the release of OpenSSL-0.9.7-beta1. Beta2 will be released soon. > + gcc (same versions mentioned above) > + Solaris 8 (patched) > + rsaref-2.0 RSAREF is no longer being used or required. > + openssl-0.9.7-stable-SNAP-20020529 > + mm-1.1.3 > + mod_ssl-2.8.8-1.3.24 > + apache-1.3.24 > > When compiling apache with these ingredients I get: > > /include -DMOD_SSL_VERSION=\"2.8.8\" ssl_engine_vars.c && mv > ssl_engine_vars.o ssl_engine_vars.lo > ssl_engine_vars.c:410: `NID_uniqueIdentifier' undeclared here (not in a > function) The OpenSSL developers are aware of this problem. It is created by uniqueIdentifier not being the correct name of the OID (object identifier). The correct OID is X500UniqueIdentifier (thus leading to NID_X500UniqueIdentifier being available instead). The name change was required in order to become compatible to the LDAP scheme defined in RFC2253. However: as you already found out, it breaks compatibility. We have not yet decided about what to do about this problem. Unfortunately UniqueIdentifier was already used for another OID in RFC1274 (that is however currently disabled in OpenSSL), so that it does not make sense for OpenSSL to simply leave things as they were... For a more complete discussion of this item please check out the OpenSSL request tracker http://www.openssl.org/support/rt2/ http://www.aet.tu-cottbus.de/rt2/NoAuth/Buglist.html and more specifically Ticket #82 http://www.aet.tu-cottbus.de/rt2/Ticket/Display.html?id=82 (guest account is "guest"/"guest"). Best regards, Lutz -- Lutz Jaenicke [EMAIL PROTECTED] http://www.aet.TU-Cottbus.DE/personen/jaenicke/ BTU Cottbus, Allgemeine Elektrotechnik Universitaetsplatz 3-4, D-03044 Cottbus ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
