Advertisement
Guest User

Untitled

a guest
Jan 15th, 2017
261
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.06 KB | None | 0 0
  1. [global]
  2. nt acl support = yes
  3. acl map full control = no
  4.  
  5. This boolean parameter controls whether smbd(8) will attempt to map
  6. UNIX permissions into Windows NT access control lists. The UNIX
  7. permissions considered are the traditional UNIX owner and group
  8. permissions, as well as POSIX ACLs set on any files or directories.
  9.  
  10. This boolean parameter controls whether smbd(8) maps a POSIX ACE
  11. entry of "rwx" (read/write/execute), the maximum allowed POSIX
  12. permission set, into a Windows ACL of "FULL CONTROL". If this
  13. parameter is set to true any POSIX ACE entry of "rwx" will be
  14. returned in a Windows ACL as "FULL CONTROL", is this parameter is
  15. set to false any POSIX ACE entry of "rwx" will be returned as the
  16. specific Windows ACL bits representing read, write and execute.
  17.  
  18. [global]
  19. acl allow execute always = false
  20. guest ok = no
  21. writeable = yes
  22. available = yes
  23. browseable = yes
  24. printable = no
  25. locking = yes
  26.  
  27. This boolean parameter controls the behaviour of smbd(8) when
  28. receiving a protocol request of "open for execution" from a Windows
  29. client. With Samba 3.6 and older, the execution right in the ACL
  30. was not checked, so a client could execute a file even if it did
  31. not have execute rights on the file. In Samba 4.0, this has been
  32. fixed, so that by default, i.e. when this parameter is set to
  33. "False", "open for execution" is now denied when execution
  34. permissions are not present.
  35.  
  36. If this parameter is set to "True", Samba does not check execute
  37. permissions on "open for execution", thus re-establishing the
  38. behaviour of Samba 3.6. This can be useful to smoothen upgrades
  39. from older Samba versions to 4.0 and newer. This setting is not
  40. meant to be used as a permanent setting, but as a temporary relief:
  41. It is recommended to fix the permissions in the ACLs and reset this
  42. parameter to the default after a certain transition period.
  43.  
  44. If this parameter is yes for a service, then no password is
  45. required to connect to the service. Privileges will be those of the
  46. guest account.
  47.  
  48. This parameter nullifies the benefits of setting restrict anonymous
  49. = 2
  50.  
  51. See the section below on security for more information about this
  52. option.
  53.  
  54. Inverted synonym for read only.
  55.  
  56. An inverted synonym is writeable.
  57.  
  58. If this parameter is yes, then users of a service may not create or
  59. modify files in the service's directory.
  60.  
  61. Note that a printable service (printable = yes) will ALWAYS allow
  62. writing to the directory (user privileges permitting), but only via
  63. spooling operations.
  64.  
  65. This parameter lets you "turn off" a service. If available = no,
  66. then ALL attempts to connect to the service will fail. Such
  67. failures are logged.
  68.  
  69. This controls whether this share is seen in the list of available
  70. shares in a net view and in the browse list.
  71.  
  72. If this parameter is yes, then clients may open, write to and
  73. submit spool files on the directory specified for the service.
  74.  
  75. Note that a printable service will ALWAYS allow writing to the
  76. service path (user privileges permitting) via the spooling of print
  77. data. The read only parameter controls only non-printing access to
  78. the resource.
  79.  
  80. This controls whether or not locking will be performed by the
  81. server in response to lock requests from the client.
  82.  
  83. If locking = no, all lock and unlock requests will appear to
  84. succeed and all lock queries will report that the file in question
  85. is available for locking.
  86.  
  87. If locking = yes, real locking will be performed by the server.
  88.  
  89. This option may be useful for read-only filesystems which may not
  90. need locking (such as CDROM drives), although setting this
  91. parameter of no is not really recommended even in this case.
  92.  
  93. Be careful about disabling locking either globally or in a specific
  94. service, as lack of locking may result in data corruption. You
  95. should never need to set this parameter.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement