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

Playbook needed for IPSec management #5

Open
KellerFuchs opened this issue Nov 10, 2015 · 0 comments
Open

Playbook needed for IPSec management #5

KellerFuchs opened this issue Nov 10, 2015 · 0 comments

Comments

@KellerFuchs
Copy link
Member

I would like to propose a way to setup IPSec in transport mode between all our machines, because:

  • we can ;)
  • it makes sure that communication between our boxes is authenticated and encrypted (I haven't reviewed the TLS settings for everything, and that would be a daunting task...)
  • it hides some communication metadata (protocol & port).

However, managing a full mesh by hand is not going to be fun, so we should have a playbook that:

  • fetches the IPSec pubkeys, and make the server generate keys if needed;
  • sends the pubkeys to all servers (or as a hash in the config?);
  • generate the StrongSwan config from a template;
  • reloads.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant