Hello all,
I found that mk1mf.pl in OpenSSL-0.9.8 doesn't generate a correct
makefile for Windows CE. It uses VC-32.pl instead of VC-CE.pl.
Here is a patch to fix this problem.
Although there still are some problems to be solved to compile, it is a
good starting point, I think.
--
Satoshi
Hi,
I am using d2i_RSAPublicKey and d2i_DSAPublicKey
successfully, but have run into something strange.
I have a server which maintains accounts that may
or may not have public keys associated with them.
This server communicates with the outside world
using TLS-enabled connections. I was
[EMAIL PROTECTED] wrote:
Hi,
Hello Mike,
The problem is that calling the
d2i functions with a length of 0 somehow corrupted
my TLS connection and I would get protocol errors
that required shutting down the connection. Note
that the RSA and DSA objects are in no way connect-
ed to the TLS
I found that mk1mf.pl in OpenSSL-0.9.8 doesn't generate a correct
makefile for Windows CE. It uses VC-32.pl instead of VC-CE.pl.
Here is a patch to fix this problem.
I've chosen to unify VC-32.pl and VC-CE.pl instead. I mean VC-CE.pl is
gone now and VC-32.pl is expected to take care of all
In the linker options for the win32 build, the generated makefile
reads:
$(O_CRYPTO): $(CRYPTOOBJ)
$(MKLIB) /out:$(O_CRYPTO) @
$(CRYPTOOBJ) advapi32.lib
(and the same for SSLOBJ a few lines further up).
There's a significant problem with having advapi32.lib in there
Correct.
test BN_sqr
make[2]: *** [test_bn] Error 139
Could you examine
https://www.aet.tu-cottbus.de/rt2/Ticket/Display.html?id=1146 and see if
you confirm that it's identical problem. A.
__
OpenSSL Project
Hi,
At 25 Jul 2005 00:19:17 +0200 Andy Polyakov wrote:
I've chosen to unify VC-32.pl and VC-CE.pl instead. I mean VC-CE.pl is
gone now and VC-32.pl is expected to take care of all Windows flavors,
Win32, Win64 and WinCE. See http://cvs.openssl.org/chngview?cn=14275
for reference.
I see. I
