Upgrading STINGAR v2 Platform
STINGARv2 Updates
Forewarned provides updates to Version 2 of STINGAR as minor release versions (e.g. 2.1, 2.2, ...) to keep up to date with the latest OS builds and dependencies and fix any reported bugs or vulnerabilities.
Update annoucements
The STINGAR slack channel is the primary communications tool for all such annoucements, along with forewarned.io/blog website and direct email notifications to the primary technical contact person at your institution.
Updating steps
These updates will be released as new docker images in the registry. The docker image tag labels will be updated for all docker images in the platform for any given minor release and a new docker-compose.yml file will be supplied referencing the new release version images.
In order to update your STINGAR version you will need to complete the following steps:
1) Backup your STINGAR honeypot data (see Backup Elasticsearch Data)
2) Stop your currently running STINGAR system
% docker-compose down
3) Backup your current STINGAR files
% cp docker-compose.yml docker-compose_ORIG.yml % cp stingar.env stingar_ORIG.env
4) Delete the existing docker images from the vm so they new images can be downloaded
% docker image prune -a
Risk of loss of honeypot data
The docker image prune command will not delete any of your persisted Honeypot details. However, there are other docker commands that could, please take care not to delete the docker volumes from your vm or you will lose your honeypot information and admin account password.
5) Replace the docker-compose.yml file with the latest version
% mv docker-compose-2.1.yml docker-compose.yml
6) Start the new version
% docker-compose up -d
See Reference example docker-compose.yml for v2.1