AmiSSL Released

[AMIGASYSTEM]

Originally Posted by Bruce Abbott

Sorry I got the version letter wrong. I do have 4.9 installed and it seems to be working fine with AmiGemini, but I haven't tried pasting links. Can you give an example of a link that fails?

I spoke with the author of AmiGemini and he confirmed that his software was developed with AmiSSL 4.9 and that it doesn't need old AmiSSL libraries.

Did some verification in my system and now it works fine "only" with AmiSSL 4.9. I have also started to the developer the error "OS3.2-DNS-lookup failed" that I have encountered with both AfA One and OS3.2, see screenshot

[AMIGASYSTEM]

There is always something to learn in life, excuse my ignorance

Thanks to the developer now everything works fine on AfA One, OS 3.2 and AROS One, see screenshot.


AmiGemini is not a web browser It does not support http:// or https:// It only supports gemini://

[Futaura]

Hope this doesn't confuse things too much, but I released AmiSSL 4.10 a short while ago - any application built for any previous AmiSSL 4.x version (with the exception of 4.3) will automatically be able to use this new release, once installed.

[AMIGASYSTEM]

Thank you very much for what you do !

[AMIGASYSTEM]

Update News AmiSSL v4.10

[rabidgerry]

Originally Posted by AMIGASYSTEM

If the volume is named DH0: it will not work Workbench:, unless you make an assignment

You can avoid any problems if you use SYS:

With SYS: you can change the name of the volume and everything will work.

So I often say DH0: but my DH0: when I created the hard drive got named Workbench.

The assign was created using the script, I did not create it manually.

The script took the name Workbench: not me. The reason it took the name Workbench: is because this is where I chose to install AmiSSL folder.

In my previous post I might have described the route of where I installed as DH0: but it is actually Workbench:

I still don't understand why this makes any difference? Because when I type DH0: into other paths in startup-sequence things work fine. I do not have to label them as Workbench:

Also if I type something into shell and type path as DH0: they also work.

So why would it make a difference if this assign used DH0: or Workbench: labels?

Can someone clarify?

Originally Posted by Futaura

The assign was correct if DH0 = Workbench, which most likely it does. The AmiSSL: assign should always point to the root install location - not the libs dir.


Any application compiled to use AmiSSL 4.0-4.2 or 4.4-4.8 will automatically use 4.9, as it is fully backwards compatible. Only applications that are built using the AmiSSL 4.3 SDK will need the library from 4.3 installed (hopefully, most have been compiled to use 4.4 or indeed an older version by now). There is no need for applications to require newer AmiSSL versions, unless they use newly added OpenSSL functions.

So you reckon (as I do) my assign is fine and does not need modified?

And I don't really need any older amissl_vxxx.library files?

Originally Posted by Futaura

Hope this doesn't confuse things too much, but I released AmiSSL 4.10 a short while ago - any application built for any previous AmiSSL 4.x version (with the exception of 4.3) will automatically be able to use this new release, once installed.

Ahhhhhhhh! Do I need to reinstall now? Not that it was working in the first place

[AMIGASYSTEM]

From a Shell or from Filemanager to access a certain volume you can use:

- Partition Name: Example DH0:, HD0: etc...
- Volume Name: Example DH0:, HD0: etc...
- SYS: Any Name Partition any name Volume(system).

If you have Partition Name DH0 and Volume Name DH0:
You cannot use Workbench:

If you have DH0 Partition and Workbench Name Volume :
You can use both DH0: or Workbench:

[rabidgerry]

Originally Posted by AMIGASYSTEM

From a Shell or from Filemanager to access a certain volume you can use:

- Partition Name: Example DH0:, HD0: etc...
- Volume Name: Example DH0:, HD0: etc...
- SYS: Any Name Partition any name Volume(system).

If you have Partition Name DH0 and Volume Name DH0:
You cannot use Workbench:

If you have DH0 Partition and Workbench Name Volume :
You can use both DH0: or Workbench:

Well I have the very last example you give. Partition was created as DH0.

Then when I formatted later on I named DH0: as Workbench:

[AMIGASYSTEM]

Ok then the Assigns are correct then.
On which Sites do you get the AmiSSL request?

[rabidgerry]

Originally Posted by AMIGASYSTEM

Ok then the Assigns are correct then.
On which Sites do you get the AmiSSL request?

