WAMF v0.4.2¶
Released 27 October 2026. GitHub release
v0.4.2 is a security and setup maintenance release for the v0.4 series. It retains Python 3.11, the existing CPU TFLite classifier and AMD64 deployment scope. It does not introduce Kingfisher features or a new detection architecture.
What Changed¶
- Detection-card values are rendered as text/data rather than executable HTML, and Frigate event identifiers are validated before ingestion, requests, publication and archiving.
- Login throttling ignores spoofable forwarding headers and preserves limits across concurrent attempts and overflow handling.
- Frigate media proxy paths, redirects, streaming cleanup and forwarded headers are hardened. Login destinations and Wikipedia redirects are validated.
- Corrected responses and diagnostic logs avoid YAML source excerpts, credential-bearing exception text and unescaped control characters.
- Monaco Editor 0.52.2 and its workers are served locally with licence and provenance records. External Bootstrap and jQuery assets use SHA-384 integrity checks and anonymous CORS.
- The mobile navigation hamburger and collapse controls are restored.
- The test dependency pytest is updated to 9.0.3.
First-run Setup¶
Fresh authentication-enabled installations print a private, single-use
/setup#token=... link instead of a temporary administrator password.
Choose a password within 15 minutes. Restarting pending setup invalidates the
old link; HTTP requests cannot renew it.
Operational workers pause until administrator setup succeeds and start when Frigate configuration is ready. Configuration changes use locked, mode-0600 atomic replacement, requiring a writable configuration-directory mount in Docker.
See Quick Start and Authentication. Protect startup logs, disable setup request-body capture, and use HTTPS or a trusted tunnel for remote setup.
Hardening Carried Forward from v0.4.1¶
Users upgrading directly from v0.4.0 also receive the v0.4.1 dependency and Docker changes:
- Updated Flask, Werkzeug, Requests, Pillow, certifi and urllib3, with constrained Python 3.11 runtime dependencies.
- A reviewed Python base-image digest and Debian package updates during builds.
- Removal of unused multimedia/OpenCV components.
- Build-time dependency checking and removal of pip, setuptools, wheel, packaging and ensurepip from the merged runtime filesystem.
- Compatibility handling for supported legacy administrator and API credentials, preserving existing hashes and session secrets.
These are carried-forward changes, not new v0.4.2 image-scan results. Removing files does not erase inherited image layers.
Installing or Upgrading¶
The versioned container reference is:
Use Docker Deployment for a new installation.
Existing provisioned v0.4.0/v0.4.1 installations with valid credentials require no data-format migration or credential reset. Stop WAMF cleanly and back up configuration, database and media together. Retain the previous image and reuse existing mounts, ports and session-secret settings.
Follow Updating WAMF for the upgrade and rollback procedure. Verify login, API access, archived media, MQTT detection and restart persistence afterwards.
Security Limitations and Validation Scope¶
This release does not eliminate all known vulnerabilities. The protobuf compatibility deferral, local packaging-tool risk acceptance and conditional setup-token risk acceptance remain, together with root-container, Flask, legacy-credential and native-library limitations. Read Security before deployment.
The tagged source release record reports 1,344 full-suite tests and 1,220 overlapping targeted security tests from the pre-metadata audit. These counts must not be added together or presented as a scan of the published container. That record retains pre-publication wording and outstanding image-verification conditions; it is not evidence of a completed v0.4.2 image-security scan.