Secure remote private server, access with password

[revloc02c]

Is there a way to setup a regular server that shows up on the server list and allows remote access, but requires a server password to play?

So in other words, a private server with remote access. You list your server on the server list, but only those who have the password can get on. Is there functionality that allows this?

[sorvani]

You can lock the server and set the people you want to get in to enough status to log in anyway.
You can allows log ins only from certain IP addresses and have a web form where they can sign in and update their IP. PEQ does GM IP restrictions in a similar method.

[revloc02c]

You can allows log ins only from certain IP addresses and have a web form where they can sign in and update their IP. PEQ does GM IP restrictions in a similar method.
Ooo, how do you do this one? Not the web form part, but the only allowing certain IPs part.

[sorvani]

have not tested it but one would assume it is tied to the GM_IP table.

[trevius]

If you wanted to use the GM IPs table for that, you would most likely need to modify the settings in the source for what is considered a GM, otherwise you would probably have to give a certain minimum status for all accounts you want to be able to access your server. If you lock it out, it is effectively the same thing, but people could still log into your server with the GM accounts from other IPs (which may or may not be a problem).

Probably one work around would be to set all GM commands to be over X status, where X is the required status to allow a GM to log into a locked server (maybe status 80 or something). Then, they would be able to access the server and shouldn't have access to any commands you don't want them to have. Though, you will need to make sure your commands table includes every GM command, which you can check by logging in and typing #help to see a list of what commands you have access to for the status your account is set to.

The only downside to this type of setup would be that /who would show everyone as guides or GMs or whatever.

You could also probably just create a script in your default_player.pl that checks account names against a list of account names you want to allow, and then kick anyone that doesn't match that list.

I am sure there are otherways that wouldn't involve editing the source, but you could definitely edit the source if needed to make it work exactly whichever way you wish.

[revloc02c]

Probably one work around would be to set all GM commands to be over X status, where X is the required status to allow a GM to log into a locked server (maybe status 80 or something). Then, they would be able to access the server and shouldn't have access to any commands you don't want them to have. Though, you will need to make sure your commands table includes every GM command, which you can check by logging in and typing #help to see a list of what commands you have access to for the status your account is set to.

The only downside to this type of setup would be that /who would show everyone as guides or GMs or whatever.

You could also probably just create a script in your default_player.pl that checks account names against a list of account names you want to allow, and then kick anyone that doesn't match that list.

Thanks Trev, clever and well spoken as usual. Both good ideas. I'd rather avoid editing source right now, but these other two ideas have merit.