Sandfly v6.0.0 release.
Important
Upgrade notes
- 🚨 Upgrading to Sandfly 6.0 will delete all existing results from the Sandfly database. All other data will be preserved, but fresh host scans will need to run to re-populate scan artifacts. (Sandfly now stores artifacts instead of individual Sandfly results in the database.)
- Postgres 14 has reached end-of-life. Sandfly installations prior to Sandfly 5.7.0 were installed with Postgres 14. If your installation is using Postgres 14 (after upgrading to Sandfly 6.0, you can view the Postgres version in the Settings -> About Sandfly page), Sandfly 6.0 includes a script to upgrade to Postgres 18. Shut down Sandfly with the
shutdown_sandfly.shscript, then run thesandfly-setup/setup/util_scripts/upgrade_postgres.shscript to upgrade the Sandfly postgres volume to 18. Thestart_postgres.shscript (called bystart_sandfly.shscript) automatically uses the correct Postgres version to match the data on disk. - Docker Compose and Kubernetes users (installations not using the traditional sandfly-startup scripts): In addition to updating the image versions, increase the Postgres max connections parameter to 90 in the docker-compose.yaml file or the Kubernetes deployment descriptor for Postgres.
Note: The release bundle, sandfly-setup-6.0.0.tgz, includes the offline Docker images. When installing on a server that doesn't have outside internet access, no additional steps are required. The setup and start scripts will use the Docker images included in this setup archive instead of requiring connectivity to Docker Hub and quay.io.