Matthias wrote:
Kyle Hamilton wrote:
Did you make sure to remove %SYSTEMROOT%\system32\ssleay32.dll and
libeay32.dll? Just running the uninstaller doesn't get rid of them.
No, I forgot that. Sorry, my fault.
I now replaced those two DLLs with the ones I compiled myself.
Good news: in
Matthias wrote:
I deleted all ssl-related DLLs on my system now.
When I compile OpenSSL as described in INSTALL.W32, point the include
library directory of my example program on openssl\out32dll, recompile
my example program, copy the 2 DLLs from openssl\out32dll to my
example project
On 2/21/06, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
One most confusing thing is that MS actually has two -different- pdb
files. One is a source program database, one is an executable program
database. You want to locate the one with a name matching your .dll
files into the same
Kyle Hamilton wrote:
Did you make sure to remove %SYSTEMROOT%\system32\ssleay32.dll and
libeay32.dll? Just running the uninstaller doesn't get rid of them.
No, I forgot that. Sorry, my fault.
I now replaced those two DLLs with the ones I compiled myself.
Good news: in Release mode my
The best thing to do, when compiling, is to copy the DLLs to the
directory (either Debug or Release) that the rest of your project is
going to, and then create empty files named ssleay32.dll.local and
libeay32.dll.local in the same directory. (This causes Windows to use
the versions of the files
Also, you didn't compile openssl in debug mode, otherwise the
libeay32.dll!(address)() calls in the stack would be showing the
function names. To do so, you need to run:
perl Configure -d [VC-NT | VC-WIN32]
if you're running Visual C++. The -d causes it to build for the debug
target, which
ignore this, I'm used to the POSIX-system variants. :P
-Kyle
On 2/20/06, Kyle Hamilton [EMAIL PROTECTED] wrote:
Also, you didn't compile openssl in debug mode, otherwise the
libeay32.dll!(address)() calls in the stack would be showing the
function names. To do so, you need to run:
perl
To get the debugging symbols for Windows, read the INSTALL.W32 file.
Of particular note is this little gem:
There are various changes you can make to the Win32 compile environment. By
default the library is not compiled with debugging symbols. If you add 'debug'
to the mk1mf.pl lines in the do_*
I deleted all ssl-related DLLs on my system now.
When I compile OpenSSL as described in INSTALL.W32, point the include
library directory of my example program on openssl\out32dll, recompile
my example program, copy the 2 DLLs from openssl\out32dll to my
example project directory...
...then my
Are you making sure to link properly with the multithreaded libraries?
(I think that was the default starting with VC++.net 2003, but I
can't recall.)
Incidentally, you can download a free ISO of VC++ 2005 Express Edition
from Microsoft. The IDE doesn't support resource editing, but I'm
having
Did recompiling OpenSSL myself solve my problem with
PEM_read_RSAPrivateKey not returning?
Short answer: no.
Long answer: I did uninstall the precompiled binaries. Then I compiled
OpenSSL 0.9.8a (openssl-0.9.8a.tar.gz which is found at your website)
myself and tried my test program - but same
Did you make sure to remove %SYSTEMROOT%\system32\ssleay32.dll and
libeay32.dll? Just running the uninstaller doesn't get rid of them.
-Kyle H
On 2/17/06, Matthias [EMAIL PROTECTED] wrote:
Did recompiling OpenSSL myself solve my problem with
PEM_read_RSAPrivateKey not returning?
Short
Kyle Hamilton wrote:
msvcr71d.dll? That looks like a debug version of the VC library to me.
It was compiled and run in debug mode.
Incidentally, I'm getting the same problem on VC8 (VC++2005 Express
Edition). And I'm getting it even in release configuration.
Somehow I am relieved and
On Thu, Feb 16, 2006, Matthias wrote:
Somehow I am relieved and worried the same time that it affects not
only me...
I recently noticed a problem when attempting to use an OpenSSL DLL compiled
against Visual Studio 2005 with an OpenSSL application compiled with another
compiler.
When both
I was using the precompiled binaries when that test failed.
After I rebuilt the libraries with the VC8 compiler as Dr. Henson
suggested, it worked.
I consider it a bug in the Application Binary Interface of Windows,
not a bug that OpenSSL can work around.
-Kyle H
On 2/16/06, Matthias [EMAIL
One of the most important things about this is, when did you obtain
the installer from slproweb.com? It's difficult to figure out if
it's older, or a problem in a very recent build, or what.
Did you attach a debugger to the program and examine it to see what
might be looping?
(In the meantime,
Hi again
I downloaded from slproweb at 9. February 2006 and the file
is called Win32OpenSSL-v0.9.8a.exe. I didn't have any
OpenSSL stuff on my computer before, so even no old things
lieing around on the harddisc.
If I run the program in VS .net 2003 v7.1.3088 with Start F5
the program seems to
Subject: Re: function PEM_read_RSAPrivateKey not returning
Hi again
I downloaded from slproweb at 9. February 2006 and the file
is called Win32OpenSSL-v0.9.8a.exe. I didn't have any
OpenSSL stuff on my computer before, so even no old things
lieing around on the harddisc.
If I run the program
On Wed, Feb 15, 2006, Matthias wrote:
Good day everyone!
I do have the problem that the OpenSSL function PEM_read_RSAPrivateKey
does nothing, not even returning. Since I can not find any more hints
in the net I am asking here for help. I wrote a minimalistic example
program and hope
to a release version of MS libraries. Please ensure
that you run the release version of your program.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Matthias
Sent: Wednesday, February 15, 2006 4:24 PM
To: openssl-users@openssl.org
Subject: Re: function
20 matches
Mail list logo
