We’re excited to announce Fleet 3.6.0, which includes easier first-time setup, more flexible configuration, Amazon S3 integration for file carving, and more!
Let’s jump into the highlights…
- S3 buckets as file carving storage
- Build a Docker container with Fleet running as a non-root user
- Read in the MySQL password and JSON Web Token from a file
For the complete summary of changes check out the release notes on GitHub.
Amazon S3 buckets as file carving storage
Prior to these changes, file carving in Fleet could only be saved to the Fleet database. A couple of concerns with this limitation were surfaced by the Fleet community and Matteo’s contribution kicks off the ability to add more backends in the future.
Check out the new documentation on how to configure Fleet so file carving data is stored in an S3 bucket.
Build a Docker container with Fleet running as a non-root user
Shoutout to Ben Bornholm! The author of the sweet holdmybeersecurity.com packed in two contributions for this release. The first allows Fleet users to build the Docker container with Fleet running as a non-root user, an upgrade that aligns Fleet with Docker best practices.
Read in the MySQL password and JSON Web Token from a file
The second of Ben’s contributions adds support to read in your MySQL password and JWT from a file. With this addition, Fleet users can avoid storing secrets in a static configuration file or in environment variables.
Using Docker secrets for supplying the above credentials is an example use case of reading in such credentials.
Example config for Docker supplied by Ben
Upgrading to 3.6.0
Visit our Updating Fleet guide for instructions on how to update.