[Libevent-users] SSL problems after update to libeven 2.1.8

2018-01-22 Thread Alexander Rojas
/libprocess/src/libevent_ssl_socket.cpp#L1176 -- Alexander Rojas alexan...@mesosphere.io *** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-usersin the body.

Re: [Libevent-users] SSL problems after update to libeven 2.1.8

2018-01-24 Thread Alexander Rojas
Hi Azat, thanks for looking into this. On Mon, Jan 22, 2018 at 9:27 PM, Azat Khuzhin wrote: > On Mon, Jan 22, 2018 at 09:55:49AM +0100, Alexander Rojas wrote: > > Hey guys, > > > > Over the past couple of weeks I've been struggling with an old bug of >

Re: [Libevent-users] SSL problems after update to libeven 2.1.8

2018-01-29 Thread Alexander Rojas
On 24. Jan 2018, at 16:53, Azat Khuzhin wrote: On Wed, Jan 24, 2018 at 09:55:15AM +0100, Alexander Rojas wrote: I did the update, the problem changed from the accept to the recv call. While now it can `accept()` socket connections, the `recv` callback fails. I need to investigate further here

Re: [Libevent-users] SSL problems after update to libeven 2.1.8

2018-02-14 Thread Alexander Rojas
Hi Azat > On 4. Feb 2018, at 20:49, Azat Khuzhin wrote: > > Hi Alexander, > > Sorry for the delay, No problem, I have also been fixing other issues. Crunch time! > >> So far, yes > > Great. > >> NOTE: Set LIBPROCESS_SSL_REQUIRE_CERT=1 to require peer certificate >> verification > > Hm, mayb

Re: [Libevent-users] SSL problems after update to libeven 2.1.8

2018-02-14 Thread Alexander Rojas
> On 14. Feb 2018, at 16:52, Azat Khuzhin wrote: > > On Wed, Feb 14, 2018 at 04:33:07PM +0100, Alexander Rojas wrote: >> Really hard to achieve, I was playing around and failed to get a minimal >> reproducer. > > Maybe you have a container with all this stuff (+d

Re: [Libevent-users] SSL problems after update to libeven 2.1.8

2018-10-01 Thread Alexander Rojas
Thanks Azat! This was a great catch! Alexander Rojas alexan...@mesosphere.io > On 30. Sep 2018, at 23:52, Azat Khuzhin wrote: > > On Thu, Sep 13, 2018 at 03:05:41AM +0200, Till Toenshoff wrote: >>> On 10. Sep 2018, at 12:02, Azat Khuzhin wrote: