Re: [openssl-users] Help with ssl error

On Tue, Apr 18, 2017 at 05:06:40PM +, Viktor Dukhovni wrote: > The ClientHello decodes via tshark as: > > [...] > Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) > Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) > Cipher

Re: [openssl-users] SSL_shutdown return error when close in init

On 19/04/2017 14:35, Salz, Rich via openssl-users wrote: The OpenSSL documentation makes it clear that you must keep calling the same asynchronous function with the same parameters until the async job has completed. Is there a way we can (relatively cheaply) check for that type of programming

Re: [openssl-users] Help with ssl error

Is there a way to enable one or both of those ciphers in OpenSSL? > On Apr 18, 2017, at 1:28 PM, Jason Schultz wrote: > > RSA_With_AES_128_CBC_SHA and RSA_With_3DES_EDE_CBC_SHA -- openssl-users mailing list To unsubscribe:

[openssl-users] Openssl

Hi, New to this list! I am using Openssl in a project that send large amounts of data in bursts from a windows 2008 server to an Ubuntu 16.04 client. It works well with low data rates (<1mbs) but when mean data rates hits around 2 mbs, things get ugly. I use blocking wrtite calls and my buffers

Re: [openssl-users] Network problems (not OpenSSL)

> On Apr 19, 2017, at 10:39 AM, Lasse Thorbro-Steenberg > wrote: > > Using Wireshark I can see the TCP window remains open, but after a few > seconds on 2mbs the server start fragmenting IP packets which completely > drops the throughput to around 1 mbs. > Data

Re: [openssl-users] openssl-users Digest, Vol 29, Issue 20

After some debugging (exactly as mentioned above) it appears that the cipher suite does not show up in the ClientHello using the s_client/s_server. I modified the cipher for testing to use 512 bits instead of 64 so that it is ranked highest. Error server side: SSL

Re: [openssl-users] Help with ssl error

> On Apr 19, 2017, at 12:48 PM, Joseph Southwell > wrote: > > Sorry we did do that. It just didn’t look different so I didn’t send it > (pasted below). I also have asked for help from the server admin but it is a > non English speaking country and they don’t seem to

Re: [openssl-users] Help with ssl error

Sorry we did do that. It just didn’t look different so I didn’t send it (pasted below). I also have asked for help from the server admin but it is a non English speaking country and they don’t seem to be interested in talking to me. I have another product supposedly using OpenSSL that is

Re: [openssl-users] SSL_shutdown return error when close in init

> The OpenSSL documentation makes it clear > that you must keep calling the same asynchronous function with the same > parameters until the async job has completed. Is there a way we can (relatively cheaply) check for that type of programming error and return an "in progress on another op"

Re: [openssl-users] Query regarding DTLS handshake

For those following this discussion Mahesh has created a github issue with much more detail (at least I am assuming this is the same issue): https://github.com/openssl/openssl/issues/3251 Matt On 18/04/17 21:17, Michael Tuexen wrote: >> On 13. Apr 2017, at 11:11, mahesh gs

[openssl-users] re-negotiated master key in s_client

I am using openssl command line client (s_client) and wireshark to identify the behaviour of a server that enforces secure renegotiation for client certificate verification. Since the Master-Key is printed along with SSL-Session information, I am able to use it in wireshark to decrypt the messages