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

Configure iptables in Citadel #4

Open
brl opened this issue Mar 4, 2018 · 0 comments
Open

Configure iptables in Citadel #4

brl opened this issue Mar 4, 2018 · 0 comments

Comments

@brl
Copy link
Contributor

brl commented Mar 4, 2018

A set of iptables rules need to be added to Citadel to not allow any access to the network at all from components running inside Citadel. Some exceptions will exist of course, such as the dhcp client.

Not only should all network access be blocked but it must be logged as well so that we can investigate any component that believes that it needs to do something on the network.

Of course the user will want to be able to use the internet so application image instances will need to be permitted to reach the network. Currently the nspawn containers are just using the simplest networking option and sharing the host network namespace. The plan I'm proposing is to configure them with Veth interfaces instead, and assign those interfaces to a bridge named something like 'clearnet'. Later when VPNs are supported, we can manage assigning application images to the correct network context by just adding them to the appropriate bridge.

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

1 participant