Well I can certainly give you my opinion :)<div>I run registration on both the clusters I admin. I do not have a mandatory password policy as it only counts for the one cluster anyway. It is also a LOT of work for the sysop. Please do consider registration though as it really does help the network. I feel this will become more and more important in the years to come and we need to get ahead of it now!</div>
<div><br></div><div>Dirk, could you make it possible to export a list of registered users please in case of crash etc? It would be a really useful addition.</div><div><br></div><div>73 Ian</div><div><br></div><div>-- <br>
Ian J Maude, G0VGS<br>SysOp GB7MBC & HB9DRV-9 DX Clusters<br>Member RSGB, GQRP 9838, FISTS 14077 | K3 #455<br><a href="http://www.amateurradiotraining.org" target="_blank">http://www.amateurradiotraining.org</a> <br>
<br></div><div><br><div class="gmail_quote">2009/10/25 Luigi Carlotto, IK5ZUK <span dir="ltr"><<a href="mailto:ik5zuk@tiscali.it">ik5zuk@tiscali.it</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Wolfram, hi all.<br>
I'm totally agree with you, Wolfram.<br>
<br>
In order to discourage any improper use, at my cluster I've enabled the registration (set/var $main::regreq = 1) and for any registered call I've set (manually) a password. This is the better way, IMHO, because my node is open for everybody via internet in "passive" mode, and to become active is needed the registration by the sysop and a password.<br>
<br>
It should be nice to share the password database using a new PC protocol sting, but this solution hasn't an high level security.<br>
Another solution may be to have a remote password database, stored in one (two or three for redundancy) server reachable via internet, so that spider can aks/verify to those servers the password for the user's connection... but in this way if the servers are not reachable, the cluster network became unopened to any connection.<br>
<br>
Another problem to this question, is that today we can see in our network some spider nodes still running a very old release... and it is very important that all nodes, with no exceptions, runs a new release and with the same policy !<br>
<br>
Here in Italy we have a Yahoo! group (<a href="http://groups.yahoo.com/group/retedxcitalia" target="_blank">http://groups.yahoo.com/group/retedxcitalia</a>) in order to coordinate the job for all the italian sysops, but I must admit that we have discussed this problem some times and since today we haven't obtained a single policy to apply to our cluster nodes, due to diverging opinions... And we are only a little number in comparison to the total cluster nodes spreaded across the world !<br>
<br>
Dirk, please, could you tell us your opinion ?!?<br>
<br>
73 de Luigi, ik5zuk<div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello<br>
<br>
at the last time are more and more "black-user" (improper use) in the<br>
cluster-net with any spam and false spots...<br>
Badspotter, badwords or badnodes are a posssibility. But the calls are<br>
imaginative or they use simple a existing call....<br>
<br>
The problem is that the clusternet via internet is open for everybody and<br>
nobody have control for the calls. I dont want to deny the access for the<br>
user to read the spots - but there has to be a simple control for the spotter.<br>
<br>
set/password is no the solution. You get a question for the password and if<br>
you have not set a password you can log in with "ENTER" and have all<br>
functions. If you set a password it is local to this cluster and there are<br>
still about 400 cluster without password for you (better - or worse - for the<br>
blacks..)<br>
(a possibility can be - forwarding for the passwords - the most clusters are<br>
dxspider - is it possible to do it Dirk?)<br>
<br>
With "register on" it is possible to read all clusterinformation. No spots and<br>
no ann are possible to send. Only send a mail to sysop....<br>
<br>
I have now set at db0erf-5:<br>
<br>
set/var $main::regreq = 1<br>
set/var $main::passwdreq = 1<br>
<br>
I think if more (best all) sysop take these regulations we have less trouble....<br>
<br>
73 from Erfurt de Wolfram DL3AMi<br>
</blockquote>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a><br>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</div></div></blockquote></div><br></div>