Odyssey 1.23 progress: r5 RC2

Thanks Roman for preparing this new release.
If you want you caninclude my github script from https://git.walkero.gr/walkero/odyssey-scripts in the next release.

Also, I wanted to ask, do we have access to latest code releases from MorphOS Odyssey?

@George
Yep will add your script.

As for sources: the last one we have was 1.23. Then there were just 1.24 updates (small one) and that all. All other stuff was done by morphos-team devs but nothing really interesting like core updates.

But after a while, DeadWood made 1.25 for AROS which has 1 year better WebKit core than in our and morphos latest versions of Odyssey. As samo79 points out on the thread i already made a year or two ago port of 1.25 but it just crashes and i don't spend time on fixing this.

@kas1e

Is it possible to use RadeonRX Video decoder with Odyssey ?

@Sinan
Everything possible is just not easy enough to be a simple task.

@Raziel, Skateman

Quote:

Did it work at all before with any version?

Also, do any of you have some test link with 5051 on the web which brings that error so i can play a bit with it to see if it core issues or openssl one.

@kas1e

PM send

@kas1e

I don't have the NAS that long, but as long as I own it, it never worked

@Skateman
Ok tried from win32 and from the odyssey: from odyssey yeah, as you say. From windows through (chrome) I have that:

Error, your connection is not secure. NET::ERR_CERT_AUTHORITY_INVALID

It also said "Your operation system does not trust server's cert. Seems the server configured wrong, or someone try to steal data. want to continue the nonsecure version ?"

So i can only access it if the choice "continues unsecure".

Probably we first need to understand why it happens on my Chrome (so will be easy to understand details), and that will help to understand why it happens in Odyssey as well

EDIT: maybe its something about "Trust to a Self-Signed Certificates" ?

@kas1e

The Certificate on the Synology is a self signed Cert. (not backed by any Certificate Authority)

Thats why the Security error shows up. You can continue based on the Self signed Cert. Thats what the error is telling.

If you continue you will be shown the Synology login screen.

(if i am correct )

@Skateman
Yeah, but then that mean Odyssey didn't support self-signed certs or didn't support functionality to continue to the self-signed certs ?

I tested now with IBrowse , as Oliver made a lot of work to the security in ibrowse. So when i first time go to page, i have:

Quote:

And i can click on the "proceed" button and while ibrowse didn't read a shit mostly, i still can see that i come to the login page.

Now, main questions:

Do we have the functionality to "continue insecurity" in the Odyssey at all? I never ever seen anything of that sort of window in Odyssey, so I assume that not (or even if WebKit has it, it didn't handled by Odyssey)

@kas1e

I am not sure how Odyssey handles CERTs that are self signed, so cannot be validated at any Cert Authority..

Even if less secury based on the self signed Cert.. its still encrypted HTTPS traffic based on that Cert.

Good question.....

@Skateman
In netsurf it is also handled as in ibrowse. Through without nice window and just render information in the browsers window with CSS button "procced" but also can handle it.

What we need now is to find where in Odyssey's to handle return error, so if we will have "SSL peer certificate or SSH remote key was not OK" error, then add code to bring nice mui window with buttons "continue unsafe" / "abort".


This error "SSL peer bablalba" is coming from LibCurl. So at least all the connections happen to be with Curl, and all we need is to search on world "curl" in all the Odyssey's sources to find out where those errors checks happen.

@kas1e

Looks like similair issues: https://stackoverflow.com/questions/27 ... certificates-in-wkwebview

But i cant help with coding stuff .... sorry ..

@Skateman




So I can just add this functionality to just "ignore SSL errors" by default. Or create a new option in the security tab with "allow self-signed certs" (which IMHO better). Later for the next releases, we can make a proper mui window with process/about maybe, etc. But not sure maybe just an option in prefs/security will be enough?

@kas1e

I would opt for the Allow Self Signed Certs as an option in the security tab.

Great work !!

@Skateman




Only left to add proper CD/locale stuff (for now that just English only string)

@kas1e
Quote:
Thanks for the new update. Testing now. So far it's working well.

Quote:
I've found that if I spoof as ipad 13.2.3 it works but if you scroll to the bottom of the page automatic loading of more videos does not work. If I spoof as ipad 6.1 then the automatic loading of new videos when I scroll to the bottom of the page works as it should.

I'd recommend spoofing as ipad 6.1 in step 2 above.
Does anyone see different behaviour?

@Breed

Worked for me here just fine...

@kas1e

Excellent.. hope this could help with my isp too

If later you need to add/adjust strings in CD, well there are almost other 6 missed:


1) "Trasferred a partial file" --> in download window

2) "Download failed" --> in download window

3) "Save As..." --> in asl requester title when saving something

4) "link URL" --> in mime type prefs

5) "generated local path" --> in mime type prefs

6) "ODYSSEY REXX port" --> in mime type prefs

@kas1e

Looking good!! (some form of a security waring would be in place just like most browsers will give when visiting self signed cert websites)

A text/string close to the checkmark would do fine.