Node configuration for user access - Revision history

EA3CV at 05:36, 28 April 2025

2025-04-28T05:36:43Z

← Older revision		Revision as of 05:36, 28 April 2025
Line 111:		Line 111:

	The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.		The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.

	Unless the cluster node is a small club node or similar, it is probably a good idea not to force people to have a password. It may put some people off and it will be a LOT of work for the sysop. Most users will be protected by registration

	<pre>		<pre>

G0TRT at 09:50, 11 April 2025

2025-04-11T09:50:53Z

← Older revision		Revision as of 09:50, 11 April 2025
Line 99:		Line 99:
	</pre>		</pre>

	===~~'''~~How To protect your cluster node (Recommended configuration)~~'''~~===		===How To protect your cluster node (Recommended configuration)===

	----		----

G0TRT: Removed bolding from headings

2025-04-11T09:50:33Z

Removed bolding from headings

← Older revision		Revision as of 09:50, 11 April 2025
Line 1:		Line 1:


	===~~'''~~User Registration~~'''~~===		===User Registration===
	----		----
	There are two types of user in a DXSpider node, a registered user and an unregistered user.		There are two types of user in a DXSpider node, a registered user and an unregistered user.
	By default, all users belong to the unregistered category.		By default, all users belong to the unregistered category.

	===~~'''~~Node in UNREGISTERED Mode~~'''~~===		===Node in UNREGISTERED Mode===
	----		----
	This is the default way of working, but not necessarily the best.		This is the default way of working, but not necessarily the best.
Line 19:		Line 19:
	Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc		Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc

	===~~'''~~Node in REGISTRATION Mode~~'''~~===		===Node in REGISTRATION Mode===
	----		----
	To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.		To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.
Line 54:		Line 54:
	</pre>		</pre>

	===~~'''~~Password Usage~~'''~~===		===Password Usage===
	----		----
	By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.		By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.
Line 76:		Line 76:
	</pre>		</pre>

	===~~'''~~Node in NO PASSWORD Mode~~'''~~===		===Node in NO PASSWORD Mode===
	----		----
	The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.		The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.
Line 87:		Line 87:
	</pre>		</pre>

	===~~'''~~Node in PASSWORD Mode~~'''~~===		===Node in PASSWORD Mode===
	----		----
	If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.		If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.
Line 127:		Line 127:
	It is <b>strongly</b> suggested that sysops enable registration to try and combat the increasing misuse on the cluster network		It is <b>strongly</b> suggested that sysops enable registration to try and combat the increasing misuse on the cluster network

	===~~'''~~Make Changes Permanent~~'''~~===		===Make Changes Permanent===
	----		----
	Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...		Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...

Dxcadmin: 1 revision imported

2025-02-08T09:20:26Z

1 revision imported

← Older revision		Revision as of 09:20, 8 February 2025
(No difference)

DXSpider Documentation>G0vgs: G0vgs moved page NODE CONFIGURATION FOR USER ACCESS to Node configuration for user access

2023-02-10T17:54:25Z

G0vgs moved page NODE CONFIGURATION FOR USER ACCESS to Node configuration for user access

New page

==='''User Registration'''===
----
There are two types of user in a DXSpider node, a registered user and an unregistered user.
By default, all users belong to the unregistered category.

==='''Node in UNREGISTERED Mode'''===
----
This is the default way of working, but not necessarily the best.

The global variable that sets the node type is '''$main::reqreg'''
and its default value is '''0'''.
<pre>
set/var $main::reqreg = 0
</pre>

In this mode the sysop doesn't have to register users, but if they are registered, then it will simply be a database entry.
Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc

==='''Node in REGISTRATION Mode'''===
----
To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.
The way to change it is

<pre>
set/var $main::reqreg = 1
</pre>

When this mode is activated, only users that the sysop has registered will be able to send and receive SPOTS, ANN, etc. Unregistered users will only be able to receive information.

The way to register/unregister a user is as follows:
<pre>
set/register <call>
unset/register <call>
</pre>

You can check which users we have registered using

<pre>
sh/register <call>
</pre>

A specific login banner for registered users can be shown. The file containing it is the following

<pre>
/spider/_local_data/motd
</pre>

When an unregistered user starts the login process, they can be sent a different file that can be configured to say that they are not registered and how to register should they wish to do so. This file is ...

<pre>
/spider/local_data/motd_nor
</pre>

==='''Password Usage'''===
----
By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.

It should be noted that this only works on the node they regularly use. Their password is not propagated across the network for security reasons.

For a user to be assigned a password, the sysop needs to use the command ...

<pre>
set/password <call> <string>
</pre>

and the user can change his password with the command

<pre>
set/password
Enter old password:
Enter new password:
Re-enter new password:
Password changed
</pre>

==='''Node in NO PASSWORD Mode'''===
----
The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.

To see the value of the variable use ...

<pre>
sh/var $main::passwdreq
</pre>

==='''Node in PASSWORD Mode'''===
----
If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.

The node will not establish the session if there is no positive authentication.

To set this mode of operation:

<pre>
set/var $main::passwdreq = 1
</pre>

==='''How To protect your cluster node (Recommended configuration)'''===

----
One way to control the correct use of our node, is to use the combination of registration and password as follows.

We enable the registration for all the users

<pre>
set/var $main::reqreg = 1
</pre>

The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.

Unless the cluster node is a small club node or similar, it is probably a good idea not to force people to have a password. It may put some people off and it will be a LOT of work for the sysop. Most users will be protected by registration

<pre>
set/var $main::passwdreq = 0
</pre>

Of course, a user may wish to have a password set to increase their security on the node, meaning that unless someone also knows the password, their call cannot be used by someone else unless they know the password.

<pre>
set/register <call>
set/password <call> <string>
</pre>

It is <b>strongly</b> suggested that sysops enable registration to try and combat the increasing misuse on the cluster network

==='''Make Changes Permanent'''===
----
Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...

<pre>
/spider/scripts/startup
</pre>

and include the following lines
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

The changes to this file will not take effect until there is a reboot, so we can activate it manually the first time from the console by typing
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>