Release SecureDrop 0.11.0

[kushaldas]

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

Feature freeze: November 27, 2018
String freeze: December 04, 2018
Pre-release announcement: December 04, 2018
Release date: December 11, 2018

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

Prepare release candidate (0.11.0~rc1)

• Prepare 0.11.0-rc1 release changelog - @kushaldas
• Branch off 0.11.0~rc1 into release/0.11.0 - @kushaldas
• Build debs (including new Tor package) and put up 0.11.0~rc1 on test apt server - @emkll

Prepare release candidate (0.11.0~rc2)

• Prepare 0.11.0-rc2 release changelog - @emkll
• Add 0.11.0~rc2 tag - @emkll
• Build debs and put up 0.11.0~rc2 on test apt server - @emkll

Prepare release candidate (0.11.0~rc3)

• Prepare 0.11.0-rc3 release changelog - @kushaldas
• Add 0.11.0~rc3 tag - @emkll
• Build debs and put up 0.11.0~rc3 on test apt server - @emkll

Prepare release candidate (0.11.0~rc4)

• Prepare 0.11.0-rc4 release changelog - @emkll
• Add 0.11.0~rc4 tag - @emkll
• Build debs and put up 0.11.0~rc4 on test apt server - @emkll

Prepare release candidate (0.11.0~rc5)

• Prepare 0.11.0-rc5 release changelog - @emkll
• Add 0.11.0~rc5 tag - @emkll
• Build debs and put up 0.11.0~rc5 on test apt server - @emkll

QA Matrix for 0.11.0

Test Plan for 0.11.0

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

Final release

• Ensure builder in release branch is updated and/or update builder image - @emkll or @msheiny
• Merge final translations - @kushaldas
• Push signed tag - @redshiftzero
• Build final Debian packages for 0.11.0 - @conorsch
• Upload Debian packages (including new linux-image, linux-firmware, and tor packages) to apt test - @conorsch
• Pre-Flight: Test install and upgrade of 0.11.0 works w/ prod repo debs, test updater logic in Tails - @zenmonkeykstop
• Write and send release announcement - @eloquence
• Publish blog post about 0.11.0 Debian package release and instructions for admins - @eloquence

Post release

• Merge changelog (i.e. rc commits) back to develop - @redshiftzero
• Bump version on develop in prep for 0.12.0 release - @redshiftzero
• Update upgrade testing boxes - @conorsch
• Update roadmap wiki page - @eloquence

[emkll]

(IN PROGRESS)

Environment

• Install target: Prod VMs
• Tails version: 3.10.1
• Test Scenario: Clean install
• SSH over Tor: No
• Release candidate: 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
• AppArmor is loaded on mon
• 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

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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• No screensaver in the source interface (Sunset the screensaver #3722)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[conorsh]

Hi @kushaldas, unfortunately I can't complete the task "Build final Debian packages for 0.11.0", you might need @conorsch to help with this.

[kushaldas]

Environment

• Install target: Prod VMs
• Tails version: 3.9.x
• Test Scenario: Update
• SSH over Tor: No
• Release candidate: 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
• AppArmor is loaded on mon
• 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

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 0.10.0 and restore this backup on 0.11.0.

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
• [ x 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 (did not test)
• Updating occurs without issue (did not test)

0.11.0-specific changes

• No screensaver in the source interface (Sunset the screensaver #3722)

• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)

• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913) grsec package is held back, did not upgrade.

• Change the OSSEC pubkey post-install using securedrop-admin

  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key

• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)

• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)

• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

[kushaldas]

Though I am running the latest kernel, I can still see 3.14.x series of kernels on the vm. @emkll also check the output of the following command:

# cron-apt -i -s
CRON-APT RUN [/etc/cron-apt/config]: Mon Dec  3 12:04:34 UTC 2018
CRON-APT ACTION: 0-update
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2 -o Dir::Etc::SourceList=/etc/apt/security.list -o Dir::Etc::SourceParts=""
CRON-APT ACTION: 1-remove
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 remove -y linux-image-generic-lts-xenial linux-image-.*generic -o quiet=2
CRON-APT ACTION: 5-security
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 autoclean -y
Reading package lists...
Building dependency tree...
Reading state information...
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 dist-upgrade -y -o APT::Get::Show-Upgraded=true -o Dir::Etc::SourceList=/etc/apt/security.list -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold
Reading package lists...
Building dependency tree...
Reading state information...
The following packages have been kept back:
  securedrop-grsec
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
W: Duplicate sources.list entry https://apt-test.freedom.press/ trusty/main amd64 Packages (/var/lib/apt/lists/apt-test.freedom.press_dists_trusty_main_binary-amd64_Packages)
W: You may want to run apt-get update to correct these problems
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 autoremove -y
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

