Iptables rules are not getting applied if removed completely

[kushaldas]

Description

Steps to Reproduce

• On app run iptables -F
• ./securedrop-admin install on tails again
• reboot app

Expected Behavior

• The rules should come back on app

Actual Behavior

• No rules even after reboot via iptables -L

Comments

Suggestions to fix, any other relevant information.

[conorsch]

Cannot reproduce. I tested using staging VMs in Qubes, running the following commands on app-staging:

# updating input policy to avoid breaking ssh session during flush
sudo iptables -P INPUT ACCEPT
sudo iptables -P OUTPUT ACCEPT
sudo iptables -P FORWARD ACCEPT
sudo iptables -F
sudo iptables -X
sudo iptables -S # to confirm the rules were purged

I then rebooted the app-staging VM, logged in again, and ran sudo iptables -S, which showed that all the rules had been restored. I did not run playbooks against the server as described in the initial report—a reboot was sufficient to reload the rules back to baseline.

[eloquence]

I suggest we try one more repro during the 1.5.0 QA cycle. Milestoned accordingly.

[eloquence]

During 1.5.0 QA, nobody has been able to reproduce, so closing - can reopen if we get a repro.