[Dxspider-support] Tons of russian spots

[Joaquin]

Hi,

Following Dirk's implementation of origin IP address logging in 
DXSpider, there are "users" who are using VPNs to mask their origin.
I propose to include in DXSpider the possibility to reject telnet 
connections from IPs that come from a "VPN blacklist".
As the software of the nodes is not updated frequently, an input filter 
should be included for the spots that come from other nodes and that 
their origin IP is on the "VPN blacklist".
An example of these lists can be seen at: 
https://github.com/X4BNet/lists_vpn

It might also be useful to have files with "badwords" in various 
languages. If the sysops could provide these "chains", thus reducing 
part of the garbage that floods the Internet.
If Dirk considers it appropriate, the management of these files could be 
delegated to trusted people, relieving him of this work.

I think that it is the closest thing that can be done at present, 
because just as not all nodes are updated, it is impossible for all 
nodes to request authentication when logging in. It is difficult to 
eliminate these madmen.

Regards.

Kin

Sysop EA3CV-2, EA4URE-2, 3, 5


El 31/08/2022 a las 11:01, Dirk Koopman via Dxspider-support escribió:
> DXSpider was written because, in the 1990s (yes, it's been going that 
> long), there was a situation where anybody could disconnect someone on 
> another node, at any time. And there was a (sub) command to do that 
> disconnection "silently", i.e. just as though the connection dropped. 
> A sysop could read another node's logs to see what someone "was up to" 
> and also interfere generally with that node as though he (and all 
> sysops were male) was in control.
>
> I make no apology for making that sort of thing difficult -> nearly 
> impossible. But I am open to adding code to allow something more 
> nuanced in the way of remote control. But I am constantly aware that 
> this could and, sadly, might well be abused.
>
> My UK 2p worth