Re: need help on handshake failure

2012-08-30 Thread Mithun Kumar
Thanks Dave, i see the below output. soniclx24(misingh): openssl s_client -connect NC-WIN2008X64:1433 -state -debug -msg -ssl3 CONNECTED(0003) SSL_connect:before/connect initialization write to 08A018A8 [08A0B660] (100 bytes => 100 (0x64)) - 16 03 00 00 5f 01 00 00-5b 03 00 50 3f fb 58 6

Re: FIPS Module 2.0 on OS-X 10.7.4 (Lion)

2012-08-30 Thread Steve Marquess
On 08/30/2012 04:20 PM, Jason Todd wrote: > I'm sorry, I misread one of your earlier messages on the subject: > > "Normally recompilation would only be done by the > vendor of record (OSF for this validation), but for the OpenSSL FIPS > Object Module series of validations compilation from source

Re: FIPS Module 2.0 on OS-X 10.7.4 (Lion)

2012-08-30 Thread Jason Todd
Another confusing part, is that since you never release binaries. Is it the organization's own internal testing that has to change in order to approve "Vendor affirmed". And I apologize if these are dumb questions, FIPS is like a house of mirrors where clowns murder you if you blink. On Thu, Aug 3

Re: FIPS Module 2.0 on OS-X 10.7.4 (Lion)

2012-08-30 Thread Jason Todd
I'm sorry, I misread one of your earlier messages on the subject: "Normally recompilation would only be done by the vendor of record (OSF for this validation), but for the OpenSSL FIPS Object Module series of validations compilation from source is part of the module installation process. " I was

Re: FIPS Module 2.0 on OS-X 10.7.4 (Lion)

2012-08-30 Thread Steve Marquess
On 08/30/2012 02:02 PM, Jason Todd wrote: > I understand that its not validated. But if I understand correctly, I > can claim "vendor affirmed" if I can build it with no modifications (and > at least the canister builds with no modifications). Is this correct? Only if you are the vendor. In the ca

RE: need help on handshake failure

2012-08-30 Thread Dave Thompson
>From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar >Sent: Thursday, 30 August, 2012 02:04 >Also when i use s_client tool it just hangs with following output. >Any input on how to get full handshake dump? >... openssl s_client -connect ... -state -debug -msg >CONNECTED(0003) >S

RE: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Dave Thompson
>From: owner-openssl-us...@openssl.org On Behalf Of Mithun Kumar >Sent: Thursday, 30 August, 2012 08:32 >cryptlib.h >#ifdef OPENSSL_USE_APPLINK >#define BIO_FLAGS_UPLINK 0x8000 >#include "ms/uplink.h" >#endif >On Thu, Aug 30, 2012 at 6:00 PM, Mithun Kumar wrote: > i am extremely sorry. i

FIPS Module 2.0 on OS-X 10.7.4 (Lion)

2012-08-30 Thread Jason Todd
I understand that its not validated. But if I understand correctly, I can claim "vendor affirmed" if I can build it with no modifications (and at least the canister builds with no modifications). Is this correct?

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Mithun Kumar
Its in cryptlib.h #ifdef OPENSSL_USE_APPLINK #define BIO_FLAGS_UPLINK 0x8000 #include "ms/uplink.h" #endif On Thu, Aug 30, 2012 at 6:00 PM, Mithun Kumar wrote: > i am extremely sorry. its BIO_FLAGS_UPLINK flag. > > > > > On Thu, Aug 30, 2012 at 5:24 PM, Saurabh Pandya < > er.saurabhpan...

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Mithun Kumar
i am extremely sorry. its BIO_FLAGS_UPLINK flag. On Thu, Aug 30, 2012 at 5:24 PM, Saurabh Pandya wrote: > How do you identified that the dame flag is causing problem > > On Aug 30, 2012 4:49 PM, "Mithun Kumar" wrote: > > > > Thanks for the quick reply. > > > > I could see that following con

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Saurabh Pandya
How do you identified that the dame flag is causing problem On Aug 30, 2012 4:49 PM, "Mithun Kumar" wrote: > > Thanks for the quick reply. > > I could see that following condition compiler flag is used OPENSSL_USE_APPLINK causing the problem. Any idea why this flag is used? > > -mithun > > > On Th

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Mithun Kumar
Thanks for the quick reply. I could see that following condition compiler flag is used OPENSSL_USE_APPLINK causing the problem. Any idea why this flag is used? -mithun On Thu, Aug 30, 2012 at 3:58 PM, Saurabh Pandya wrote: > is as simple as below > > const *errString = ERR_error_string(ERR_get

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Saurabh Pandya
is as simple as below const *errString = ERR_error_string(ERR_get_error(), NULL)); On 8/30/12, Mithun Kumar wrote: > Hello All, > > I am using the function ERR_print_errors_fp() to get the last error in > case of any failure. I want to divert the output to file. When ever there > is a handshak

Re: crash when calling ERR_print_errors_fp()

2012-08-30 Thread Mithun Kumar
i could see following method failing.. uplink.c :19 static void unimplemented (void) { OPENSSL_showfatal (sizeof(TCHAR)==sizeof(char)?"%s\n":"%S\n",msg); ExitProcess (1);//causing crash } On Thu, Aug 30, 2012 at 3:25 PM, Mithun Kumar wrote: > Hello All, > > I am using the function ERR_pr

crash when calling ERR_print_errors_fp()

2012-08-30 Thread Mithun Kumar
Hello All, I am using the function ERR_print_errors_fp() to get the last error in case of any failure. I want to divert the output to file. When ever there is a handshake failure application crashes. If handshake is successful i don't see any crash. Any idea where things are going wrong. -mith

moving from EVP to BIO_f_cipher

2012-08-30 Thread Carolin Latze
Hi all since OpenSSL allows to do the encryption using the BIO API and since I need the BIO API anyways for the sockets I thought I rewrite my code to use the BIOs instead of EVPs. However I see some strange behavior. I create a cipher BIO on the server as follows: encbio = BIO_new(BIO_f_cipher()

Re: need help on handshake failure

2012-08-30 Thread Saurabh Pandya
use err = ERR_get_error(); to get error no and use ERR_string(ec) to stringify On 8/30/12, Mithun Kumar wrote: > Also when i use s_client tool it just hangs with following output. Any > input on how to get full handshake dump? > > > *vm-soniclx13(misingh): openssl s_client -connect NC-WI