NetworkManager » History » Version 31

Tobias Brunner, 18.05.2011 16:41

1 19 Andreas Steffen
h1. NetworkManager
2 1 Martin Willi
3 19 Andreas Steffen
"NetworkManager": allows configuration and control of VPN daemons through a plugin interface. We provide such a plugin for NetworkManager to configure road warrior clients for the most common setups.
4 19 Andreas Steffen
5 1 Martin Willi
NetworkManager uses DBUS to communicate with a plugin loaded by the IKEv2 charon daemon.
6 19 Andreas Steffen
7 1 Martin Willi
The plugin uses a certificate for gateway authentication and supports EAP and RSA authentication for client authentication. PSK is not supported, as it is considered insecure if the secrets are not strong enough. 
8 19 Andreas Steffen
9 31 Tobias Brunner
You can use any password based EAP method supported by strongSwan (MD5/GTC/MSCHAPv2) or private key authentication. Private keys are either stored in a file or accessed through your ready-to-use ssh-agent. You'll need a certificate matching that key. Starting with [[4.5.0|strongSwan 4.5.0]] / NetworkManager-strongswan 1.2.0, private keys and certificates on a smartcard can be used.
10 12 Martin Willi
11 31 Tobias Brunner
If you configure the gateway certificate directly on the clients, there are no requirements to the certificate. If you deploy CA certificates (supported since [[4.3.1]]), the gateway certificate will need a subjectAltName including the Hostname of the gateway (the same you enter in the clients configuration). Starting with [[4.3.5|version 4.3.5]], you can also use preinstalled root CA certificates of your distribution, using the @--with-nm-ca-dir@ configure option. Just don't specify any gateway/CA certificate to use preinstalled root certificates. CA certificates on a smartcard are automatically used.
12 26 Andreas Steffen
13 26 Andreas Steffen
h2. Screenshots
14 26 Andreas Steffen
15 26 Andreas Steffen
!nm-strongswan-config.png! !nm-strongswan-auth.png!
16 26 Andreas Steffen
17 1 Martin Willi
h2. Dependencies
18 1 Martin Willi
19 26 Andreas Steffen
The strongSwan NM plugin and the NetworkManager VPN module are currently based on the NetworkManager 7.1/7.99 interface. It should work out-of-the-box with the latest packages of your favorite Linux distribution.
20 19 Andreas Steffen
21 19 Andreas Steffen
h2. Installation
22 21 Martin Willi
23 27 Martin Willi
In Debian and Ubuntu, install the _network-manager-strongswan_ packages.
24 19 Andreas Steffen
25 27 Martin Willi
If you are not running Ubuntu/Debian/Suse, you have to build strongSwan from source.
26 1 Martin Willi
27 1 Martin Willi
h3. Building from source
28 19 Andreas Steffen
29 1 Martin Willi
To build from source, you additionally need the PAM headers for EAP-GTC and NetworkManager headers for the plugin:
30 20 Martin Willi
31 1 Martin Willi
aptitude install libpam0g-dev network-manager-dev libnm-util-dev libnm-glib-dev libgnomeui-dev gnome-common
32 20 Martin Willi
33 19 Andreas Steffen
34 31 Tobias Brunner
NM integration works only for IKEv2, but this allows us to disable a lot of IKEv1 legacy stuff. Since on a desktop we have OpenSSL installed anyway, we are going to use libcrypto for all cryptographical operations. @--enable-agent@ builds the ssh-agent private key plugin, EAP plugins are enabled using @--enable-eap-gtc --enable-eap-md5 --enable-eap-mschapv2@. For Smartcard support, @--enable-pkcs11@. You may omit options you don't need.
35 19 Andreas Steffen
36 19 Andreas Steffen
37 1 Martin Willi
# get the strongSwan tarball
38 24 Martin Willi
39 24 Martin Willi
tar xjf strongswan-4.3.5.tar.bz2
40 24 Martin Willi
cd strongswan-4.3.5
41 1 Martin Willi
42 20 Martin Willi
# build charon with OpenSSL/NM Plugin
43 1 Martin Willi
./configure --sysconfdir=/etc --prefix=/usr --libexecdir=/usr/lib \
44 18 Andreas Steffen
   --disable-aes --disable-des --disable-md5 --disable-sha1 --disable-sha2 \