[emkll]

@kushaldas I just reproduced this, the intel-microcode package is not installed due to iucode tool (>=1.0) not being installable.

intel-microcode comes from the security repo, but it's dependency iucode-tool comes from multiverse. Cron-apt will therefore not pull in the depencency, and lead to a broken install.

I propose we back out the microcode update for 0.11.0 and investigate mirroring iucode-tools for the next release

[kushaldas]

I propose we back out the microcode update for 0.11.0 and investigate mirroring iucode-tools for the next release

I am +1 to this idea.

[kushaldas]

@emkll even with rc3, I can see old kernels in the box.

I used a wrong command to verify it. we should use sudo apt list --installed | grep grsec

[emkll]

Upgrade testing on VMs (Completed)

Environment

• Install target: Prod VMs
• Tails version: 3.10.1
• Test Scenario: Upgrade from 0.10.0
• SSH over Tor: No
• Release candidate: 0.11.0-rc3
• 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
• AppArmor is loaded on mon
• 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 forgot to do this, will do this next RC and/or on hardware

• 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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• [] Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[zenmonkeykstop]

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

Environment

• Install target: 5-series NUC
• Tails version: 3.10.1
• Test Scenario: upgrade
• SSH over Tor: disabled
• Release candidate: RC3
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor - DISABLED
• AppArmor is loaded on app
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[kushaldas]

0.11.0 rc3 update testing

Environment

• Install target: VM
• Tails version: 3.9.x
• Test Scenario: upgrade
• SSH over Tor: disabled
• Release candidate: RC3
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor - DISABLED
• AppArmor is loaded on app
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[zenmonkeykstop]

0.11.0 QA Checklist

Environment

• Install target: 2014 Mac Mini
• Tails version: 3.10.1
• Test Scenario: Upgrade
• SSH over Tor: disabled - LAN only
• Release candidate: 0.11.0-rc4
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor (or LAN if Tor disabled)
• AppArmor is loaded on app
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

Application Acceptance Testing - Skipped

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[kushaldas]

0.11.0 QA Checklist

NOTE: I am not receiving OSSEC test emails, can anyone please confirm? Other OSSEC emails are flowing properly.

Environment

• Install target: Prod VMs
• Tails version: 3.9.x
• Test Scenario: Upgrade tests
• SSH over Tor: No
• Release candidate: 0.11.0-rc5
• General notes: Things seem to be working

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
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915) (did not test)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[emkll]

rc5 clean install (Completed)

Environment

• Install target: NUC5PYH
• Tails version: 3.10.1
• Test Scenario: Clean install
• SSH over Tor: no
• Release candidate: rc5
• General notes:

Basic Server Testing

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor local lan
• AppArmor is loaded on app
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

[zenmonkeykstop]

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

Environment

• Install target: 2014 Mac mini
• Tails version: 3.10.1
• Test Scenario: fresh install
• SSH over Tor: enabled
• Release candidate: 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
• AppArmor is loaded on mon
• 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 0.10.0 and restore this backup on 0.11.0.

Application Acceptance Testing - skipped!

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

0.11.0-specific changes

• Kernel version is 4.4.162-grsec
• (Upgrade only) Latest kernel version is selected for boot on a previously downgraded instance (Update grsecurity kernels to 4.4.162 #3913)
• (Upgrade only) Make sure no 3.14.x grsecurity kernels are left in the system (Update grsecurity kernels to 4.4.162 #3913)
• Change the OSSEC pubkey post-install using securedrop-admin
  • key is changed successfully
  • OSSEC alerts continue to flow and are decrypted by the new key
• No screensaver in the source interface (Sunset the screensaver #3722)
• Journalist API returns uuid after posting replies (Posting a Reply should return a UUID #3915)
• Icons on source interface are now updated (Source interface: data store icon is confusing #2508, Update Tor icon in security warning consistent with latest browser experience #3809)
• Make sure that we are running Tor 0.3.4.9 and there are no errors in tor log (Upgrade Tor on instances to 0.3.4.9 #3813)

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

Tails

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

[emkll]

Tails (3.11) with 0.11.0 tag

• The updater GUI appears on boot
• The update successfully occurs to 0.11.0
• After reboot, updater GUI no longer appears
• source .venv/bin/activate && ansible --version returns 2.6.8

[redshiftzero]

SecureDrop 0.11.0 was released on December 11th, and all post-release items are finished, closing!