Can't say the same when using AWeb, Voyager or even older versions of IBrowse on high-end Amigas, though.
#IBROWSE 2.4 O30 HOW TO#
Maybe this is now covered in AmiSSL 4.0 - but just in case it is not, I'd like to share this info with you on how to make IBrowse nevertheless access "http s -sites". Using IBrowse 2.4 on a high-end Amiga with gfx card (8Mb CVPPC or better) in some instances is more pleasant than using a PC under Win XP/Vista (even on decent spec machines with 1Gb ram and a bunch of essential apps installed). iBrowse (4 bytes): A 32-bit unsigned integer. This field MUST be set to 0x00000000 to indicate that there is no right child node.
The right child MUST sort to the same value as the current node or greater. Unfortunately I missed the news last year - and so I have not tested it up to now (And yes, I'm one of those infamous users "who are really still occasionally using IBrowse to surf the web"). oGT (4 bytes): A 32-bit unsigned integer that specifies the offset of the right RDN2REC child of the current node in the RDN Index file. At the end of this news item there is an 'editor's note':Įditor's note: Those who are really still occasionally using IBrowse to surf the web should enable TLS to improve IBrowse's compatibility with encrypted websites significantly - even without AmiSSL-4-support.Ĭlicking on the "enable TLS"-link led me to an old news item of Feb 2016, where the original message of the IBrowse-development-team with an instruction on how to enable TLS in IBrowse v2.4 was linked. Regarding the m68k version of AmiSSL 4.0, there was a news item at on Feb 8th. Related to the recent release of AmiSSL 4.0 for AmigaOS 3.x/4.x, I stumbled across an instruction on how to enable TLS in IBrowse v2.4 and making it a bit more usable today by that.
0 kommentar(er)
