Ensure version of tor installed is from FPF repo #4169
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
Ready for review
Description of Changes
Fixes #4162 .
Because we don't want to couple Tor versions with SecureDrop releases, and that we probably won't go back in Tor versions, specifying
>=
the current Tor version seems like a sensible approach, given the versions being served in Ubuntu Trusty and Xenial apt repos:Changes proposed in this pull request:
Testing
CI/staging scenarios are not an accurate test as they also include apt-test in their source list (for kernel tests).
Deployment
This change only affects new installs, and will be provided via the Ansible install logic.
Checklist
If you made non-trivial code changes: