1.8.2 Test Plan

1.8.2 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.

If you have submitted a QA report already for a 1.8.2 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.8.2-specific changes as well as changes since the previous release candidate.

Note: in order to test the upgrade scenario with an SMTP server that requires From: addresses to match the authenticated user, the ossec_from_address variable must be set appropriately in site-specific for the initial ``1.8.1` install.

Environment

Install target:
Server OS:
Tails version:
Test Scenario:
SSH over Tor:
Onion service version:
Release candidate:
General notes:

Basic Server Testing

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.8.1 and restore this backup on this release candidate
"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 Account" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

Basic Tails Testing

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

The Updater GUI appears on boot
Updating occurs without issue

1.8.2 release-specific changes

Use actual hostname in Postfix generic db #5924
- on mon, the myhostname variable in /etc/postfix/main.cf is set to the server hostname
- on mon, the smtp_generic_maps variable in /etc/postfix/main.cf is set to hash:/etc/postfix/generic
- on mon, /etc/postfix/generic exists and contains a line matching the address ossec@mon (or ossec@<non-standard hostname>) with the SMTP address used to deliver OSSEC messages
- OSSEC mail alerts are being sent successfully.
Backup file not copied locally during restore #5919
- On the Admin Workstation, create a large backup file using an existing backup file (sd-backup.tar.gz using the following commands:
```
cd ~/Persistent/securedrop/install_files/ansible-base
dd if=/dev/urandom of=bigfile.rnd bs=1M count=1500  # this will take some time
gzip -d sd-backup.tar.gz
tar rvf sd-backup.tar bigfile.rnd
gzip sd-backup.tar
```
  then, use sd-backup.tar.gz to perform a restore, while monitoring diskspace usage in another terminal with watch -n 1 df -h
  - diskspace usage does not increase significantly during the Extract Tor configuration from backup task.
Add new pubkey for future securedrop release key rotation #5930
- After install/upgrade, the command ssh app sudo apt-key list lists entries for both the existing release key with fingerprint 22245C81E3BAEB4138B36061310F561200F4AD77 and the replacement key with fingerprint 2359E6538C0613E652955E6C188EDD3B7B22E6A3
- The command ssh app sudo apt-get update completes without error
- the GUI updater completes without error, and the command gpg --list-keys list both keys with fingerprints as above
POST method is used for JI /ossec-test-alert method #5947
- Log in to the JI as an admin and navigate to Admin > Instance config, then click SEND TEST OSSEC ALERT
  - Verify that the flash message indicates a test OSSEC alert was sent
- Log in to the JI as an admin and visit the URL http://<JI address>/ossec-test
  - Verify that a 405 error page is displayed
- Create a file with the content below, subbing in the JI address, and open it in the same browser session as your logged-in JI session, then click SUBMIT:
```
<html>
<body>
  <script>history.pushState('', '', '/')</script>
    <form method="post" action="http://127.0.0.1:8081/admin/ossec-test">
      <input type="submit" value="Submit request" />
    </form>
  </body>
</html>
```
  - Verify that you are logged out from the JI
  - Verify that and error is logged in the JI error log containing the text The CSRF token is invalid.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly