N9: Server-side cheat and abuse protection
- A hostile test client crafts INPUT packets byte by byte and sends them through NetGame.take_input() into a real match: extreme axes, the same tick claimed repeatedly, the whole lead window at once, past, far-future and maximum ticks, fire toggled every tick with slot swaps, builds aimed anywhere with junk kinds and materials and no materials, and pickup/drop/select tricks. Speed stays within sprint speed per tick, shots within the weapon's rate, pieces within build reach and paid for, and every item is conserved. - Fix: a command tick beyond the simulation's lead window no longer moves NetGame's dedupe marker, so one bogus far-future tick can't lock out a player's real commands. - Connections are rate-limited per address (32 per 10 s, 8 handshakes in progress) with a new REASON_BUSY and a message for it. - ParserFuzz mutates real messages from a bot match and random bytes and feeds them to every network decoder, the snapshot receiver and the list server. 20,000 per make check; make fuzz runs 1,000,000 (about 40 s): no errors, 2.9 KB of memory growth. - ARCHITECTURE.md: "Trusting nothing from clients". Closes #40 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -39,6 +39,8 @@ const REASON_LEFT: int = 7
|
||||
## Client-side only: nothing answered, or the connection went quiet.
|
||||
const REASON_NO_ANSWER: int = 8
|
||||
const REASON_LOST: int = 9
|
||||
## Too many connections from one address in a short time.
|
||||
const REASON_BUSY: int = 10
|
||||
|
||||
const NAME_MAX_CHARS: int = 16
|
||||
const NAME_MAX_BYTES: int = 64
|
||||
@@ -168,6 +170,8 @@ static func reason_text(reason: int, server_version: int = 0, own_version: int =
|
||||
return "The server removed you from the game."
|
||||
REASON_LEFT:
|
||||
return "You left the game."
|
||||
REASON_BUSY:
|
||||
return "Too many connections from your address just now. Wait a few seconds and try again."
|
||||
REASON_NO_ANSWER:
|
||||
return "No answer from the server. Check the address and port, and that the server is running."
|
||||
REASON_LOST:
|
||||
|
||||
Reference in New Issue
Block a user