Release SecureDrop 1.1.0

[emkll]

This is a tracking issue for the upcoming release of SecureDrop 1.1.0 - tasks may get added or modified.

String and feature freeze: 2019-10-08 (1700 PDT)
String comment period: 2019-10-08 (1700 PDT) to 2019-10-15 (2000 PDT)
Feature freeze: 2019-10-08 (1700 PDT) (release branch will be cut AM Eastern time on September 3rd)
Translation period: 2019-10-08 (1700 PDT) to 2019-10-18 (1700 PDT)
Pre-release announcement: 2019-10-15
Translation freeze: 2019-10-18 (1700 PDT)
Release date: 2019-10-21

Release manager: @kushaldas
Deputy release manager: @emkll
Localization manager: @rmol
Deputy localization manager: @redshiftzero

SecureDrop maintainers and testers: As you QA 1.1.0, 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.1.0 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.1.0

Test Plan for 1.1.0

Prepare release candidate (1.1.0~rc1)

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

Prepare release candidate (1.1.0~rc2)

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

Prepare release candidate (1.1.0~rc3)

• Prepare 1.1.0-rc3 release changelog - @kushaldas
• Prepare 1.1.0~rc3 - @kushaldas
• Build debs and put up 1.1.0~rc3 on test apt server (this is now done via a PR into this repository) - @emkll
• Commit build logs to https://github.com/freedomofpress/build-logs - @emkll I forgot :(

Prepare release candidate (1.1.0~rc4)

• Prepare 1.1.0-rc4 release changelog - @emkll
• Prepare 1.1.0~rc4 - @emkll
• Build debs and put up 1.1.0~rc4 on test apt server (this is now done via a PR into this repository) - @emkll : Add securedrop 1.1.0-rc4 debs securedrop-apt-test#19
• Commit build logs to https://github.com/freedomofpress/build-logs - @emkll

Prepare release candidate (1.1.0~rc5)

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

Other pre-release tasks

• Prepare and distribute pre-release messaging - @eloquence

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

Final release

• Ensure builder in release branch is updated and/or update builder image - @emkll
• Merge final translations @rmol
• Push signed tag @emkll
• Build final Debian packages for 1.1.0 (and preserve build logs) @conorsch
• Commit package build logs to https://github.com/freedomofpress/build-logs @conorsch : https://github.com/freedomofpress/build-logs/blob/master/core/20191021-securedrop-1.1.0.log
• Upload Debian packages to apt QA server @conorsch
• Pre-Flight: Test install and upgrade (both cron-apt on Xenial, and Ansible on Xenial) of 1.1.0 works w/ prod repo debs, test updater logic in Tails @zenmonkeykstop @redshiftzero @emkll
• Prepare and distribute release messaging @eloquence

Post release

• Create GitHub release object @emkll
• Merge changelog back to develop
• Bump version on develop in prep for 1.2.0 release
• Update upgrade testing boxes
• Update roadmap wiki page @emkll

[emkll]

Cron-apt upgrade 1.0.0 -> 1.1.0 in VMs (Completed)

Environment

• Install target: Vagrant VMs
• Tails version: 3.16 (because cron-apt)
• Test Scenario: cron-apt upgrade
• SSH over Tor: No
• Onion service version: v2 and V3
• Release candidate: 1.1.0-rc2
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor Local network
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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 (to 1.0.0)

1.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options
  note: Not sure if seeing DANGER!!!!! in the manage.py is. It might be worth investigating exposing that functionality only if we detect it's running in the dev container (perhaps env var?).

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 3.16

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• A spinning cursor is displayed when Source or Journalist icons are double-clicked
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password

Tails 4.0 - DID NOT TEST

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged) DID NOT TEST

• (TBD, not yet merged) Czech and Slovak are displayed on the interface if enabled in SDCONFIG

[rmol]

Cron-apt upgrade 1.0.0 -> 1.1.0 on NUC7i5BNH (Completed)

Environment

• Install target: NUC7i5BNH
• Tails version 3.16
• Test Scenario: cron-apt update
• SSH over Tor: yes
• Onion service version: v2+v3
• Release candidate: 1.1.0~rc2
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 3.16

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• A spinning cursor is displayed when Source or Journalist icons are double-clicked
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password

