Inside the launcher: architecture and security
Context isolation, validated IPC, encrypted token storage and a main process that owns every privileged operation. A tour of how the new launcher is put together.
A launcher sits between a user, a game installation and an authentication provider. That makes it a security boundary by accident. We designed the new FireClient around that reality instead of bolting it on afterwards.
Two processes, one contract
The Electron renderer runs with node integration disabled, context isolation enabled and a strict content security policy. It cannot read the filesystem, spawn processes or touch tokens. Everything privileged is a named channel on a typed, validated IPC surface in the main process.
- Every IPC payload is parsed with a schema before it is used.
- Channel names are an allowlist, not a dispatch string.
- The renderer receives plain view models, never raw tokens or file handles.
- Navigation to external URLs is blocked in-app and opened in the system browser.
Authentication, end to end
Signing in runs the official Microsoft OAuth flow in the main process, exchanges the authorization code through Xbox Live and XSTS, then validates Minecraft ownership before a profile is stored. Refresh tokens are encrypted with the operating system keystore; access tokens live in memory and expire on their own schedule. Passwords are never requested and never stored.
The renderer should never be able to answer the question ‘what is the user's token’ — only ‘who is signed in’.
Downloads that verify themselves
Game assets, libraries and mod files are fetched into a staging directory, hashed, and only moved into the instance once the digest matches the manifest. A failed hash is a failed download — never a launch with a truncated jar. Transfers are resumable, so a dropped connection costs seconds, not the whole file.
This is why the release pipeline publishes a checksum manifest next to the binaries rather than trusting a download page: if the digest of the file you received does not match the published one, you do not run it. The verification report and security summary ship as release assets so the claim can be checked, not just read.
Next post
What performance profiles actually change