From a4d0e4a7f8cd829de8346fb6edd9866cc855134f Mon Sep 17 00:00:00 2001 From: Guilhem Moulin Date: Wed, 25 Jun 2014 05:22:58 +0200 Subject: Don't require a PKI for IPSec. Instead, generate a server certificate for each host (on the machine itself). Then fetch all these certs locally, and copy them over to each IPSec peer. That requires more certs to be stored on each machines (n vs 2), but it can be done automatically, and is easier to deploy. Note: When adding a new machine to the inventory, one needs to run the playbook on that machine (to generate the cert and fetch it locally) first, then on all other machines. --- roles/common/handlers/main.yml | 3 --- 1 file changed, 3 deletions(-) (limited to 'roles/common/handlers') diff --git a/roles/common/handlers/main.yml b/roles/common/handlers/main.yml index 2f4f900..89e4b6b 100644 --- a/roles/common/handlers/main.yml +++ b/roles/common/handlers/main.yml @@ -17,9 +17,6 @@ - name: Restart fail2ban service: name=fail2ban state=restarted -- name: Missing IPSec certificate - fail: msg="strongswan IPsec is lacking public or private keys on '{{ ansible_fqdn }}'." - - name: Restart IPSec service: name=ipsec state=restarted -- cgit v1.2.3