Patch notes
FutureMUD Web MUD Client 1.3.2
Hardens client deployment ownership, connection cleanup and trusted browser identity forwarding.
ยท mudclient · release · security · upgrade
Upgrade note: Web MUD Client 1.3.2 remains self-contained for Windows x64, Linux x64 and Linux ARM64. Upgrade the FutureMUD Engine before enabling trusted browser identity forwarding; the matching Engine release understands the PROXY header.
Safer Edge Deployment
Linux deployment and update ownership are now hardened so that release files, verification tools and the unprivileged proxy service retain their intended separation. The updater continues to verify the signed update manifest and archive checksum before activation, preserves rollback releases, and leaves operator-owned configuration in its durable location.
Reliable Connections And Shared Engine Protections
The proxy now closes detached asynchronous account connections through the transport lifecycle and more consistently forwards the browser's client address to a trusted FutureMUD Engine. This keeps the Engine's established bans, registration controls and flood protections as the one source of truth for Telnet and WebSocket players.
Continue to keep the proxy bound privately, use HTTPS/WSS publicly, require the exact public AllowedOrigins, and list only the proxy's trusted address on the third line of Connection.config.
Use /downloads for release archives and checksums. Package-local deployment instructions remain the source of truth for installation and rollback commands.