Authentication - Revision history

Cadillac at 01:05, 23 August 2021

2021-08-23T01:05:06Z

← Older revision		Revision as of 21:05, 22 August 2021
Line 56:		Line 56:
	# Login in-game by using the Authentication menu		# Login in-game by using the Authentication menu
	</pre>		</pre>

			[[Category:Development]]

Kyle: zthreads

2015-01-18T03:22:32Z

zthreads

← Older revision		Revision as of 23:22, 17 January 2015
Line 40:		Line 40:

	You can define "local users", too, if you don't want to use external sources for authentication (Or if you just have no forum account). This would require these two settings: LOCAL_USER <name> <password> and USER_LEVEL <name>@ <level>		You can define "local users", too, if you don't want to use external sources for authentication (Or if you just have no forum account). This would require these two settings: LOCAL_USER <name> <password> and USER_LEVEL <name>@ <level>

			===zthreads===
			For mid round authentication zthreads is needed, you can install the libzthread-dev package on most linux distributions, but configuring armagetron before building may require a few extra options if the zthread-config script is not installed.
			./configure --disable-glout LIBS="-lZThread" CXXFLAGS="-DHAVE_LIBZTHREAD" CFLAGS="-DHAVE_LIBZTHREAD"

	=== Example server_info.cfg ===		=== Example server_info.cfg ===

Epsy: Oops, fixed a typo in the link.

2012-04-01T22:34:26Z

Oops, fixed a typo in the link.

← Older revision		Revision as of 18:34, 1 April 2012
Line 1:		Line 1:
	<strong>This is a development document. You may find information about the current authentication systems on [[Authentication ~~For~~ Players]].</strong>		<strong>This is a development document. You may find information about the current authentication systems on [[Authentication for Players]].</strong>

	Several possible ways of doing authentication are listed here.		Several possible ways of doing authentication are listed here.

Epsy: Added a link to Authentication For Players

2012-04-01T22:33:26Z

Added a link to Authentication For Players

← Older revision		Revision as of 18:33, 1 April 2012
Line 1:		Line 1:
			<strong>This is a development document. You may find information about the current authentication systems on [[Authentication For Players]].</strong>

	Several possible ways of doing authentication are listed here.		Several possible ways of doing authentication are listed here.

Corewar at 05:07, 14 May 2010

2010-05-14T05:07:39Z

← Older revision		Revision as of 01:07, 14 May 2010
Line 41:		Line 41:
	=== Example server_info.cfg ===		=== Example server_info.cfg ===
	<pre>		<pre>
	GLOBAL_ID 1 # Enable external authentication authorities		GLOBAL_ID 1 # Enable external authentication authorities
	USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges		USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges
	# Login in-game by typing: /login forums		# Login in-game by typing: /login forums

	TRUST_LAN 1 # Allow login via local network (LAN)		TRUST_LAN 1 # Allow login via local network (LAN)
	LOCAL_USER itsme superpassword # Define username and password		LOCAL_USER itsme superpassword # Define username and password
	USER_LEVEL itsme@ 0 # Grant "Owner" privileges		USER_LEVEL itsme@ 0 # Grant "Owner" privileges
	# Login in-game by using the Authentication menu		# Login in-game by using the Authentication menu
	</pre>		</pre>

Corewar at 05:06, 14 May 2010

2010-05-14T05:06:00Z

← Older revision		Revision as of 01:06, 14 May 2010
Line 43:		Line 43:
	GLOBAL_ID 1 # Enable external authentication authorities		GLOBAL_ID 1 # Enable external authentication authorities
	USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges		USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges
			# Login in-game by typing: /login forums

	TRUST_LAN 1 # Allow login via local network (LAN)		TRUST_LAN 1 # Allow login via local network (LAN)
	LOCAL_USER itsme superpassword # Define username and password		LOCAL_USER itsme superpassword # Define username and password
	USER_LEVEL itsme@ 0 # Grant "Owner" privileges		USER_LEVEL itsme@ 0 # Grant "Owner" privileges
			# Login in-game by using the Authentication menu
	</pre>		</pre>

