OpenProof 1.1.0-rc6 — October 24, 2026
This release candidate is built from the latest reviewed `main` source and supersedes `v1.1.0-rc5`.
Fixed: browser-session proliferation on repeat login
- JSON password/MFA login and OAuth browser-form login now replace the previous valid browser session cookie after successful verification. The earlier session is revoked only after a new one is saved, and other sessions remain untouched.
- A failed password or MFA attempt does not issue a session or revoke an existing session. Revocation failures do not expose a newly issued token.
- Session records are not deduplicated by User-Agent or IP; those fields are not secure device identifiers. Pre-existing sessions may be revoked manually from Account Security.
- New C++ integration and session-service regression tests cover failed proof, session replacement, and isolation between browsers with identical User-Agent metadata.
Security and operational improvements
- Documentation MCP source dependencies updated to `@modelcontextprotocol/[email protected]` and `[email protected]`, with patched transitive dependencies. The lockfile passed `npm audit --audit-level=moderate` with zero known vulnerabilities at release preparation time.
- CI and tag-triggered Release workflow now perform Docs MCP dependency security checks and public MCP client-protocol smoke tests before packaging/publishing.
- Includes Argon2id password-hash upgrade guidance and earlier OAuth/SDK hardening from the merged main branch.
- OpenAPI, SDK metadata, installation examples, handbook and VERSION synchronized to `1.1.0-rc6`.
- Both Linux amd64/arm64 and Debian packages are built from the release tag and must pass full C++ tests plus migration-inventory validation. Verify distributed archives with `SHA256SUMS`.
Scope and deployment
- The Genyleap website JavaScript adjustments for post-login recovery, session labeling and duplicate form submission were deployed separately and are not part of the OpenProof server binary package.
- This is a pre-release, not a stable general-availability release. GitHub Release publication does not automatically upgrade customized production installations.
- Release checks demonstrate the tested build under supported conditions; they do not guarantee that all vulnerabilities or logic defects are absent.