[Dxspider-support] Bad IP

[Gregor Surmann]

Dirk, with all due respect, I don't think I would need any "recalibration", 
as I am successfully working in networking for 30 years now. However, I have 
a fully equipped HF laboratory up to many GHz, so I could surely do it if 
needed ;)

I have a valid reason here to use the xinetd, besided the listen socket, as 
this node (after the old DB0SUE-7 failed) is used for registered and checked 
users of a free website to allow them to spot, as I used to do on DB0SUE-7 
for the last 12 years or so.

I will act immediately, if any bad spots will occure, and I don't think, 
that this may be a problem. Many sites do that, like dxheat.com for example.

I mean, I could change the setup to be unnecessarily complicated, only to 
show the "real" IP of the users (from webserver), for the solely purpose of 
beeing there in the cluster messages, but this would be additional work, 
which I would like to avoid.

There were no bad spots in the last 12 years, so please, please, with sugar 
on top, have a little confidence that I know what I'm doing ;)

Over the last 30 years I have contributed quite a lot to the Internet for 
free and at my own expense. This node is also a part of it. I respect 
protocols, RFCs, etc. but sometimes one need to "bend" it slightly to 
achieve a goal more easily.

best regards

73 de Gregor, DO5SSB



On 05.02.25 17:51, Dirk Koopman via Dxspider-support wrote:
> (x)inet(d) a secure system??
> 
> xinet (and all similar systems various) has been deprecated as a (potential) 
> security nightmare for at least the last 30 years (yes I am that old, and 
> more).
> 
> The only reason continued to include the client program is for dealing with 
> things like raw ax25 connections.
> 
> Please recalibrate this sysop.
> 
> 73 Dirk