Corewar: How to make Authentication work - section added

2010-05-14T05:04:11Z

How to make Authentication work - section added

← Older revision		Revision as of 01:04, 14 May 2010
Line 31:		Line 31:
	* The client sends the resulted scrambled egg MD5 hash back to the server.		* The client sends the resulted scrambled egg MD5 hash back to the server.
	* The server has done the same operation on the MD5 hash of the password from the player database (The retrieval of that is the missing bit) and compares the result with what it gets from the client. If the results match, the client is authorized to use that player name.		* The server has done the same operation on the MD5 hash of the password from the player database (The retrieval of that is the missing bit) and compares the result with what it gets from the client. If the results match, the client is authorized to use that player name.

			== How To Set Up Authentication ==
			Read the file <code>settings_authentication.cfg</code> in your [[Configuration Files]] directory for more details.

			In short: One can configure the 0.3.x (perhaps even 0.2.8.x) server in a way, so that users can use their forum's user name and password for authenticating on your server. To aquire this, create a file <code>/etc/armagetronad-dedicated/server_info.cfg</code>, enable GLOBAL_ID 1 and assign a USER_LEVEL <username>@forums <level>. To login, type "/login forums" when connected to the server in-game (Using the menu didn't work for me).

			You can define "local users", too, if you don't want to use external sources for authentication (Or if you just have no forum account). This would require these two settings: LOCAL_USER <name> <password> and USER_LEVEL <name>@ <level>

			=== Example server_info.cfg ===
			<pre>
			GLOBAL_ID 1 # Enable external authentication authorities
			USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges

			TRUST_LAN 1 # Allow login via local network (LAN)
			LOCAL_USER itsme superpassword # Define username and password
			USER_LEVEL itsme@ 0 # Grant "Owner" privileges
			</pre>

Meriton: linked my proposal

2006-03-09T20:30:26Z

linked my proposal

← Older revision		Revision as of 16:30, 9 March 2006
Line 7:		Line 7:
	== Full Blown ==		== Full Blown ==

	On the forum, a way to handle authentication with full fledged security and privacy has been worked out. It is based on public key cryptography and allows central or decentral player account management. Read about it in [[Key Based Authentication]].		On the forum, a way to handle authentication with full fledged security and privacy has been worked out. It is based on public key cryptography and allows central or decentral player account management. Read about it in [[Key Based Authentication]]. Meriton has suggested another approach: [[Distributed Authentification Using Digital Signatures]].

	== Test Balloon ==		== Test Balloon ==

Z-man at 23:21, 6 March 2006

2006-03-06T23:21:10Z

← Older revision		Revision as of 19:21, 6 March 2006
Line 1:		Line 1:
	Several possible ways of doing authentication are listed here.		Several possible ways of doing authentication are listed here.

			== IM Based ==

			Read about how we could profit from the work of others by abusing instant message systems in [[XMPP Based Authentication]].

	== Full Blown ==		== Full Blown ==

Z-man: /* Test Balloon */

2006-03-06T22:44:11Z

Test Balloon

← Older revision		Revision as of 18:44, 6 March 2006
Line 11:		Line 11:
	Disadvantages over key based scheme:		Disadvantages over key based scheme:
	* Less privacy, the authentication server is contacted on every login		* Less privacy, the authentication server is contacted on every login
	* Less security, it suffices if an attacker can intercept and take over communication between the game and		* Less security, it suffices if an attacker can intercept and take over communication between the game and authentication server to log in as anyone. In the key based scheme, the attacker needs to steal the authority's private key.
	authentication server to log in as anyone. In the key based scheme, the attacker needs to steal the authority's private key.
	* It does not support self-signed login where the fact that you're playing on a certain machine is taken as enough authentication.		* It does not support self-signed login where the fact that you're playing on a certain machine is taken as enough authentication.