SecureDrop Noble Upgrade Progress
Upgrades to Ubuntu Noble are going strong, with approximately 40% of all Application Servers updated. Over the next week, we will push a series of point releases to begin automated upgrades of all remaining Application Servers, with Monitor Servers to follow. Read More
SecureDrop 2.12.3 Released
SecureDrop 2.12.3 has been released. This version enables the second phase of automated upgrades, and fixes a bug where failing the Noble migration check could disable unattended updates. Read More
SecureDrop 2.12.2 released
SecureDrop 2.12.2 has been released. This release enables the first phase of automated Noble upgrades and provides an additional check to verify the state of Ethernet interfaces prior to upgrade. Read More
SecureDrop Workstation 1.1.2 released
SecureDrop Workstation 1.1.2 has been released! This version removes the “sd-retain-logvm” that was created for forensic analysis purposes in response to a vulnerability disclosed in February. Read More
SecureDrop 2.12.1 released
SecureDrop 2.12.1 has been released. This is an Admin Workstation-only release, which improves the reliability of the semiautomated Ubuntu Noble upgrade when using SSH-over-Tor. Read More
Introducing WEBCAT: Web-based Code Assurance and Transparency
In this post, we introduce Web-based Code Assurance and Transparency, a project that supports verifiable in-browser code for single-page browser applications. Along with this post, we are publishing the WEBCAT project repository; follow-up posts will provide more detailed information. Read More
SecureDrop 2.12.0 released
SecureDrop 2.12.0 has been released, adding support for Ubuntu Noble, plus a semiautomated upgrade process. Administrators can upgrade themselves before April 15 or wait for our automated upgrade process after that date. Read More
SecureDrop 2.12.0 pre-release announcement
SecureDrop 2.12.0 is scheduled to be released on March 18, 2025, adding support for Ubuntu Noble, plus a semiautomated upgrade process. Administrators will have three weeks following the release to perform the semiautomated upgrade, or wait for our automated upgrade process after that period. Read More