https://wiki.bzflag.org/api.php?action=feedcontributions&feedformat=atom&user=CygalBZFlagWiki - User contributions [en]2026-04-09T16:45:37ZUser contributionsMediaWiki 1.43.5https://wiki.bzflag.org/index.php?title=Server_authentication&diff=6560Server authentication2009-07-21T13:45:26Z<p>Cygal: Minor edit: typos and ponctuation.</p>
<hr />
<div>==Overview==<br />
Version 3.0 and later of the BZFlag server ([[BZFS]]) require an authentication key in order to list on the global public list server.<br />
<br />
==Authentication==<br />
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. <br />
<br />
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.<br />
<br />
===The Key===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
===Key Management===<br />
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.<br />
<br />
==Questions==<br />
'''Q)''' What happens if my key gets out?<br />
<br />
'''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.<br />
<br />
'''Q)''' What if I run BZFS instances for other people?<br />
<br />
'''A)''' Then you have 2 choices. <br />
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.<br />
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.<br />
<br />
'''Q)''' Does 2.0.x need a key?<br />
<br />
'''A)''' No, 2.0.x servers do not need a key.</div>Cygalhttps://wiki.bzflag.org/index.php?title=V3RCChecklist&diff=6552V3RCChecklist2009-07-16T16:49:30Z<p>Cygal: /* RC Critical fixes. */ fix typo</p>
<hr />
<div>==Overview==<br />
V3.0 is very close to a release candidate. This page will list the remaining items that need to be addressed before an RC can be made.<br />
<br />
==RC Critical fixes.==<br />
# MsgPause fix '''<trepan>'''<br />
# 32-bit teleporter-vs-box bug '''<BulletCatcher ? >'''<br />
# Network data is being received or processed by the client in the opposite order causing many odd bugs, such as the motto not being displayed, and possibly causing players' flags from not showing up when you join.<br />
# Fix Replay System crashes. '''<cygal>'''<br />
<br />
==RC Critical Tasks==<br />
# Windows installer review (install VC9 runtimes etc..)<br />
# Linux Package review (new files in the right places )<br />
# Mac installer review (check it in)<br />
# Readme Updates<br />
# Docs for V3 changes (-a missing, caps on server, lag comp, etc..)<br />
# API review (spelling, consistency)<br />
# Dead-reckoning / lag-compensation testing '''<JeffM ? >'''<br />
<br />
==RC 'really nice' features ==<br />
# Ask user to accept non bzflag.org images '''<trepan>'''<br />
# Ask user to join non bzflag.org servers (MsgJoinServer) '''<trepan>'''<br />
# Parity mesh checks to replace inside/outside points '''<trepan>'''<br />
<br />
==RC 'really nice' Fixes/Tasks==<br />
# Webadmin template review ( for style )</div>Cygalhttps://wiki.bzflag.org/index.php?title=V3RCChecklist&diff=6551V3RCChecklist2009-07-16T16:46:14Z<p>Cygal: replay system tested. let's fix it now</p>
<hr />
<div>==Overview==<br />
V3.0 is very close to a release candidate. This page will list the remaining items that need to be addressed before an RC can be made.<br />
<br />
==RC Critical fixes.==<br />
# MsgPause fix '''<trepan>'''<br />
# 32-bit teleporter-vs-box bug '''<BulletCatcher ? >'''<br />
# Network data is being received or processed by the client in the opposite order causing many odd bugs, such as the motto not being displayed, and possibly causing players' flags from not showing up when you join.<br />
# Fix Replay System crahses. '''<cygal>'''<br />
<br />
==RC Critical Tasks==<br />
# Windows installer review (install VC9 runtimes etc..)<br />
# Linux Package review (new files in the right places )<br />
# Mac installer review (check it in)<br />
# Readme Updates<br />
# Docs for V3 changes (-a missing, caps on server, lag comp, etc..)<br />
# API review (spelling, consistency)<br />
# Dead-reckoning / lag-compensation testing '''<JeffM ? >'''<br />
<br />
==RC 'really nice' features ==<br />
# Ask user to accept non bzflag.org images '''<trepan>'''<br />
# Ask user to join non bzflag.org servers (MsgJoinServer) '''<trepan>'''<br />
# Parity mesh checks to replace inside/outside points '''<trepan>'''<br />
<br />
==RC 'really nice' Fixes/Tasks==<br />
# Webadmin template review ( for style )</div>Cygal