Re: [openssl-users] session resumption tls1.2/tls1.3

2017-07-31 Thread Matt Caswell
On 31/07/17 20:37, Neetish Pathak wrote: > On 26/07/17 00:05, Neetish Pathak wrote: > >> *Pseudocode for server* > >> * > >> * > >> tcp_accept > >> * > >> * > >> read_early{ > >> > >> if(read_early_success){ > >>

[openssl-users] OpenSSL on windows

2017-07-31 Thread amritha thorath
Hi I'm trying to run amy application with OpenSSL libraries. I've generated fipscanister.lib, ssleay32.lib and libeayfips32.lib. In my code I'm making a call to FIPS_rsa_sign(). The test crashes when the control hits this function. But the same code runs successfully on Linux. -- Thanks... -- op

Re: [openssl-users] session resumption tls1.2/tls1.3

2017-07-31 Thread Neetish Pathak
On Mon, Jul 31, 2017 at 9:43 AM, Matt Caswell wrote: > Apologies for the delayed response - I've been away on holiday. Comments > inserted below. > No problem thanks for the replies > > Matt > > > On 26/07/17 00:05, Neetish Pathak wrote: > >> *Pseudocode for server* > >> * > >> * >

Re: [openssl-users] openssl 1.0 and 1.1 co-exist

2017-07-31 Thread Ken Goldman
On 6/22/2017 7:05 AM, Jakob Bohm wrote: On 22/06/2017 04:31, Viktor Dukhovni wrote: On Wed, Jun 21, 2017 at 01:44:34PM -0400, Ken Goldman wrote: This is probably Linux specific ... Can both openssl versions co-exist on the same platform. I know that the .so is versioned, but how about the

Re: [openssl-users] session resumption tls1.2/tls1.3

2017-07-31 Thread Matt Caswell
On 31/07/17 17:43, Matt Caswell wrote: > It could be the NewSessionTicket message going from the server to the > client. But if so that is a little strange. The NST message is only sent > after the handshake is complete (so no more early data is possible). At > this point SSL_read_early_data() sh

Re: [openssl-users] session resumption tls1.2/tls1.3

2017-07-31 Thread Matt Caswell
Apologies for the delayed response - I've been away on holiday. Comments inserted below. Matt On 26/07/17 00:05, Neetish Pathak wrote: >> *Pseudocode for server* >> * >> * >> tcp_accept >> * >> * >> read_early{ >> >> if(read_early_success){ >> w

Re: [openssl-users] Openssl 1.1 RSA_get0_key() documentation -> needs-cla

2017-07-31 Thread Matt Caswell
On 31/07/17 15:31, Kenneth Goldman wrote: > "openssl-users" wrote on 07/31/2017 > 09:20:59 AM: > >> From: Matt Caswell >> To: openssl-users@openssl.org >> Date: 07/31/2017 09:21 AM >> >> Click "New Issue" on this page: >> >> https://github.com/openssl/openssl/issues >> >> You'll need a github

Re: [openssl-users] Openssl 1.1 RSA_get0_key() documentation -> needs-cla

2017-07-31 Thread Kenneth Goldman
"openssl-users" wrote on 07/31/2017 09:20:59 AM: > From: Matt Caswell > To: openssl-users@openssl.org > Date: 07/31/2017 09:21 AM > > Click "New Issue" on this page: > > https://github.com/openssl/openssl/issues > > You'll need a github user id. > > > > > I'd also be willing to help with d

Re: [openssl-users] Openssl 1.1 RSA_get0_key() documentation

2017-07-31 Thread Matt Caswell
On 28/07/17 21:15, Ken Goldman wrote: > On 7/28/2017 4:05 PM, Salz, Rich via openssl-users wrote: >>> The __current__ code for this function returns values if the **BIGNUM is >>> not NULL. Thus, it appears safe to pass in NULL for values not needed. >> >>> >>> If this behavior is guaranteed, it