diff options
Diffstat (limited to 'net/sctp/Kconfig')
-rw-r--r-- | net/sctp/Kconfig | 89 |
1 files changed, 89 insertions, 0 deletions
diff --git a/net/sctp/Kconfig b/net/sctp/Kconfig new file mode 100644 index 000000000000..9cba49e2ad43 --- /dev/null +++ b/net/sctp/Kconfig | |||
@@ -0,0 +1,89 @@ | |||
1 | # | ||
2 | # SCTP configuration | ||
3 | # | ||
4 | |||
5 | menu "SCTP Configuration (EXPERIMENTAL)" | ||
6 | depends on INET && EXPERIMENTAL | ||
7 | |||
8 | config IP_SCTP | ||
9 | tristate "The SCTP Protocol (EXPERIMENTAL)" | ||
10 | depends on IPV6 || IPV6=n | ||
11 | select CRYPTO if SCTP_HMAC_SHA1 || SCTP_HMAC_MD5 | ||
12 | select CRYPTO_HMAC if SCTP_HMAC_SHA1 || SCTP_HMAC_MD5 | ||
13 | select CRYPTO_SHA1 if SCTP_HMAC_SHA1 | ||
14 | select CRYPTO_MD5 if SCTP_HMAC_MD5 | ||
15 | ---help--- | ||
16 | Stream Control Transmission Protocol | ||
17 | |||
18 | From RFC 2960 <http://www.ietf.org/rfc/rfc2960.txt>. | ||
19 | |||
20 | "SCTP is a reliable transport protocol operating on top of a | ||
21 | connectionless packet network such as IP. It offers the following | ||
22 | services to its users: | ||
23 | |||
24 | -- acknowledged error-free non-duplicated transfer of user data, | ||
25 | -- data fragmentation to conform to discovered path MTU size, | ||
26 | -- sequenced delivery of user messages within multiple streams, | ||
27 | with an option for order-of-arrival delivery of individual user | ||
28 | messages, | ||
29 | -- optional bundling of multiple user messages into a single SCTP | ||
30 | packet, and | ||
31 | -- network-level fault tolerance through supporting of multi- | ||
32 | homing at either or both ends of an association." | ||
33 | |||
34 | To compile this protocol support as a module, choose M here: the | ||
35 | module will be called sctp. | ||
36 | |||
37 | If in doubt, say N. | ||
38 | |||
39 | config SCTP_DBG_MSG | ||
40 | bool "SCTP: Debug messages" | ||
41 | depends on IP_SCTP | ||
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 | |||
48 | config SCTP_DBG_OBJCNT | ||
49 | bool "SCTP: Debug object counts" | ||
50 | depends on IP_SCTP | ||
51 | help | ||
52 | If you say Y, this will enable debugging support for counting the | ||
53 | type of objects that are currently allocated. This is useful for | ||
54 | identifying memory leaks. If the /proc filesystem is enabled this | ||
55 | debug information can be viewed by | ||
56 | 'cat /proc/net/sctp/sctp_dbg_objcnt' | ||
57 | |||
58 | If unsure, say N | ||
59 | |||
60 | choice | ||
61 | prompt "SCTP: Cookie HMAC Algorithm" | ||
62 | depends on IP_SCTP | ||
63 | default SCTP_HMAC_MD5 | ||
64 | help | ||
65 | HMAC algorithm to be used during association initialization. It | ||
66 | is strongly recommended to use HMAC-SHA1 or HMAC-MD5. See | ||
67 | configuration for Cryptographic API and enable those algorithms | ||
68 | to make usable by SCTP. | ||
69 | |||
70 | config SCTP_HMAC_NONE | ||
71 | bool "None" | ||
72 | help | ||
73 | Choosing this disables the use of an HMAC during association | ||
74 | establishment. It is advised to use either HMAC-MD5 or HMAC-SHA1. | ||
75 | |||
76 | config SCTP_HMAC_SHA1 | ||
77 | bool "HMAC-SHA1" | ||
78 | help | ||
79 | Enable the use of HMAC-SHA1 during association establishment. It | ||
80 | is advised to use either HMAC-MD5 or HMAC-SHA1. | ||
81 | |||
82 | config SCTP_HMAC_MD5 | ||
83 | bool "HMAC-MD5" | ||
84 | help | ||
85 | Enable the use of HMAC-MD5 during association establishment. It is | ||
86 | advised to use either HMAC-MD5 or HMAC-SHA1. | ||
87 | |||
88 | endchoice | ||
89 | endmenu | ||