What computer are you trying to run it on? When I try to run Timberwolf on my X5000, I get a DSI after a few seconds of the splash screen. I dismiss the DSI, and then instantly get an ISI. It used to run on my A1-XE. But no more here.
Paul
Builder of Frankenthousand The monster A1000 The Young Frankenthousand A1-XE G4 X5000
While I suspect there has to be a way to replace the certs, I wonder if the problem has more one to do with the various encryption algorthyms themselves...
It looks like the last builds of TW were in 2012 and we've gone through a lot of hacks/updates to SSL, etc. since then.
Like with Oddity, even if the old TW could be recompiled with new SSL (etc) components, it might open up a few things?
But the only people that can compile it are the Friedens AFAIK. I thought ssolie looked at trying to get it to compile, but ran out of time/energy. It's not an insignificant challenge.
What filesystem do you use on the partition where TW is located?
TW still works on all os4 systems that i have tested it on including X5k. iirc the public version of NGFS for X5000 did not work with TW so you better install it into a partition with sfs and then it should run.
First try was with NGFS. But I have a small partition with FFS which I tried it from too. I could switch that little partition to SFS and see if it helps.
Paul
Builder of Frankenthousand The monster A1000 The Young Frankenthousand A1-XE G4 X5000
I cant get ANY SSL support on amiga os4 fe now. Can anyone please help me? I installed the Amissl from os4 depot but I still get SSL/Cert errors. Its frustrating. I end up booting into Morphos and use Odyessey
I cant get ANY SSL support on amiga os4 fe now. Can anyone please help me? I installed the Amissl from os4 depot but I still get SSL/Cert errors. Its frustrating. I end up booting into Morphos and use Odyessey
I believe the problem you have is that you need to have applications that are NOT using the latest SSL (etc) algorithms.
After the Heartbeat (etc) security holes, all the security/encryption algorithms got updated. So you need to be running apps with new security code. That code is in the new AmiSSL 4.N versions.
AFAIK, the web apps that use that might only be IBrowse, AWeb, Netsurf, and the recent betas of Odyssey. An application written for the old AmiSSL3 will not benefit from the new AmiSSL4 code.
Obviously, a 2014-2016 build of Timberwolf, an old Oddity, etc. will not have the new HTTPS/SSL code and will barf when it hits a website requiring that code.