This is thread intended for advices, tips, security questions and answers related to servers ...
irrelevant posters receive infraction, so don't post unless You on subject
0.
it's now fully recomended to use BattlEye even on closed community / passworded servers (due to additional layers of protection)
1.
ATTENTION! Warning to All Admins!
Emergency Responder to Event OMFGBBQFAIL#65535: http://dev-heaven.net/issues/20994
Immediately rename Your server -config= files to unique filenames!
http://community.bistudio.com/wiki/A...Server_Options
http://community.bistudio.com/wiki/server.cfg
do NOT share these filenames with anyone who is not trustable! (ideally only Yourself)
Start using custom -BEpath= immediately
http://community.bistudio.com/wiki/B...Epath_location
More countermeasures for beserver.cfg soon(tm)!
beserver.cfg is now automatically renamed to beserver_active_[randomtext].cfg while the server is running to prevent this exploit.
Summary:
move Your -profiles= , -config= and -BEpath= outside Your game/server directory
and use unique filenames (yet rename of file not possible for beserver.cfg)
2.
use verifySignatures=2; and v2 signatures on your server
v2 signatures are supported also in ARMA 2 version 1.10+ and ARMA 2:OA 1.59+!
http://community.bistudio.com/wiki/A..._on_the_server
3.
Use RCON from BattlEye and it's BEGUID to ban players,
forget about in-game UID (they spoofable easily and deprecated)
4.
remove regularCheck line from your config (or comment it out by ; infront of it),
incorrect value negates the defaut setting now
255.
if all fails then password the server up
remove reportIP from gamespy master line in config
and play only with Your trustable friends
but that sort of prevents the public reach it ...
note: this is WIP topic, so any text is subject for change w/o warning![]()
HOME 

Reply With Quote


