[Dxspider-support] Tons of russian spots

Luigi Carlotto IK5ZUK ik5zuk at tiscali.it
Wed Aug 31 13:04:24 BST 2022


It would be nice to have a separate text log file where all the remote 
commands are logged and the "local sysop" - i.e. owner of the node - can 
check and monitorate the RCMDs clearly.

73 Luigi IK5ZUK

Il 31/08/2022 11:36, Dirk Koopman via Dxspider-support ha scritto:
> I suppose there is the "nuclear" option of partitioning the network. 
> Obviously I am (extremely) loath to do this, and it would require some 
> sort of "charter" or agreement for cluster nodes / sysops to be agreed 
> so that we can create a regularly updated set of nodes with similar 
> configurations that agree to work together.  I'm not (at all) certain 
> that such a partition would survive the users' voracious need for 
> spots, any spots - especially during contests. But something needs to 
> be done...
>
> Discuss - and - keep it gentle.
>
>
> On 31/08/2022 10:25, Luigi Carlotto IK5ZUK via Dxspider-support wrote:
>> Hi all,
>>
>> Thanks Dirk for your courtesy: assuming you add code to allow "remote 
>> control", at the moment we have another big problem because inside 
>> our cluster network a very large number of spider nodes are running a 
>> very old spider version... and unfortunately I don't see a way to 
>> "force" the owners of that nodes to update to the latest Spider's 
>> version.
>>
>> 73 Luigi IK5ZUK
>>
>> Il 31/08/2022 11:01, Dirk Koopman via Dxspider-support ha scritto:
>>> So: here we go...
>>>
>>> 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
>>>
>>> Dirk G1TLH
>>>
>>> On 31/08/2022 08:50, Danilo Brelih via Dxspider-support wrote:
>>>>
>>>>     Looks like some genius have modified skimmer software???
>>>>
>>>>
>>>> The dxcluster network is most vulnerable due to the 
>>>> unresponsiveness of some administrators so enabling registration on 
>>>> well maintained systems does not provide a permanent solution. 
>>>> dxcuster programs should be designed in such a way that it is 
>>>> possible to disconnect the malicious system remotely from the 
>>>> network with super user administrator rights. We are far from such 
>>>> a solution due to the facts described above and fight spammers to 
>>>> the best of our abilities.
>>>>
>>>> Dan S50U
>>>>
>>>>
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>>
>>>
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20220831/4a3f2535/attachment.htm>


More information about the Dxspider-support mailing list