SecureDrop 2.15.1 is now available. This release improves the memory management used by the SecureDrop application when responding to v2 Journalist API requests (#7809), and fixes an issue where restoring backups without transferring over the network would previously fail (#7802).

This update will be installed automatically via the daily update process. No further action is required.

Acknowledgments

This release incorporates Freedom of the Press Foundation (FPF) contributions by Martin C; Nathan Dyer, communications manager; Micah Lee; Kunal Mehta; Cory Francis Myers, release manager; Vicki Niu; Kevin O’Gorman; Francisco Rocha; John Skinner; and Rowen S.

Questions and comments

If you have questions or comments regarding this release, please contact us:

• Via Signal, either in your dedicated SecureDrop support group, or by contacting the support account listed at securedrop.org/help/.
• Via securedrop@freedom.press (PGP encrypted) for sensitive security issues (please use judiciously), or submit a report via Bugcrowd.

We also encourage you to file nonsensitive issues via our GitHub repository. Thank you for using SecureDrop!