Re: [exim] expansion error in OAuth2 client authenticator

Top Page
Delete this message
Reply to this message
Author: Victor Ustugov
Date:  
To: Jeremy Harris via Exim-users
Subject: Re: [exim] expansion error in OAuth2 client authenticator
Victor Ustugov via Exim-users wrote on 12.03.2023 23:32:

>>>>> Is it possible to use SNI with ${readsocket?
>>>> No.
>>>
>>> Do you plan to implement this functionality?
>>
>> It's not currently on the radar.  Glancing round the
>> code, it could be implemented with a bit of a hack.
>> Choosing a syntax would also be needed.
>>
>> How badly do you need it?
>
> The cause of the problem that I encountered when updating the OAuth2
> access token turned out to be not in the making of HTTPS requests to
> non-default virtual hosts. Therefore, the implementation of SNI has
> become non-critical for me.


Rather, the lack of SNI support does not prevent me from getting
response to access token refresh request. But Exim puts certificate
verification error message into the logs.


> In any case, I would get around the problem by proxying requests through
> the nearest nginh.
>
>> Testing is an issue.  I think you mentioned building
>> a FreeBSD port for yourself;
>
> Yes
>
>> does that mean you
>> could take a patch and test that?
>
> Yes, of course.


--
Best wishes Victor Ustugov
mailto:victor@corvax.kiev.ua
public GnuPG/PGP key: https://victor.corvax.kiev.ua/corvax.asc