Server-Side Custom Launcher Authentication & Anti-Bypass Protection
Why it matters: Currently, RF Online server owners who develop custom launchers have no reliable way to enforce their use. Even with SHA-256 file integrity verification, signed manifests, automatic patching, and client file repair, players can bypass these protections by directly launching the original rflauncher.exe. This makes launcher-based file protection less effective because modified clients may still connect without completing the required verification. A native server-side launcher authentication feature in GoMMO would help server owners enforce their custom launchers, improve client integri
I suggest adding an optional Server-Side Custom Launcher Authentication System to GoMMO RF 4.55.
Proposed functionality:
- Mandatory Launcher Authorization: Require valid server-issued launch authorization before accepting a game login.
- Short-Lived Tokens: Use single-use session tokens with expiration and replay protection.
- Server-Side Validation: Reject login attempts that do not have valid authorization, including direct launches through the original rflauncher.exe.
- Admin Panel Configuration: Allow server owners to enable or disable this feature. Keep it disabled by default for backward compatibility.
- Custom Launcher API: Provide a documented integration method for custom launchers.
- FireGuard Compatibility: Preserve existing authentication, character selection, and FireGuard functionality.
- Secure Session Binding: Bind authorization to the correct login session rather than relying solely on the player's IP address.
Example workflow:
Official Custom Launcher → Client File Integrity Verification → Request Server Authorization → Receive Temporary Launch Session → GameServer Validates Authorization → Player Login Accepted
If a player directly opens the original rflauncher.exe without valid authorization, the server rejects the login.
Implementation suggestion:
Since GoMMO is written in Go, this feature could be integrated directly into the existing authentication flow instead of requiring external authentication proxies or executable binary patches.
The feature should remain optional so servers using the original launcher are unaffected.
This would provide a reusable security feature for the entire GoMMO community, not just one private server.
Note: This would strengthen launcher enforcement, but it should not be presented as complete anti-cheat protection, since a modified client may still attempt to imitate an authorized launcher.