Odyssey 1.23 progress: r5 RC2

@kas1e

HERO!!!

thanks for all the hard work!

@kas1e

testing...


I do have a question regarding picture loading and displaying.
This seems to eat away all the cpu power )not only with this release, but with all the versions)...couldn't that be done by the gpu?

Or at least with some ppc power, like the ak-datatypes?

@Raziel
Sure all kinds of optimization can be done :) Just need developers who will works on :)

@kas1e

I have a Synology NAS and it brings up the same SSL error samo79 is getting

Unable to open 'https://xxx.xxx.xxx.xxx:5001/'.
Error 60: SSL peer certificate or SH remote key was not OK.

This was with earlier version and this new one.

It works fine with Windows and Android.

@Raziel
Unpacked to the new place fresh unarchive, etc ?

If that never works maybe that depends on core changes or something ...

@Raziel

Same issue here with my Synolosy NAS when connection to https on port 5001.

@Skateman
And that was the same and before with other betas?

@kas1e

My guess is that this has been a problem for quite a while already.
I just Fired up the Beta7 and the same issue is present.

I can acces the NAS by HTTP on the local network as well so for me this is not a big issue.

Still testing a bit, but unfortunely my mailer doesn't work even with the new beta release ...

Got also a strange new moment while browsing:

newlib.library error

exit() of process 132 called from wrong process 409, using IExec->RemTask(NULL).

Process: "[OWB] MediaPlayer"


BTW, the italian catalog was obsolete, here the latest one to put in final archive

https://dropmefiles.com/Dlelu

@kas1e

The Synology problem was with older revisions as well, not a new problem.

https://www.hvsc.c64.org
stopped working with the new beta, i only get a grey screen

edit: Bah!
Nevermind, they perfectly timed their site change, doesn't work with the old version either anymore...

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)