Difference between revisions of "Security"

From AAGRINDER wiki
Jump to navigationJump to search
imported>Maze
(describe insecure mode with links)
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
 
This page describes the current status of security in AAGRINDER.
 
This page describes the current status of security in AAGRINDER.
  
Line 9: Line 10:
 
this transmission will be encrypted.
 
this transmission will be encrypted.
  
On the server, the password is hashed and salted using [https://www.npmjs.com/package/bcryptjs bcryptjs] and then saved in a [[wikipedia:MySQL|MySQL]] database. The relevant part of the code can be found [https://gitlab.com/MRAAGH/aagrinder/blob/master/server/User.js#L120 here]. The plaintext password does not persist in memory on neither the client or the server.
+
On the server, the password is hashed and salted using [https://www.npmjs.com/package/bcryptjs bcryptjs] and then saved in a json file. The plaintext password does not persist in memory on neither the client nor the server.
 +
 
 +
Users can change their passwords by using the '''/passwd''' [[command list|command]] in-game. It is also possible to change the password with a direct [[AAGRINDER REST api|api call]]. In both cases, the current password is required in order to set a new one.
 +
 
 +
The server administrator can change any user's password using the '''passwd''' command in the [[server console]]. If you lost your current password, you should contact the server administrator.
  
There is currently no functionality for changing an account's password. If you want your password changed, you should contact the server administrator to reset your account (progress in the game will not be lost).
+
The server administrator is able to remove a password from an account, allowing this account to instantly log in without needing to type a password. This is recommended only for testing.
  
There is an alternative mode called [[insecure mode|Running in insecure mode]] which can be enabled by toggling a server setting. We call it "insecure" to decrease the confusion between the similar words "authentication" and "authorization". If enabled, passwords will be completely ignored at login, and the client will not prompt the user for password.
+
Older versions of AAGRINDER have an "insecure_mode" setting, which can be used to disable checking passwords. This setting was on [https://gitlab.com/MRAAGH/aagrinder/-/commit/bd503d736fcd120b4f2130d77839048c6dbb275d 8th July 2022] renamed to "check_passwords" and [https://gitlab.com/MRAAGH/aagrinder/-/commit/53940c37dd5d1f7b322e003450a365bda0f02a5e 6 days later] removed.
  
 
== Authorization ==
 
== Authorization ==
 
Additional privileges may be granted to specific users at login.
 
Additional privileges may be granted to specific users at login.
  
Among the in-game commands that get executed on the server, some are in the group of ''admin commands'', which prevents users from accessing these commands unless they have the ''admin'' role. The names of users with the admin role are specified in the file ''admins.txt'' in the server directory. This file needs to be edited manually.
+
Among the in-game commands that get executed on the server, some are in the group of ''admin commands'', which prevents users from accessing these commands unless they have the ''admin'' role. The names of users with the admin role are specified in the file ''admins.txt'' in the server directory. This file needs to be edited manually and reloaded using the '''admin''' command in the [[server console]], or by [[Administration tips|restarting the server]].
 
 
An additional privilege may be granted to users which allows them to run the /sudo command. To do this, the server setting ''allow_sudo'' needs to be set to ''true'' and the name of the user needs to be specified in the file ''sudo.txt'' in the server directory. This file needs to be edited manually.
 
  
It is possible to turn off authorization for admin commands, by changing the server setting ''authorization'' to ''false''. Then, all players are allowed to run admin commands, regardless of the content of ''admins.txt''. However, access to the /sudo command remains restricted.
+
Older versions of AAGRINDER have a ''/sudo'' command, which allows a user to run a command as any other user, and requires additional privileges (an entry in ''sudo.txt''). The ''/sudo'' command [https://gitlab.com/MRAAGH/aagrinder/-/commit/e89398ba2f59e5f84a601d87d5fe7dd8296612b1 was removed] on September 4, 2022.

Latest revision as of 09:27, 8 July 2024

This page describes the current status of security in AAGRINDER.

Authentication[edit]

In AAGRINDER, users authenticate with their passwords. The password is chosen when the account is created and needs to be at least 1 character long. The password may contain any characters.

The password is transmitted to the server in plaintext. However, if you are using a https connection, this transmission will be encrypted.

On the server, the password is hashed and salted using bcryptjs and then saved in a json file. The plaintext password does not persist in memory on neither the client nor the server.

Users can change their passwords by using the /passwd command in-game. It is also possible to change the password with a direct api call. In both cases, the current password is required in order to set a new one.

The server administrator can change any user's password using the passwd command in the server console. If you lost your current password, you should contact the server administrator.

The server administrator is able to remove a password from an account, allowing this account to instantly log in without needing to type a password. This is recommended only for testing.

Older versions of AAGRINDER have an "insecure_mode" setting, which can be used to disable checking passwords. This setting was on 8th July 2022 renamed to "check_passwords" and 6 days later removed.

Authorization[edit]

Additional privileges may be granted to specific users at login.

Among the in-game commands that get executed on the server, some are in the group of admin commands, which prevents users from accessing these commands unless they have the admin role. The names of users with the admin role are specified in the file admins.txt in the server directory. This file needs to be edited manually and reloaded using the admin command in the server console, or by restarting the server.

Older versions of AAGRINDER have a /sudo command, which allows a user to run a command as any other user, and requires additional privileges (an entry in sudo.txt). The /sudo command was removed on September 4, 2022.