=code directive, the linker ends up putting the
assembler in the data segment, which sometime later hits
WinXPSP2/Windows Server 2003's Data Execution Prevention, since the data
segment is loaded without the execute bit set.
--
Jon Bright
Silicon Circus Ltd.
http://www.siliconcircus.com
Hi,
The attached patch is necessary in order to compile bn_nist.c with
Borland Builder 5. It turns off the Condition is always true and
Unreachable code warnings, without which the compiler eventually drops
out with a Too many warnings error.
--
Jon Bright
Silicon Circus Ltd.
http
Jon Bright wrote:
The attached patch is necessary in order to compile bn_nist.c with
Borland Builder 5. It turns off the Condition is always true and
Unreachable code warnings, without which the compiler eventually drops
out with a Too many warnings error.
...and I should probably mention
.
--
Jon Bright
Silicon Circus Ltd.
http://www.siliconcircus.com
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager
just sit patiently until it gets to the top of someone's queue?
--
Jon Bright
Silicon Circus Ltd.
http://www.siliconcircus.com
__
OpenSSL Project http://www.openssl.org
Development Mailing List
key exchange
and the mathematics behind it.
--
Jon Bright
Silicon Circus Ltd.
http://www.siliconcircus.com
__
OpenSSL Project http://www.openssl.org
Development Mailing List
could avoid this problem by using the SHA1 hash (or MD5 hash) of
your ASCII key as the Blowfish key. This would avoid the problem you're
referring to since the hashes for 'fred' and 'fredfred' would be different.
--
Jon Bright
Lead Programmer, Silicon Circus Ltd.
http://www.siliconcircus.com
'
This same error happpened for me when compiling with Builder 5. I
haven't checked Builder 6 yet. This is the one outstanding error for
Builder 5 for which I still have local patches - I did submit a working
fix for this some time ago, but it was kind-of controversial and didn't
make it in.
--
Jon
