ID:1050754
 
Resolved
Sticky bans have been simplified and improved. All bans are now handled in the same config file, ban.txt. The old files hostban.txt, keyban.txt, and ipban.txt are obsolete.

Games also now have the option of using per-game bans and can interact with those via GetConfig() and SetConfig(). These bans can also be sticky, timed, and/or session-based just like host bans were in the past. Games can only see and change their own bans, not bans belonging to other games or those that apply to all games. See world.GetConfig() and world.IsBanned() for more details.

Please note: In the past, games could read all bans in keyban.txt and ipban.txt. Now they will only see bans for that specific game. If your game used GetConfig/SetConfig with keyban in the past, and you wish to make changes to old bans from within the game, they will have to be made game-specific. This can be done by editing ban.txt and adding :[hubpath] after the key for each ban, or in Dream Daemon by hosting the game and checking the "Apply to this game only" box for each ban you wish to change.
Applies to:Dream Daemon
Status: Resolved (498.1148)

This issue has been resolved.
The ban system is too complex and can be simplified.
Can we have more detail about what you have done please?
Basically the ban system will now query the hub to correlate users behind-the-scenes. So you can ban a user and feel reasonably confident than any alt keys won't be able to get in as well. We use identifying sid, ip, activity info to associate users to a high degree of confidence.
Excellent! this is fantastic news! how will it handle bans if it can't reach the hub?

Is this also in place for Linux?
Yes, this works on Linux. If the hub can't be reached, it'll just use the local info. This is somewhat experimental so we hope people test it out and make sure it works. We have some other security measures in this build that I'll mention shortly.
Thanks for the information Tom glad to see some progress!
Was wondering if this feature request was wrapped up into that?

http://www.byond.com/forum/?post=998546
No, but we can probably get that in.
Can somebody explain more about this? Is it only hub-related bans? or also applied to the games displayed in that hub?
It's all DreamDaemon bans, the hub only does association look-ups to handle sticky bans. Aside from that the hub has nothing to do with it, and it has nothing to do with hub entries.
Excellent :) thanks for the descriptive resolution post.
Lummox JR resolved issue with message:
Sticky bans have been simplified and improved. All bans are now handled in the same config file, ban.txt. The old files hostban.txt, keyban.txt, and ipban.txt are obsolete.

Games also now have the option of using per-game bans and can interact with those via GetConfig() and SetConfig(). These bans can also be sticky, timed, and/or session-based just like host bans were in the past. Games can only see and change their own bans, not bans belonging to other games or those that apply to all games. See world.GetConfig() and world.IsBanned() for more details.

Please note: In the past, games could read all bans in keyban.txt and ipban.txt. Now they will only see bans for that specific game. If your game used GetConfig/SetConfig with keyban in the past, and you wish to make changes to old bans from within the game, they will have to be made game-specific. This can be done by editing ban.txt and adding :[hubpath] after the key for each ban, or in Dream Daemon by hosting the game and checking the "Apply to this game only" box for each ban you wish to change.