We’re pleased to announce that SecureDrop 2.4.1 has been released. This is a bugfix release. A complete list of changes can be found on GitHub.
What’s new in SecureDrop 2.4.1?
- Bugfix: SecureDrop 2.3.0 introduced an optional feature to prevent initial submission of a source’s secret seven word codename. The bug caused a server error for any initial messages containing non-ASCII characters. With this bugfix, the feature can be safely re-enabled in the submission preferences section of the admin Interface. (Issue, Pull Request)
What administrators need to do
SecureDrop Application and Monitor Servers will be updated to SecureDrop 2.4.1 automatically within 24 hours of the release. As with previous releases, we recommend that you update your Tails workstations to the latest version of Tails and the latest version of SecureDrop. Please see our upgrade guide for instructions.
Questions and comments
If you have questions or comments regarding this release, please contact us:
- Via our Support Portal, if you are a member (membership is available to SecureDrop administrators on request);
- Via firstname.lastname@example.org (GPG encrypted) for sensitive security issues (please use judiciously);
- Via our community forums.
We also encourage you to file non-sensitive issues you encounter in our GitHub repository (issue report form).
Thank you for using SecureDrop!