> On Feb 19, 2019, at 10:50 AM, A. Schulze <s...@andreasschulze.de> wrote:
>
>>> Feb 19 13:28:53 spider postfix/tlsproxy[1061]: warning: No server certs
>>> available. TLS can't be enabled
>>
>> For me, applying the patch
>> made the segfaults in a certificateless proxy configuration
>> go away.
>
> indeed, my fault / I falsely assumed the autoupdater did it's job.
> The tlsproxy start without noise in certificateless configuration.
Thanks. Mind you I still see the "TLS can't be enabled message" logged
at proxy startup, but what it means is that *server-side* TLS is not
available, the client side still works. I've not tested what happens
with server-side operation in that case, does it refuse service, or
try and fail in some manner?
--
Viktor.
