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

[Till Toenshoff <till@xxxxxxxxxxxxx>]

On 10. Sep 2018, at 02:58, Till Toenshoff <till@xxxxxxxxxxxxx> wrote:

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

The above bisect was done on macOS 10.14 - which works fine with Mesos l+ libevent 2.1.5 but breaks with libevent 2.1.8.

Will do the same bisect on Ubuntu 18.04 as well - just to be sure.

Till