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

[Till Toenshoff <till@xxxxxxxxxxxxx>]

> On 10. Sep 2018, at 01:13, Azat Khuzhin <a3at.mail@xxxxxxxxx> wrote:
> 
>> ```
>> docker run -it docker.io/tillt/mesos-debug-libevent-ubuntu18:version1 /root/mesos/build/3rdparty/libprocess/libprocess-tests --gtest_filter="SSLTest.SSLSocket" --verbose
>> ```
> 
> That is great!
> 
>> Any help debugging further into this issue is highly welcome.
> 
> Can you bisect libevent to see the specific commit/commits which breaks
> this? Plus I'm looking into this too and will get back once I will find
> something.
> 

The offending commit is:
```
f4b6284b8393dbabf389ddce734a30f4cdeffa17 is the first bad commit
commit f4b6284b8393dbabf389ddce734a30f4cdeffa17
Author: Azat Khuzhin <a3at.mail@xxxxxxxxx>
Date:   Thu Nov 5 17:40:25 2015 +0300

    be_openssl: don't add events during bev creation (like be_sock)

    Using the following examples you can get changes between be_openssl and
    be_sock:
    $ function diff_addr()
    {
        eval diff -u $(printf "<(strip_addr %s) " "$@")
    }
    $ function strip_addr()
    {
        sed 's/0x[a-zA-Z0-9]*/0xFFFF/g' "$@"
    }
    $ EVENT_DEBUG_LOGGING_ALL= regress --verbose --no-fork +http/https_connection_retry 2> /tmp/https-retry.log >&2
    $ EVENT_DEBUG_LOGGING_ALL= regress --verbose --no-fork +http/connection_retry 2> /tmp/http-retry.log >&2
    $ diff_addr /tmp/http-retry.log /tmp/https-retry.log

:100644 100644 4afdde27b2ab63cb92de31922688e77d97fc037b 7d469bfad00806fb4f124e55619bfa59813b09f6 M	bufferevent_openssl.c
bisect run success
```

Will also look closer at that….

Thanks for your help!
Till


***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.