Tails 4.0

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged)

• (TBD, not yet merged) Czech and Slovak are displayed on the
  interface if enabled in SDCONFIG
  • Czech is working as of rc2

[eloquence]

Pre-release messaging is live:

• Blog post
• Tweet
• Support portal bulk announcement completed

[rmol]

Clean install of 1.1.0-rc3 on NUC7i5BNH (Completed)

Environment

• Install target: NUC7i5BNH
• Tails version: 4.0rc1
• Test Scenario: clean install
• SSH over Tor: yes
• Onion service version: installed with v2, with v3 added later
• Release candidate: 1.1.0~rc3
• General notes: Tails upgraded from 3.16 to 4.0rc1

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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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
  • NOTE: the updater breaks when 1.0.0 is checked out

1.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 4.0 (rc1, upgraded from 3.16)

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new
  version of Keepass in Tails 4
  - NOTE: Did not; forgot. Another tester is covering this.

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged)

• (TBD, not yet merged) Czech and Slovak are displayed on the
  interface if enabled in SDCONFIG
  - [x] Czech is working

[kushaldas]

Cron-apt upgrade 1.0.0 -> 1.1.0-rc4 in VMs (Completed)

Environment

• Install target: Vagrant VMs
• Tails version: 4.0-rc1 (because cron-apt)
• Test Scenario: cron-apt upgrade
• SSH over Tor: No
• Onion service version: v2 and V3
• Release candidate: 1.1.0-rc4
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor Local network
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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 (to 1.0.0)

1.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 4.0

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4 (did not test)

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged) DID NOT TEST

• (TBD, not yet merged) Czech and Slovak are displayed on the interface if enabled in SDCONFIG

[emkll]

1.1.0-rc5 Clean install (complete)

Environment

• Install target: Vagrant prod vms
• Tails version: 4.0-rc1 (Clean install)
• Test Scenario: Clean install
• SSH over Tor: Yes
• Onion service version: v2 + v3
• Release candidate: 1.1.0-rc5
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 3.16

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• A spinning cursor is displayed when Source or Journalist icons are double-clicked
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password

Tails 4.0

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged)

• (TBD, not yet merged) Czech and Slovak are displayed on the interface if enabled in SDCONFIG

rc3-specific testing

We want to ensure the virtualenv transition when upgrading from Tails 3.x to Tails 4.x is handled by ./securedrop-admin

• Test plan from 4914 completes successfully

[kushaldas]

1.1.0-rc5 upgrade (complete)

Environment

• Install target: Vagrant prod vms
• Tails version: 4.0-rc1 (Upgraded from 3.16)
• Test Scenario: Upgrade from 1.0.0
• SSH over Tor: No
• Onion service version: v3
• Release candidate: 1.1.0-rc5
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 1.0.0 and restore this backup on 1.1.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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

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.1.0-specific changes

• Tor version running is 0.4.1.6

manage.py

• Running manage.py in /var/www/securedrop/ returns a correct and ordered list of options

securedrop-app-code dependencies

• cron-apt update was successful (if upgrade scenario)

Securedrop-admin

Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.

Tails 3.16

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• A spinning cursor is displayed when Source or Journalist icons are double-clicked
• Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password

Tails 4.0

• ./securedrop-admin setup works as expected
• ./securedrop-admin sdconfig works as expected
• ./securedrop-admin install works as expected
• ./securedrop-admin tailsconfig works as expected
• ./securedrop-admin backup works as expected
• ./securedrop-admin restore works as expected
• Desktop icon is functional for Source and Journalist interfaces
• x ] Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
• Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4

Dependency update

• There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries

New Languages (TBD, languages not yet merged)

• (TBD, not yet merged) Czech and Slovak are displayed on the interface if enabled in SDCONFIG

rc3-specific testing

We want to ensure the virtualenv transition when upgrading from Tails 3.x to Tails 4.x is handled by ./securedrop-admin

• Test plan from 4914 completes successfully

[eloquence]

Release comms completed.

Tweet:
https://twitter.com/SecureDrop/status/1186403427997245440

Blog post:
https://securedrop.org/news/securedrop-110-released/

Redmine bulk announcement completed.

We'll do another tweet tomorrow when the Tails 4 release is out.