Release SecureDrop 1.2.1

[rmol]

This is a tracking issue for the release of SecureDrop 1.2.1.

The 1.2.1 release will contain no new strings requiring translation.

Feature freeze: 2020-02-12 (1700 PST)
Release date: 2019-12-19

Release manager: @rmol
Deputy release manager: @zenmonkeykstop

SecureDrop maintainers and testers: As you QA 1.2.1, please report back your testing results as comments on this ticket. File GitHub issues for any problems found, tag them "QA: Release", and associate them with the 1.2.1 milestone for tracking (or ask a maintainer to do so).

Test debian packages will be posted on https://apt-test.freedom.press signed with the test key. An Ansible playbook testing the upgrade path is here.

QA Matrix for 1.2.1

Test Plan for 1.2.1

Prepare release candidate (1.2.1~rc1)

• Prepare 1.2.1-rc1 release changelog
• Branch off release/1.2.1
• Prepare 1.2.1~rc1
• Build debs and put up 1.2.1~rc1 on test apt server (this is now done via a PR into this repository)
• Commit build logs to https://github.com/freedomofpress/build-logs

After each test, please update the QA matrix and post details for Basic Server Testing, Application Acceptance Testing and 1.2.1-specific testing below in comments to this ticket.

Final release

• Ensure builder in release branch is updated and/or update builder image
• Push signed tag
• Build final Debian packages for 1.2.1 (and preserve build logs)
• Commit package build logs to https://github.com/freedomofpress/build-logs
• Upload Debian packages to apt QA server
• Pre-Flight: Test install and upgrade (both cron-apt on Xenial, and Ansible on Xenial) of 1.2.1 works w/ prod repo debs, test updater logic in Tails
• Prepare and distribute release messaging

Post release

• Create GitHub release object
• Merge changelog back to develop
• Update upgrade testing boxes
• Update roadmap wiki page

[kushaldas]

Environment

• Install target: VM
• Tails version: 4.2
• Test Scenario:
• SSH over Tor: Yes
• Onion service version: 3
• Release candidate: rc1
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor
• AppArmor is loaded on app
  • 0 processes are running unconfined
• AppArmor is loaded on mon
  • 0 processes are running unconfined
• Both servers are running grsec kernels
• iptables rules loaded
• OSSEC emails begin to flow after install
• OSSEC emails are decrypted to correct key and I am able to decrypt them
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

Administration

• I have backed up and successfully restored the app server following the backup documentation
• If doing upgrade testing, make a backup on 1.2.0 and restore this backup on 1.2.1
• If doing upgrade testing, verify that document submission via the Source Interface is enabled after the upgrade is complete
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent
• Can successfully add journalist account with HOTP authentication

Application Acceptance Testing

Source Interface

Landing page base cases

• JS warning bar does not appear when using Security Slider high
• JS warning bar does appear when using Security Slider Low

First submission base cases

• On generate page, refreshing codename produces a new 7-word codename
• On submit page, empty submissions produce flashed message
• On submit page, short message submitted successfully
• On submit page, file greater than 500 MB produces "The connection was reset" in Tor Browser quickly before the entire file is uploaded
• On submit page, file less than 500 MB submitted successfully

Returning source base cases

• Nonexistent codename cannot log in
• Empty codename cannot log in
• Legitimate codename can log in
• Returning user can view journalist replies - need to log into journalist interface to test

Journalist Interface

Login base cases

• Can log in with 2FA tokens
• incorrect password cannot log in
• invalid 2fa token cannot log in
• 2fa immediate reuse cannot log in
• Journalist account with HOTP can log in

Index base cases

• Filter by codename works
• Starring and unstarring works
• Click select all selects all submissions
• Selecting all and clicking "Download" works

Individual source page

• You can submit a reply and a flashed message and new row appears
• You cannot submit an empty reply
• Clicking "Delete Source And Submissions" and the source and docs are deleted
• You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

After updating to this release candidate and running securedrop-admin tailsconfig

• The Updater GUI appears on boot
• Updating occurs without issue

1.2.1-specific changes

