[antispam-f] Re: SecureSockets
- From: Harriet Bazley <lists@xxxxxxxxxxxxxxxxxx>
- To: antispam@xxxxxxxxxxxxx
- Date: Fri, 08 Feb 2019 10:13:33 GMT
On 8 Feb 2019 as I do recall,
Frank de Bruijn wrote:
In article <578301fac0antispam@xxxxxxxxx>,
Frank de Bruijn <antispam@xxxxxxxxx> wrote:
In article <8297dc8257.harriet@xxxxxxxxxxxxxxxx>,
Harriet Bazley <lists@xxxxxxxxxxxxxxxxxx> wrote:
On 7 Feb 2019 as I do recall,
Frank de Bruijn wrote:
This is with the module already loaded?
Apparently, although I'm not sure what's loading it if not AntiSpam.
That could mean AntiSpam loads the module and then the version check
fails, but...
*help securesockets
==> Help on keyword SecureSockets
Module is: SecureSockets 1.04 (26 Nov 2005)
...this means it shouldn't.
All of this is happening on an Iyonix, right? So the OS version number
should be 5.xx. I'll check things in a RISC OS 5 RPCEmu later today.
Considering the version check code was written when I still used my
Iyonix I doubt it will make any difference, but who knows?
Nope. No difference. Module is loaded by AntiSpam, no errors.
I'm stumped.
Let's go back a bit. You wrote earlier that version 1.67 was OK until
you rebooted. So what happens when you load the module manually by
double clicking the file and then run AntiSpam?
No difference. It doesn't work until I 'load' the module from within
AntiSpam by clicking on the 'Module' button. Whereupon...
Module is: SecureSockets 1.04 (26 Nov 2005)
Yep, still same version in memory, apparently.
However, if I then do a 'Quit and restart' from AntiSpam's menu, it
registers the presence of the module correctly when it reloads. And I
don't see how it can be preserving the contents of its own memory
(unless maybe it is? Maybe it's the old bugbear of fragments of data
persisting in uninitialised Wimpslot space when a program is quit and
then rerun?)
Also, where is the module file stored on that machine and what's its
name?
There are several versions of the SecureSockets module within Hermes,
although I don't know for certain that this is where the module is being
loaded from: <Hermes$Dir>.Resources.Secure (v1.01),
<Hermes$Dir>.Resources.Secure32 (v1.03), and
<Hermes$Dir>.Resources.SecureG (v1.04). It was the latter that is
loaded by <Hermes$Dir>.NewSecure and which I tried double-clicking on
manually.
I can imagine that the anomalous filename may well be causing problems,
since <Hermes$Dir>.Resources.Secure is *not* going to satisfy the
conditions of an RMEnsure... but I can't see in that case how
SecureSockets 1.05 is nonetheless getting loaded and yet not being
recognised as present when AntiSpam checks for it.
There doesn't seem to be a version of the module within !Messenger or
!NewsDir. There's another copy of !Hermes within !DialUp with the same
internal structure including the multiple copies of the module, although
DialUp is no longer being booted or run. There doesn't seem to be one
inside WebsterXL or System:Modules, so I assume it *must* be coming from
Hermes, which is booted but not run on start-up.
!Hermes.!Boot doesn't seem to load anything....
--
Harriet Bazley == Loyaulte me lie ==
He who hesitates is last.
Other related posts:
