[Dxspider-support] FYI: 4 new nodes added to ROS Auto-Spotting function.

Ron Stordahl N5IN ronn5in-dxspider at yahoo.com
Wed Jul 14 15:51:38 BST 2010


If Dirk allowed the 'parameters' to be set easily by the sysop then the 
offender(s) could be treated strictly or leniently.  I bet most would choose 
strict.  Yes it adds more complexity.

While I applaud Dirk for his ingenuity someday the whole issue of security needs 
to be addressed.  'Full' control through node passwords is not 'full' since 
connected nodes themselves might not enforce the same level of control.  The 
nodes would need to exchange control information, with connections between nodes 
refused if the level of control at the connecting node is judged insufficient. 


It is not easy..by analogy consider e-mail spam!  

Ron, N5IN




________________________________
From: Wayne <wa1pma at gmail.com>
To: The DXSpider Support list <dxspider-support at dxcluster.org>
Sent: Wed, July 14, 2010 9:22:35 AM
Subject: Re: [Dxspider-support] FYI: 4 new nodes added to ROS Auto-Spotting 
function.

Ok Dirk, you asked for it! <G>

I'm not sure why you would want to "play nice" with this kind of activity. It 
would seem you are only opening up a path for someone to try and create yet 
another workaround. I'm in favor of a "cripple mode"  being enacted by the 
repeated quick connect and disconnect action, however once in "cripple mode," It 
should not be automatic to come out of "cripple mode."

I think pretending to be nice sends a message that only leads to more conflict.

My best teachers in school demanded respect for their classroom and also 
enforced that policy. They in turn earned my respect.

73

Wayne  WA1PMA

On 7/14/2010 12:39 AM, Dirk Koopman wrote:
> On 12/07/10 21:51, VK3AMA wrote:
>> FYI
>> 
>> The latest release of ROS software has added 4 new nodes to
>> auto-spotting function.
>> 
>> BG2RVL-9 dx.5iyou.cn:7373
>> BD5RV dxc.jsdxc.net:7300
>> BA2IA-2 spot.ba2ia.com:7300
>> 9H1LO-1 dx.9h1lo.net:7300
>> 
>> At time of this email, of the last 150 ROS cluster spots,
>> 148 were auto-generated (98.7%).
>> 
> 
> If all major nodes were to do a "set/badword ros" then it probably does not 
>matter that he keeps adding to the list, as the spots won't propagate very far.
> 
> On an other tack: I have been wondering for a while what to do with all the 
>programs (of which the ROS stuff is but one) that insist on logging in, doing 
>one or two things (eg send a spot or sh/dx), then immediately logging out.
> 
> Now, the code already does not bother (in most cases) to send out routing 
>information for these in/out merchants, but I am now thinking that I ought 
>perhaps to be a bit more brutal.
> 
> It would be a fairly simple job to have some kind of averaging or pump up timer 
>that has the effect going into "cripple" mode if the last n connections were 
>less than m seconds long.
> 
> "Cripple" mode would something like pretending to be a nice cooperative cluster 
>that accepts spots, but does not send them on, and/or returns a *very* limited 
>view of data such as spots (maybe only two or three spots else spots that are an 
>hour or so old).
> 
> If the user starts to behave like a real person and connects p times for more 
>than m seconds, it automatically comes out of "cripple" mode. While in "cripple" 
>mode for more than (say) 2*m+random amount seconds then de-cripples that user 
>for that session. This behaviour persists until they have behaved for p 
>sessions.
> 
> "Misbehaviour" puts the user back into "cripple" mode.
> 
> Views anyone?
> 
> Dirk G1TLH
> 

_______________________________________________
Dxspider-support mailing list
Dxspider-support at dxcluster.org
http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20100714/073648a1/attachment.html>


More information about the Dxspider-support mailing list