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

dns host iptables rules should be restricted to specific user #438

Closed
dolanjs opened this issue Jun 13, 2014 · 2 comments
Closed

dns host iptables rules should be restricted to specific user #438

dolanjs opened this issue Jun 13, 2014 · 2 comments

Comments

@dolanjs
Copy link
Contributor

dolanjs commented Jun 13, 2014

the host iptables rules do restrict outbound connections to the root user but the destination for the outbound rules and source for the inbound rules is not restricted on the host iptables rules. The destination ip address for outbound rules and the source for inbound rules are defined and restricted on the network firewall currentyl though it should still be applied to the host iptables rules also. Reported by @iSEC

@garrettr
Copy link
Contributor

@dolanjs Question about the title: the rules are restricted to a specific user (root) - did you mean they should be restricted to a specific destination (the DNS server chosen at installation)?

@garrettr
Copy link
Contributor

At the time this issue as filed, we were still planning to solely use Debian packages to manage the installation and automatic upgrading of SecureDrop. Fixing this issue would've required input from the installer during the package installation process to configure this correctly. While this is possible via debconf (among other options), we ultimately decided to switch to using Ansible for the configuration, installation, and maintenance of SecureDrop instances. The ultimate solution was to allow the admin to specify which external DNS servers should be used in the configuration file for the playbook, and then templatetize the IP tables rules to insert the chosen DNS servers into the rules and restrict DNS traffic to only the specified servers.

This was implemented in a8a4979. I am not sure why this issue was not updated to reflect this at that time, but it is resolved now.

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

No branches or pull requests

2 participants