The SecureDrop engineering team welcomes the contributions of security researchers. SecureDrop is relied on by sources to talk with journalists at dozens of news organizations, many of whom are taking significant risks to bring information to the public eye. We want to do everything we can to make the whistleblowing process as safe for them as possible. Testing by external security researchers is an important part of that process.
Today we are announcing the release of SecureDrop 0.4.3. This release:
The release of the next version of SecureDrop, 0.4.3, is scheduled for September 12th, 2017. We will send out another notification through our blog on securedrop.org, Twitter, and the support portal when the release goes live.
We have recently become aware of attacks attempting to exfiltrate data from the SecureDrop airgapped Secure Viewing Station. These attacks come in the form of QR codes that journalists must scan with an internet-connected device such as a phone. The QR code contains a link that sends exfiltrated data from the airgap environment to an attacker.
Today we are announcing the release of SecureDrop 0.4.2. This is a bugfix release to fix an issue with the AppArmor profile for Apache, which caused the Source and Journalist Interface web applications to fail. The root of the problem was an implicit dependency on upstream AppArmor abstractions from the Tor package, which has been resolved.
Today we are announcing the release of SecureDrop 0.4.1. This is a bugfix release to fix an issue with one of the scripts that configures the Tails workstation environment. If you encountered a permissions issue when running securedrop-admin tailsconfig, this release will fix that issue. We have updated our upgrade guide accordingly.
Today we are announcing the release of SecureDrop 0.4.
The release of the next version of SecureDrop, 0.4, is scheduled for July 25th, 2017. We will send out another notification through this blog on securedrop.org, Twitter, and the support portal when the release goes live.
Today we are announcing the release of SecureDrop 0.3.12. This release disables swap functionality on the Application Server, as originally intended by the first-run config used during install time. Instances will upgrade automatically, and any existing swap partitions will be deactivated, scrubbed, and disabled permanently. For full details, see the changelog.
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.