<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Gregor<br>
<br>
Is there any reason why you can't "simply<sup>*</sup>" use an
instance of DXSpider as your back end? I would be happy to help if
that would suit you. It is pretty secure (no known compromises of
the code itself, nor by some of the questionable data it is fed).
It was designed, from the ground up, to be a self standing
internet facing daemon. It (deliberately) does not run as root and
users are actively discouraged from trying to do so. Having said
that, it's written in pure perl, there are no hidden backdoors
that allows the daemon to spawn arbitrary processes (although
potentially "long running" DXSpider commands do spawn processes
that offload these time consuming things to another process(or)).
<br>
<br>
As I understood it, DB0SUE-7 used a heavily modified version of
the master branch as a back end, which is why I could never get
him to upgrade. <br>
<br>
Dirk G1TLH<br>
<br>
* for certain values of "simple" :-)<br>
<br>
On 05/02/2025 19:39, Gregor Surmann via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cd903835-a56d-c3e2-8a3c-6cd134d06006@funil.de">Hi Kin,
<br>
<br>
no, it's not a "caprice" to insert the IP in the PC61 message, but
that will requiere me to write a PC61 implementation here, instead
of simply using telnet. I am sure, that I've read the
documentation carefully, but have not seen any note about the IP
beeing so important.
<br>
<br>
The previous solution worked for over 10 years (probably somehow
13 years) as I used DB0SUE-7, no one said that there was multiple
callsigns with the same IP, and there were maybe 3 cases of abuse
in those years. Now all of a sudden it's a big problem, so I'm a
little bit surprised ;)
<br>
<br>
Regardless of that I will have to do it probably, so define the
webserver as node and insert PC61 from there, with valid user IP
(from the http request), but that may need a few days/weeks.
<br>
<br>
Btw., I understand what you mean, even with my (also) "broken"
English ;)
<br>
<br>
73 de Gregor, DO5SSB
<br>
<br>
<br>
On 05.02.25 20:23, Kin wrote:
<br>
<blockquote type="cite">Hi Gregor,
<br>
<br>
I read you and I have the impression that you think that putting
the real IP
<br>
is a caprice. I guess it's because of my bad English 🙁
<br>
Dirk has tried to endow the archaic AK1A protocol with some
functionalities
<br>
that help sysops, and therefore everyone, to detect problems, to
maintain
<br>
the network. This has allowed us to know that a certain
node/user is or is
<br>
not the cause of a problem, and therefore allows us to act to
solve it. When
<br>
data is missing, problems sometimes arise and hasty decisions
are made.
<br>
<br>
When one reads the discussions here over time (I recommend it),
one can be
<br>
amazed at what some humans are capable of doing out of boredom.
<br>
<br>
There are web frontends <a class="moz-txt-link-freetext" href="likehttps://webcluster.ure.es/">likehttps://webcluster.ure.es/</a> ,
<br>
<a class="moz-txt-link-freetext" href="https://www.dxheat.com/dxc/">https://www.dxheat.com/dxc/</a> <a class="moz-txt-link-freetext" href="orhttps://www.dxfuncluster.com/">orhttps://www.dxfuncluster.com/</a>
who are using
<br>
dxspider and had no problems attaching the user IP to the spots.
I don't
<br>
remember any of them objecting to problems when I explained the
reason for
<br>
adding the real address.
<br>
Even one of them I know works with HA and it works great.
<br>
<br>
Regards,
<br>
<br>
Kin EA3CV
<br>
<br>
</blockquote>
<br>
<br>
_______________________________________________
<br>
Dxspider-support mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<br>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
<br>
</blockquote>
<br>
</body>
</html>