45 19 Andreas Steffen
   --disable-fips-prf --disable-gmp --disable-stroke --disable-pluto --disable-tools \
46 20 Martin Willi
   --disable-updown --enable-openssl --enable-nm --enable-agent \
47 20 Martin Willi
   --enable-eap-gtc --enable-eap-md5 --enable-eap-mschapv2
48 1 Martin Willi
49 18 Andreas Steffen
make install
50 1 Martin Willi
51 20 Martin Willi
# get the NetworkManager strongsSwan plugin as a tarball
52 23 Andreas Steffen
53 27 Martin Willi
tar xjf NetworkManager-strongswan-1.1.2.tar.bz2
54 27 Martin Willi
cd NetworkManager-strongswan-1.1.2
55 9 Martin Willi
56 20 Martin Willi
# build the NetworkManager strongsSwan plugin
57 19 Andreas Steffen
./configure --sysconfdir=/etc --prefix=/usr --libexecdir=/usr/lib --with-charon=/usr/lib/ipsec/charon
58 9 Martin Willi
59 19 Andreas Steffen
make install
60 19 Andreas Steffen
61 20 Martin Willi
62 1 Martin Willi
h2. Configuration
63 1 Martin Willi
64 1 Martin Willi
* Click on nm-applet -> VPN Connections -> Configure VPN...
65 1 Martin Willi
* Add -> Ipsec/IKEv2 (strongswan) -> Create ...
66 1 Martin Willi
* Configure your client
67 1 Martin Willi
* Click on nm-applet -> VPN Connections -> Your Connection
68 1 Martin Willi
* Enter password
69 1 Martin Willi
70 1 Martin Willi
As you can see, there is no subnet configuration for the tunnel. We let the gateway administration choose the subnet; the client always proposes for the remote network and the gateway narrows that down to the configured subnet. 
71 27 Martin Willi
72 29 Tobias Brunner
h2. Smart card requirements
73 27 Martin Willi
74 29 Tobias Brunner
The use of smart cards should be as simple as possible to the end user, which brings some restrictions. For instance, the daemon automatically selects the first certificate with a private key on any token in any slot.
75 27 Martin Willi
76 30 Tobias Brunner
First, you'll need to specify the PKCS#11 module in strongswan.conf. Please refer to the general description of [[SmartCardsIKEv2|smart card support with IKEv2]] for details on how to do so.
77 27 Martin Willi
78 29 Tobias Brunner
You may define multiple modules, the daemon looks for the first certificate/private key in the specified module order.
79 27 Martin Willi
80 29 Tobias Brunner
The daemon uses the following mechanism to find a private key:
81 27 Martin Willi
* enumerate all certificates which have the TLS Client Auth Extended Key usage, but no CA constraint
82 27 Martin Willi
* for each certificate:
83 29 Tobias Brunner
** extract the subjectKeyIdentifier
84 29 Tobias Brunner
** enumerate all modules with all tokens
85 29 Tobias Brunner
** for each token:
86 29 Tobias Brunner
*** look for a public key having the certificates subjectKeyIdentifier as ID
87 29 Tobias Brunner
*** if found, log in to the smartcard using the supplied PIN
88 29 Tobias Brunner
*** if logged in, load the associated private key
89 27 Martin Willi
90 27 Martin Willi
In short, the private key on the token must have a public key readable without login, and both objects must have an ID matching the certificates subjectKeyIdentifier (or the hash of the subjectPublicKey field of the public key). The certificate needs the TLS CLient Auth Extended Key usage flag.
91 27 Martin Willi
92 27 Martin Willi
The daemon uses the the first subjectAltName of the selected certificate as IKEv2 identity, or uses the full DN if none found.
93 27 Martin Willi
94 27 Martin Willi
The "SuisseID": certificates from "Swiss Post": are known to work fine with such a setup.
95 1 Martin Willi
96 20 Martin Willi
h2. Server configuration
97 1 Martin Willi
98 20 Martin Willi
Depending on the used authentication methods, you can use gateway configurations very similar to Windows 7 ([[Win7MultipleConfig|Certificate]]/[[Win7EapMultipleConfig|MSCHAPv2]]), or use [[EapGtc|EAP-GTC]] to authenticate against PAM.