v9.4.0

Two ways in that did not exist before: the viewer can sign in through your own OpenID Connect provider, and the backup can log in to Telegram with a QR code when the verification code never arrives. No migration. Docker deployments only need the new pins.

Added

• OpenID Connect single sign-on. Set OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET and OIDC_REDIRECT_URI and the login page offers a single sign-on button. See Single sign-on with OpenID Connect. Thanks to @jordanfelle. (#588)
• Log in with a QR code when the verification code never arrives. telegram-archive auth --qr shows a QR code in the terminal; scan it from a Telegram app that is already logged in (Settings > Devices > Link Desktop Device) and no code is needed. Typing qr at the code prompt does the same. Telegram sometimes never delivers the login code to third-party apps, and it stopped sending SMS codes to them in 2023, so this was the only way in for some accounts. Two-step verification and the phone number check work as before; the 2FA password is not echoed on this path. Adds the qrcode package. (#590)

Security

• opentelemetry-api 1.45.1 in both images. 1.45.0 parsed a long tracestate header in quadratic time. The archive never reads tracing headers, so this is hygiene. (#589)

---

📋 Full changelog: docs/CHANGELOG.md