Server Integrity

By
Domovishche6986

Adds security by verifying client mod jars against a server-side SHA-256 whitelist. Required both on server and client

Server Integrity helps server owners check which mod files their players really run. Every player’s game sends the server a SHA-256 hash of each mod file, and the server compares those hashes with a list that you control.

What it does

Checks mod files by hash. Anything that is not on your list is logged or kicked, whatever its file name or mod id.

To allow mods, join as an operator and run the command /modallow op mods. Your client’s mods are hashed and allowed, and regular players with the same modpack can join. Run it again whenever you change your modpack.

No client-side configuration. The server’s own mods folder is allowed automatically.

Class check. The bytes of loaded Minecraft and Forge classes are compared with what your operator’s client taught the server. It starts in report mode, so you decide when to enforce it.

Main commands

/modallow op mods: allow everything the online operators run;
/integrity status: shows mode, list sizes, build id and active checks;
/integrity pending: lists unknown files the server saw, so you can review them;
/integrity approve (hash): allow a pending file;
/integrity ban (hash or file) (reason): ban a file;
/integrity check (player): check a player right now;
/integrity mode (report or enforce): log only, or kick;
/integrity reload: re-read config and lists.