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

Test securedrop-admin with Tails 5.0 #6400

Closed
legoktm opened this issue Apr 13, 2022 · 5 comments · Fixed by #6408
Closed

Test securedrop-admin with Tails 5.0 #6400

legoktm opened this issue Apr 13, 2022 · 5 comments · Fixed by #6408
Assignees
@zenmonkeykstop
Milestone
2.4.0

Comments

@legoktm
Copy link
Member

legoktm commented Apr 13, 2022

Description

https://tails.boum.org/news/test_5.0-beta1/

Tails 5.0 is based on Debian Bullseye, which means it's using a newer Python version (3.9) among plenty of other things.

It's probably worth walking through a full SD install + backup/restore to make sure it works as expected.
@zenmonkeykstop zenmonkeykstop added this to the 2.4.0 milestone Apr 16, 2022
@zenmonkeykstop zenmonkeykstop self-assigned this Apr 19, 2022
@zenmonkeykstop
Copy link
Contributor

zenmonkeykstop commented Apr 19, 2022 •
edited
Loading

In-progress comment for notes as I go through a (virtualized) from-scratch setup on 5.0:

  • ⚠️ menubar layout has changed (Activities is first option, screenshots and docs will need revising)
  • ⚠️ initial ./securedrop-admin setup failed because the torified torproject mirror was not available - could be a flake
  • ❌ was a flake but looks like the ccontrol package has been dropped from Bullseye, so the initial installation of apt deps is gonna fail. Updating admin/bootstrap.py to remove it and retrying.
  • ✔️ with ccontrol gone, got as far as virtualenv install and failed a few times, getting name resolution failures for files.pythonhosted.org - finally venv setup succeeded
  • ❌ ./securedrop-admin sdconfig and ./securedrop-admin install completed successfully, but tailsconfig fails as there is no python executable in Tails5, just python3. Updating the ansible task accordingly... and it works.
  • ✔️ GUI updater updates from develop to 2.3.1 with no issues, with the changes above.
  • ✔️ on an local-ssh install, ssh app and ssh mon work correctly
  • ✔️ Source and Journalist Interfaces are available via shortcuts
  • ✔️ backup and restore work without errors
  • ✔️ testinfra deps installed without issue and testinfra tests run happily

@zenmonkeykstop
Copy link
Contributor

Looks like ccontrol is a vestigial install left over from the days of Tails 3, removing it doesn't appear to have any effect on setup in Tails 4.29. Also, changing python to python3 in in the tailsconfig task seems to work fine too. So with those changes basic functionality should be the same in 4 and 5, leaving aside some look-and-feel differences.

@zenmonkeykstop zenmonkeykstop mentioned this issue Apr 19, 2022
Merged
19 tasks
legoktm added a commit that referenced this issue May 3, 2022
@legoktm
Update old venv deleting logic for Tails 5 (bullseye)
4bc1fa9 
The bootstrap detects when a legacy venv is being used on a newer
major Tails version, but the logic was still using stretch → buster
versions. Update it for buster → bullseye, renaming functions and
error messages as appropriate.

Refs #6400.
@legoktm legoktm mentioned this issue May 3, 2022
Merged
7 tasks
@legoktm
Copy link
Member Author

legoktm commented May 3, 2022

  • ✔️ with ccontrol gone, got as far as virtualenv install and failed a few times, getting name resolution failures for files.pythonhosted.org - finally venv setup succeeded

I've been unable to get past this, it keeps failing on name resolution for files.pythonhosted.org.

legoktm added a commit that referenced this issue May 3, 2022
@legoktm
Update old venv deleting logic for Tails 5 (bullseye)
77852de 
The bootstrap detects when a legacy venv is being used on a newer
major Tails version, but the logic was still using stretch → buster
versions. Update it for buster → bullseye, renaming functions and
error messages as appropriate.

Refs #6400.
@legoktm
Copy link
Member Author

legoktm commented May 3, 2022

Scratch that, I think I just got a bad circuit or something. After a restart it installed pretty quickly. Theoretically we could use https://pip.pypa.io/en/stable/cli/pip/?highlight=timeout#cmdoption-timeout to bump the pip timeout, but I don't know if that would actually help with DNS lookups.

@zenmonkeykstop
Copy link
Contributor

Scratch that, I think I just got a bad circuit or something. After a restart it installed pretty quickly. Theoretically we could use https://pip.pypa.io/en/stable/cli/pip/?highlight=timeout#cmdoption-timeout to bump the pip timeout, but I don't know if that would actually help with DNS lookups.

Worked first time for me this time on a fresh tails5 stick, gonna see how the upgrade process in your PR goes next.

zenmonkeykstop pushed a commit that referenced this issue May 3, 2022
@legoktm @zenmonkeykstop
Update old venv deleting logic for Tails 5 (bullseye)
369e866 
The bootstrap detects when a legacy venv is being used on a newer
major Tails version, but the logic was still using stretch → buster
versions. Update it for buster → bullseye, renaming functions and
error messages as appropriate.

Refs #6400.

(cherry picked from commit 77852de)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zenmonkeykstop zenmonkeykstop

Labels
None yet
Projects
None yet
Milestone
2.4.0
Development

Successfully merging a pull request may close this issue.

Added Tails 5 compatibility updates freedomofpress/securedrop
2 participants
@legoktm @zenmonkeykstop