1.6.3
A security fix for the web robot engine on self-hosted installs. Update soon, and with Docker Compose take the compose file from this version.
Action needed before you update
Before
With Docker Compose, get this version's compose file. It gives the robot engine the one extra permission it needs to start its network protections.
git pullAfter
Check the robot engine's log. It should say that egress to 169.254.0.0/16 is blocked.
docker compose logs scraper-engine | grep entrypointSecurity
- On self-hosted installs the web robot engine started without the permission it uses to block robots from reaching the cloud metadata address and private networks, so those blocks were off. Update soon, especially on a cloud server.
- With Helm, the engine now starts with that permission and drops to an unprivileged user right after setting the blocks.
Fixed
- Site-wide crawling works on self-hosted installs. It was turned off because the same blocks could not be set.
Update commands
# .env
WAISO_VERSION=1.6.3
docker compose pull && docker compose up -d --remove-orphans