Linux Audio

Check our new training course

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