1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # SCTP configuration 2 # SCTP configuration
4 # 3 #
5 4
6 menuconfig IP_SCTP 5 menuconfig IP_SCTP
7 tristate "The SCTP Protocol" !! 6 tristate "The SCTP Protocol (EXPERIMENTAL)"
8 depends on INET !! 7 depends on INET && EXPERIMENTAL
9 depends on IPV6 || IPV6=n 8 depends on IPV6 || IPV6=n
10 select CRYPTO 9 select CRYPTO
11 select CRYPTO_HMAC 10 select CRYPTO_HMAC
12 select CRYPTO_SHA1 11 select CRYPTO_SHA1
>> 12 select CRYPTO_MD5 if SCTP_HMAC_MD5
13 select LIBCRC32C 13 select LIBCRC32C
14 select NET_UDP_TUNNEL !! 14 ---help---
15 help <<
16 Stream Control Transmission Protocol 15 Stream Control Transmission Protocol
17 16
18 From RFC 2960 <http://www.ietf.org/r 17 From RFC 2960 <http://www.ietf.org/rfc/rfc2960.txt>.
19 18
20 "SCTP is a reliable transport protoc 19 "SCTP is a reliable transport protocol operating on top of a
21 connectionless packet network such a 20 connectionless packet network such as IP. It offers the following
22 services to its users: 21 services to its users:
23 22
24 -- acknowledged error-free non-dupli 23 -- acknowledged error-free non-duplicated transfer of user data,
25 -- data fragmentation to conform to 24 -- data fragmentation to conform to discovered path MTU size,
26 -- sequenced delivery of user messag 25 -- sequenced delivery of user messages within multiple streams,
27 with an option for order-of-arrival 26 with an option for order-of-arrival delivery of individual user
28 messages, 27 messages,
29 -- optional bundling of multiple use 28 -- optional bundling of multiple user messages into a single SCTP
30 packet, and 29 packet, and
31 -- network-level fault tolerance thr 30 -- network-level fault tolerance through supporting of multi-
32 homing at either or both ends of an 31 homing at either or both ends of an association."
33 32
34 To compile this protocol support as 33 To compile this protocol support as a module, choose M here: the
35 module will be called sctp. Debug me !! 34 module will be called sctp.
36 kernel's dynamic debugging framework <<
37 35
38 If in doubt, say N. 36 If in doubt, say N.
39 37
40 if IP_SCTP 38 if IP_SCTP
41 39
>> 40 config SCTP_DBG_MSG
>> 41 bool "SCTP: Debug messages"
>> 42 help
>> 43 If you say Y, this will enable verbose debugging messages.
>> 44
>> 45 If unsure, say N. However, if you are running into problems, use
>> 46 this option to gather detailed trace information
>> 47
42 config SCTP_DBG_OBJCNT 48 config SCTP_DBG_OBJCNT
43 bool "SCTP: Debug object counts" 49 bool "SCTP: Debug object counts"
44 depends on PROC_FS 50 depends on PROC_FS
45 help 51 help
46 If you say Y, this will enable debug !! 52 If you say Y, this will enable debugging support for counting the
47 type of objects that are currently a !! 53 type of objects that are currently allocated. This is useful for
48 identifying memory leaks. This debug 54 identifying memory leaks. This debug information can be viewed by
49 'cat /proc/net/sctp/sctp_dbg_objcnt' 55 'cat /proc/net/sctp/sctp_dbg_objcnt'
50 56
51 If unsure, say N 57 If unsure, say N
52 choice <<
53 prompt "Default SCTP cookie HMAC encod <<
54 default SCTP_DEFAULT_COOKIE_HMAC_MD5 <<
55 help <<
56 This option sets the default sctp co <<
57 when in doubt select 'md5' <<
58 <<
59 config SCTP_DEFAULT_COOKIE_HMAC_MD5 <<
60 bool "Enable optional MD5 hmac cookie <<
61 help <<
62 Enable optional MD5 hmac based SCTP <<
63 select SCTP_COOKIE_HMAC_MD5 <<
64 58
65 config SCTP_DEFAULT_COOKIE_HMAC_SHA1 !! 59 choice
66 bool "Enable optional SHA1 hmac cookie !! 60 prompt "SCTP: Cookie HMAC Algorithm"
>> 61 default SCTP_HMAC_MD5
67 help 62 help
68 Enable optional SHA1 hmac based SCTP !! 63 HMAC algorithm to be used during association initialization. It
69 select SCTP_COOKIE_HMAC_SHA1 !! 64 is strongly recommended to use HMAC-SHA1 or HMAC-MD5. See
>> 65 configuration for Cryptographic API and enable those algorithms
>> 66 to make usable by SCTP.
>> 67
>> 68 config SCTP_HMAC_NONE
>> 69 bool "None"
>> 70 help
>> 71 Choosing this disables the use of an HMAC during association
>> 72 establishment. It is advised to use either HMAC-MD5 or HMAC-SHA1.
>> 73
>> 74 config SCTP_HMAC_SHA1
>> 75 bool "HMAC-SHA1"
>> 76 help
>> 77 Enable the use of HMAC-SHA1 during association establishment. It
>> 78 is advised to use either HMAC-MD5 or HMAC-SHA1.
70 79
71 config SCTP_DEFAULT_COOKIE_HMAC_NONE !! 80 config SCTP_HMAC_MD5
72 bool "Use no hmac alg in SCTP cookie g !! 81 bool "HMAC-MD5"
73 help 82 help
74 Use no hmac algorithm in SCTP cookie !! 83 Enable the use of HMAC-MD5 during association establishment. It is
>> 84 advised to use either HMAC-MD5 or HMAC-SHA1.
75 85
76 endchoice 86 endchoice
77 <<
78 config SCTP_COOKIE_HMAC_MD5 <<
79 bool "Enable optional MD5 hmac cookie <<
80 help <<
81 Enable optional MD5 hmac based SCTP <<
82 select CRYPTO_HMAC if SCTP_COOKIE_HMAC <<
83 select CRYPTO_MD5 if SCTP_COOKIE_HMAC_ <<
84 <<
85 config SCTP_COOKIE_HMAC_SHA1 <<
86 bool "Enable optional SHA1 hmac cookie <<
87 help <<
88 Enable optional SHA1 hmac based SCTP <<
89 select CRYPTO_HMAC if SCTP_COOKIE_HMAC <<
90 select CRYPTO_SHA1 if SCTP_COOKIE_HMAC <<
91 <<
92 config INET_SCTP_DIAG <<
93 depends on INET_DIAG <<
94 def_tristate INET_DIAG <<
95 <<
96 87
97 endif # IP_SCTP 88 endif # IP_SCTP
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.