AmiSSL under WinUAE

[Thomas]

Well, SnoopDOS says it tries to open AmiTCP:libs/usergroup.library. This certainly isn't present on WinUAE, but it happily runs without it. So just add an Assign AmiTCP: RAM: to your user-startup and you'll be fine.

Installing AmiTCP (without actually configuring it) will cure it, too, but it is much of an overkill just to get the assign into your startup script.

However you might want to install some programs from AmiTCP:bin like ping, traceroute and netstat and you might need the INet-Handler (TCP: device) for some programs. So installing AmiTCP (or Genesis) might not be a bad idea after all.

Bye,
Thomas

[Thomas]

:juggler: Well, usually I am called a walking library. :-D

[Thomas]

I recon this might be a non-starter, as the BSD socket emulation is unknown to anything within UAE.

I don't fully understand this sentence, but if you call me a beginner, you are wrong. I won't ever give an advice which I didn't try myself before.

AmiSSL runs well on WinUAE. It asks for AmiTCP, yes, but if you click on Cancel it continues as normal without problems. So assigning AmiTCP to an empty directory will remove the requester.

You can as well install Genesis or AmiTCP, so AmiSSL really finds what it is looking for. Of course you cannot configure it when using bsdsocker emulation. Just install it and leave it alone.

I can think of another reason why it does not work for you: AmiSSL V2 only works with IBrowse. If you want to use AWeb, you have to use AmiSSL V1.

Bye,
Thomas

[Thomas]

Then you did something wrong. It cannot ask you for AmiTCP, if you have an assign for AmiTCP. AmiTCP, not AmiSSL (AmiSSL is already assign by the installation. Don't change this).

I just tried it again: a fresh OS3.1 install, with AWeb and AmiSSL V1. When opening a https page, AmiSSL asks for AmiTCP once for each file downloaded. If AmiTCP is assigned to RAM:, it no longer asks but works without problems.

Bye,
Thomas