We recently discovered that the SecureDrop Application and Monitor servers have swapfiles enabled on production instances. This is not intended behavior, and was identified during the expansion of our automated testing efforts. We intended to disable swap during installation, and discovered that this setting was not persisting across reboots. Since the machines are configured to reboot nightly, to aid in clearing memory, the method currently used is ineffective.
Today we are announcing the release of SecureDrop 0.3.10. This release adds a new package, securedrop-keyring, to manage the public keys used to verify packages provided by the Freedom of the Press Foundation's apt package server.
Today we are announcing the release of SecureDrop 0.3.9. This release fixes several minor issues; for details, see the changelog.
Existing installations should upgrade automatically within the next 24 hours. If you have any questions, or experience difficulties with this upgrade, please create an issue on our support site.
Today we are announcing the release of SecureDrop 0.3.8, to fix a regression in 0.3.7 where a dependency of SecureDrop's Python web application was mistakenly removed from the list of dependencies. This regression did not impact already running production instances, but it prevented the successful installation of new SecureDrop 0.3.7 instances. The issue is fixed in 0.3.8 and new installations are working again.
Today we are announcing the release of SecureDrop 0.3.7. The important changes in this release are:
Today we are announcing the release of SecureDrop 0.3.6. If you are a SecureDrop administrator, please check your instance to ensure that you are running the latest version; if not, follow the instructions below to upgrade your system.
You can easily determine your SecureDrop version by visiting either of the web interfaces and looking for the "Powered by SecureDrop x.y.z" string at the bottom of the page. If your site reports 0.3.6, you do not need to take any further action for this release.
Today the Tow Center for Digital Journalism at Columbia Journalism School has published a first-of-its-kind study on how newsrooms are using SecureDrop, our open-source whistleblower submission system that is now in-use at over thirty news organizations worldwide.
In July, we announced the release of SecureDrop 0.3.4 and published the accompanying security audit by iSEC partners (now NCC Group). The audit found 10 issues, one of which – issue 7, Finding ID iSEC-15FTC-4 – was redacted. It was redacted because it was not an issue in SecureDrop itself, but in one of its dependencies.