Commit Graph
9 Commits
Author SHA1 Message Date
Tad Hunt d3b0aba94f Flesh out allowlist handling
Addresses comments from https://github.com/LOOHP/Limbo/pull/57#issuecomment-1304543589

In particular:

* Functionality now matches other server types

* only enforce the allowlist if a new "enforce-allowlist"
  boolean in server.properties is set to true

* Loads and process the allowlist only once when the server starts (or
  the reload command is executed), instead of every time a user connects.

* Add a new command & associated permissions "allowlist reload"
  to reload the allowlist
2022-11-05 14:32:25 -06:00
Tad Hunt 898fe20b14 add allowlist processing 2022-11-04 18:36:56 -06:00
Tad Hunt 23dfbd0df2 fix whitespace 2022-09-30 08:27:14 -06:00
Tad Hunt 4d1fade2e7 Merge remote-tracking branch 'upstream/master' into fix-issue-54 2022-09-29 16:15:32 -06:00
Tad Hunt a1ba8fc0b1 conditionalize debug messages on debug flag 2022-09-29 16:08:15 -06:00
Tad Hunt 39d90d79ff revert extraneous .gitignore changes 2022-09-29 15:25:28 -06:00
Tad Hunt 70caa3cd0a handle floodgate stuff in login packets 2022-09-26 14:41:12 -06:00
Tad Hunt 2866d9c015 remove extra debug info from log message 2022-09-23 11:15:24 -06:00
Tad Hunt d29279285e This commit fixes https://github.com/LOOHP/Limbo/issues/51
"Incorrect Payload Received in KeepAlive packet for player"

The problem is that in my setup (described in the issue linked above)
the loohp-limbo server is receiving an unsolicited PacketInKeepAlive
message prior to sending any out.  This causes the payload validation
check to fail, resulting in the connection then being closed.

This commit changes the PacketInKeepAlive handler to ignore (other than
logging) unsolicited KeepAlive messages rather than act on them.

Possibly the logging is a bad idea unless it's limited to being
suppressed via a debug flag...
2022-09-22 22:54:50 -06:00