-
Notifications
You must be signed in to change notification settings - Fork 697
Reinstalling mon with existing app server triggers missing iptables-persistent dependency #7119
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
Comments
I just did a clean install of one of my SecureDrop servers, and ran into this again. Out of the box, it's not possible to install SecureDrop on a freshly provisioned Ubuntu Server (ubuntu server 20.04.6) without manually installing this additional package. With the noble transition (and moving away from iptables) I'm not sure if this is worth fixing directly, but we probably ought to at least document it in the meantime for orgs who are doing a clean install. |
Can you provide the full ansible log/output? At what step did it fail? |
Full output from the run that failed:
|
Thanks, I see the bug. I did multiple 2.11.1 installs today, so let me try to figure out why I'm not hitting this! |
Do you think this merits a hotfix? Fresh installs being busted is bad, though less so if it's ssh-over-local, which is not the preferred config. |
Also fwiw, testing for the past 2 releases for me was over ssh-over-local and I didn't hit this. |
Just to clarify Nathan, in this case you already had a provisioned app server, and you were just reinstalling mon, right? The logic is:
So restrict-direct-access is run early only when 1) ssh over local network AND 2)
Ironically, I've had my mon server setup, and solely been reinstalling my app server, with no issues (i.e. the opposite of what I think you were doing). |
@legoktm Wow, what are the chances! :) Yes that's correct, I was only reinstalling |
In the specific case of installing a fresh mon server when the app server is already configured AND you're using ssh over the local network, we'll try to write to /etc/iptables before the iptables-persistent package is installed. This is because we end up running the restrict-direct-access role before the common role, which installs the base packages. The easy fix is to install iptables-persistent ahead of time if we see that it's necessary. Fixes #7119.
In the specific case of installing a fresh mon server when the app server is already configured AND you're using ssh over the local network, we'll try to write to /etc/iptables before the iptables-persistent package is installed. This is because we end up running the restrict-direct-access role before the common role, which installs the base packages. The easy fix is to install iptables-persistent ahead of time if we see that it's necessary. Fixes #7119.
Description
During a recent SD install to a freshly provisioned server running Ubuntu Server 20.04.6, the
./securedrop-admin install
process ran into an error during the run, citing that the/etc/iptables
directory was missing and that it couldn't continue.To workround this, I had to do an
apt install iptables-persistent
on the server, at which point./securedrop-admin install
was able to complete the installation without issue.We should determine if this is a required package, and if so, add it as a dependency.
Steps to Reproduce
./securedrop-admin install
(along withsetup
andsdconfig
beforehand, if necessary)Expected Behavior
The install happens without issue.
Actual Behavior
An error regarding a missing
/etc/iptables
directory that stops the installation.Comments
Not sure if this was a one-off, and also not sure of any potential security concerns about the
iptables-persistent
package.The text was updated successfully, but these errors were encountered: