1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Administration Manual v1.50: Security</TITLE>
6 <LINK HREF="adminmanual-9.html" REL=next>
7 <LINK HREF="adminmanual-7.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc8" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-9.html">Next</A>
13 <A HREF="adminmanual-7.html">Previous</A>
14 <A HREF="adminmanual.html#toc8">Contents</A>
16 <H2><A NAME="s8">8. Security</A></H2>
18 <P>From version 1.49 DXSpider has some additional security features. These
19 are not by any means meant to be exhaustive, however they do afford some
20 security against piracy. These two new features can be used independently
21 of each other or in concert to tighten the security.
23 <H2><A NAME="ss8.1">8.1 Registration</A>
26 <P>The basic principle of registration is simple. If a user is not registered
27 by the sysop, then they have read-only access to the cluster. The only
28 thing they can actually send is a talk or a message to the sysop. In
29 order for them to be able to spot, send announces or talks etc the sysop
30 must register them with the <EM>set/register</EM> command, like this ...
37 <P>The user g0vgs can now fully use the cluster. In order to enable
38 registration, you can issue the command ...
42 set/var $main::reqreg = 1
45 <P>Any users that are not registered will now see the motd_nor file rather
46 than the motd file as discussed in the Information, files and useful
49 <P>Entering this line at the prompt will only last for the time the cluster
50 is running of course and would not be present on a restart. To make the
51 change permanent, add the above line to /spider/scripts/startup. To
52 read more on the startup file, see the section on Information, files
55 <P>To unregister a user use <EM>unset/register</EM> and to show the list
56 of registered users, use the command <EM>show/register</EM>.
58 <H2><A NAME="ss8.2">8.2 Passwords</A>
61 <P>At the moment, passwords only affect users who login to a DXSpider
62 cluster node via telnet. If a user requires a password, they can
63 either set it themselves or have the sysop enter it for them by using
64 the <EM>set/password</EM> command. Any users who already have passwords,
65 such as remote sysops, will be asked for their passwords automatically
66 by the cluster. Using passwords in this way means that the user has a
67 choice on whether to have a password or not. To force the use of
68 passwords at login, issue the command ...
72 set/var $main::passwdreq = 1
75 <P>at the cluster prompt. This can also be added to the /spider/scripts/startup
76 file as above to make the change permanent.
78 <P>Of course, if you do this you will have to assign a password for each of
79 your users. If you were asking them to register, it is anticipated that
80 you would ask them to send you a message both to ask to be registered and
81 to give you the password they wish to use.
83 <P>Should a user forget their password, it can be reset by the sysop by
84 first removing the existing password and then setting a new one like so ...
89 set/password g0vgs new_password
94 <A HREF="adminmanual-9.html">Next</A>
95 <A HREF="adminmanual-7.html">Previous</A>
96 <A HREF="adminmanual.html#toc8">Contents</A>