Kconfig 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212
  1. config CIFS
  2. tristate "CIFS support (advanced network filesystem, SMBFS successor)"
  3. depends on INET
  4. select NLS
  5. select CRYPTO
  6. select CRYPTO_MD4
  7. select CRYPTO_MD5
  8. select CRYPTO_HMAC
  9. select CRYPTO_ARC4
  10. select CRYPTO_ECB
  11. select CRYPTO_DES
  12. select CRYPTO_SHA256
  13. select CRYPTO_CMAC
  14. help
  15. This is the client VFS module for the Common Internet File System
  16. (CIFS) protocol which is the successor to the Server Message Block
  17. (SMB) protocol, the native file sharing mechanism for most early
  18. PC operating systems. The CIFS protocol is fully supported by
  19. file servers such as Windows 2000 (including Windows 2003, Windows 2008,
  20. NT 4 and Windows XP) as well by Samba (which provides excellent CIFS
  21. server support for Linux and many other operating systems). Limited
  22. support for OS/2 and Windows ME and similar servers is provided as
  23. well.
  24. The module also provides optional support for the followon
  25. protocols for CIFS including SMB3, which enables
  26. useful performance and security features (see the description
  27. of CONFIG_CIFS_SMB2).
  28. The cifs module provides an advanced network file system
  29. client for mounting to CIFS compliant servers. It includes
  30. support for DFS (hierarchical name space), secure per-user
  31. session establishment via Kerberos or NTLM or NTLMv2,
  32. safe distributed caching (oplock), optional packet
  33. signing, Unicode and other internationalization improvements.
  34. If you need to mount to Samba or Windows from this machine, say Y.
  35. config CIFS_STATS
  36. bool "CIFS statistics"
  37. depends on CIFS
  38. help
  39. Enabling this option will cause statistics for each server share
  40. mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
  41. config CIFS_STATS2
  42. bool "Extended statistics"
  43. depends on CIFS_STATS
  44. help
  45. Enabling this option will allow more detailed statistics on SMB
  46. request timing to be displayed in /proc/fs/cifs/DebugData and also
  47. allow optional logging of slow responses to dmesg (depending on the
  48. value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
  49. These additional statistics may have a minor effect on performance
  50. and memory utilization.
  51. Unless you are a developer or are doing network performance analysis
  52. or tuning, say N.
  53. config CIFS_WEAK_PW_HASH
  54. bool "Support legacy servers which use weaker LANMAN security"
  55. depends on CIFS
  56. help
  57. Modern CIFS servers including Samba and most Windows versions
  58. (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
  59. security mechanisms. These hash the password more securely
  60. than the mechanisms used in the older LANMAN version of the
  61. SMB protocol but LANMAN based authentication is needed to
  62. establish sessions with some old SMB servers.
  63. Enabling this option allows the cifs module to mount to older
  64. LANMAN based servers such as OS/2 and Windows 95, but such
  65. mounts may be less secure than mounts using NTLM or more recent
  66. security mechanisms if you are on a public network. Unless you
  67. have a need to access old SMB servers (and are on a private
  68. network) you probably want to say N. Even if this support
  69. is enabled in the kernel build, LANMAN authentication will not be
  70. used automatically. At runtime LANMAN mounts are disabled but
  71. can be set to required (or optional) either in
  72. /proc/fs/cifs (see fs/cifs/README for more detail) or via an
  73. option on the mount command. This support is disabled by
  74. default in order to reduce the possibility of a downgrade
  75. attack.
  76. If unsure, say N.
  77. config CIFS_UPCALL
  78. bool "Kerberos/SPNEGO advanced session setup"
  79. depends on CIFS && KEYS
  80. select DNS_RESOLVER
  81. help
  82. Enables an upcall mechanism for CIFS which accesses userspace helper
  83. utilities to provide SPNEGO packaged (RFC 4178) Kerberos tickets
  84. which are needed to mount to certain secure servers (for which more
  85. secure Kerberos authentication is required). If unsure, say N.
  86. config CIFS_XATTR
  87. bool "CIFS extended attributes"
  88. depends on CIFS
  89. help
  90. Extended attributes are name:value pairs associated with inodes by
  91. the kernel or by users (see the attr(5) manual page, or visit
  92. <http://acl.bestbits.at/> for details). CIFS maps the name of
  93. extended attributes beginning with the user namespace prefix
  94. to SMB/CIFS EAs. EAs are stored on Windows servers without the
  95. user namespace prefix, but their names are seen by Linux cifs clients
  96. prefaced by the user namespace prefix. The system namespace
  97. (used by some filesystems to store ACLs) is not supported at
  98. this time.
  99. If unsure, say N.
  100. config CIFS_POSIX
  101. bool "CIFS POSIX Extensions"
  102. depends on CIFS_XATTR
  103. help
  104. Enabling this option will cause the cifs client to attempt to
  105. negotiate a newer dialect with servers, such as Samba 3.0.5
  106. or later, that optionally can handle more POSIX like (rather
  107. than Windows like) file behavior. It also enables
  108. support for POSIX ACLs (getfacl and setfacl) to servers
  109. (such as Samba 3.10 and later) which can negotiate
  110. CIFS POSIX ACL support. If unsure, say N.
  111. config CIFS_ACL
  112. bool "Provide CIFS ACL support"
  113. depends on CIFS_XATTR && KEYS
  114. help
  115. Allows fetching CIFS/NTFS ACL from the server. The DACL blob
  116. is handed over to the application/caller. See the man
  117. page for getcifsacl for more information.
  118. config CIFS_DEBUG
  119. bool "Enable CIFS debugging routines"
  120. default y
  121. depends on CIFS
  122. help
  123. Enabling this option adds helpful debugging messages to
  124. the cifs code which increases the size of the cifs module.
  125. If unsure, say Y.
  126. config CIFS_DEBUG2
  127. bool "Enable additional CIFS debugging routines"
  128. depends on CIFS_DEBUG
  129. help
  130. Enabling this option adds a few more debugging routines
  131. to the cifs code which slightly increases the size of
  132. the cifs module and can cause additional logging of debug
  133. messages in some error paths, slowing performance. This
  134. option can be turned off unless you are debugging
  135. cifs problems. If unsure, say N.
  136. config CIFS_DFS_UPCALL
  137. bool "DFS feature support"
  138. depends on CIFS && KEYS
  139. select DNS_RESOLVER
  140. help
  141. Distributed File System (DFS) support is used to access shares
  142. transparently in an enterprise name space, even if the share
  143. moves to a different server. This feature also enables
  144. an upcall mechanism for CIFS which contacts userspace helper
  145. utilities to provide server name resolution (host names to
  146. IP addresses) which is needed for implicit mounts of DFS junction
  147. points. If unsure, say N.
  148. config CIFS_NFSD_EXPORT
  149. bool "Allow nfsd to export CIFS file system"
  150. depends on CIFS && BROKEN
  151. help
  152. Allows NFS server to export a CIFS mounted share (nfsd over cifs)
  153. config CIFS_SMB2
  154. bool "SMB2 and SMB3 network file system support"
  155. depends on CIFS && INET
  156. select NLS
  157. select KEYS
  158. select FSCACHE
  159. select DNS_RESOLVER
  160. help
  161. This enables support for the Server Message Block version 2
  162. family of protocols, including SMB3. SMB3 support is
  163. enabled on mount by specifying "vers=3.0" in the mount
  164. options. These protocols are the successors to the popular
  165. CIFS and SMB network file sharing protocols. SMB3 is the
  166. native file sharing mechanism for the more recent
  167. versions of Windows (Windows 8 and Windows 2012 and
  168. later) and Samba server and many others support SMB3 well.
  169. In general SMB3 enables better performance, security
  170. and features, than would be possible with CIFS (Note that
  171. when mounting to Samba, due to the CIFS POSIX extensions,
  172. CIFS mounts can provide slightly better POSIX compatibility
  173. than SMB3 mounts do though). Note that SMB2/SMB3 mount
  174. options are also slightly simpler (compared to CIFS) due
  175. to protocol improvements.
  176. config CIFS_SMB311
  177. bool "SMB3.1.1 network file system support (Experimental)"
  178. depends on CIFS_SMB2 && INET
  179. help
  180. This enables experimental support for the newest, SMB3.1.1, dialect.
  181. This dialect includes improved security negotiation features.
  182. If unsure, say N
  183. config CIFS_FSCACHE
  184. bool "Provide CIFS client caching support"
  185. depends on CIFS=m && FSCACHE || CIFS=y && FSCACHE=y
  186. help
  187. Makes CIFS FS-Cache capable. Say Y here if you want your CIFS data
  188. to be cached locally on disk through the general filesystem cache
  189. manager. If unsure, say N.