On a CentOS 5.4 x86_64 system, OpenSSL 0.9.8l builds correctly under
binutils 2.17.50. However, on the same system using binutils 2.20.51
the GNU assembler (as) generates errors in both MD5 and SHA1 assembly
code of the form:
md5-x86_64.s:41: Error: 0xd76aa478 out range of signed 32bit
Hello Richard,
I have tested the OPENSSL-100-STABLE-SNAP-20091116 and it looks much
better.
Thank you for the merge.
I have two small remarks:
1. I'm still missing the pointer size choice. I think that it is wise to
give the possibility to choose between 64 and 32 bit pointer size build.
2.
[tom.rothr...@us.army.mil - Tue Nov 17 09:36:56 2009]:
On a CentOS 5.4 x86_64 system, OpenSSL 0.9.8l builds correctly under
binutils 2.17.50. However, on the same system using binutils 2.20.51
the GNU assembler (as) generates errors in both MD5 and SHA1 assembly
code of the form:
On Sun, Nov 15, 2009 at 12:54:11PM +0200, Eren T?rkay wrote:
On Wednesday 11 November 2009 10:16:54 am Tomas Hoger wrote:
0.9.8-stable does send an alert and tears down connection immediately.
So the behavior in 0.9.8l was not really intended.
Will the new version of the package be
Hello all,
Does openssl have support for SHA-2. ?
I know that SHA-2 is part of the crypto library but looking at the way the
context is setup in ssl_ctx_new we are setiing up
ret-sha1=EVP_get_digestbyname(ssl3-sha1))
So is there a way to establish an openssl connection using SHA-2 currently?
