admin-guide/cifs/usage.rst

13 servers.  This code was developed in participation with the Protocol Freedom
139 Most current servers support SMB2.1 and SMB3 which are more secure,
144 2.2.5 or later) but the CIFS vfs works fine with a wide variety of CIFS servers.
168 The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers
186 open files (required for strict POSIX compliance).  Windows Servers already
208 Mac or Windows servers::
255 Servers must support either "pure-TCP" (port 445 TCP/IP CIFS connections) or RFC
257 problem as most servers support this.
263 servers can remap such characters when an explicit mapping is specified in
295 		passed in on mount. For mounts to servers
305 		For servers which do not support the CIFS Unix
314 		servers which do not report a uid/gid owner
374 		newer servers (e.g. Samba 3.0.26 or later) do. rsize can be
417 		to servers such as Samba which support the CIFS Unix Extensions.
418 		If you do not trust the servers in your network (your mount
470 		single share (since inode numbers on the servers might not
506 		When mounting to servers via port 139, specifies the RFC1001
569 		posix path name support (this may cause servers to
583 		cifs servers do not yet support requesting advisory
602 		very slow, and some servers may be reliable enough (to risk
623 		This is needed for mounting to some older servers (such
690 		Limit retries to unresponsive servers (usually only
775 			protocol enhancements that allow CIFS servers
777 			as support symbolic links. If you use servers
831 be configured in the file /etc/request-key.conf.  Samba, Windows servers and