-
Notifications
You must be signed in to change notification settings - Fork 688
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
SecureDrop validate role fails on Tails 3.3 #2591
Comments
3.3
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
The solution proposed in aa22719 is not a sufficient patch, given that the |
yeah i totally agree @conorsch - its not a sufficient patch it was just a hot-fix for a new install but this issue should definitely be left open |
Even if we modify the apt install logic to run every time, we're still breaking Tails 3.3, since the |
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
will repush with actually informative commit message when this is working
will repush with actually informative commit message when this is working
* Replace nslookup with host so dnsutils is not required (fix for #2591). * Instead of using return code, inspect output of host command, which should have something like: smtp.gmail.com has address 209.85.232.109 if successful.
* Replace nslookup with host so dnsutils is not required (fix for #2591). * Instead of using return code, inspect output of host command, which should have something like: smtp.gmail.com has address 209.85.232.109 if successful.
dnsutils was removed from Tails 3.3 which causes problems with our validate role.
Bug
Description
Under Tails
3.3
- the validate script will bomb out because it is trying to shell out tonslookup
but the deb packagednsutils
is not installed.A short summary of the issue.
Steps to Reproduce
Under a fresh tails 3.3:
./securedrop-admin setup
./securedrop-admin sdconfig
or./securedrop-admin install
Expected Behavior
You'll get prompted for variables and everything should pass validation.
Actual Behavior
The validation role bombs out with the following output:
Comments
We really shouldn't be shellin' out and instead should be taking advantage of either the
dig
lookup or stop using ansible and use python scripts. As the fastest short-term work-around we could installdnsutils
during the setup step.The text was updated successfully, but these errors were encountered: