Re: [PATCH] cfi/fpo directives in md5 assembly code

2011-06-29 Thread yoni londner
I agree entirely, but why not fix the other registers while we're at it? I've attached a version of your diff with the extra registers' unwind info added--- untested, unfortunately--- it'll also need a sub ::cfi_restore { ::emit(.cfi_restore,@_); } in x86gas.pl and the corresponding stub

Re: [openssl.org #2549] [Bug report / Linux / openssl 0.9.8k-7ubuntu8.6] openssl s_client does not verify certificate against server's host name

2011-06-29 Thread Alain Knaff via RT
On 27/06/11 11:54, Peter Sylvester via RT wrote: On 06/26/2011 08:05 PM, Peter Sylvester wrote: On 06/26/2011 02:59 PM, Alain Knaff via RT wrote: Hello, openssl s_client -connect hostname.domain.com:443 does not verify that the certificate matches the hostname. (i.e. hostname.domain.com

Re: Build Error on 1.0.1 with FIPS

2011-06-29 Thread Tyrel Haveman
Thanks Steve. This helps a lot. One more related question: Why are the FIPS test vectors different for different platforms? It seems like Windows and Linux, for example, should both be able to encrypt the same things and produce the same outputs. Thanks again, Tyrel On Tue, Jun 28, 2011 at 10:44

Re: Build Error on 1.0.1 with FIPS

2011-06-29 Thread Dr. Stephen Henson
On Wed, Jun 29, 2011, Tyrel Haveman wrote: Thanks Steve. This helps a lot. One more related question: Why are the FIPS test vectors different for different platforms? It seems like Windows and Linux, for example, should both be able to encrypt the same things and produce the same outputs.

Re: Build Error on 1.0.1 with FIPS

2011-06-29 Thread Steve Marquess
On 06/29/2011 04:46 PM, Dr. Stephen Henson wrote: On Wed, Jun 29, 2011, Tyrel Haveman wrote: Thanks Steve. This helps a lot. One more related question: Why are the FIPS test vectors different for different platforms? It seems like Windows and Linux, for example, should both be able to encrypt

Re: [PATCH] cfi/fpo directives in md5 assembly code

2011-06-29 Thread Wim Lewis
On 28 Jun 2011, at 5:56 PM, Wim Lewis wrote: Several of the other assembly files could use the same treatment as well: md5-x86_64.pl uses %rbp to point to one of its arguments, sha1-586.pl uses %ebp as a scratch register, etc. It occurs to me that a lot of the CFI management could be done