• Confirm that Tor Browser is properly detected (Update UA regex to match TB9 user agent strings #5087)
• Confirm that there is no longer an option in the journalist interface to change a source's codename and designation. (remove "Change codename" feature in Journalist Interface #4304)
• Check the caching of source keys for the get_all_sources API endpoint (Cache CryptoUtil.getkey (redshiftzero's idea) #5100) (you probably want to do this at the end of all your testing):
  • Add sources with qa_loader.py
  • Confirm that the endpoint is returning all sources
  • Confirm that there is no cold-start penalty; the first call to the endpoint after Apache is started should not take longer than subsequent requests

Preflight

• Ensure the builder image is up-to-date on release day

These tests should be performed the day of release prior to live Debian packages on apt.freedom.press

Basic testing

• Install or upgrade occurs without error
• Source interface is available and version string indicates it is 1.2.1
• A message can be successfully submitted

Tails

• The updater GUI appears on boot
• The update successfully occurs to 1.2.1
• After reboot, updater GUI no longer appears

[rmol]

Environment

• Install target: NUC7i5BNH
• Tails version: 4.3
• Test Scenario: cron-apt upgrade
• SSH over Tor: yes
• Onion service version: 2+3
• Release candidate: 1.2.1~rc1
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor
• AppArmor is loaded on app
  • 0 processes are running unconfined
• AppArmor is loaded on mon
  • 0 processes are running unconfined
• Both servers are running grsec kernels
• iptables rules loaded
• OSSEC emails begin to flow after install
• OSSEC emails are decrypted to correct key and I am able to decrypt them
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

Administration

• I have backed up and successfully restored the app server following the backup documentation
• If doing upgrade testing, make a backup on 1.2.0 and restore this backup on 1.2.1
• If doing upgrade testing, verify that document submission via the Source Interface is enabled after the upgrade is complete
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent
• Can successfully add journalist account with HOTP authentication

Application Acceptance Testing

Source Interface

Landing page base cases

• JS warning bar does not appear when using Security Slider high
• JS warning bar does appear when using Security Slider Low

First submission base cases

• On generate page, refreshing codename produces a new 7-word codename
• On submit page, empty submissions produce flashed message
• On submit page, short message submitted successfully
• On submit page, file greater than 500 MB produces "The connection was reset" in Tor Browser quickly before the entire file is uploaded
• On submit page, file less than 500 MB submitted successfully

Returning source base cases

• Nonexistent codename cannot log in
• Empty codename cannot log in
• Legitimate codename can log in
• Returning user can view journalist replies - need to log into journalist interface to test

Journalist Interface

Login base cases

• Can log in with 2FA tokens
• incorrect password cannot log in
• invalid 2fa token cannot log in
• 2fa immediate reuse cannot log in
• Journalist account with HOTP can log in

Index base cases

• Filter by codename works
• Starring and unstarring works
• Click select all selects all submissions
• Selecting all and clicking "Download" works

Individual source page

• You can submit a reply and a flashed message and new row appears
• You cannot submit an empty reply
• Clicking "Delete Source And Submissions" and the source and docs are deleted
• You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

After updating to this release candidate and running securedrop-admin tailsconfig

• The Updater GUI appears on boot
• Updating occurs without issue

1.2.1-specific changes

• Confirm that Tor Browser is properly detected (Update UA regex to match TB9 user agent strings #5087)
• Confirm that there is no longer an option in the journalist interface to change a source's codename and designation. (remove "Change codename" feature in Journalist Interface #4304)
• Check the caching of source keys for the get_all_sources API endpoint (Cache CryptoUtil.getkey (redshiftzero's idea) #5100) (you probably want to do this at the end of all your testing):
  • Add sources with qa_loader.py
  • Confirm that the endpoint is returning all sources
  • Confirm that there is no cold-start penalty; the first call to the endpoint after Apache is started should not take longer than subsequent requests

[rmol]

Environment

• Install target: NUC7i5BNH
• Tails version: 4.3
• Test Scenario: clean install
• SSH over Tor: yes
• Onion service version: 2+3
• Release candidate: 1.2.1~rc1
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor
• AppArmor is loaded on app
  • 0 processes are running unconfined
• AppArmor is loaded on mon
  • 0 processes are running unconfined
• Both servers are running grsec kernels
• iptables rules loaded
• OSSEC emails begin to flow after install
• OSSEC emails are decrypted to correct key and I am able to decrypt them
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

Administration

• I have backed up and successfully restored the app server following the backup documentation
• If doing upgrade testing, make a backup on 1.2.0 and restore this backup on 1.2.1
• If doing upgrade testing, verify that document submission via the Source Interface is enabled after the upgrade is complete
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent
• Can successfully add journalist account with HOTP authentication

Application Acceptance Testing

Source Interface

Landing page base cases

• JS warning bar does not appear when using Security Slider high
• JS warning bar does appear when using Security Slider Low

First submission base cases

• On generate page, refreshing codename produces a new 7-word codename
• On submit page, empty submissions produce flashed message
• On submit page, short message submitted successfully
• On submit page, file greater than 500 MB produces "The connection was reset" in Tor Browser quickly before the entire file is uploaded
• On submit page, file less than 500 MB submitted successfully

Returning source base cases

• Nonexistent codename cannot log in
• Empty codename cannot log in
• Legitimate codename can log in
• Returning user can view journalist replies - need to log into journalist interface to test

Journalist Interface

Login base cases

• Can log in with 2FA tokens
• incorrect password cannot log in
• invalid 2fa token cannot log in
• 2fa immediate reuse cannot log in
• Journalist account with HOTP can log in

Index base cases

• Filter by codename works
• Starring and unstarring works
• Click select all selects all submissions
• Selecting all and clicking "Download" works

Individual source page

• You can submit a reply and a flashed message and new row appears
• You cannot submit an empty reply
• Clicking "Delete Source And Submissions" and the source and docs are deleted
• You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

After updating to this release candidate and running securedrop-admin tailsconfig

• The Updater GUI appears on boot
• Updating occurs without issue

1.2.1-specific changes

• Confirm that Tor Browser is properly detected (Update UA regex to match TB9 user agent strings #5087)
• Confirm that there is no longer an option in the journalist interface to change a source's codename and designation. (remove "Change codename" feature in Journalist Interface #4304)
• Check the caching of source keys for the get_all_sources API endpoint (Cache CryptoUtil.getkey (redshiftzero's idea) #5100) (you probably want to do this at the end of all your testing):
  • Add sources with qa_loader.py
  • Confirm that the endpoint is returning all sources
  • Confirm that there is no cold-start penalty; the first call to the endpoint after Apache is started should not take longer than subsequent requests

[zenmonkeykstop]

1.2.1 QA plan

As 1.2.1 includes no kernel or admin changes, we're testing on a subset of supported hardware:

• NUC7s
• Mac Minis

1.2.1 QA Checklist

For both upgrades and fresh installs, here is a list of functionality that requires testing. You can use this for copy/pasting into your QA report. Feel free to edit this message to update the plan as appropriate.

If you have submitted a QA report already for a 1.2.1 release candidate with successful basic server testing and application acceptance testing sections, then you can skip these sections in subsequent reports, unless otherwise indicated by the Release Manager. This is to ensure that you focus your QA effort on the 1.2.1-specific changes as well as changes since the previous release candidate.

Environment

• Install target: Mac Mini
• Tails version: 4.3
• Test Scenario: fresh install
• SSH over Tor: yes
• Onion service version: v3
• Release candidate: rc1
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor
• AppArmor is loaded on app
  • 0 processes are running unconfined
• AppArmor is loaded on mon
  • 0 processes are running unconfined
• Both servers are running grsec kernels
• iptables rules loaded
• OSSEC emails begin to flow after install
• OSSEC emails are decrypted to correct key and I am able to decrypt them
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

Administration

• I have backed up and successfully restored the app server following the backup documentation
• If doing upgrade testing, make a backup on 1.2.0 and restore this backup on 1.2.1 N/A
• If doing upgrade testing, verify that document submission via the Source Interface is enabled after the upgrade is complete N/A
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent
• Can successfully add journalist account with HOTP authentication not tested

Application Acceptance Testing

Source Interface

Landing page base cases

• JS warning bar does not appear when using Security Slider high
• JS warning bar does appear when using Security Slider Low

First submission base cases

• On generate page, refreshing codename produces a new 7-word codename
• On submit page, empty submissions produce flashed message
• On submit page, short message submitted successfully
• On submit page, file greater than 500 MB produces "The connection was reset" in Tor Browser quickly before the entire file is uploaded
• On submit page, file less than 500 MB submitted successfully

Returning source base cases

• Nonexistent codename cannot log in
• Empty codename cannot log in
• Legitimate codename can log in
• Returning user can view journalist replies - need to log into journalist interface to test

Journalist Interface

Login base cases

• Can log in with 2FA tokens
• incorrect password cannot log in
• invalid 2fa token cannot log in
• 2fa immediate reuse cannot log in
• Journalist account with HOTP can log in not tested

Index base cases

• Filter by codename works
• Starring and unstarring works
• Click select all selects all submissions
• Selecting all and clicking "Download" works

Individual source page

• You can submit a reply and a flashed message and new row appears
• You cannot submit an empty reply
• Clicking "Delete Source And Submissions" and the source and docs are deleted
• You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

After updating to this release candidate and running securedrop-admin tailsconfig

• The Updater GUI appears on boot
• Updating occurs without issue

1.2.1-specific changes

• Confirm that Tor Browser is properly detected (Update UA regex to match TB9 user agent strings #5087)
• Confirm that there is no longer an option in the journalist interface to change a source's codename and designation. (remove "Change codename" feature in Journalist Interface #4304)
• Check the caching of source keys for the get_all_sources API endpoint (Cache CryptoUtil.getkey (redshiftzero's idea) #5100) (you probably want to do this at the end of all your testing):
  • Add sources with qa_loader.py
  • Confirm that the endpoint is returning all sources
  • Confirm that there is no cold-start penalty; the first call to the endpoint after Apache is started should not take longer than subsequent requests

Preflight

• Ensure the builder image is up-to-date on release day

These tests should be performed the day of release prior to live Debian packages on apt.freedom.press

Basic testing

• Install or upgrade occurs without error
• Source interface is available and version string indicates it is 1.2.1
• A message can be successfully submitted

Tails

• The updater GUI appears on boot
• The update successfully occurs to 1.2.1
• After reboot, updater GUI no longer appears