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

[v3 onion migration] Modify securedrop-admin tailsconfig to use v3 if available #4629

Closed
redshiftzero opened this issue Jul 19, 2019 · 1 comment · Fixed by #4675
Closed
Milestone

Comments

@redshiftzero
Copy link
Contributor

Description

This ticket is to modify securedrop-admin tailsconfig (used for configuring desktop shortcuts and torrc additions in the SecureDrop Tails workstations) to:

  • Use v3 addresses if v3 files are present for desktop shortcuts, else continue to use v2
  • Add v3 Client auth details to torrc if they are present (and NOT add v2 HidServAuth so that it’s easier in the future to rip out v2 without making a round of updates in journalist and admin drives)

Subticket of #2951

@zenmonkeykstop
Copy link
Contributor

So it looks like in order to do this, the client-side changes are:

  1. Create the ClientOnionAuthDir and add an entry to to torrc specifying its location
  2. add files <descriptor>.auth_private containing a single line like:
    <AddressWithoutDotOnion>:<descriptor>:x25519:<Base32PrivateKey>
  3. restart Tor.

So the securedrop_init.py script will need to be modified to update torrc with that directive, and a task will need to be added to the playbook to create those single line files.

Substituting the onion addresses into the desktop shortcuts and ssh config will also need to be done, with some conditional logic for the cases v2 only; v2+v3; v3 only

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 a pull request may close this issue.

2 participants