Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: beller on June 17, 2019, 05:34:18 AM
-
Getting iBrowse up and running again on my 3.1.4 systems. Installed AmiSSL 3.6 and 4 and I'm using Roadshow for my connection. All of the Amiga.org forums let me in without a problem but this form hangs with a complaint about the SSL certificates and locks me out....
Any fixes or does someone need to look at the certificate for the forum?
-
Back in the day you could only view this forum with IBrowse by using the proxy. Obviously that all changed with the site redesign. I'd be very surprised if it works at all, now...?
-
I am now logged on and am also using AmiSSL V3.6. The site actually works very well with the current version of iBrowse. There's a couple of configs that you might have to perform to get the cert to work correctly. There's an explanation of what to do over on the iBrowse site. I gotta get back out to the front of the house ATM, the stump grinding dudes are out there. ;-) Posted from my A2000.
BTW, the VersionWB program is the BOMB! It IS awesome! Thanks OM!
-
What TCP/IP stack are you using? I'm using RoadShow which looks like it might be the issue. They is no fix listed...
-
What TCP/IP stack are you using? I'm using RoadShow which looks like it might be the issue. They is no fix listed...
I'm using AmiTCP. Also, here's a link over to EAB that tells what to do to use the new AmiSSL 4.1 certificates. Read the whole thread as there is a good clarification 'cause someone was doing it wrong. LOL
http://eab.abime.net/showthread.php?t=90478
-
Thanks....I did that fix. I think it a conflict with Roadshow’w stack and iBrowse. How much longer until we get 2.5?
-
I'm still running AmiSSL 3.6 as I don't have any new programs to make use of version 4. I have Roadshow and IBrowse, so I'll try and log on Amiga.org tonight and see what happens.
-
Okay, I am actually typing this from my A1200, so it appears to be working fine for me. I have downloaded a photo attachment too from a different thread so all appears to be working here.
I'm using IBrowse 2.4 with Roadshow 1.13 and AmiSSL 3.6. I'm now going to attach a .iff screen grab to see if I can attach :)
I've found a rather good screen grabber called QuickGrab on aminet for this (so that I may attach proof!):
http://m68k.aminet.net/package/gfx/misc/QuickGrab1_1
Hopefully this post will come out okay without LF issues! If it doesn't, I do apologise for messing your screen up ;)
-
Working great! Now amiga.org... why couldn't I attach a good old Amiga IFF file? I had to convert it first via Personal Paint to PNG. Should I have just renamed it to a .txt file and then it would have uploaded? But if I did that it either would fail or create an unpleasant mess on someones screen... Any advice other than "convert to PNG or JPG"?
-
I forgot to mention that I'm using OS3.1...not 3.1.4!
I'm posting this from my mobile...not anywhere near as much fun! I used to use the amiga.org proxy when that was running but now since the site update the proxy isn't required anyway.
-
That may be the issue...I'm using 3.1.4
-
That may be the issue...I'm using 3.1.4
Are you certain that you have the env var set up correctly and IBrowse security configured correctly?
In IBrowse go to the Menu > Preferences > Settings...
Make sure both 'SSL v2 support' and 'SSLv3 support' are enabled
Save the settings.
There was some confusion about the setenv command as it differs between the OS3.9 version and OS3.1. The OS3.9 version can create directories in ENV: and the 3.1 version not. You can set it up manually though quite simply:
Create a new directory (drawer :) in ENVARC: called AmiSSL (ENVARC: lives in SYS:Prefs/Env-Archive)
Use your favourite text editor to create a text file containing four characters as follows (without quotes) : 'tls1'
Save this text file into your newly created AmiSSL directory with the filename 'SSL_CLIENT_VERSION' (without quoues)
So to summarise, in the path 'SYS:Prefs/Env-Archive/AmiSSL' there is a 4 byte file called 'SSL_CLIENT_VERSION' the content of which is 'tls1'.
That is it. You can now reboot and it should work. If you don't want to reboot just copy that AmiSSL drawer over to ENV: and restart IBrowse.
-
That may be the issue...I'm using 3.1.4
Are you certain that you have the env var set up correctly and IBrowse security configured correctly?
In IBrowse go to the Menu > Preferences > Settings...
Make sure both 'SSL v2 support' and 'SSLv3 support' are enabled
Save the settings.
There was some confusion about the setenv command as it differs between the OS3.9 version and OS3.1. The OS3.9 version can create directories in ENV: and the 3.1 version not. You can set it up manually though quite simply:
Create a new directory (drawer :) in ENVARC: called AmiSSL (ENVARC: lives in SYS:Prefs/Env-Archive)
Use your favourite text editor to create a text file containing four characters as follows (without quotes) : 'tls1'
Save this text file into your newly created AmiSSL directory with the filename 'SSL_CLIENT_VERSION' (without quoues)
So to summarise, in the path 'SYS:Prefs/Env-Archive/AmiSSL' there is a 4 byte file called 'SSL_CLIENT_VERSION' the content of which is 'tls1'.
That is it. You can now reboot and it should work. If you don't want to reboot just copy that AmiSSL drawer over to ENV: and restart IBrowse.
I was quite certain that I had completed all of the steps you list and i just confirmed that I had. I installed AmiSSL 4.3 on top of the previous installation....I'm still told the remote server is using an encryption protocol not supported by iBrowse.
-
I've just re-read your first post and it's hard to tell but did you install AmiSSL 4.3 because version 3.6 didn't work either? I haven't personally installed 4.3, but according to what I've read it shouldn't make a difference with IBrowse 2.4...either 3.6 or 4.3 should work.
-
The instructions I've seen called for installing AmiSSL 3.6 and then 4.3 I uninstalled and tried 3.6 alone and when it didn't work I reinstalled 4.3.
-
Lets double check it's working. Open a shell and type in:
getenv amissl/ssl_client_version
The result should be tls1
By the way, is this a clean 3.1.4 install you're running? Some env handlers are crappy, but I use env-handler 1.13 by Stephan Rupprecht and I've never had any bother. I don't know whether 3.1.4 actually comes with it's own env handler or not, but if it does then obviously stick with that one.
-
Lets double check it's working. Open a shell and type in:
getenv amissl/ssl_client_version
The result should be tls1
By the way, is this a clean 3.1.4 install you're running? Some env handlers are crappy, but I use env-handler 1.13 by Stephan Rupprecht and I've never had any bother. I don't know whether 3.1.4 actually comes with it's own env handler or not, but if it does then obviously stick with that one.
And the result.....tis1
-
Lets double check it's working. Open a shell and type in:
getenv amissl/ssl_client_version
The result should be tls1
By the way, is this a clean 3.1.4 install you're running? Some env handlers are crappy, but I use env-handler 1.13 by Stephan Rupprecht and I've never had any bother. I don't know whether 3.1.4 actually comes with it's own env handler or not, but if it does then obviously stick with that one.
And the result.....tis1
You mean tls1 yes and not tis1? TEE ELL ESS WON
-
Lets double check it's working. Open a shell and type in:
getenv amissl/ssl_client_version
The result should be tls1
By the way, is this a clean 3.1.4 install you're running? Some env handlers are crappy, but I use env-handler 1.13 by Stephan Rupprecht and I've never had any bother. I don't know whether 3.1.4 actually comes with it's own env handler or not, but if it does then obviously stick with that one.
And the result.....tis1
You mean tls1 yes and not tis1? TEE ELL ESS WON
Oh...yea...small type and old eyes...looked like an i and not an l! ha
-
Did you get this sorted then? If not then I forgot to mention for you to check that the AmiSSL assign exists. I can't really think of anything else at this point.
-
Did you get this sorted then? If not then I forgot to mention for you to check that the AmiSSL assign exists. I can't really think of anything else at this point.
I can get in the forum but not via a secure https connection. The typo was the overall issue...thanks for the help!