Re: [openssl.org #2996] PATCH: cygwin (and probably others) support broken by long time

2013-04-10 Thread carlo . bramix
On Feb 23 17:01, carlo.bra...@libero.it via RT wrote: Hello, in the file crypto/sha/sha.h there is this line: #if (defined(_WIN32) || defined(_WIN64)) !defined(__MINGW32__) used to conditionally declare SHA_LONG64 and U64 macros. Unfortunately, this causes OpenSSL to be unusable on

Apache 2.2.16 with fips prints a Hex value on start up

2013-04-10 Thread Cipher
Hi , I recently build Apache 2.2.16 with fips support using following confs. $CC=fipsld , $FIPSLD_CC=gcc ./configure --with-ssl=/software/openssl/openssl-1.0.1c --enable-so --enable-ssl LIBS=-ldl make But when i run the created executable, it prints a hex value. bash-3.00$ cd

Re: [openssl.org #2051] [PATCH] IPv6 support for s_client and s_server

2013-04-10 Thread Balakumaran Kannan
On Tue, Apr 9, 2013 at 10:13 PM, Mike Frysinger via RT r...@openssl.orgwrote: i've improved the original patch to make the -4/-6 behavior consistent across the tools. i also tweaked the behavior slightly to make it run correctly (imo). -mike I tried your patch it works well. Thank you

Re: [openssl.org #2051] [PATCH] IPv6 support for s_client and s_server

2013-04-10 Thread Balakumaran Kannan
Anyway, I need IPv6 support. I'm going to refine this patch and use. If the community people are interested I'll share it. Regards, Bala. On Wed, Apr 10, 2013 at 5:02 PM, Michael Tuexen tue...@fh-muenster.dewrote: On Apr 10, 2013, at 1:19 PM, Balakumaran Kannan wrote: On Tue, Apr 9, 2013

Re: [openssl.org #2051] [PATCH] IPv6 support for s_client and s_server

2013-04-10 Thread Michael Tuexen
On Apr 10, 2013, at 1:19 PM, Balakumaran Kannan wrote: On Tue, Apr 9, 2013 at 10:13 PM, Mike Frysinger via RT r...@openssl.org wrote: i've improved the original patch to make the -4/-6 behavior consistent across the tools. i also tweaked the behavior slightly to make it run correctly

What are the procedures to authenticate certificate?

2013-04-10 Thread igenyar
After receiving a certificate, the client needs to send challenge to server to verify that the server does have the private key associated with the certificate. (Besides other checkings such as DNS, etc.) I wonder what OpenSSL API's would accomplish that. Links to knowledge or sample source code

Re: What are the procedures to authenticate certificate?

2013-04-10 Thread Wim Lewis
On 10 Apr 2013, at 5:25 PM, igenyar wrote: After receiving a certificate, the client needs to send challenge to server to verify that the server does have the private key associated with the certificate. (Besides other checkings such as DNS, etc.) This happens as part of the SSL handshake ---

RE: What are the procedures to authenticate certificate?

2013-04-10 Thread Salz, Rich
The proper term is proof of possession. SSL/TLS define how to do it in the protocol spec. /r$ -- Principal Security Engineer Akamai Technology Cambridge, MA __ OpenSSL Project