Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release SecureDrop 0.12.2 #4338

Closed
15 of 16 tasks
emkll opened this issue Apr 12, 2019 · 7 comments · Fixed by #4393
Closed
15 of 16 tasks

Release SecureDrop 0.12.2 #4338

emkll opened this issue Apr 12, 2019 · 7 comments · Fixed by #4393

Comments

@emkll
Copy link
Contributor

emkll commented Apr 12, 2019 •
edited
Loading

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

Feature freeze: EOD Pacific time, Tuesday, April 16
String freeze: EOD Pacific time, Tuesday, April 16
Pre-release announcement: N/A - point releases will not have pre-release announcements
Release date: EOD Pacific time, Thursday, April 25

Release manager: @emkll
Deputy release manager: @rmol

SecureDrop maintainers and testers: As you QA 0.12.2, 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.2 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.2~rc1)

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

Prepare release candidate (0.12.2~rc2)

  • Prepare 0.12.2-rc2 release changelog - @emkll
  • Build debs (including new Tor package) and put up 0.12.2~rc1 on test apt server - @rmol

QA Matrix for 0.12.2

Test Plan for 0.12.2

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

Final release

Post release
@emkll emkll pinned this issue Apr 12, 2019
@emkll
Copy link
Contributor Author

emkll commented Apr 18, 2019 •
edited
Loading

Environment

  • Install target: 14.04 VMs
  • Tails version: 0.13.1
  • Test scenarios:
  1. Installation of 0.12.1 on Trusty, cron-apt simulated upgrade to 0.12.2 again on Trusty
  2. Upgrade in-place to Xenial
  • Server locale setting: en_US
  • SSH over Tor: no
  • Release candidate: 0.12.2~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.1 and restore this backup on 0.12.2
  • "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

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/__init.__py:L111.
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError.
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing)
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

@zenmonkeykstop
Copy link
Contributor

QA plan

  • NUCs
  • Mac Minis
  • 1U servers in SF

0.12.2 QA Checklist

