Changed
-
Sign in by pairing. The editor shows a short code that you approve at mjolnircore.com/link while signed in. The key arrives on the next poll and is never seen or typed.
The flow it replaces produced a key with whatever permissions you happened to tick, usually with no expiry, dragged through the clipboard. What arrives by pairing asks only for what the editor needs, expires in 90 days, is named on your account page, and can be revoked there.
-
The approval page lists exactly what a client is asking for before you approve it, and warns more sharply when publishing is on the list — that approval puts your name on a release.
-
Existing paired launchers are unaffected and keep the permissions they had. There is no hand-off between the launcher and the editor: each pairs for itself, deliberately, so one desktop key cannot mint another.
Security
- The editor's stored key moves out of a plaintext settings file into Windows-protected storage, beside the signing key.
- The hub can now require that uploads be author-signed, ready for the point where a signing editor is what everyone is running.