This wiki is archived and useful information is being migrated to the main bzflag.org website

Editing Server authentication

Jump to: navigation, search

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The administrator who locked it offered this explanation: Archived wiki

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
==Overview==
 
==Overview==
Version 2.4 and later of the BZFlag server ([[BZFS]]) require an authentication key in order to list on the global public list server.
+
Version 3.0 and later of the BZFlag server ([[BZFS]]) require an authentication key in order to list on the global public list server.
  
 
==Authentication==
 
==Authentication==
 
Authentication is required in order to provide players and project staff members a point of contact for any issues or problems that may arise with the server when it is being run publicly.  
 
Authentication is required in order to provide players and project staff members a point of contact for any issues or problems that may arise with the server when it is being run publicly.  
  
Any server that uses the -public option and contacts the project's public list server (http://my.bzflag.org/db/) will be required to provide an authentication key in order to show up on the list.
+
Any server that uses the -public option and contacts the project's public list server( http://my.bzflag.org/db/ ) will be required to provide an authentication key in order to show up on the list.
  
 
===The Key===
 
===The Key===
 
The authentication key is automatically generated by the Key management site, and is tied to a specific domain name, or IP address. Server owners simply have to log into the Key Manager and they can generate as many keys as they need. The key is effectively tied to a single server machine, but can be used with any number of BZFS instances on any number of ports.
 
The authentication key is automatically generated by the Key management site, and is tied to a specific domain name, or IP address. Server owners simply have to log into the Key Manager and they can generate as many keys as they need. The key is effectively tied to a single server machine, but can be used with any number of BZFS instances on any number of ports.
  
Servers that do not have static IPs or domain names, should look at using one of the many free DNS name services that are available such as http://www.no-ip.com. Dynamic IPs will need new keys every time the address changes if a domain name is not used.
+
Servers that do not have static IPs or domain names, should look at using one of the many free DNS name services that are available such as http://www.no-ip.com . Dynamic IPs will need new keys every time the address changes if a domain name is not used.
  
 
The key is numeric and will be completely unique. Keys are not valid for domain names or IP address that they were not created with.
 
The key is numeric and will be completely unique. Keys are not valid for domain names or IP address that they were not created with.
  
 
===Key Management===
 
===Key Management===
Key Management is handled by the website: http://my.bzflag.org/listkeys/. After logging in with a global username and password (forum login) server owners can enter as many domain names or IP addresses as they wish.  Provide the key to bzfs using the "-publickey <key>" option.
+
Key Management is handled by the website: http://my.bzflag.org/listkeys/ . After logging in with a global username and password (forum login) server owners can enter as many domain names or IP addresses as they wish.
  
==Questions==
+
==Questions===
'''Q)''' What happens if my key gets out?
+
Q) What happens if my key gets out.
 +
A) Not much, they key is only valid for your server machine, so unless the user also has access to the same computer they can not user.
  
'''A)''' Not much, the key is only valid for your server machine, so unless the user also has access to the same computer they can not use it.
+
Q) What if I run BZFS instances for other people.
 
+
A) Then you have 2 choices.  
'''Q)''' What if I run BZFS instances for other people?
+
 
+
'''A)''' Then you have 2 choices.  
+
 
   1) You can give out your key to your people and they can use it. This will make all servers show up as belonging to you.
 
   1) You can give out your key to your people and they can use it. This will make all servers show up as belonging to you.
 
   2) You can tell your users to generate there own keys using the server address or domain name. Then each BZFS instance will be owned by each person.
 
   2) You can tell your users to generate there own keys using the server address or domain name. Then each BZFS instance will be owned by each person.
  
'''Q)''' Does 2.0.x need a key?
+
Q) Does 2.0.x need a key.
 
+
A) no, 2.0.x servers do not need a key.
'''A)''' No, 2.0.x servers do not need a key.
+
 
+
[[Category:Server]]
+

Please note that all contributions to BZFlagWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BZFlagWiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)