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