Re: Broken port qmail-tls, upstream dead

2018-11-12 Thread Kurt Jaeger
Hi! > On 12.11.18 07:20, Kurt Jaeger wrote: > > > Which feature breaks ? > > Relaying after auth with client certs. The patch manually resets > openssl's ssl context state to trigger a second handshake after reneg > and those fields are now opaque in openssl. > > > Patches can be applied

Re: Broken port qmail-tls, upstream dead

2018-11-12 Thread Dirk Engling
On 12.11.18 07:20, Kurt Jaeger wrote: > Which feature breaks ? Relaying after auth with client certs. The patch manually resets openssl's ssl context state to trigger a second handshake after reneg and those fields are now opaque in openssl. > Patches can be applied conditionally (e.g. only for

Re: Broken port qmail-tls, upstream dead

2018-11-11 Thread Kurt Jaeger
Hi! > due to recent changes in openssl that comes with 12, qmail-tls and > derived ports don't build anymore. I fixed most of the compile issues > and submitted them upstream, but despite checking via several channels, > got no reply. > > If it was just for the ports-patch for the tls-patch, I

Re: Broken port qmail-tls, upstream dead

2018-11-11 Thread Nathan Owens via freebsd-ports
Is the error from older version of OpenSSL or platforms specific?  On Sunday, November 11, 2018, 5:02:16 PM CST, Dirk Engling wrote: Hey, due to recent changes in openssl that comes with 12, qmail-tls and derived ports don't build anymore. I fixed most of the compile issues and

Broken port qmail-tls, upstream dead

2018-11-11 Thread Dirk Engling
Hey, due to recent changes in openssl that comes with 12, qmail-tls and derived ports don't build anymore. I fixed most of the compile issues and submitted them upstream, but despite checking via several channels, got no reply. If it was just for the ports-patch for the tls-patch, I would just