Re: What happend from beta till now.. OpenServer 5.0.X build gccerror...
The fix is to remove -DFILIO_H form the sco5-gcc-shared in Configure. Thanks, -- Boyd Gerber [EMAIL PROTECTED] ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
For 0.9.6d a is missing from the shlib/svr5-shared-gcc.sh FLAGSline
I just noticed that a is missing and version change. *** svr5-shared-gcc.sh.org Thu Sep 6 06:30:17 2001 --- svr5-shared-gcc.sh Sat May 11 15:37:00 2002 *** *** 1,7 #!/usr/bin/sh major=0 ! minor=9.6b slib=libssl sh_slib=$slib.so.$major.$minor --- 1,7 #!/usr/bin/sh major=0 ! minor=9.6d slib=libssl sh_slib=$slib.so.$major.$minor *** *** 9,15 clib=libcrypto sh_clib=$clib.so.$major.$minor ! FLAGS=-O3 -DFILIO_H -fomit-frame-pointer -pthread SHFLAGS=-DPIC -fPIC touch $sh_clib --- 9,15 clib=libcrypto sh_clib=$clib.so.$major.$minor ! FLAGS=-O3 -DFILIO_H -fomit-frame-pointer -pthread SHFLAGS=-DPIC -fPIC touch $sh_clib -- Boyd Gerber [EMAIL PROTECTED] ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
-Wl,-Bsymbolic in 0.9.6d broke shared builds
JFYI, when updating our package from 0.9.6c to 0.9.6d I've noticed that the new shared libcrypto library doesn't work anymore. The openssl(1) binary wouldn't recognize any of the block ciphers. I tracked this down to the addition of -Wl,-Bsymbolic. Removing that option solved the problem for us. GNU ld version 2.10.91 (with BFD 2.10.1.0.4) Supported emulations: elf_i386 i386linux Also 0.9.6d would tend to recompile some previously built files during the make install stage, resulting in static linking of openssl(1) (which is undesired in our case). I didn't investigate this too deeply but rather applied the following workaround for now: touch now find -type f -print0 | xargs -0 touch -r now -- right after unpacking the original tarball (before any patches are applied or anything is built). That helped. -- /sd __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
how to include openssl files in our programe
Sir After instalation of ssl I use library of ssl but when I compile the programe, the message comes that can't include the files(header files). Please tell me how to set the path. So that the programe will compile and execute. regards hafiz mail at : [EMAIL PROTECTED] __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[STATUS] OpenSSL (Sun 12-May-2002)
OpenSSL STATUS Last modified at __ $Date: 2002/05/09 23:54:02 $ DEVELOPMENT STATE o OpenSSL 0.9.7: Under development... o OpenSSL 0.9.6d: Released on May9th, 2002 o OpenSSL 0.9.6c: Released on December 21st, 2001 o OpenSSL 0.9.6b: Released on July 9th, 2001 o OpenSSL 0.9.6a: Released on April 5th, 2001 o OpenSSL 0.9.6: Released on September 24th, 2000 o OpenSSL 0.9.5a: Released on April 1st, 2000 o OpenSSL 0.9.5: Released on February 28th, 2000 o OpenSSL 0.9.4: Released on August09th, 1999 o OpenSSL 0.9.3a: Released on May 29th, 1999 o OpenSSL 0.9.3: Released on May 25th, 1999 o OpenSSL 0.9.2b: Released on March 22th, 1999 o OpenSSL 0.9.1c: Released on December 23th, 1998 RELEASE SHOWSTOPPERS o BIGNUM library failures on 64-bit platforms (0.9.7-dev): - BN_mod_mul verificiation (bc) fails for solaris64-sparcv9-cc and other 64-bit platforms Checked on Result alpha-cc (Tru64 version 4.0)works linux-alpha+bwx-gcc doesn't work. Reported by Sean O'Riordain [EMAIL PROTECTED] OpenBSD-sparc64 doesn't work. BN_mod_mul breaks. Needs checked on [add platforms here] - BN_mod_mul verification fails for mips3-sgi-irix unless configured with no-asm AVAILABLE PATCHES o IN PROGRESS o Steve is currently working on (in no particular order): ASN1 code redesign, butchery, replacement. OCSP EVP cipher enhancement. Enhanced certificate chain verification. Private key, certificate and CRL API and implementation. Developing and bugfixing PKCS#7 (S/MIME code). Various X509 issues: character sets, certificate request extensions. o Geoff and Richard are currently working on: ENGINE (the new code that gives hardware support among others). o Richard is currently working on: UI (User Interface) UTIL (a new set of library functions to support some higher level functionality that is currently missing). Shared library support for VMS. Kerberos 5 authentication Constification OCSP NEEDS PATCH o inappropriate AlgorithmIdentifier used in S/MIME signatures (key type instead of signature algorithm) o AES ciphersuites are not (yet) official and should not be enabled unless explicitly requested o apps/ca.c: Sign the certificate? - n creates empty certificate file o OpenSSL STATUS is never up-to-date. OPEN ISSUES o Do we want the EVP API changes in 0.9.7? Can compatibility be improved? o The Makefile hierarchy and build mechanism is still not a round thing: 1. The config vs. Configure scripts It's the same nasty situation as for Apache with APACI vs. src/Configure. It confuses. Suggestion: Merge Configure and config into a single configure script with a Autoconf style interface ;-) and remove Configure and config. Or even let us use GNU Autoconf itself. Then we can avoid a lot of those platform checks which are currently in Configure. o Support for Shared Libraries has to be added at least for the major Unix platforms. The details we can rip from the stuff Ralf has done for the Apache src/Configure script. Ben wants the solution to be really simple. Status: Ralf will look how we can easily incorporate the compiler PIC and linker DSO flags from Apache into the OpenSSL Configure script. Ulf: +1 for using GNU autoconf and libtool (but not automake, which apparently is not flexible enough to generate libcrypto) WISHES o Add variants of DH_generate_parameters() and BN_generate_prime() [etc?] where the callback function can request that the function be aborted. [Gregory Stark [EMAIL PROTECTED], [EMAIL PROTECTED]] o SRP in TLS. [wished by: Dj [EMAIL PROTECTED], Tom Wu [EMAIL PROTECTED], Tom Holroyd [EMAIL PROTECTED]] See http://search.ietf.org/internet-drafts/draft-ietf-tls-srp-00.txt as well as http://www-cs-students.stanford.edu/~tjw/srp/. Tom Holroyd tells us there is a SRP patch for OpenSSH at http://members.tripod.com/professor_tom/archives/, that could be useful. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Announce: Time Stamp Protocol (RFC 3161) patch
On Fri, May 10, 2002 at 11:23:53PM +0100, Zoltan Glozik wrote: Hi All, I am working on an extension to OpenSSL that implements the Time Stamp protocol as specified in RFC 3161 and it reached a quite stable state to make it available to the public. If you are interested you can find the patch for openssl-engine-0.9.6d, installation instructions and manual at this URL: http://glozik-zoltan.int.eu.org/tsa/ Added to the list of applications. 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 Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: For 0.9.6d a is missing from the shlib/svr5-shared-gcc.sh FLAGS line
On Sat, May 11, 2002 at 03:54:52PM -0600, Boyd Lynn Gerber wrote: I just noticed that a is missing and version change. *** svr5-shared-gcc.sh.org Thu Sep 6 06:30:17 2001 --- svr5-shared-gcc.sh Sat May 11 15:37:00 2002 ... *** *** 9,15 clib=libcrypto sh_clib=$clib.so.$major.$minor ! FLAGS=-O3 -DFILIO_H -fomit-frame-pointer -pthread SHFLAGS=-DPIC -fPIC touch $sh_clib --- 9,15 clib=libcrypto sh_clib=$clib.so.$major.$minor ! FLAGS=-O3 -DFILIO_H -fomit-frame-pointer -pthread SHFLAGS=-DPIC -fPIC Hmm. In a previous mail you just stated, that the -DFILIO_H should be removed from the sco5-gcc-shared entry in Configure. In this shared library build script, you however do leave it in. Shouldn't it also be removed here? 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 Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #26] 64 bit Suse Linux on PowerPC
Thank you Lutz and Tim. By configuring with the following: ./Configure linux-ppc I was able to run make successfully and then run make test and make install successfully as well. I was able therefore to successfully build, run the build verification tests and install on the 64 bit Suse Linux on powerPC. Now all we need to do is get ./config to recognize this environment as linux-ppc and we will be fine. Thanks again. John __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #26] 64 bit Suse Linux on PowerPC
Thanks. I have added a corresponding entry into config. Please check out a new snapshot for correct behaviour. Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: SSL_shutdown.3 makewhatis failure under IRIX
On Thu, May 09, 2002 at 04:55:16PM -0400, Rick Troxel wrote: In order for makewhatis -M under IRIX 6.5.14m not to fail on SSL_shutdown.3 as follows: nroff: Macro argument too long; line 170, file /usr/local/man/man3/SSL_shutdown.3 stack: N I found it necessary (well, at least it was sufficient) to recast the long .Ip ...\*(N...\*(T... 4 lines as .Ip ...\*(L...\*(R... The version is openssl-0.9.6c, in case that should matter. I did not have to change the corresponding .IX Item lines. A context diff is attached. Hmm. The manual pages that come with OpenSSL are in POD format. Only during installation, they are converted to manual pages using the util/pod2man.pl script. Did you install OpenSSL from source? (In which case we would have to check pod2man for problems...) 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 Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #29] -Wl,-Bsymbolic in 0.9.6d broke shared builds
JFYI, when updating our package from 0.9.6c to 0.9.6d I've noticed that the new shared libcrypto library doesn't work anymore. The openssl(1) binary wouldn't recognize any of the block ciphers. I tracked this down to the addition of -Wl,-Bsymbolic. Removing that option solved the problem for us. GNU ld version 2.10.91 (with BFD 2.10.1.0.4) Supported emulations: elf_i386 i386linux Also 0.9.6d would tend to recompile some previously built files during the make install stage, resulting in static linking of openssl(1) (which is undesired in our case). I didn't investigate this too deeply but rather applied the following workaround for now: touch now find -type f -print0 | xargs -0 touch -r now -- right after unpacking the original tarball (before any patches are applied or anything is built). That helped. -- /sd __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #29] -Wl,-Bsymbolic in 0.9.6d broke shared builds
[[EMAIL PROTECTED] - Sun May 12 22:48:56 2002]: JFYI, when updating our package from 0.9.6c to 0.9.6d I've noticed that the new shared libcrypto library doesn't work anymore. The openssl(1) binary wouldn't recognize any of the block ciphers. I tracked this down to the addition of -Wl,-Bsymbolic. Removing that option solved the problem for us. This option has only recently been added. The comment in the commitlog says: Make shared libraries resolve global symbols within themselves first. Currently only on GNUish linkers... Submitted by Steven Bade [EMAIL PROTECTED] The issue was raised with respect to integration of a soft token using OpenSSL into iPlanet. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
