[openssl.org #1132] double pass SMIME

Hi Steve, I found a bug in the earlier submission where the single run (2 pass) produced slightly different encoding than 2 separate passes. The attachment is a fixed /apps/smime.c - its actually less lines changed than the previous one. I'm not sure how to generate just a patch file. The pat

[openssl.org #1132] double pass SMIME

Hi Steve, I found a bug in the earlier submission where the single run (2 pass) produced slightly different encoding than 2 separate passes. The attachment is a fixed /apps/smime.c - its actually less lines changed than the previous one. I'm not sure how to generate just a patch file. The patc

Re: linux+mingw -> create openssl for windows [u]

it has to do with the definition files, but as I don't know what those exactly do, I'm pretty much lost. Regards, Andreas diff -udrNP openssl-0.9.8-stable-SNAP-20050703.orig/Configure openssl-0.9.8-stable-SNAP-20050703/Configure --- openssl-0.9.8-stable-SNAP-20050703.orig/Configure 2005

Re: Error in July releases of Openssl 0.9.7

7On Sun, 3 Jul 2005, Andy Polyakov wrote: > Are you sure that not earlier? The closest change that might affect > certificate look-ups is dated 23rd, to be specific > http://cvs.openssl.org/chngview?cn=14114. The new code is buggy! As it > is now dir variable can be used uninitialized and it ap

Re: Win 64a dynamic link library build was unsuccessful using beta6

Stop saying "it works properly." It links, it passes the test, but it's missing the functionality. Well, functionality which I don't need. Sorry, bit for me it's either everything or nothing. In this particular context Applink is either there, ready to be used or not there [in which case I'd

Re: Error in July releases of Openssl 0.9.7

The previews versions have an error. They do not recognize Certs in Apache-SSL. The problems turns up in 20050701 . Are you sure that not earlier? The closest change that might affect certificate look-ups is dated 23rd, to be specific http://cvs.openssl.org/chngview?cn=14114. The new code is

Re: Win 64a dynamic link library build was unsuccessful using beta6

Hi again! > Well, no multiple $lazyN is improvement, isn't it? The above error > message doesn't make sense though. uplink.obj complains about symbol > being already defined in itself... H-m-m-m... I have to ponder over > this... Thanks. But i have made some progress... see later in this mail.

Re: Error in July releases of Openssl 0.9.7

On Sun, Jul 03, 2005 at 03:34:09PM +0200, Andy Polyakov wrote: > >>The previews versions have an error. > >> > >>They do not recognize Certs in Apache-SSL. > >>The problems turns up in 20050701 . > > > >Are you sure that not earlier? The closest change that might affect > >certificate look-ups is

Re: Error in July releases of Openssl 0.9.7

The previews versions have an error. They do not recognize Certs in Apache-SSL. The problems turns up in 20050701 . Are you sure that not earlier? The closest change that might affect certificate look-ups is dated 23rd, to be specific http://cvs.openssl.org/chngview?cn=14114. The new code is

Re: Win 64a dynamic link library build was unsuccessful using beta6

So I cleaned my openssl directory and started again. I cannot build the dlls as you directed me because if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then I got the following: link /nologo /subsystem:console /opt:ref bufferoverflowU.lib /dll /out:out32dll\libeay32.dll /def:ms/L

Re: Win 64a dynamic link library build was unsuccessful using beta6

Another try :)) So I cleaned my openssl directory and started again. I cannot build the dlls as you directed me because if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then I got the following: link /nologo /subsystem:console /opt:ref bufferoverflowU.lib /dll /out:out32dll\libeay

Re: Win 64a dynamic link library build was unsuccessful using beta6

First of all I figured it out that i should use SHLIB_EX_OBJ not APP_EX_OBJ :)) Keep in mind that the instructions were provided off the top of my head and not actually tested, which is why it's so "bumpy." Bear with me:-) Second if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then

Re: Win 64a dynamic link library build was unsuccessful using beta6

Hi! First of all I figured it out that i should use SHLIB_EX_OBJ not APP_EX_OBJ :)) Second if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then I cannot link libeay32.dll: link /nologo /subsystem:console /opt:ref bufferoverflowU.lib /dll /out:o ut32dll\libeay32.dll /def:ms/LIBEA

Re: Error in July releases of Openssl 0.9.7

The previews versions have an error. They do not recognize Certs in Apache-SSL. The problems turns up in 20050701 . Are you sure that not earlier? The closest change that might affect certificate look-ups is dated 23rd, to be specific http://cvs.openssl.org/chngview?cn=14114. The new code

Re: Win 64a dynamic link library build was unsuccessful using beta6

bss_file.obj : error LNK2001: unresolved external symbol OPENSSL_UplinkTable b_dump.obj : error LNK2001: unresolved external symbol OPENSSL_UplinkTable So as you adviced I tried the following: perl ms/uplink.pl win64a > uplink.asm ml64 -c uplink.asm add it to APP_EX_OBJ in ntdll.mak file. Sti