6.1 Loading private key files in PKCS#1 format
6.2 Entering passphrases interactively
6.3 Multiple private keys
- 7. Configuring CA properties - ipsec.\ 1onf
+ 7. Configuring CA properties - ipsec.conf
8. Smartcard support
8.1 Configuring a smartcard-based connection
8.2 Entering the PIN code
strongSwan is an OpenSource IPsec solution for the Linux operating system
and currently supports the following features:
- * runs both on Linux 2.4 (KLIPS) and Linux 2.6 (native IPsec) kernels.
+ * runs on Linux 2.6 (native IPsec) kernels.
* strong 3DES, AES, Serpent, Twofish, or Blowfish encryption.
In the following examples we assume for reasons of clarity that left designates
the local host and that right is the remote host. Certificates for users, hosts
-and gateways are issued by a ficticious strongSwan CA. How to generate private keys
+and gateways are issued by a fictitious strongSwan CA. How to generate private keys
and certificates using OpenSSL will be explained in section 3. The CA certificate
"strongswanCert.pem" must be present on all VPN end points in order to be able to
authenticate the peers.
part of the certificate request message when strongSwan is the initiator.
A special case occurs when strongSwan responds to a roadwarrior. If several
roadwarrior connections based on different CAs are defined then all eligible
-CAs will be listed in Pluto\92s certificate request message.
+CAs will be listed in Pluto�s certificate request message.
4.9 IPsec policies based on group attributes
if self-signed certificates are used which wouldn't be accepted any way by
the other side. In these cases it is recommended to add
- leftsendcert=never
+ leftsendcert=never
to the connection definition[s] in order to avoid the sending of the host's
own certificate. The default value is
- leftsendcert=always.
+ leftsendcert=ifasked
+
+If a peer does not send a certificate request then use the setting
+
+ leftsendcert=always
If a peer certificate contains a subjectAltName extension, then an alternative
rightid type can be used, as the example "conn sun" shows. If no rightid
000 8836362e030e6707c32ffaa0bdad5540
The leading three characters represent the return code of the whack channel
-with 000 signifying that no error has occured. Here is another example showing
+with 000 signifying that no error has occurred. Here is another example showing
the use of the inbase and outbase attributes
ipsec scdecrypt m/ewDnTs0k...woE= --inbase base64 --outbase text
ipsec listpubkeys [--utc]
lists all public keys currently installed in the chained list of public
-keys. These keys were statically loaded from ipsec.conf or aquired either
+keys. These keys were statically loaded from ipsec.conf or acquired either
from received certificates or retrieved from secure DNS servers using
opportunistic mode.
and can be used when the following prerequisites are fulfilled:
- - Linux 2.4.x kernel, KLIPS IPsec stack, and arbitrary iptables version.
- Filtering of tunneled traffic is based on ipsecN interfaces.
-
- Linux 2.6.16 kernel or newer, native NETKEY IPsec stack, and
iptables-1.3.5 or newer. Filtering of tunneled traffic is based on
IPsec policy matching rules.
Copyright (c) 2000, Kai Martius
X.509, OCSP and smartcard functionality:
-°
+
Copyright (c) 2000, Andreas Hess, Patric Lichtsteiner, Roger Wegmann
Copyright (c) 2001, Marco Bertossa, Andreas Schleiss
Copyright (c) 2002, Uli Galizzi, Ariane Seiler, Mario Strasser
for more details.
-----------------------------------------------------------------------------
-This file is RCSID $Id: README,v 1.38 2007/01/14 18:16:51 as Exp $
-
projects / strongswan.git / blobdiff