For both upgrades and fresh installs, here is a list of functionality that requires testing. You can use this for copy/pasting into your QA report. 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: SF 1U servers
  • Tails version: 3.13.1
  • Test scenario: cron-apt update from 0.12.1 (Xenial)
  • Server locale setting: (choose non-English to test Ansible scripts depend on English locale #4219)
  • SSH over Tor: enabled
  • Release candidate: 0.12.2~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 - untested, no access to current email/key
  • 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
  • "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent. can't verify, no access to email/key

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, don't have private key

Basic Tails Testing

Updater GUI

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

  • The Updater GUI appears on boot

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/__init.__py:L111. not tested, updated from Xenial to Xenial`
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError. *passed, but server under test has 48GB physical memory, so inconclusive
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing) not tested, no access to email/key
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

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

@emkll
Copy link
Contributor Author

emkll commented Apr 23, 2019

Environment

  • Install target: NUC5PYH
  • Tails version: 0.13.1
  • Test scenarios:
  1. Installation of 0.12.1 on Trusty, cron-apt simulated upgrade to 0.12.2 again on Trusty
  2. Installation of 0.12.1 on Trusty, backup, install 0.12.2 via cron-apt, upgrade in place to Xenial, restore from Trusty backup
  • Server locale setting: en_US
  • SSH over Tor: Yes
  • Release candidate: 0.12.2~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.1 and restore this backup on 0.12.2
  • "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

Application Acceptance Testing

Basic Tails Testing

Updater GUI

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

  • The Updater GUI appears on boot

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/__init.__py:L111.
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError.
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing)
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

@redshiftzero
Copy link
Contributor

Environment

  • Install target: Mac Mini
  • Tails version: 0.13.1
  • Test scenarios:
  1. Installation of 0.12.1 on Trusty, cron-apt simulated upgrade to 0.12.2~rc2 again on Trusty
  • Server locale setting: en_US
  • SSH over Tor: Yes
  • Release candidate: 0.12.2~rc2

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 (:warning: except those that require CPU microcode updates, see QA matrix)

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 - DID NOT TEST
  • If doing upgrade testing, make a backup on 0.12.1 and restore this backup on 0.12.2 - DID NOT TEST
  • "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent. - DID NOT TEST

Basic Tails Testing

Updater GUI

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

  • The Updater GUI appears on boot

0.12.2-specific changes

@emkll
Copy link
Contributor Author

emkll commented Apr 25, 2019

Environment

  • Install target: NUC5PYH
  • Tails version: 0.13.1
  • Test scenario:
  1. Installation of 0.12.1 on Trusty, cron-apt simulated upgrade to 0.12.2~rc2 again on Trusty,
  2. Installation of 0.12.1 on Trusty, backup, install 0.12.2 via cron-apt, upgrade in place to Xenial, restore from Trusty backup
  • Server locale setting: en_US
  • SSH over Tor: No
  • Release candidate: 0.12.2~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 0.12.1 and restore this backup on 0.12.2
  • "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

Application Acceptance Testing (DID NOT TEST)

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 (DID NOT TEST)

Updater GUI

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

  • The Updater GUI appears on boot

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/disable.py.
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError. DID NOT TEST
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing)
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

0.12.2-rc2-specific changes

  • When deleting a source:
  • There are no errors in /var/log/apache2/journalist-error.log
  • There are no AppArmor violations in /var/log/syslog
  • gpg --homedir /var/lib/securedrop/keys/pubring.gpg as www-data user no longer contains the deleted source public key
  • /var/lib/securedrop/keys/private-keys-v1.d does not contain the deleted source's private key

@emkll emkll mentioned this issue Apr 25, 2019
Merged
2 tasks
@kushaldas
Copy link
Contributor

Environment

  • Install target: 16.04 VMs
  • Tails version: 0.13.1
  • Server locale setting: en_US
  • SSH over Tor: no
  • Release candidate: 0.12.2~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 0.12.1 and restore this backup on 0.12.2
  • "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

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/__init.__py:L111. (DID NOT TEST)
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError.
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing)
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

@rmol
Copy link
Contributor

rmol commented Apr 25, 2019

Environment

  • Install target: NUC 7i5BNH
  • Tails version: 3.13.1
  • Test scenario: Installation of 0.12.2 on Xenial
  • Server locale setting: en_US
  • SSH over Tor: only as needed for specific tests
  • Release candidate: 0.12.2~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 0.12.1 and restore this backup on 0.12.2
  • "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

0.12.2-specific changes

  • (#4325): On 14.04 Trusty, the source interface disabled page appears when TRUSTY_DISABLE_DATE is set to a date in the past in /var/www/securedrop/source_app/disable.py.
  • (#4325): On 16.04, after following the instructions above, the source interface is still working.
  • (#4326): Create a large file in /var/lib/securedrop/store (>1GB), backup should not fail with MemoryError.
  • (#4319): NoScript XSS no longer appears on source interface
  • (#4340: Go to Journalist Interface, click on Admin, navigate to Instance Config and click on "Send Test OSSEC Alert" button. An email is received. (note that this has now been added to basic server testing)
  • (#4305: uname -r returns 4.4.177-grsec. The kernel boots, the application is functional and there are no errors in /var/log/syslog

0.12.2-rc2-specific changes

  • When deleting a source:
  • There are no errors in /var/log/apache2/journalist-error.log
  • There are no AppArmor violations in /var/log/syslog
  • gpg --homedir /var/lib/securedrop/keys/pubring.gpg no longer contains the deleted source public key
  • /var/lib/securedrop/keys/private-keys-v1.d does not contain the deleted source's private key

@emkll emkll mentioned this issue Apr 25, 2019
Merged
2 tasks
@rmol rmol mentioned this issue Apr 26, 2019
Merged
@emkll emkll mentioned this issue Apr 30, 2019
Merged
4 tasks
@emkll emkll mentioned this issue Apr 30, 2019
Merged
1 task
@emkll emkll unpinned this issue May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Provide 0.12.2 upgrade boxes freedomofpress/securedrop
5 participants
@kushaldas @zenmonkeykstop @redshiftzero @emkll @rmol