Important info about public servers in V3.0+
Important info about public servers in V3.0+
With version 3.0 we are making a small change to the public list server usage policy that will affect all users that host public servers. So this post is here to let you know what's coming up and how to be ready for it.
BZFlag servers of version 2.99.44 and later are now required to authenticate with the public list server before they are able to list a game.
This authentication is so that players and project staff members have some contact information for the owner of the server in case there are any problems. This will also tie into the new stats system that is being worked on.
To authenticate each server will need an Authentication Key and use that key with the -publickey config option. Keys are automatically generated by a key management website, and tie the server instance to a specific forum account.
This policy does not affect players in any way. It only affects how servers connect to the public list. Server owners are NOT required to force player registration. This policy does not affect private, unlisted, or LAN servers, only servers that wish to use the public list, or the global authentication system.
A wiki page describing more about the policy and the key system is located at http://my.bzflag.org/w/ServerAuthentication
Please note that this feature is still under development and parts of it may not be final (the key management website for sure).
BZFlag servers of version 2.99.44 and later are now required to authenticate with the public list server before they are able to list a game.
This authentication is so that players and project staff members have some contact information for the owner of the server in case there are any problems. This will also tie into the new stats system that is being worked on.
To authenticate each server will need an Authentication Key and use that key with the -publickey config option. Keys are automatically generated by a key management website, and tie the server instance to a specific forum account.
This policy does not affect players in any way. It only affects how servers connect to the public list. Server owners are NOT required to force player registration. This policy does not affect private, unlisted, or LAN servers, only servers that wish to use the public list, or the global authentication system.
A wiki page describing more about the policy and the key system is located at http://my.bzflag.org/w/ServerAuthentication
Please note that this feature is still under development and parts of it may not be final (the key management website for sure).
JeffM
- I_Died_Once
- Special Forces
- Posts: 635
- Joined: Sun Nov 28, 2004 5:27 pm
- Location: The Dark Side
- Contact:
Re: Important info about public servers in V3.0+
What if my server can only be accessed by command line, remotely. I can't "go to a website" from the machine in question in the traditional sense. How do I generate a key from that IP address if I can't use firefox (or whatever) to go to the key site?
...This has been a recording.
Re: Important info about public servers in V3.0+
You can go to the page from any machine and generate a key for the IP address of your server, no need to do it from the actual machine.
There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
Re: Important info about public servers in V3.0+
Is this in its end format, even needed for servers using auth but not listing?
Re: Important info about public servers in V3.0+
Well, to use auth, you have to be set up as a public server, and would therefore be using the list. Sure, you might have "-advertise NONE" in your config, but your server is still being stored in the list server's database and would fall under the same rules.tobylane wrote:Is this in its end format, even needed for servers using auth but not listing?
Re: Important info about public servers in V3.0+
So just to make this clear, basically you need ONE authentication key per IP Address, not one per IP:PORT? So if I had 3 servers,
1.1.1.1:5154
1.1.1.1:5155
1.1.1.1:5156
I would only need one authentication key to cover all of those? But what if you have a chaning IP (dynamic I believe), Do you have to get a new Authentication Key every time it changes for the new IP?
Thanks for clearing this up!
1.1.1.1:5154
1.1.1.1:5155
1.1.1.1:5156
I would only need one authentication key to cover all of those? But what if you have a chaning IP (dynamic I believe), Do you have to get a new Authentication Key every time it changes for the new IP?
Thanks for clearing this up!
Re: Important info about public servers in V3.0+
It is up to you. You can use a single key for all the ports on a single server if you want them all to have the same owner.
If you want each instance to have a different owner, then you can use a key for each if you want.
Basically it's a key per Owner/machine pair.
If you want each instance to have a different owner, then you can use a key for each if you want.
Basically it's a key per Owner/machine pair.
JeffM
Re: Important info about public servers in V3.0+
If you want to avoid the issue of a changing IP, then use a hostname that always points to your IP.
Re: Important info about public servers in V3.0+
static domain names that point to dynamic IPs are available for free from websites like http://www.no-ip.com
JeffM
- Spazzy McGee
- Sergeant Major
- Posts: 1405
- Joined: Mon Mar 21, 2005 4:59 pm
- Location: Planet MoFo, Sheffield Division; United Kingdom
Re: Important info about public servers in V3.0+
Here's a question. If I have two host names that point at the same machine do I need two separate keys, for example:
spazzy.planet-mofo.com and bzflag.planet-mofo.com both point to the same machine, and are for all intents and purposes the same IP address. Do I need a separate key for each host name, or will the same one work?
spazzy.planet-mofo.com and bzflag.planet-mofo.com both point to the same machine, and are for all intents and purposes the same IP address. Do I need a separate key for each host name, or will the same one work?
"Life is what happens to you while you're busy making other plans." - John Lennon
Re: Important info about public servers in V3.0+
nope, you can use the same one.
What it does is simply verify that the hostname that is associated with the key resolves to the same IP as your server when it hits the list server.
The use of the hostname is just to prevent the key from being used by another machine.
What it does is simply verify that the hostname that is associated with the key resolves to the same IP as your server when it hits the list server.
The use of the hostname is just to prevent the key from being used by another machine.
JeffM
Re: Important info about public servers in V3.0+
But, you CAN have different ones if you like (if I understand this)
There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
Re: Important info about public servers in V3.0+
I think the important thing to understand about the host portion of the key is that it is just there to prevent someone else flagging you as the owner of a machine that you did not want to own ( assuming they got your key somehow)
The key ONLY sets the listed owner for a server. It does not affect the public address or any other aspect of the server. The list server just checks to see if the IP of the host associated with the key matches the ip of the requesting server. The web page for making keys can be accessed from anywhere, and does not need to be used from the server, there is just a place for you to type in the host/IP.
People that host more then one bzfs server can choose to use one key for all servers, or individual keys for each bzfs server, it is up to them.
Being the 'Owner' of a server does not confer any permisions, those are still handled by your groups file.
The key ONLY sets the listed owner for a server. It does not affect the public address or any other aspect of the server. The list server just checks to see if the IP of the host associated with the key matches the ip of the requesting server. The web page for making keys can be accessed from anywhere, and does not need to be used from the server, there is just a place for you to type in the host/IP.
People that host more then one bzfs server can choose to use one key for all servers, or individual keys for each bzfs server, it is up to them.
Being the 'Owner' of a server does not confer any permisions, those are still handled by your groups file.
JeffM