Re: TLS connect error: "an EOF was observed that violates the protocol"

Hi Alex,

On Tue, Aug 27, 2024 at 09:56:46PM +0200, [email protected] wrote:
>Hi Rodrigo,
>
>On Tue, 27 Aug 2024 20:19:32 +0200
>Rodrigo Arias <[email protected]> wrote:
>
>> >1) socks5 proxy on 127.0.0.1:8080 not working.
>>
>> There is currently no support for socks5 proxies, only HTTP proxies
>> are supported.
>
>Thanks for confirming, the docs are not really clear on that.
>Could be a nice feature for the future :)

Yeah, unfortunately I only have two hands :-)

>> >dillo-dev.auriga.wearlab.narkive.com:443
>> >
>> >Is this site just broken/misconfigured?
>>
>> Cannot reproduce with LibreSSL 3.9.2 on Linux.
>> ...
>> Can you test with the latest LibreSSL 3.9.2?
>>
>> Is this it happening with the proxy enabled? Also, which user agent
>> are you using in curl and Dillo?
>
>It happens with the stock user agent and no proxy, same with curl. I'm
>running the latest snapshot of OpenBSD, which would have the latest
>version of LibreSSL.
>
>I don't care about that site, my only worry is that the error can crash
>Dillo.

If it happens it is a bug on Dillo side as it is not handling all 
errors, regardless of the site. I would like to reproduce it to fix it.

>This could be an OpenBSD specific issue which wouldn't show up on 
>Linux. Maybe this is a similar issue:
>https://github.com/mitmproxy/mitmproxy/issues/7128

It could be, but I would first reject that is not due to mismatch of 
versions.

The last LibreSSL as per https://www.libressl.org/ is:

> The latest stable release is 3.9.2

Which should be printed in the first lines when starting Dillo:

> TLS library: LibreSSL 3.9.2

If it says 3.9.0, then Dillo is not using the last release.

I can try installing 3.9.0 and see if I can reproduce it with that one.

Best,
Rodrigo.
_______________________________________________
Dillo-dev mailing list -- dillo-dev-lx9mn2B4QYRWk0Htik3J/[email protected]
To unsubscribe send an email to dillo-dev-leave-lx9mn2B4QYRWk0Htik3J/[email protected]