OpenFlux-mod v4.1.3

OpenFlux-mod v4.1.3

Downstream release built and tested from GitHub main.

• Functional baseline remains the proven Yandex v4 line.
• Safe authentication events are visible without debug logging.
• Versioned Router Panel integration shows Connected, Connecting, AUTH_BLOCKED and retained authentication errors.
• Generic semantic-version updates verify the binary, cookie helper and integration bundle together, with complete local rollback.
• Install OpenFlux itself on a Linux amd64 client or server using openflux-node.py.
• The server includes openfluxctl menu, release updates, rollback and direct cookie import.
• Cookie recovery files are created on the client from Router Panel or CLI; no Windows application is required.
• Optional signed and encrypted Yandex Disk recovery lets the server refresh cookies without inbound SSH.
• See integration/README.md for installer, pairing and dependency instructions.
• Dynamic Yandex bootstrap/session discovery is retained.
• First-tier showcaptchafast PoW is solved automatically.
• Persistent per-document Yandex cookie state is supported with an optional one-time browser seed.
• Second-tier SmartCaptcha enters AUTH_BLOCKED and makes no further Yandex requests until the cookie store changes.
• A safe openflux-yandex-cookie-import helper is included for browser cURL refresh without printing cookie values.
• Private 4-packet / 1 ms batching and current reliability hardening are retained.
• Volga is a separate opt-in runtime with a frozen profile, public-only egress and at most 64 concurrent connections.
• Legacy remains the default; installing this release does not switch protocols.
• One updater installs Legacy and Volga together, with one checkpoint and one rollback. Volga keeps its own container/service and cookies with explicit CPU and memory limits.
• Known limitation: Volga serves one mini-PC at a time per document pair. Stop it on one mini-PC before starting it on the other.
• Router Panel has one browser-cookie section per protocol with document links and server state. A Volga server without a client stays quiet.
• A Legacy session Yandex has revoked (a redirect loop through Yandex Passport) enters AUTH_BLOCKED like a SmartCaptcha. When Yandex answers but refuses the exit, retries slow down to one per 10 min; network failures keep quick retries. Cookies delivered by the Disk inbox are used without a restart.
• An idle Volga server keeps its editor sessions alive with the ping an open browser tab sends every minute, instead of re-authorizing every lane every 90 s; a safety renewal runs every 20 min. New cookies end an AUTH_BLOCKED wait within seconds.
• Cookie recovery calls Yandex Disk far less often: the server checks its inboxes every 2 min by metadata and publishes status on a change or every 10 min; clients fetch it every 5 min.
• No Yandex session token, private key, environment file or runtime secret is baked into the binary or container image.
• The exit-node runtime is packaged as a container image. Host networking is not required and no public container port is declared.
• Release creation does not deploy or restart running installations.

Container image:

ghcr.io/levl-max/openflux-mod:v4.1.3

Registry digest:

sha256:7cb7d5f2259ad9ca0b79416c2611b18fc4ff53484542db4727324ef628cc1c38

Historical production binary SHA256 remains recorded for comparison only:

6f242d3c7ef9184811e58df5893e0ad0095da6aeb7354ba02df5da99fa569715