build and host the dangerzone docker image ourselves
the flmcode/dangerzone
docker image that we use is out of date by several months, and is vulnerable to the (low risk) CVE-2023-39342. i think this is due to FPF adopting dangerzone, and the freelookmedia team no longer maintaining the code.
FPF doesn't publish a docker image for dangerzone, so we would need to manually build and host the image ourselves. now that we have a container registry, that's something we can actually do! this particular image is pretty big (over a gigabyte) so perhaps a TPA-RFC is the right way to go with this ticket
Edited by Kez