Time to switch to HTTPS...

It would be a good idea to switch this forum to using HTTPS. That way, usernames and passwords would no longer be sent in plain text over insecure networks (like free wifi with no encryption).

You can get a free SSL certificate vial LetsEncrypt. Their service comes with a client to auto-renew (their certificates have a short validity period).

Hans

I made the same point already, privately

@Hans

Good idea.

Make it happen :)

This can be done easily. I only consider those who might have issues with their browsers.

Do you guys have issues visiting other websites with https?

@walkero

I would be amazed if anybody was using a browser that had trouble with HTTPS, given how prevalent it is now. Mind you I'm constantly amazed that people still use iBrowse, given it can't do CSS.

Not only do they use iBrowse, but some even prefer it! :)

Simon

@Rigo

Quote:

Yeah it's mystifying when AWeb is clearly superior


BUt more seriously, OWB iBrowse and AWeb all support SSL but may not support access to the latest https: based sites.

OWB and AWeb (my choices for browsing on my SAM) both fail to access some more "modern" https URLS, which is a pain, and I use Chrome under linux for those site, but that would be unfortuntate if they were amiga sites.

If it were possible to enable https without redirecting http to https, which many site now do, that would be my preference.

@broadblues

Yes, it's possible to have an HTTPS site that doesn't automatically redirect HTTP => HTTPS.

However...
- Ibrowse 2.5 was demo'd recently which supports the new AmiSSL 4.0. So I assume that would be able to handle modern SSL/TLS
- Voyager is now open-source (link), so it could be fixed if people really want to use it. The same goes for AWeb
- Classic 68K AmigaOS users could also use Netsurf (link)
- AmigaOS 4 users have Odyssey

Hans

@Hans

I know AWeb is Open src

I have an AmiSSL 4 build, but it currently has issues, memory related crashes in AmiSSL which so far elude understanding.

@Hans

Quote:

*ahem*

I use such an SSL at my other websites, like amiga.gr and I managed to make IBrowse read it just fine. The only problem was that it seems slower to get the data. I didn't manage to make AWeb to work though. Maybe it needs some more work to find where the problem is.

@walkero

Which version of iBrowse ? The version I have, ie. the standard public distribution does not work, it fails in exatly the same way as AWeb 3.5.10 but with an error requester, rather than AWebs silent fail.


AWeb 3.5.12 can access amiga.gr but crashes while fetching the images, always in the CRYPTO_free() function, I had some interaction with the amissl guys over this and we couldn't find the issue either in amissl or AWeb. I've given up for little while TBH, other coding comitments....

@broadblues
I use the IBrowse 2.4. I had to make the AmiSSL changes they recommend to their website and the TLS env variable set.
Also, if you check the Amikit installation, the IBrowse works fine, at least with the site I mentioned.

@Chris

Thanks for the correct NetSurf OS3.x link. I've corrected the link in my post.

Hans