Release SecureDrop 0.12.1

[heartsucker]

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

Feature freeze: EOD Pacific time, Thursday, March 14
String freeze: N/A - no string changes this release
Pre-release announcement: N/A - point releases will not have pre-release announcements
Release date: EOD Pacific time, Tuesday, March 19

Release manager: @heartsucker
Deputy release manager: @zenmonkeykstop

SecureDrop maintainers and testers: As you QA 0.12.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.12.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.12.1~rc1)

• Prepare 0.12.1-rc1 release changelog - @heartsucker
• Branch off release/0.12.0 into release/0.12.1 - @heartsucker
• Build debs (including new Tor package) and put up 0.12.1~rc1 on test apt server - @zenmonkeykstop

QA Matrix for 0.12.1

Test Plan for 0.12.1

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

Final release

• Ensure builder in release branch is updated and/or update builder image - @emkll
• Push signed tag - @redshiftzero
• Build final Debian packages for 0.12.1 (including Tor packages) - @conorsch
• Upload Debian packages to apt-qa - @conorsch
• Pre-Flight: Test install and upgrade (both cron-apt on Trusty, and Ansible on Xenial) of 0.12.1 works w/ prod repo debs - @zenmonkeykstop, @emkll
• Prepare and distribute release messaging - @eloquence - [0.12.1] Write and disseminate point release messaging #4273

Post release

• Merge changelog back to develop - @emkll Backport 0.12.1 changelog to develop #4285
• Update upgrade testing boxes - @conorsch Adds "upgrade" boxes for 0.12.1 #4291
• Update roadmap wiki page -

[zenmonkeykstop]

QA plan

• NUCs
• Mac Minis
• 1U servers in SF

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

Environment

• Install target: 2014 Mac Mini
• Tails version: 3.12.1
• Test scenario: cron-apt upgrade against Xenial install
• Server locale setting: Norwegian
• SSH over Tor: enabled
• Release candidate: 0.12.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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 0.12.0 and restore this backup on 0.12.1

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 Not tested - what has two thumbs and saved the submission to his non-persistent tbb directory?

Basic Tails Testing

Updater GUI

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

• The Updater GUI appears on boot
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.11 on Trusty or 0.3.5.8 on Xenial
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts
• (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wirelesstools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.

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

Tails

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

[kushaldas]

Environment

• Install target: vm
• Tails version: 3.12.1
• Test scenario:
• Server locale setting: (choose non-English to test Ansible scripts depend on English locale #4219)
• SSH over Tor: No
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 0.12.0 and restore this backup on 0.12.1

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
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.11 on Trusty or 0.3.5.8 on Xenial
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts
• 🔥 🔥 (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wirelesstools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.

vagrant@app-prod:~$ dpkg -l | grep wpasupplicant
ii  wpasupplicant                      2.4-0ubuntu6.3                                       amd64        client support for WPA and WPA2 (IEEE 802.11i)
vagrant@app-prod:~$ dpkg -l | grep libiw30
ii  libiw30:amd64                      30~pre9-8ubuntu1                                     amd64        Wireless tools - library

[kushaldas]

Environment

• Install target: NUC upgraded from Trusty
• Tails version: 3.12.1
• Test scenario:
• Server locale setting: fr_FR.UTF-8
• SSH over Tor: No
• 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 0.12.0 and restore this backup on 0.12.1

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
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.11 on Trusty or 0.3.5.8 on Xenial
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts
• 🔥 🔥 (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wirelesstools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.

vagrant@app-prod:~$ dpkg -l | grep wpasupplicant
ii  wpasupplicant                      2.4-0ubuntu6.3                                       amd64        client support for WPA and WPA2 (IEEE 802.11i)
vagrant@app-prod:~$ dpkg -l | grep libiw30
ii  libiw30:amd64                      30~pre9-8ubuntu1                                     amd64        Wireless tools - library

[emkll]

0.12.1 QA Checklist

Environment

• Install target: Trusty VMs
• Tails version: 3.12.1
• Test scenario: Trusty 0.12.1 clean install
• Server locale setting: fr_FR
• SSH over Tor: Yes
• Release candidate: 1
• 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 0.12.0 and restore this backup on 0.12.1

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
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.9 on Trusty or 0.3.5.8 on Xenial
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts
• (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wirelesstools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.
• (#4252) securedrop-admin backup, restore and logs commands complete successfully

[zenmonkeykstop]

QA plan

• NUCs
• Mac Minis
• 1U servers in SF

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

Environment

• Install target: 2014 Mac Mini
• Tails version: 3.12.1
• Test scenario: upgrade in place
• Server locale setting: (choose non-English to test Ansible scripts depend on English locale #4219): Norsk
• SSH over Tor: enabled
• Release candidate: 3.12.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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 0.12.0 and restore this backup on 0.12.1

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
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.11 on Trusty or 0.3.5.8 on Xenial 0.3.4.9 initially, 0.3.5.8 after first cron-apt run
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts
• (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wireless-tools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.

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

Tails

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

[zenmonkeykstop]

QA plan

• NUCs
• Mac Minis
• 1U servers in SF

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

Environment

• Install target: 2014 Mac Mini
• Tails version: 3.12.1
• Test scenario: fresh install
• Server locale setting: (choose non-English to test Ansible scripts depend on English locale #4219) Irish (Gaelige)
• SSH over Tor: enabled
• Release candidate: 0.12.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 - SKIPPED

• 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.12.0 and restore this backup on 0.12.1

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
• (#4100) Updating occurs without issue

0.12.1-specific changes

• (#4170) Tor version is 0.3.4.11 on Trusty or 0.3.5.8 on Xenial
• (#4219) If non-English locale set during OS install, ./securedrop-admin install completes successfully
• (#4221)
  • tmux session is started/reconnected after SSH to app and mon.
  • If testing Xenial upgrade-in-place, tmux session reconnects successfully after tor and sshd restarts not tested
• (#4163) The following packages are not installed on app or mon: libiw30, wpasupplicant, wirelesstools.
• (#4208) The NoScript info page on the Source Interface includes a link back to the submissions page.

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

Tails

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

[conorsch]

I'm happy to take the upgrade box version bump tomorrow in order in support of closing out here. Previously we'd discussed delegating that task to e.g. @rmol, to broaden understanding of the procedures in the team, but I believe that's blocked on AWS API access. Let's discuss at engineering meeting tomorrow to make sure we've covered any potential blockers.

[emkll]

The final item on the checklist has been merged in #4291, closing!