VOR Stream 2026.2.1 is the first patch release on the v26.2 line and a security release. It updates the Python interpreter in the deployment package, limits the message broker’s encrypted connections to TLS 1.3, trims the offline installation bundle to the components the deployment uses, and adds a log of sign-in activity. Processes, models, studies and screens work as they do on v26.2.0, and the upgrade applies no database migrations.

Highlights

An updated Python interpreter

The deployment package builds Python 3.11.18, which carries the security fixes released since the version the package built before. The deployment rebuilds the interpreter and the shared and web application environments on each host.

Deploy outside job windows

Python nodes on a host fail for the length of the deployment while the interpreter is rebuilt. Playpen environments keep their packages and keep working; run venv/bin/python -m venv --upgrade venv in a playpen to move its environment to the new interpreter.

One behavior changes with the interpreter: parsing a malformed email address with Python’s email.utils.parseaddr returns an empty address rather than a partial one. A script of your own that parses addresses that way sees the difference.

A smaller offline installation bundle

The offline Ansible bundle in the deployment package carries Ansible’s core and the five collections the playbooks call, in place of the full Ansible distribution and its 106 collections. The collections that went unused brought their own test and development requirement files, which filled vulnerability scans run against the package with findings for software the deployment never executes. The installation procedure is unchanged; see Offline Installation.

Playbooks of your own

Playbooks you maintain alongside the deployment that use collections outside those five need those collections installed separately.

TLS 1.3 on the message broker

With TLS enabled, the message broker’s data and management listeners accept only TLS 1.3 connections. TLS 1.3 has no connection renegotiation, so security scans that report renegotiation (CVE-2009-3555) against the broker’s ports find nothing to report. The compute engine, Go and Python nodes, the secrets store and current browsers connect with TLS 1.3.

Check what connects to the broker from outside VOR Stream

A reverse proxy or load balancer in front of the broker’s management port must connect with TLS 1.3. An AWS Application Load Balancer does so only when its HTTPS listener uses a TLS 1.3 security policy; nginx before 1.23.4 needs proxy_ssl_protocols TLSv1.3. 

See Deploying Behind a Reverse Proxy.

 

A log of sign-in activity

The web application writes one line to django_auth.log in the log directory for each login, failed login and logout, and for each API call whose token it refuses. A line holds the time, the event, the sign-in method (identity provider, password or API token), the user, the reason a sign-in failed, and the client address. The log answers where login events are recorded; see Auth Log for the fields and reason codes, and Log Files for every file in the log directory.

Rotate the file without loosening it

A user who types a password into the username field leaves it in a failed-login line, so the playbooks create django_auth.log readable only by vor_user and vor_group. Nothing rotates the file; Log Files explains how to rotate it and keep that mode.

Stability & Quality Improvements

Jobs survive an SSH service restart on the compute host

OpenSSH 9.8 added a penalty that blocks an address whose connections close without attempting to authenticate. The service registry’s health check on the compute port closes connections that way, so within seconds of an SSH service restart the check’s address was blocked, and on a single-host installation that address is the compute engine’s. Jobs failed with a handshake error. The compute host’s SSH configuration turns off that one penalty and keeps the penalties for crashes, failed authentication and connections that stall before signing in.

Security updates

The release also includes these updates:

  • The token library behind the web application’s identity provider sign-in and behind Digital Teams moves to its patched release, closing an advisory where a token listing several issuers passed a check meant to accept one.
  • The PDF reader that Digital Teams uses to read uploaded documents moves to its patched release.
  • The image library behind Digital Teams moves to Pillow 13, clearing the advisories reported against the release it replaces.
  • The packaging library in the compute environment moves to its patched release.
  • The HTTP redirect library in the web interface’s dependencies moves to its patched release.

The deployment keeps the secrets store, service registry, message broker, web server, database, Erlang runtime and Go toolchain versions that v26.2.0 introduced; see Third-Party Software for the bundled versions.

Upgrading

Installations running v26.2.0 can upgrade directly. There are no database migrations and no breaking changes. Before deploying:

  • Plan the deployment outside job windows, since the Python interpreter is rebuilt on each host.
  • Confirm that anything connecting to the message broker from outside VOR Stream, such as a reverse proxy in front of its management port, uses TLS 1.3.
  • Add django_auth.log and django.log to your log rotation, keeping the restricted file mode described above.

Installations on versions prior to v26.2.0 should read the v26.2.0 release post as well, which covers the database upgrade, the sign-in token validity check, and the secrets store, service registry and message broker upgrades that release introduced.