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.
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 v3 onion support to tor-hidden-services ansible role #4652
Add v3 onion support to tor-hidden-services ansible role #4652
Changes from all commits
c433e14
5eaa63e
2c62b81
3b5eaab
0921ca6
5769b5f
8b3ff1b
d7856a8
2f5f934
332c6fc
50c67d6
09749f9
140207d
9c14e02
847f5e6
9c323d3
440847c
eb5b30e
f822546
f4cad49
0466711
b545bc9
dd787ce
6c1dd65
2dc859b
50b21d1
9154e9d
96497fb
a866a22
c94d3da
c11af15
0399bdc
78f83fa
816fdd8
0248ef0
67e0924
728ef38
fd9da6f
261bba6
769a05f
6057fc8
fc00d79
a834177
e0412d7
5637a81
f24ffc0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as we currently have two discrete files on the Admin Workstation for the v2 auth info, it'd be great to have the same for the v3 info. Doing so would simplify the lookup logic required in the dynamic-inventory script (not yet implemented in this PR), as well. Perhaps the function should receive
hostname=None
, and select the files that way.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel that one file for admin workstation with all 3 different key pairs (journalist, ssh app, and ssh mon) and a file for journalist workstations (only with the journalist keypair) is simpler. Also, this is only for the key information, if we want, we can also remove the
ths
files all together and just the.onion
address from the JSON files iteself (we have to add them there).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having taken a closer look at the keygen logic, we're still going to need separate files for the dynamic-inventory support (OK to defer to #4629). With the v2 logic, if-and-only-if the
-ths
files are present on the Admin Workstation, then Onion URLs are used for the SSH connection. Since those-ths
files are created on the Admin Workstation at the end of the install process, the logic is sound. For the v3 keygen logic, however, we need a way to denote whether the corresponding Onion URLs should be used for the SSH connection.I suggest moving the keygen logic into Ansible via a script, so that the JSON file does not exist when Ansible builds the SSH connection, meaning local IPv4 addresses (or v2 Onion URLs) will be used. At the end of the run, we can sprinkle in appropriate
-v3-ths
files back onto the Admin Workstation.We cannot relegate the v3 keygen logic solely to the
securedrop-admin
init, because that's only relevant for Tails environments, which means developer staging VMs will not have v3 connectivity.