Well I have a better idea, give me a site to try out?

What I experimented with was literally going to google, but it brought me to the http: version instead. Then from Google I typed in English Amiga board. When the search results appeared I clicked on the link and it then said I needed AmiSSL or MiamiSSL and a million messages saying I am going to an unsecured site blah blah blah.

Tried going to BBC website as well but not sure that even loaded.

I wouldn't rely on my Amiga for web browsing 100% but it would be nice to access websites unrestricted particularly for those that are of use to the Amiga. WHDload works and allows me to download new slaves etc but then that worked without AmiSSL.

[AMIGASYSTEM]

The messages you received don't say that you need AmiSSL installed, but they talk about protections, which is different, that is you can't access https sites, you can only access them if they have http access too.


So it's all normal with AWeb, if you want to access https sites you need a browser that supports this protocol, i.e. iBrowser or NetSurf.

[rabidgerry]

Originally Posted by AMIGASYSTEM

The messages you received don't say that you need AmiSSL installed, but they talk about protections, which is different, that is you can't access https sites, you can only access them if they have http access too.


So it's all normal with AWeb, if you want to access https sites you need a browser that supports this protocol, i.e. iBrowser or NetSurf.

No you are wrong about this the message clearly says I cannot access this site and I can proceed to an unsecured version and that I need AmiSSL or MiamiSSL installed.

I'll take a picture later and show you. AWeb must support https: as why does it give me the option to select those sites in the address bar?

[rabidgerry]

as you can see AWeb actually provides me with https: in the template so why wouldn't it support them?



and here it is mentioning AmiSSL in the message



So to me this suggest something is wrong with AmiSSL as I have it installed yet AWeb doesn't seem to know about it.

[AMIGASYSTEM]

Unfortunately my English by Google translator is not understandable.

aWeb is an "old" software and cannot predict what will be created in the future, and it is for this reason that it does not recognize and does not use the new versions of AmiSSL.

On some sites like "eab.abime.net" aWeb accesses despite the message because these sites have a double access with or without the "s" in http.

[Futaura]

Originally Posted by rabidgerry

So to me this suggest something is wrong with AmiSSL as I have it installed yet AWeb doesn't seem to know about it.

AWeb APL 3.4 really is quite ancient - I don't remember which AmiSSL version it uses, but it is probably v1 or v2. You can find these at http://www.heightanxiety.com/AmiSSL/ - install v1, followed by v2, then v3.6, 4.3 and 4.10 for a "complete" installation. However, as has been mentioned already, the majority of websites have shut down SSLv2, SSLv3 and TLSv1.0 access, meaning that AmiSSL v4 is a minimum requirement these days. I think there were some AWeb 3.5 versions that added AmSSL v3 support and 3.5.12 (OS4 only, IIRC) added support for AmiSSL v4.

In short, use IBrowse 2.5 instead

[Rotzloeffel]

Originally Posted by rabidgerry

So to me this suggest something is wrong with AmiSSL as I have it installed yet AWeb doesn't seem to know about it.

Check sys:LIBS IF THERE is an amisslmaster.library and delete it

[AMIGASYSTEM]

Originally Posted by Rotzloeffel

Check sys:LIBS IF THERE is an amisslmaster.library and delete it

I had already asked this to Rotzloeffel, post 108 and 109

http://eab.abime.net/showpost.php?p=...&postcount=108

http://eab.abime.net/showpost.php?p=...&postcount=109

[Futaura]

First post here using AmiSSL 4.11 (and IBrowse)

[AMIGASYSTEM]

How come the library included in AmiSSL 4.11 has the same name "amissl_v111l.library" and same file size as the AmiSSL 4.10 one?

[Futaura]

Originally Posted by AMIGASYSTEM

How come the library included in AmiSSL 4.11 has the same name "amissl_v111l.library" and same file size as the AmiSSL 4.10 one?

Same name because it is still using OpenSSL 1.1.1l - not the first time this has happened (this is still the latest 1.1.x version). Same size because it's just lucky, I guess . Well noticed though. Version number is different, of course.

There were not so many changes in the library code itself - switching from UNIT_VBLANK to UNIT_MICROHZ won't have changed the code size and the other entropy changes were relatively small in terms of code changes, although functionally different, but a little surprising the generated code didn't change size by at least a few bytes. Most of the code changes are in the AmiSSL:OpenSSL tool.