1.2.0 Test plan

QA plan

• NUC5s
• NUC7s
• Mac Minis
• 1U test servers

1.2.0 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.0 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.0-specific changes as well as changes since the previous release candidate.

Environment

• Install target:
• Tails version:
• Test Scenario:
• SSH over Tor:
• Onion service version:
• Release candidate:
• 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.1.0 and restore this backup on 1.2.0
• If doing upgrade testing, verify that document submission via the Source Interface are enabled after the upgrade is complete #4879
• "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

• Reply option is available #4909
• 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.0-specific changes

• Kernel version running is 4.14.154-grsec #4990
• Alt text for the SecureDrop logo is "Logo Image" #4980
• API response for valid /token POST request includes journalist_first_name and journalist_last_name fields, with correct values for user requesting token #4971

Systemd replacing supervisor #4855

• The supervisor package is not installed on the Application Server
• Submit a message via the Source Interface:
  • A hash was generated for the message in the submissions table
  • The hashing operation is logged - check via sudo journalctl -u securedrop_rqworker --no-pager on the Application Server
• Add a reply to the source via the Journalist Interface, then delete the message and finally the collection:
  • The deletions are logged - check via journalctl -f -u securedrop_shredder --no-pager, checking once, then 60 seconds later
  • The submission and reply files are deleted from /var/lib/securedrop/store and /var/lib/securedrop/shredder
• Submit a large file (>100MB) via the Source Interface:
  • A hash was generated for the file in the submissions table
  • The hashing operation is logged - check via sudo journalctl -u securedrop_rqworker --no-pager on the Application Server
• Delete the submission via the Journalist Interface:
  • The deletion is logged - check via journalctl -f -u securedrop_shredder --no-pager, checking once, then 60 seconds later
  • The submission file is deleted from /var/lib/securedrop/store and /var/lib/securedrop/shredder
• Submit multiple messages as different sources via the Source Interface and delete them by choosing Select All and Delete from the Journalist Interface:
  • Deletions are logged in the securedrop_shredder logs.
  • The /var/lib/securedrop/store directory is not deleted on the Application Server #5031

Disabling document uploads #4879

• A Prevent sources from uploading documents checkbox is available under Instance Config on the Journalist Interface.
• Submit a document on the Source Interface, then disable document uploads on the Journalist Interface, by selecting the checkbox and clicking Update Submission Preferences:
  • The Source Interface does not display an option to upload files
  • The previous submission is visible and can be downloaded from the Journalist Interface
• Submit a message on the Source Interface:
  • The message was successfully submitted
  • The message is visible and can be downloaded in the Journalist Interface
• Enable document uploads on the Journalist Interface:
  • The Source interface displays an option to upload files
  • The previous submissions are visible and can be downloaded from the Journalist Interface
• Submit a new file and message via the Source Interface:
  • The submissions complete successfully
  • All submissions above are visible and can be downloaded from the Journalist Interface

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.0
• A message can be successfully submitted

Tails

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