I've noticed downloading and installing that latest cert file can make some sites like f.ex. Facebook not working any more. I switched back to some older version.
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
"sicky"'s problem sounds very much like mine, and we have about the same result after trying the suggested fixes. (I notice that the new curl-ca-bundle.crt is 11K shorter than the old one; could that cause other problems?)
One difference is that so far I can access my bank, and view and/or download recent activity, make transfers, etc. The only thing I know I can't do is look at my official monthly statement.
Hey, me too! Thanks, sicky (and Chris?). OT: I guess Essex is north of the Sussexes?
It was ChrisH in this thread (ANT member and friend) who pointed out where to find the working certificate.
And yes Essex is north of Sussex, Essex is on north bank of Thames and Sussex on South coast, ironically although I live in Essex currently in my caravan in East Sussex (Camber Sands) on a little holiday
SAM 460 with 2GB or RAM, 1000GB HD, 4 port SATA, DVDRW drive and Radeon HD 4650 GFX card.
It was ChrisH in this thread (ANT member and friend) who pointed out where to find the working certificate.
By golly, so it was! And the curiouser thing is, his fix is the one I tried and it didn't work then, but now does. I'm sure I had rebooted; maybe it had to be a complete machine reboot?
My daughter and grandsons live in Lewes, East Sussex. That's what made me wonder about Essex proper, although I should have noticed it when I visited them for three weeks in 1998.
By golly, so it was! And the curiouser thing is, his fix is the one I tried and it didn't work then, but now does. I'm sure I had rebooted; maybe it had to be a complete machine reboot?
I think that one was slightly different from one that was posted previously, the one installed now is the latest I believe!
SAM 460 with 2GB or RAM, 1000GB HD, 4 port SATA, DVDRW drive and Radeon HD 4650 GFX card.
I thought it was the new http://curl.haxx.se/ca/cacert.pem file I put in OWB/Resources as curl-ca-bundle.crt that had fixed my problem, but I was completely wrong!
For one thing, it turns out not to have been the 264046 byte August 30 file that I had there, but a 68545 old one that I'm not sure where I got.
It took me quite some time (I've become rather senile) to figure out what was up. It started when I discovered that I couldn't fix mui-owb on my AmigaOne with that same file that I thought had cured OWB 3.32. Then I found out that it wouldn't fix either mui-owb or OWB 3.32 on my SAM460.
In the process of trying to find one of the various curl-ca-bundle.crt files I had available on disk (the two mentioned above, plus a 225828 model from 2009-09-22 and the 370603 byte one from 2011-03-09 that I think I got from a URL earlier in this thread. *Everything* worked with OWB 3.32; none worked with mui-owb.
Then I found out that OWB 3.32 didn't need any curl-ca- file; I could still get my statement from my bank.
It turns out that I had taken the advice to put a file reading "1" and named WEBKIT_IGNORE_SSL_ERRORS in Env-Archive that had done the trick.
Unfortunately that doesn't effect mui-owb, but that's a different forum. In a few moments I will check whether it works on OWB on the SAM.
It took me quite some time (I've become rather senile) to figure out what was up. It started when I discovered that I couldn't fix mui-owb on my AmigaOne with that same file that I thought had cured OWB 3.32. Then I found out that it wouldn't fix either mui-owb or OWB 3.32 on my SAM460.
In the process of trying to find one of the various curl-ca-bundle.crt files I had available on disk (the two mentioned above, plus a 225828 model from 2009-09-22 and the 370603 byte one from 2011-03-09 that I think I got from a URL earlier in this thread. *Everything* worked with OWB 3.32; none worked with mui-owb.
Then I found out that OWB 3.32 didn't need any curl-ca- file; I could still get my statement from my bank.
It turns out that I had taken the advice to put a file reading "1" and named WEBKIT_IGNORE_SSL_ERRORS in Env-Archive that had done the trick.
Unfortunately that doesn't effect mui-owb, but that's a different forum. In a few moments I will check whether it works on OWB on the SAM.
It does, but more importantly I found the "Ignore SSL errors" in the muiowb configuration that you guys were all keeping secret from me and can now get my bank statements with muiowb on either machine!
kilaueabart wrote: In the process of trying to find one of the various curl-ca-bundle.crt files I had available on disk (the two mentioned above, plus a 225828 model from 2009-09-22 and the 370603 byte one from 2011-03-09 that I think I got from a URL earlier in this thread. *Everything* worked with OWB 3.32; none worked with mui-owb.
Then I found out that OWB 3.32 didn't need any curl-ca- file; I could still get my statement from my bank.
Are you sure you don't have another copy of (some version of) the file in DEVS:? OWB can read it from there as well.
kilaueabart wrote: [...] I found out that OWB 3.32 didn't need any curl-ca- file; I could still get my statement from my bank.
Are you sure you don't have another copy of (some version of) the file in DEVS:? OWB can read it from there as well.
Pretty sure. Unless it's disguised as AmiSSL/Certs.
One way I went wrong is I thought the bank was keeping me out because I didn't have the right certification and they thought I might be some kind of hacker. Now I realize that the browsers are trying to protect me from potential bad guys, and all I need to do is say, I don't need your protection right now. With the original OWB I have to tell Env-Archive; with muiowb, it's part of Preferences.