Re: fipscanister with assembly language optimization and non-SSE2 capable processors?

2012-12-19 Thread Jeffrey Walton
On Tue, Dec 18, 2012 at 11:15 PM, Bill Durant cipherte...@gmail.com wrote: Is it not possible to build a FIPS-capable OpenSSL with assembly language optimization enabled in the fipscanister that works under non-SSE2 capable processors? On SUSE Linux Enterprise Server 10, I have built the

Re: fipscanister with assembly language optimization and non-SSE2 capable processors?

2012-12-19 Thread Bill Durant
Hello Jeffrey: Thank you for the response. So FIPS mode enable is supported on non-SSE2 processors *only* with a fipscanister that is built with the no-asm option? Thanks, Bill On Dec 19, 2012, at 1:13 AM, Jeffrey Walton wrote: On Tue, Dec 18, 2012 at 11:15 PM, Bill Durant

Re: loading public point

2012-12-19 Thread Douglas E. Engert
Where did you get the hex version of the point? It does not look correct, its the wrong length. For the curve you picked, The field size is 21 bytes. The hex should be 04|x|y which would be 43 bytes, so string should be 86 bytes with a leading 04. On 12/13/2012 12:23 AM, jeetendra gangele

Re: fipscanister with assembly language optimization and non-SSE2 capable processors?

2012-12-19 Thread Steve Marquess
On 12/19/2012 05:21 AM, Bill Durant wrote: Hello Jeffrey: Thank you for the response. So FIPS mode enable is supported on non-SSE2 processors *only* with a fipscanister that is built with the no-asm option? Correct. That's an unfortunate limitation of the requirements of the validation

Re: fipscanister with assembly language optimization and non-SSE2 capable processors?

2012-12-19 Thread Bill Durant
Wow... That is certainly a very unfortunate limitation... Thank you for clarifying... Bill On Dec 19, 2012, at 6:40 AM, Steve Marquess wrote: On 12/19/2012 05:21 AM, Bill Durant wrote: Hello Jeffrey: Thank you for the response. So FIPS mode enable is supported on non-SSE2 processors

Injecting previously received data into the openssl bios?

2012-12-19 Thread David Hinkle
I have a system where I want to selectively man in the middle some SSL connections. My proxy server currently has the capability to man in the middle all connections using openssl, or simply extract the server names from the client hellos. What I'd like to do is use my code to parse the client

{Spam?} openssl-1.0.2-stable-SNAP-20121220 issues

2012-12-19 Thread The Doctor
From make test signed content DER format, RSA key: OK signed detached content DER format, RSA key: OK signed content test streaming BER format, RSA: OK signed content DER format, DSA key: OK signed detached content DER format, DSA key: OK signed detached content DER format, add RSA signer: OK