IPSEC(4) BSD Programmer's Manual IPSEC(4)
ipsec - IP Security Protocol
IPsec may be enabled or disabled using the following sysctl(3) variables in /etc/sysctl.conf. By default, both protocols are enabled: net.inet.esp.enable Enable the ESP IPsec protocol net.inet.ah.enable Enable the AH IPsec protocol
IPsec is a pair of protocols, ESP (for Encapsulating Security Payload) and AH (for Authentication Header), which provide security services for IP datagrams. The original Internet Protocol - IPv4 - does not inherently provide any protection to transferred data. Furthermore, it does not even guarantee that the sender is who he claims to be. IPsec tries to remedy this by providing the required security services for IP datagrams. There are four main security properties provided by IPsec: Confidentiality - Ensure it is hard for anyone but the receiver to understand what data has been communicated. For example, ensuring the secrecy of passwords when logging into a remote machine over the Internet. Integrity - Guarantee that the data does not get changed in tran- sit. If you are on a line carrying invoicing data you probably want to know that the amounts and account numbers are correct and have not been modified by a third party. Authenticity - Sign your data so that others can see that it is really you that sent it. It is clearly nice to know that documents are not forged. Replay protection - We need ways to ensure a datagram is processed only once, regardless of how many times it is received. I.e. it should not be possible for an attacker to record a transaction (such as a bank account withdrawal), and then by replaying it ver- batim cause the peer to think a new message (withdrawal request) had been received. WARNING: as per the standards specification, re- play protection is not performed when using manual-keyed IPsec (e.g., when using ipsecadm(8)).
IPsec provides these services using two new protocols: AH, Authentication Header, and ESP, Encapsulating Security Payload. ESP can provide the properties authentication, integrity, replay protec- tion, and confidentiality of the data (it secures everything in the pack- et that follows the IP header). Replay protection requires authentication and integrity (these two always go together). Confidentiality (encryp- tion) can be used with or without authentication/integrity. Similarly, one could use authentication/integrity with or without confidentiality. AH provides authentication, integrity, and replay protection (but not confidentiality). The main difference between the authentication features of AH and ESP is that AH also authenticates portions of the IP header of the packet (such as the source/destination addresses). ESP authenticates only the packet payload.
These protocols require certain parameters for each connection, describ- ing exactly how the desired protection will be achieved. These parameters are collected in an entity called a security association, or SA for short. Typical SA parameters include encryption algorithm, hash algo- rithm, encryption key, and authentication key, to name a few. When two peers have established matching SAs (one at each end), packets protected with one end's SA may be verified and/or decrypted using the information in the other end's SA. The only issue remaining is to ensure that both ends have matching SAs. This may be done manually, or automatically using a key management daemon. Further information on manual SA establishment is described in ipsecadm(8). Information on automated key management may be found in isakmpd(8).
AH works by computing a value that depends on all of the payload data, some of the IP header data, and a certain secret value (the authentica- tion key). This value is then sent with the rest of each packet. The re- ceiver performs the same computation, and if the value matches, he knows no one tampered with the data (integrity), the address information (au- thenticity) or a sequence number (replay protection). He knows this be- cause the secret authentication key makes sure no active attacker (man- in-the-middle) can recompute the correct value after altering the packet. The algorithms used to compute these values are called hash algorithms and are parameters in the SA, just like the authentication key.
ESP optionally does almost everything that AH does except that it does not protect the outer IP header but furthermore it encrypts the payload data with an encryption algorithm using a secret encryption key. Only the ones knowing this key can decrypt the data, thus providing confidentiali- ty. Both the algorithm and the encryption key are parameters of the SA.
In order to identify an SA we need to have a unique name for it. This name is a triplet, consisting of the destination address, security param- eter index (aka SPI) and the security protocol (ESP or AH). Since the destination address is part of the name, an SA is necessarily a unidirec- tional construct. For a bidirectional communication channel, two SAs are required, one outgoing and one incoming, where the destination address is our local IP address. The SPI is just a number that helps us make the name unique, it can be arbitrarily chosen in the range 0x100 - 0xffffffff. The security protocol number should be 50 for ESP and 51 for AH, as these are the protocol numbers assigned by IANA.
IPsec can operate in two modes, either tunnel or transport mode. In tran- sport mode the ordinary IP header is used to deliver the packets to their endpoint, in tunnel mode the ordinary IP header just tells us the address of a security gateway, knowing how to verify/decrypt the payload and for- ward the packet to a destination given by another IP header contained in the protected payload. Tunnel mode can be used for establishing VPNs, virtual private networks, where parts of the networks can be spread out over an unsafe public network, but security gateways at each subnet are responsible for encrypting and decrypting the data passing over the pub- lic net. An SA will hold information telling if it is a tunnel or tran- sport mode SA, and for tunnels, it will contain values to fill in into the outer IP header.
The SA also holds a couple of other parameters, especially useful for au- tomatic keying, called lifetimes, which puts a limit on how much we can use an SA for protecting our data. These limits can be in wall-clock time or in volume of our data.
To better illustrate how IPsec works, consider a typical TCP packet: [IP header] [TCP header] [data...] If we apply ESP in transport mode to the above packet, we will get: [IP header] [ESP header] [TCP header] [data...] where everything after the ESP header is protected by whatever services of ESP we are using (authentication/integrity, replay protection, confi- dentiality). This means the IP header itself is not protected. If we apply ESP in tunnel mode to the original packet, we would get: [IP header] [ESP header] [IP header] [TCP header] [data...] where, again, everything after the ESP header is cryptographically pro- tected. Notice the insertion of an IP header between the ESP and TCP header. This mode of operation allows us to hide who the true source and destination addresses of a packet are (since the protected and the unpro- tected IP headers don't have to be exactly the same). A typical applica- tion of this is in Virtual Private Networks (or VPNs), where two firewalls use IPsec to secure the traffic of all the hosts behind them. For example: Net A <----> Firewall 1 <--- Internet ---> Firewall 2 <----> Net B Firewall 1 and Firewall 2 can protect all communications between Net A and Net B by using IPsec in tunnel mode, as illustrated above. This implementation makes use of a virtual interface enc0, which can be used in packet filters to specify those packets that have been or will be processed by IPsec. NAT can also be applied to enc# interfaces, but special care should be taken because of the interactions between NAT and the IPsec flow match- ing, especially on the packet output path. Inside the TCP/IP stack, pack- ets go through the following stages: UL/R -> [X] -> PF/NAT(enc0) -> IPsec -> PF/NAT(IF) -> IF UL/R <-------- PF/NAT(enc0) <- IPsec -> PF/NAT(IF) <- IF With IF being the real interface and UL/R the Upper Layer or Routing code. The [X] Stage on the output path represents the point where the packet is matched against the IPsec flow database (SPD) to determine if and how the packet has to be IPsec-processed. If, at this point, it is determined that the packet should be IPsec-processed, it is processed by the PF/NAT code. Unless PF drops the packet, it will then be IPsec- processed, even if the packet has been modified by NAT. Security Associations can be set up manually with the ipsecadm(8) utility or automatically with the isakmpd(8) key management daemon.
The following IP-level setsockopt(2) and getsockopt(2) options are specific to ipsec. A socket can specify security levels for three dif- ferent categories: IP_AUTH_LEVEL Specifies the use of authentication for packets sent or received by the socket. IP_ESP_TRANS_LEVEL Specifies the use of encryption in transport mode for packets sent or received by the socket. IP_ESP_NETWORK_LEVEL Specifies the use of encryption in tunnel mode. For each of the categories there are five possible levels which specify the security policy to use in that category: IPSEC_LEVEL_BYPASS Bypass the default system security policy. This op- tion can only be used by privileged processes. This level is necessary for the key management daemon, isakmpd(8). IPSEC_LEVEL_AVAIL If a Security Association is available it will be used for sending packets by that socket. IPSEC_LEVEL_USE Use IP Security for sending packets but still accept packets which are not secured. IPSEC_LEVEL_REQUIRE Use IP Security for sending packets and also require IP Security for received data. IPSEC_LEVEL_UNIQUE The outbound Security Association will only be used by this socket. When a new socket is created, it is assigned the default system security level in each category. These levels can be queried with getsockopt(2). Only a privileged process can lower the security level with a setsockopt(2) call. For example, a server process might want to accept only authenticated connections to prevent session hijacking. It would issue the following setsockopt(2) call: int level = IPSEC_LEVEL_REQUIRE; error = setsockopt(s, IPPROTO_IP, IP_AUTH_LEVEL, &level, sizeof(int)); The system does guarantee that it will succeed at establishing the re- quired security associations. In any case a properly configured key management daemon is required which listens to messages from the kernel. A list of all security associations in the kernel tables can be obtained via the kernfs file <ipsec> (typically in </kern/ipsec>).
A socket operation may fail with one of the following errors returned: [EACCES] when an attempt is made to lower the security level below the system default by a non-privileged process. [EINVAL] The length of option field did not match or an unknown security level was given. netstat(1) can be used to obtain some statistics about AH and ESP usage, using the -p flag. Using the -r flag, netstat(1) displays information about IPsec flows. vmstat(8) displays information about memory use by IPsec with the -m flag (look for ``tdb'' and ``xform'' allocations).
enc(4), icmp(4), inet(4), ip(4), netintro(4), tcp(4), udp(4), ipsecadm(8), isakmpd(8), vpn(8)
The IPsec protocol design process was started in 1992 by John Ioannidis, Phil Karn and William Allen Simpson. In 1995, the former wrote an imple- mentation for Angelos D. Keromytis ported it to OpenBSD and NetBSD. The latest transforms and new features were implemented by Angelos D. Kero- mytis and Niels Provos.
The authors of the IPsec code proper are John Ioannidis, Angelos D. Kero- mytis, and Niels Provos. Niklas Hallqvist and Niels Provos are the authors of isakmpd(8). Eric Young's libdeslite was used in this implementation for the DES algo- rithm. Steve Reid's SHA-1 code was also used. The setsockopt(2)/getsockopt(2) interface follows somewhat loosely the draft-mcdonald-simple-ipsec-api (since expired, but still available from ftp://ftp.kame.net/pub/internet-drafts/)
There's a lot more to be said on this subject. This is just a beginning. At the moment the socket options are not fully implemented. MirOS BSD #10-current September 5, 1997 4
Generated on 2014-02-10 02:47:05 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.