@primax

The player doesn't actually know what qualities are available, so that'd be hard to do.

If you've been stuck at 'You have been blocked' when trying to log in to PayPal, try changing the User Agent to Samsung Smart TV.

Wayfarer 11.2 is now out!

- Avoid opening an extra window when launched via OpenURL/commandline url
- Fixed text caret not reappearing upon reactivating the window
- Fixed enter key not scrolling contents in multiline text editing fields
- Reduced binary size by a few MB

Quote:

Splendid. Thanks Jaca

Work on Wayfarer 12 ongoing.

@ jacadcaps - You THE MAN !! . . . and Piru and of course the betatesters !!

Where would MorphOS be without a modern WebBrowser, that's regularly updated?

Not forgetting the Morph OS itself, supported by the Development Team, also being regularly updated.

Quote:

Thanks especially for that. Not crucial for surviving literally, but one of those little improvements that show how matured and well maintained the whole thing is. Thumbs up!

@jacadcaps,

I have tried Saturday and also yesterday to on https://www.agirc-arrco.fr/ . It is the site of a supplementary pension fund here in France. But I obtain this error ssl when loading the page.

Erreur SSL lors du chargement de agirc-arcco.fr
35:SSL connect error

I thought and expected to find in the preferences/settings to tick a case to ignore those ssl errors, like in Odyssey, but there is nothing. With some other sites I have the possibility to ignore ssl errors but not in this case.

So can you give me aqn explanation why do I obtain this ssl error ? Can you also investigate to solve this ssl error ?

Brumiga

I analyzed the TLS handshake with Wireshark and it seems that for some reason the server doesn't seem to be happy with the TCP ACK we send to TLS 1.3 "Hello Retry Request, Change Cipher Spec" message. The message we send it fully compliant and correct.

The server acts as if it hasn't received the ACK, it thus will think we are missing some data and keeps resending the "Hello Retry Request, Change Cipher Spec" payload again with PSH|ACK. Since we from our point of view have already received the data, we consider this message a spurious retransmission and drop the data. No matter what, the server doesn't seem to receive any of our packets attempting the recovery, and the attempts eventually fail and the connection closes. This results in error 35.

There'a another site that has similar issues:
https://www.s-pankki.fi

Only TLS 1.3 connections are affected. Downgrading the connection to TLS 1.2 makes it work.

There is no obvious explanation as to why this would happen. My best guess is that there is some "anti-DDoS" filter device between the server and us. When triggered by "unusual or odd" packet patterns, it completely ceases forwarding any further data towards the server. The server gets super confused and keeps asking us to reply, but since all further communication from us is discarded by the device, the connection will eventually be torn down, and error 35 returned.

Another option would be a buggy device that has a broken TLS 1.3 implementation.

I haven't been able to confirm this or pinpoint it to specific device or equipment.