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.

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

Add updater GUI #3300

Merged
merged 105 commits into from
Apr 26, 2018
Merged

Add updater GUI #3300

merged 105 commits into from
Apr 26, 2018

Conversation

redshiftzero
Copy link
Contributor

Status

Ready for review

Description of Changes

Fixes #3076.

Changes proposed in this pull request:

  • Adds the Updater GUI and enables automatic launching of the updater when updates are needed in the Tails workstation:

screen shot 2018-04-23 at 6 29 56 pm

Testing

  1. Check out this branch in your Tails VM.
  2. ./securedrop-admin tailsconfig
  3. The GUI will pop up at this stage because you are not running on the latest production tag. Ignore this (hit "Update Later") and reboot for the full experience.
  4. Log in and enable an admin password
  5. The updater should pop up. Attempt to upgrade your workstation (being intentionally vague).

Deployment

Users will need to re-run ./securedrop-admin tailsconfig to use this.

But from that point forward, securedrop-admin update, securedrop-admin setup and securedrop-admin tailsconfig will be automated by the GUI.

Checklist

If you made changes to the Updater GUI

  • make ci-lint passes
  • python3 test_gui.py passes

redshiftzero and others added 30 commits April 17, 2018 14:37
This commit runs check_for_updates on boot, and then runs the
updater GUI if updates are needed. If updates are not needed,
then nothing will happen.

Note: in order to run this, the venv must already be set up, as the
journalist/admin will run `./securedrop-admin tailsconfig` in
order to update this on-boot hook. So assuming that the venv
is configured in the on-boot hook is a safe assumption.
This is such that they can try again. For example, if they just fail
to type in the sudo password, they might want to try again.
If they get a scarier message they _can_ try again, though the
strings warn the user in such a case just to go to their
administrator.
This doesn't have a py extension because the name will appear
in the Tails process bar, and it's nice to show simply
SecureDropUpdater there.
(cherry picked from commit 9c67f0d)
(cherry picked from commit 4c68fcb)
(cherry picked from commit 02c68cf)
(cherry picked from commit e50d8b3)
(cherry picked from commit 8f0feb4)
(cherry picked from commit d9877b7)
@redshiftzero redshiftzero force-pushed the qt-journalist-updater branch from 2544046 to 3782f52 Compare April 25, 2018 20:50
[qt-journalist-updater] Address remainder of review comments on #3300
@redshiftzero
Copy link
Contributor Author

Hey @emkll and @heartsucker, take a look at the latest (btw @emkll #3309 should also be good to go after a rebase) - I think this should resolve all the outstanding issues. Let's discuss how to proceed (0.7 vs 0.8) tomorrow.

@heartsucker
Copy link
Contributor

My concerns have been addressed, but there's not a "dismiss review" button, so my thumbs up should not be considered sufficient for merge.

@emkll
Copy link
Contributor

emkll commented Apr 26, 2018

LGTM! Thanks for the quick fixes!

@redshiftzero redshiftzero merged commit 9e8fceb into develop Apr 26, 2018
@redshiftzero redshiftzero modified the milestones: 0.8, 0.7 Apr 26, 2018
@emkll emkll mentioned this pull request Apr 26, 2018
21 tasks
@heartsucker heartsucker deleted the qt-journalist-updater branch February 27, 2019 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants