1 .\" $KAME: setkey.8,v 1.49 2001/05/18 05:49:51 sakane Exp $
2 .\" $FreeBSD: src/usr.sbin/setkey/setkey.8,v 1.4.2.15 2003/03/12 22:08:15 trhodes Exp $
4 .\" Copyright (C) 1995, 1996, 1997, 1998, and 1999 WIDE Project.
5 .\" All rights reserved.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. Neither the name of the project nor the names of its contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
37 .Nd "manually manipulate the IPsec SA/SP database"
59 utility adds, updates, dumps, or flushes
60 Security Association Database (SAD) entries
61 as well as Security Policy Database (SPD) entries in the kernel.
65 utility takes a series of operations from the standard input
77 the SPD entries are dumped.
79 Flush the SAD entries.
82 the SPD entries are flushed.
84 Dead SAD entries are usually not displayed with
88 the dead SAD entries will be displayed as well.
89 A dead SAD entry means that
90 it has been expired but remains
91 because it is referenced by SPD entries.
93 Enable to print debugging messages for command parser,
94 without talking to kernel.
95 It is not used usually.
97 Loop forever and dump all the messages transmitted to
101 makes each timestamps unformatted.
103 Add hexadecimal dump on
107 Loop forever with short output on
111 The program will dump messages exchanged on
113 socket, including messages sent from other processes to the kernel.
116 Operations have the following grammar.
117 Note that lines starting with
118 hashmarks ('#') are treated as comment lines.
122 .Ar src Ar dst Ar protocol Ar spi
131 .Ar src Ar dst Ar protocol Ar spi
138 .Ar src Ar dst Ar protocol Ar spi
145 .Ar src Ar dst Ar protocol
148 Remove all SAD entries that match the specification.
155 Clear all SAD entries matched by the options.
162 Dumps all SAD entries matched by the options.
166 .Ar src_range Ar dst_range Ar upperspec Ar policy
173 .Ar src_range Ar dst_range Ar upperspec Fl P Ar direction
182 Clear all SPD entries.
188 Dumps all SPD entries.
192 Meta-arguments are as follows:
194 .Bl -tag -compact -width Ds
197 Source/destination of the secure communication is specified as
201 utility does not consult hostname-to-address for arguments
205 They must be in numeric form.
211 .Bl -tag -width Fl -compact
226 Security Parameter Index (SPI) for the SAD and the SPD.
227 It must be decimal number or hexadecimal number
228 You cannot use the set of SPI values in the range 0 through 255.
235 takes some of the following:
236 .Bl -tag -width Fl -compact
239 Specify a security protocol mode for use.
242 .Li transport , tunnel
249 Specify window size of bytes for replay prevention.
251 must be decimal number in 32-bit word.
254 is zero or not specified, replay check don't take place.
257 Specify the identifier of the policy entry in SPD.
261 .It Fl f Ar pad_option
262 defines the content of the ESP padding.
265 .Bl -tag -width random-pad -compact
267 All of the padding are zero.
269 A series of randomized values are set.
271 A series of sequential increasing numbers started from 1 are set.
274 .It Fl f Li nocyclic-seq
275 Don't allow cyclic sequence number.
279 Specify hard/soft life time duration of the SA.
284 .Bl -tag -width Fl -compact
285 .It Fl E Ar ealgo Ar key
286 Specify an encryption algorithm.
287 .It Fl A Ar aalgo Ar key
288 Specify an authentication algorithm.
292 .Ar protocol Li esp ,
293 it will be treated as ESP payload authentication algorithm.
294 .It Fl C Ar calgo Op Fl R
295 Specify compression algorithm.
298 is not specified with
300 line, the kernel will use well-known IPComp CPI
301 (compression parameter index)
302 on IPComp CPI field on packets, and
304 field will be ignored.
306 field is only for kernel internal use in this case.
307 .\"Therefore, compression protocol number will appear on IPComp CPI field.
313 field will appear on IPComp CPI field on outgoing packets.
315 field needs to be smaller than
325 .Ar protocol Li esp-old
335 .Ar protocol Li ipcomp
341 must be double-quoted character string or series of hexadecimal digits.
348 are specified in separate section.
353 These are selections of the secure communication specified as
354 IPv4/v6 address or IPv4/v6 address range, and it may accompany
355 TCP/UDP port specification.
356 This takes the following form:
359 .Ar address/prefixlen
361 .Ar address/prefixlen[port]
367 must be decimal number.
368 The square bracket around
371 They are not manpage metacharacters.
375 utility does not consult hostname-to-address for arguments
379 They must be in numeric form.
383 Upper-layer protocol to be used.
384 You can use one of words in
397 Also you can use the protocol number.
401 does not work against forwarding case at this moment,
402 as it requires extra reassembly at forwarding node
403 (not implemented at this moment).
404 We have many protocols in
406 but protocols except of TCP, UDP and ICMP may not be suitable to use with IPsec.
407 You have to consider and be careful to use them.
416 is the one of following:
419 .Fl P Ar direction Li discard
422 .Fl P Ar direction Li none
425 .Fl P Ar direction Li ipsec Ar protocol/mode/src-dst/level
429 You must specify the direction of its policy as
437 means the packet matching indexes will be discarded.
439 means that IPsec operation will not take place onto the packet.
441 means that IPsec operation will take place onto the packet.
458 you must specify the end-points addresses of the SA as
464 between these addresses which is used to specify the SA to use.
475 is to be one of the following:
476 .Li default , use , require
479 If the SA is not available in every level, the kernel will request
480 getting SA to the key exchange daemon.
482 means the kernel consults to the system wide default against protocol you
485 sysctl variable, when the kernel processes the packet.
487 means that the kernel use a SA if it's available,
488 otherwise the kernel keeps normal operation.
490 means SA is required whenever the kernel sends a packet matched
493 is the same to require.
494 In addition, it allows the policy to bind with the unique out-bound SA.
495 If you use the SA by manual keying,
496 you can put the decimal number as the policy identifier after
503 must be between 1 and 32767.
505 .Ar extensions Fl u .
511 are not in the syntax described in
512 .Xr ipsec_set_policy 3 .
513 There are little differences in the syntax.
515 .Xr ipsec_set_policy 3
522 The following list shows the supported algorithms.
526 are almost orthogonal.
527 Followings are the list of authentication algorithms that can be used as
535 .Bd -literal -offset indent
536 algorithm keylen (bits) comment
537 hmac-md5 128 ah: rfc2403
539 hmac-sha1 160 ah: rfc2404
540 160 ah-old: 128bit ICV (no document)
541 keyed-md5 128 ah: 96bit ICV (no document)
543 keyed-sha1 160 ah: 96bit ICV (no document)
544 160 ah-old: 128bit ICV (no document)
545 null 0 to 2048 for debugging
546 hmac-sha2-256 256 ah: 96bit ICV (no document)
547 256 ah-old: 128bit ICV (no document)
548 hmac-sha2-384 384 ah: 96bit ICV (no document)
549 384 ah-old: 128bit ICV (no document)
550 hmac-sha2-512 512 ah: 96bit ICV (no document)
551 512 ah-old: 128bit ICV (no document)
554 Followings are the list of encryption algorithms that can be used as
562 .Bd -literal -offset indent
563 algorithm keylen (bits) comment
564 des-cbc 64 esp-old: rfc1829, esp: rfc2405
566 simple 0 to 2048 rfc2410
567 blowfish-cbc 40 to 448 rfc2451
568 cast128-cbc 40 to 128 rfc2451
569 des-deriv 64 ipsec-ciph-des-derived-01 (expired)
570 3des-deriv 192 no document
571 rijndael-cbc 128/192/256 draft-ietf-ipsec-ciph-aes-cbc-00
574 Followings are the list of compression algorithms that can be used as
582 .Bd -literal -offset indent
590 add 3ffe:501:4819::1 3ffe:501:481d::1 esp 123457
591 -E des-cbc "ESP SA!!" ;
593 add 3ffe:501:4819::1 3ffe:501:481d::1 ah 123456
594 -A hmac-sha1 "AH SA configuration!" ;
596 add 10.0.11.41 10.0.11.33 esp 0x10001
597 -E des-cbc "ESP with"
598 -A hmac-md5 "authentication!!" ;
600 get 3ffe:501:4819::1 3ffe:501:481d::1 ah 123456 ;
606 spdadd 10.0.11.41/32[21] 10.0.11.33/32[any] any
607 -P out ipsec esp/tunnel/192.168.0.1-192.168.1.2/require ;
612 The command exits with 0 on success, and non-zero on errors.
615 .Xr ipsec_set_policy 3 ,
622 utility first appeared in WIDE Hydrangea IPv6 protocol stack kit.
623 The command was completely re-designed in June 1998.