| blob | 2230db34edeec1490bb46c02c4652d686ca1b617 |
3 <displayName>
4 </displayName>
5 <description>
6 </description>
7 <resources>
8 <stringTable>
17 <string id="POL_9320E11F_AC80_4A7D_A5C8_1C0F3F727061_Help">This policy setting allows you to execute commands, either local or on remote storage, daily.</string>
18 <string id="POL_825D441F_905E_4C7E_9E4B_03013697C6C1_Help">This policy setting allows you to execute commands, either local or on remote storage, hourly.</string>
19 <string id="POL_D298F3BD_44D9_426D_AF11_3163D31582F6_Help">This policy setting allows you to execute commands, either local or on remote storage, monthly.</string>
20 <string id="POL_3ACC7ECD_8086_4F4A_96DF_85B8FDE2F674_Help">This policy setting allows you to execute commands, either local or on remote storage, weekly.</string>
21 <string id="POL_DB5DF501_6F87_42D4_9FEC_E7F32C498BD3_Help">This policy configures the sudoers file with the lines specified.</string>
24 <string id="POL_33AAE399_07A8_5CC8_882A_393E4B96B259_Help">A list of additional DNS names by which this host can be identified
26 Example: host2.example.com host3.other.com </string>
28 <string id="POL_3CD2A970_826E_518E_B5F0_5E6725FF354D_Help">This global parameter allows the Samba admin
29 to limit what interfaces on a machine will serve SMB requests. It
30 affects file service smbd
31 8 and name service nmbd
32 8 in a slightly different ways.
33 For name service it causes nmbd to bind to ports 137 and 138 on the interfaces listed in the parameter. nmbd also binds to the "all addresses" interface (0.0.0.0) on ports 137 and 138 for the purposes of reading broadcast messages. If this option is not set then nmbd will service name requests on all of these sockets. If is set then nmbd will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the parameter list. As unicast packets are received on the other sockets it allows nmbd to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the list. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for nmbd.
34 For file service it causes smbd 8 to bind only to the interface list given in the parameter. This restricts the networks that smbd will serve, to packets coming in on those interfaces. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces.
35 If is set and the network address 127.0.0.1 is not added to the parameter list smbpasswd 8 may not work as expected due to the reasons covered below.
36 To change a users SMB password, the smbpasswd by default connects to the localhost - 127.0.0.1 address as an SMB client to issue the password change request. If is set then unless the network address 127.0.0.1 is added to the parameter list then smbpasswd will fail to connect in it's default mode. smbpasswd can be forced to use the primary IP interface of the local host by using its smbpasswd 8 -r remote machine parameter, with remote machine set to the IP name of the primary interface of the local host.</string>
38 <string id="POL_109FA3A4_0F92_5052_A7D9_D4BBCA75F765_Help">This controls the backend for storing the configuration. Possible values are file (the default) and registry. When registry is encountered while loading smb.conf, the configuration read so far is dropped and the global options are read from registry instead. So this triggers a registry only configuration. Share definitions are not read immediately but instead registry shares is set to yes. Note: This option can not be set inside the registry configuration itself.
40 Example: registry</string>
42 <string id="POL_08734B25_7265_5D0B_B857_B2E831B624F1_Help">DOS SMB clients assume the server has the same charset as they do. This option specifies which charset Samba should talk to DOS clients.
43 The default depends on which charsets you have installed. Samba tries to use charset 850 but falls back to ASCII in case it is not available. Run testparm 1 to check the default on your system.</string>
45 <string id="POL_4CCDFFB7_07DF_58F9_904E_13A024A3F54A_Help">This parameter specifies whether core dumps should be written on internal exits. Normally set to yes. You should never need to change this.
47 Example: no</string>
49 <string id="POL_5B751E57_31A9_5EC2_A3CD_A8511D74FCFB_Help">This parameter controls the name that multicast DNS support advertises as its' hostname.
50 The default is to use the NETBIOS name which is typically the hostname in all capital letters.
51 A setting of mdns will defer the hostname configuration to the MDNS library that is used.</string>
53 <string id="POL_461A8AAF_F51E_5FF5_9433_A8D25BBCF783_Help">If compiled with proper support for it, Samba will
54 announce itself with multicast DNS services like for example
55 provided by the Avahi daemon.
56 This parameter allows disabling Samba to register itself.</string>
58 <string id="POL_04F98D09_4223_5390_B66F_A6DA05F97FCC_Help">This is a list of NetBIOS names that nmbd will
59 advertise as additional names by which the Samba server is known. This allows one machine to appear in browse lists under multiple names. If a machine is acting as a browse server
60 or logon server none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities.
62 Example: TEST TEST1 TEST2</string>
64 <string id="POL_90CE7832_31B7_51D8_9EF2_92FEF396F49B_Help">This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host's DNS name. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under.
65 Note that the maximum length for a NetBIOS name is 15 characters.
66 There is a bug in Samba that breaks operation of browsing and access to shares if the netbios name is set to the literal name PIPE. To avoid this problem, do not name your Samba server PIPE.
68 Example: MYNAME</string>
70 <string id="POL_3B93FDE1_6461_572C_AD2E_6AEEAE4EA949_Help">This sets the NetBIOS scope that Samba will operate under. This should not be set unless every machine on your LAN also sets this value.</string>
72 <string id="POL_E633B0BE_9CF3_5D79_A9F1_CB782C82A19C_Help">This option specifies the number of seconds added to the delay before a prefork master or worker process is restarted. The restart is initially zero, the prefork backoff increment is added to the delay on each restart up to the value specified by "prefork maximum backoff".
73 Additionally the backoff for an individual service by using "prefork backoff increment: service name" i.e. "prefork backoff increment:ldap = 2" to set the backoff increment to 2.
74 If the backoff increment is 2 and the maximum backoff is 5. There will be a zero second delay for the first restart. A two second delay for the second restart. A four second delay for the third and any subsequent restarts</string>
76 <string id="POL_B4E848BD_E606_552C_8C9F_3F8CC1AEF191_Help">This option controls the number of worker processes that are started for each service when prefork process model is enabled (see samba 8 -M) The prefork children are only started for those services that support prefork (currently ldap, kdc and netlogon). For processes that don't support preforking all requests are handled by a single process for that service.
77 This should be set to a small multiple of the number of CPU's available on the server
78 Additionally the number of prefork children can be specified for an individual service by using "prefork children: service name" i.e. "prefork children:ldap = 8" to set the number of ldap worker processes.</string>
80 <string id="POL_D721EFAF_A53D_57B7_9639_3859CF9CE31E_Help">This option controls the maximum delay before a failed pre-fork process is restarted.</string>
82 <string id="POL_1630255E_61BA_5686_B3E0_995F8C4DAA5E_Help">This option specifies the kerberos realm to use. The realm is used as the ADS equivalent of the NT4 domain. It is usually set to the DNS name of the kerberos server.
84 Example: mysambabox.mycompany.com</string>
86 <string id="POL_E1D45258_0E70_5AF8_AE28_DAB6B318BB8A_Help">This option contains the services that the Samba daemon will run.
87 An entry in the smb.conf file can either override the previous value completely or entries can be removed from or added to it by prefixing them with + or -.
89 Example: -s3fs, +smb</string>
91 <string id="POL_351CFFDA_9DC3_54FB_BE9A_E434F0DB9955_Help">This controls what string will show up in the printer comment box in print
92 manager and next to the IPC connection in net view. It
93 can be any string that you wish to show to your users. It also sets what will appear in browse lists next to the machine name.
94 A %v will be replaced with the Samba version number.
95 A %h will be replaced with the hostname.
97 Example: University of GNUs Samba Server</string>
99 <string id="POL_32A7428D_00FC_5203_9943_2BDCDC3D9E0D_Help">This option specifies the backend that will be used to access the configuration of file shares.
100 Traditionally, Samba file shares have been configured in the smb.conf file and this is still the default.
101 At the moment there are no other supported backends.</string>
103 <string id="POL_ABDCEE90_90DE_55C2_A2DC_1C7D017F4B2B_Help">Specifies the charset the unix machine Samba runs on uses. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use.
104 This is also the charset Samba will use when specifying arguments to scripts that it invokes.
106 Example: ASCII</string>
108 <string id="POL_D1FAAF87_1E1E_596F_A915_BE72D67A5DC5_Help">This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain name used with the domain setting.
110 Example: MYGROUP</string>
112 <string id="POL_163183B9_195A_5290_927E_08FBB6C76AA0_Help">This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NetBIOS over TCP/IP (NBT) traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable.
113 The option takes a list of interface strings. Each string can be in any of the following forms:
114 a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth" an IP address. In this case the netmask is determined from the list of interfaces obtained from the kernel an IP/mask pair. a broadcast/mask pair.
115 The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form.
116 The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms.
117 By default Samba enables all active interfaces that are broadcast capable except the loopback adaptor (IP address 127.0.0.1).
118 In order to support SMB3 multi-channel configurations, smbd understands some extra parameters which can be appended after the actual interface with this extended syntax (note that the quoting is important in order to handle the ; and , characters):
120 Known keys are speed, capability, and if_index. Speed is specified in bits per second. Known capabilities are RSS and RDMA. The if_index should be used with care: the values must not coincide with indexes used by the kernel. Note that these options are mainly intended for testing and development rather than for production use. At least on Linux systems, these values should be auto-detected, but the settings can serve as last a resort when autodetection is not working or is not available. The specified values overwrite the auto-detected values.
121 The first two example below configures three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0.
122 The other examples show how per interface extra parameters can be specified. Notice the possible usage of "," and ";", which makes the double quoting necessary.
134 Example: "eth0;capability=RSS" , "rdma1;capability=RDMA" ; "rdma2;capability=RSS,capability=RDMA"</string>
136 <string id="POL_25731B61_FC84_5A83_93AE_296F7D6311C4_Help">This controls whether smbd 8 will serve a browse list to a client doing a NetServerEnum call. Normally set to yes. You should never need to change this.</string>
138 <string id="POL_3E9E3188_6F1A_54F8_8E13_265E2AD1BE71_Help">Tell smbd 8 to enable WAN-wide browse list collation. Setting this option causes nmbd to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given . Local master browsers in the same on broadcast-isolated subnets will give this nmbd their local browse lists, and then ask smbd 8 for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet.
139 Note that Windows NT Primary Domain Controllers expect to be able to claim this specific special NetBIOS name that identifies them as domain master browsers for that by default (i.e. there is no way to prevent a Windows NT PDC from attempting to do this). This means that if this parameter is set and nmbd claims the special name for a before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail. If yes, then the default behavior is to enable the parameter. If is not enabled (the default setting), then neither will be enabled by default.
140 When Yes the default setting for this parameter is Yes, with the result that Samba will be a PDC. If No, Samba will function as a BDC. In general, this parameter should be set to 'No' only on a BDC.</string>
142 <string id="POL_E14519D2_9B84_5A1B_B4A4_89F6151BFCE2_Help">This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations.
143 The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs.
144 You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists. Due to the restrictions of the browse protocols, these enhancements can cause a empty workgroup to stay around forever which can be annoying.
145 In general you should leave this option enabled as it makes cross-subnet browse propagation much more reliable.</string>
147 <string id="POL_7E8FBFDB_CBDD_5CE7_B101_07AB8AA71209_Help">This parameter determines if nmbd 8 will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list. This parameter can have three values, yes, no, or auto. The default is auto. If set to no Samba will never produce these broadcasts. If set to yes Samba will produce Lanman announce broadcasts at a frequency set by the parameter . If set to auto Samba will not send Lanman announce broadcasts by default but will listen for them. If it hears such a broadcast on the wire it will then start sending them at a frequency set by the parameter .
149 Example: yes</string>
151 <string id="POL_6D665B21_1F08_5183_B9CD_CFD712C1D4AB_Help">If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the parameter) then this parameter defines the frequency in seconds with which they will be made. If this is set to zero then no Lanman announcements will be made despite the setting of the parameter.
155 <string id="POL_40EA4C73_20A7_580A_A830_0EDA7FC72B7D_Help">This option allows nmbd 8 to try and become a local master browser on a subnet. If set to no then nmbd will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By default this value is set to yes. Setting this value to yes doesn't mean that Samba will become the local master browser on a subnet, just that nmbd will participate in elections for local master browser.
156 Setting this value to no will cause nmbd never to become a local
157 master browser.</string>
159 <string id="POL_95C311BC_3067_5654_A978_70326D928F48_Help">This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether nmbd 8 has a chance of becoming a local master browser for the in the local broadcast area.
160 Note: By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes. This parameter is largely auto-configured in the Samba-3 release series and it is seldom necessary to manually override the default setting. Please refer to the chapter on Network Browsing in the Samba-3 HOWTO document for further information regarding the use of this parameter. Note: The maximum value for this parameter is 255. If you use higher values, counting will start at 0!
164 <string id="POL_516D10CE_AECD_50DE_B4F5_D9DBF85FA582_Help">This boolean parameter controls if nmbd 8 is a preferred master browser for its workgroup.
165 If this is set to yes, on startup, nmbd will force an election, and it will have a slight advantage in winning the election. It is recommended that this parameter is used in conjunction with yes, so that nmbd can guarantee becoming a domain master.
166 Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser. This will result in unnecessary broadcast traffic and reduced browsing capabilities.</string>
168 <string id="POL_E468B4EF_D43C_572D_9A57_390D5D22F485_Help">This option determines what kind of updates to the DNS are allowed.
169 DNS updates can either be disallowed completely by setting it to disabled, enabled over secure connections only by setting it to secure only or allowed in all cases by setting it to nonsecure.
171 Example: disabled</string>
173 <string id="POL_7E805DF0_F3AD_55F6_AC1E_B13987AE73FC_Help">This option specifies the list of DNS servers that DNS requests will be forwarded to if they can not be handled by Samba itself.
174 The DNS forwarder is only used if the internal DNS server in Samba is used.
178 <string id="POL_DE5786B0_C694_53AA_85F2_F9B4EB2F9923_Help">This option sets the command that is called when there are DNS updates. It should update the local machines DNS names using TSIG-GSS.
180 Example: /usr/local/sbin/dnsupdate</string>
182 <string id="POL_C5C16F87_0017_5CC1_810B_398855115BC9_Help">When enabled (the default is disabled) unused dynamic dns records are periodically removed. This option should not be enabled for installations created with versions of samba before 4.9. Doing this will result in the loss of static DNS entries. This is due to a bug in previous versions of samba (BUG 12451) which marked dynamic DNS records as static and static records as dynamic. If one record for a DNS name is static (non-aging) then no other record for that DNS name will be scavenged.</string>
184 <string id="POL_23A4E426_BE59_5616_849E_94C825DDFC5B_Help">This option sets the command that is called to apply GPO policies.
185 The samba-gpupdate script applies System Access and Kerberos Policies to the KDC. System Access policies set minPwdAge, maxPwdAge, minPwdLength, and pwdProperties in the samdb. Kerberos Policies set kdc:service ticket lifetime, kdc:user ticket lifetime, and kdc:renewal lifetime in smb.conf.
187 Example: /usr/local/sbin/gpoupdate</string>
189 <string id="POL_D32F3D0B_74B1_5C8F_81B4_CC9574EAB9B7_Help">If a Samba server is a member of a Windows NT or Active Directory Domain (see the domain and ads parameters), then periodically a running winbindd process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called secrets.tdb . This parameter specifies how often this password will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.
192 <string id="POL_07339CF8_68F5_5B5F_9207_93D2E4526C44_Help">This option sets the path to the nsupdate command which is used for GSS-TSIG dynamic DNS updates.</string>
194 <string id="POL_D0F6F805_6160_55CF_9B8B_F5AD874B1E2C_Help">This option sets the command that for updating servicePrincipalName names from spn_update_list.
196 Example: /usr/local/sbin/spnupdate</string>
198 <string id="POL_6FFBB02C_6B3E_5D0E_9193_15F9B38E487D_Help">controls the number of prefix characters from the original name used when generating the mangled names. A larger value will give a weaker hash and therefore more name collisions. The minimum value is 1 and the maximum value is 6.
199 mangle prefix is effective only when mangling method is hash2.
203 <string id="POL_BE8F8AE7_99AC_582E_8105_00326D511339_Help">controls the algorithm used for the generating the mangled names. Can take two different values, "hash" and "hash2". "hash" is the algorithm that was used in Samba for many years and was the default in Samba 2.2.x "hash2" is
204 now the default and is newer and considered a better algorithm (generates less collisions) in
205 the names. Many Win32 applications store the mangled names and so changing to algorithms must not be done lightly as these applications
206 may break unless reinstalled.
208 Example: hash</string>
210 <string id="POL_62095050_5FA9_5E4F_8792_595D30BEF047_Help">This parameter limits the size in memory of any stat cache being used to speed up case insensitive name mappings. It represents the number of kilobyte (1024) units the stat cache can use. A value of zero, meaning unlimited, is not advisable due to increased memory usage. You should not need to change this parameter.
214 <string id="POL_63F6A053_E2E9_57D0_A0F8_003024AD6470_Help">This parameter determines if smbd 8 will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter.</string>
216 <string id="POL_FBDCB316_EDD2_526C_AE9F_32F50A97A72F_Help">The defines whether ldap traffic will be signed or signed and encrypted (sealed). Possible values are plain, sign and seal.
217 The values sign and seal are only available if Samba has been compiled against a modern OpenLDAP version (2.3.x or higher). This option is needed in the case of Domain Controllers enforcing the usage of signed LDAP connections (e.g. Windows 2000 SP3 or higher). LDAP sign and seal can be controlled with the registry key "HKLM\System\CurrentControlSet\Services\ NTDS\Parameters\LDAPServerIntegrity" on the Windows server side.
218 Depending on the used KRB5 library (MIT and older Heimdal versions) it is possible that the message "integrity only" is not supported. In this case, sign is just an alias for seal.
219 The default value is sign. That implies synchronizing the time with the KDC in the case of using Kerberos.</string>
221 <string id="POL_712CFB73_7887_55DD_975B_48DEDBDB9441_Help">The defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retrieving user account information. The is used in conjunction with the admin dn password stored in the private/secrets.tdb file. See the smbpasswd 8 man page for more information on how to accomplish this.
222 The requires a fully specified DN. The is not appended to the .</string>
224 <string id="POL_CEAB52CA_95EB_5DE5_863B_2399BEF5C727_Help">This parameter tells the LDAP library calls which timeout in seconds they should honor during initial connection establishments to LDAP servers. It is very useful in failover scenarios in particular. If one or more LDAP servers are not reachable at all, we do not have to wait until TCP timeouts are over. This feature must be supported by your LDAP library.
225 This parameter is different from which affects operations on LDAP servers using an existing connection and not establishing an initial connection.</string>
227 <string id="POL_4750A945_176C_5FFF_AB50_DF2BE31C3FBB_Help">This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba.</string>
229 <string id="POL_27BBF4DB_E2AE_58D3_8018_E83C4B185A3C_Help">This option controls whether Samba should tell the LDAP library to use a certain alias dereferencing method. The default is auto, which means that the default setting of the ldap client library will be kept. Other possible values are never, finding, searching and always. Grab your LDAP manual for more information.
231 Example: searching</string>
233 <string id="POL_B383A7ED_F6A4_5BD3_B85E_E6B6527D8D79_Help">This option controls whether to follow LDAP referrals or not when searching for entries in the LDAP database. Possible values are on to enable following referrals, off to disable this, and auto, to use the libldap default settings. libldap's choice of following referrals or not is set in /etc/openldap/ldap.conf with the REFERRALS parameter as documented in ldap.conf(5).
235 Example: off</string>
237 <string id="POL_E31CD0A8_5A4A_5657_8ACA_123A200C6E06_Help">This parameter specifies the suffix that is used for groups when these are added to the LDAP directory. If this parameter is unset, the value of will be used instead. The suffix string is prepended to the
238 string so use a partial DN.
240 Example: ou=Groups</string>
242 <string id="POL_FC4495FC_4C6E_50C8_9B37_08D9955A883B_Help">This parameters specifies the suffix that is used when storing idmap mappings. If this parameter is unset, the value of will be used instead. The suffix string is prepended to the string so use a partial DN.
244 Example: ou=Idmap</string>
246 <string id="POL_2ED1402F_4CF6_5CED_BE40_9B112E1238DC_Help">It specifies where machines should be added to the ldap tree. If this parameter is unset, the value of will be used instead. The suffix string is prepended to the string so use a partial DN.
248 Example: ou=Computers</string>
250 <string id="POL_12C5B04D_D734_576A_99F1_7475BC9E90D7_Help">This parameter specifies the number of entries per page.
251 If the LDAP server supports paged results, clients can request subsets of search results (pages) instead of the entire list. This parameter specifies the size of these pages.
255 <string id="POL_DB427B53_CF02_5410_AE37_5BD4E8B968CE_Help">This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password change via SAMBA.
256 The can be set to one of three values: Yes = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time. No = Update NT and LM passwords and update the pwdLastSet time.
257 Only = Only update the LDAP password and let the LDAP server do the rest.</string>
259 <string id="POL_0C51A40C_E06E_5A0A_B160_5EB21289B17D_Help">When Samba is asked to write to a read-only LDAP replica, we are redirected to talk to the read-write master server. This server then replicates our changes back to the 'local' server, however the replication might take some seconds, especially over slow links. Certain client activities, particularly domain joins, can become confused by the 'success' that does not immediately change the LDAP back-end's data.
260 This option simply causes Samba to wait a short time, to allow the LDAP server to catch up. If you have a particularly high-latency network, you may wish to time the LDAP replication with a network sniffer, and increase this value accordingly. Be aware that no checking is performed that the data has actually replicated.
263 <string id="POL_763BAFE2_3FE0_5C25_B3DC_34AE48F2F569_Help">Editposix is an option that leverages ldapsam:trusted to make it simpler to manage a domain controller eliminating the need to set up custom scripts to add and manage the posix users and groups. This option will instead directly manipulate the ldap tree to create, remove and modify user and group entries. This option also requires a running winbindd as it is used to allocate new uids/gids on user/group creation. The allocation range must be therefore configured.
264 To use this option, a basic ldap tree must be provided and the ldap suffix parameters must be properly configured. On virgin servers the default users and groups (Administrator, Guest, Domain Users, Domain Admins, Domain Guests) can be precreated with the command net sam provision. To run this command the ldap server must be running, Winbindd must be running and the smb.conf ldap options must be properly configured.
265 The typical ldap setup used with the yes option is usually sufficient to use yes as well.
266 An example configuration can be the following:
267 encrypt passwords = true passdb backend = ldapsam
268 ldapsam:trusted=yes ldapsam:editposix=yes
269 ldap admin dn = cn=admin,dc=samba,dc=org ldap delete dn = yes ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap user suffix = ou=users ldap suffix = dc=samba,dc=org
272 This configuration assumes a directory layout like described in the following ldif:
273 dn: dc=samba,dc=org objectClass: top objectClass: dcObject objectClass: organization o: samba.org dc: samba
274 dn: cn=admin,dc=samba,dc=org objectClass: simpleSecurityObject objectClass: organizationalRole cn: admin description: LDAP administrator userPassword: secret
275 dn: ou=users,dc=samba,dc=org objectClass: top objectClass: organizationalUnit ou: users
276 dn: ou=groups,dc=samba,dc=org objectClass: top objectClass: organizationalUnit ou: groups
277 dn: ou=idmap,dc=samba,dc=org objectClass: top objectClass: organizationalUnit ou: idmap
278 dn: ou=computers,dc=samba,dc=org objectClass: top objectClass: organizationalUnit ou: computers</string>
280 <string id="POL_F7979912_0010_5656_BC3A_08876A56418C_Help">By default, Samba as a Domain Controller with an LDAP backend needs to use the Unix-style NSS subsystem to access user and group information. Due to the way Unix stores user information in /etc/passwd and /etc/group this inevitably leads to inefficiencies. One important question a user needs to know is the list of groups he is member of. The plain UNIX model involves a complete enumeration of the file /etc/group and its NSS counterparts in LDAP. UNIX has optimized functions to enumerate group membership. Sadly, other functions that are used to deal with user and group attributes lack such optimization.
281 To make Samba scale well in large environments, the yes option assumes that the complete user and group database that is relevant to Samba is stored in LDAP with the standard posixAccount/posixGroup attributes. It further assumes that the Samba auxiliary object classes are stored together with the POSIX data in the same LDAP object. If these assumptions are met, yes can be activated and Samba can bypass the NSS system to query user group memberships. Optimized LDAP queries can greatly speed up domain logon and administration tasks. Depending on the size of the LDAP database a factor of 100 or more for common queries is easily achieved.</string>
283 <string id="POL_04D79AF3_042D_5ABC_BE8F_4C6628E0F703_Help">The defines whether the ldap server requires ldap traffic to be signed or signed and encrypted (sealed). Possible values are no, allow_sasl_over_tls and yes.
284 A value of no allows simple and sasl binds over all transports.
285 A value of allow_sasl_over_tls allows simple and sasl binds (without sign or seal) over TLS encrypted connections. Unencrypted connections only allow sasl binds with sign or seal.
286 A value of yes allows only simple binds over TLS encrypted connections. Unencrypted connections only allow sasl binds with sign or seal.</string>
288 <string id="POL_5B8B9520_4858_5C2F_AA85_F972FF86784A_Help">This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is NOT related to Samba's previous SSL support which was enabled by specifying the --with-ssl option to the configure script.
289 LDAP connections should be secured where possible. This may be done setting either this parameter to start tls or by specifying ldaps:// in
290 the URL argument of .
291 The can be set to one of two values: Off = Never use SSL when querying the directory.
292 start tls = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server. Please note that this parameter does only affect rpc methods. To enable the LDAPv3 StartTLS extended operation (RFC2830) for ads, set start tls and yes. See smb.conf5 for more information on .</string>
294 <string id="POL_42494B88_7254_5F5F_B738_D5D10BCFBC6C_Help">This option is used to define whether or not Samba should use SSL when connecting to the ldap server using ads methods. Rpc methods are not affected by this parameter. Please note, that this parameter won't have any effect if is set to no.
295 See smb.conf5 for more information on .</string>
297 <string id="POL_9B071174_FBD3_5CA8_82AA_3BD1EB7BCF45_Help">Specifies the base for all ldap suffixes and for storing the sambaDomain object.
298 The ldap suffix will be appended to the values specified for the , , , and the . Each of these should be given only a DN relative to the .
300 Example: dc=samba,dc=org</string>
302 <string id="POL_40F4D046_B9E1_53B0_9DC9_1AE4DE9B1976_Help">This parameter defines the number of seconds that Samba should use as timeout for LDAP operations.</string>
304 <string id="POL_26984E46_7C64_57A4_B4BF_C2C2B13C330E_Help">This parameter specifies where users are added to the tree. If this parameter is unset, the value of will be used instead. The suffix string is prepended to the string so use a partial DN.
306 Example: ou=people</string>
308 <string id="POL_AB95F2C5_BFBC_5955_8062_8B446AF7E84C_Help">This parameter specifies the maximum permitted size (in bytes) for an LDAP request received on an anonymous connection.
309 If the request size exceeds this limit the request will be rejected.
312 <string id="POL_23FFECD5_A3C4_566C_AEB3_015F25B1A978">ldap max authenticated request size</string>
313 <string id="POL_23FFECD5_A3C4_566C_AEB3_015F25B1A978_Help">This parameter specifies the maximum permitted size (in bytes) for an LDAP request received on an authenticated connection.
314 If the request size exceeds this limit the request will be rejected.
318 <string id="POL_F7C651B1_70B4_5047_BC65_2E4D382CBD15_Help">This parameter specifies the maximum permitted size (in bytes) for an LDAP search request.
319 If the request size exceeds this limit the request will be rejected.
323 <string id="POL_B3B2B9CC_3DBC_5C45_AA31_7C1E52AFEFAF_Help">The time in milliseconds that smbd should keep waiting to see if a failed lock request can be granted. This parameter has changed in default value from Samba 3.0.23 from 10 to 200. The associated parameter is no longer used in Samba 3.0.24. You should not need to change the value of this parameter.</string>
325 <string id="POL_4A0366F2_6815_5654_8DC2_F68E840E53F4_Help">This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients.
326 DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.</string>
328 <string id="POL_B49FAE41_B4C1_5AFA_870E_9E1C35F9A96F_Help">This boolean option tells smbd whether to globally negotiate SMB2 leases on file open requests. Leasing is an SMB2-only feature which allows clients to aggressively cache files locally above and beyond the caching allowed by SMB1 oplocks.
329 This is only available with yes and no.</string>
331 <string id="POL_1E9B5BE6_8C81_5141_88CD_B5AC0E8D964B_Help">With this boolean parameter enabled, the debug class (DBGC_CLASS)
332 will be displayed in the debug header.
335 For more information about currently available debug classes, see
336 section about .</string>
338 <string id="POL_07D2E039_C5A0_5123_BD71_0C74E2569310_Help">Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this
339 boolean parameter adds microsecond resolution to the timestamp message header when turned on.
343 Note that the parameter must be on for this to have an effect.</string>
345 <string id="POL_E066DF4A_5BA1_5B35_A96F_90DE6CF27132_Help">When using only one log file for more then one forked smbd
346 8-process there may be hard to follow which process outputs which
347 message. This boolean parameter is adds the process-id to the timestamp message headers in the
348 logfile when turned on.
352 Note that the parameter must be on for this to have an effect.</string>
354 <string id="POL_4B4EF8B5_3526_5583_8174_E3E332727970_Help">With this option enabled, the timestamp message header is prefixed to the debug message without the
355 filename and function information that is included with the
356 parameter. This gives timestamps to the messages without adding an additional line.
360 Note that this parameter overrides the parameter.</string>
362 <string id="POL_571A8B87_3CCC_5725_BA33_BDEE367BB740_Help">Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the
363 current euid, egid, uid and gid to the timestamp message headers in the log file if turned on.
366 Note that the parameter must be on for this to have an effect.</string>
368 <string id="POL_2167CEE9_B2C9_5574_8F7D_F38DA9EBBFF1_Help">This parameter controls the debug level of the LDAP library calls. In the case of OpenLDAP, it is the same bit-field as understood by the server and documented in the slapd.conf 5 manpage. A typical useful value will be 1 for tracing function calls. The debug output from the LDAP libraries appears with the prefix [LDAP] in Samba's logging output. The level at which LDAP logging is printed is controlled by the parameter ldap debug threshold.
372 <string id="POL_F324946B_9B0D_53F0_AD4F_56800DD63085_Help">This parameter controls the Samba debug level at which the ldap library debug output is printed in the Samba logs. See the description of ldap debug level for details.
376 <string id="POL_3A601C55_A5EB_5E86_817B_38DACFD45CF9_Help">This option allows you to override the name of the Samba log file (also known as the debug file).
380 This option takes the standard substitutions, allowing you to have separate log files for each user or machine.
382 Example: /usr/local/samba/var/log.%m</string>
384 <string id="POL_A3E0303F_93B5_5C1F_8C01_362881F843CC_Help">This parameter configures logging backends. Multiple
385 backends can be specified at the same time, with different log
386 levels for each backend. The parameter is a list of backends,
387 where each backend is specified as backend[:option][@loglevel].
389 The 'option' parameter can be used to pass backend-specific
390 options.
392 The log level for a backend is optional, if it is not set for
393 a backend, all messages are sent to this backend. The parameter
394 determines overall log levels,
395 while the log levels specified here define what is sent to the
396 individual backends.
398 When is set, it overrides the
399 and parameters.
401 Some backends are only available when Samba has been compiled
402 with the additional libraries. The overall list of logging backends:
405 syslog
406 file
407 systemd
408 lttng
409 gpfs
410 ringbuf
413 The ringbuf backend supports an
414 optional size argument to change the buffer size used, the default is 1 MB:
415 ringbuf:size=NBYTES
419 <string id="POL_E077BD91_3587_5DBA_A7CB_13044D97E451_Help">The value of the parameter (a string) allows the debug level (logging level) to be specified in the
420 smb.conf file.
423 This parameter has been extended since the 2.2.x
424 series, now it allows one to specify the debug level for multiple
425 debug classes and distinct logfiles for debug classes. This is to give
426 greater flexibility in the configuration of the system. The following
427 debug classes are currently implemented:
430 all tdb printdrivers lanman smb smb2 smb2_credits rpc_parse rpc_srv rpc_cli passdb sam auth winbind vfs idmap quota acls locking msdfs dmapi registry
431 scavenger
432 dns
433 ldb
434 tevent
435 auth_audit
436 auth_json_audit
437 kerberos
438 dsdb_audit
439 dsdb_json_audit
440 dsdb_password_audit
441 dsdb_password_json_audit
442 dsdb_transaction_audit
443 dsdb_transaction_json_audit
446 To configure the logging for specific classes to go into a different
447 file then , you can append
448 @PATH to the class, eg log level = 1
449 full_audit:1@/var/log/audit.log.
451 Authentication and authorization audit information is logged
452 under the auth_audit, and if Samba was not compiled with
453 --without-json, a JSON representation is logged under
454 auth_json_audit.
456 Support is comprehensive for all authentication and authorisation
457 of user accounts in the Samba Active Directory Domain Controller,
458 as well as the implicit authentication in password changes. In
459 the file server, NTLM authentication, SMB and RPC authorization is
460 covered.
462 Log levels for auth_audit and auth_audit_json are:
463 2: Authentication Failure 3: Authentication Success 4: Authorization Success 5: Anonymous Authentication and Authorization Success
466 Changes to the sam.ldb database are logged
467 under the dsdb_audit and a JSON representation is logged under
468 dsdb_json_audit.
470 Password changes and Password resets are logged under
471 dsdb_password_audit and a JSON representation is logged under the
472 dsdb_password_json_audit.
474 Transaction rollbacks and prepare commit failures are logged under
475 the dsdb_transaction_audit and a JSON representation is logged under the
476 password_json_audit. Logging the transaction details allows the
477 identification of password and sam.ldb operations that have been rolled
478 back.
484 <string id="POL_7E7EB779_098F_5383_A0B3_66216F434918_Help">This option (an integer in kilobytes) specifies the max size the log file should grow to.
485 Samba periodically checks the size and if it is exceeded it will rename the file, adding a .old extension.
486 A size of 0 means no limit.
490 <string id="POL_57C1D731_63A4_519D_BD0B_05683B94BFDB_Help">This parameter maps how Samba debug messages are logged onto the system syslog logging levels.
491 Samba debug level zero maps onto syslog LOG_ERR, debug level one maps onto
492 LOG_WARNING, debug level two maps onto LOG_NOTICE,
493 debug level three maps onto LOG_INFO. All higher levels are mapped to LOG_DEBUG.
497 This parameter sets the threshold for sending messages to syslog. Only messages with debug
498 level less than this value will be sent to syslog. There still will be some
499 logging to log.[sn]mbd even if syslog only is enabled.
502 The parameter should be used
503 instead. When is set, it
504 overrides the parameter.</string>
506 <string id="POL_07C28AF5_BA9B_5B55_A018_28B10E803B26_Help">If this parameter is set then Samba debug messages are logged into the system
507 syslog only, and not to the debug log files. There still will be some logging to log.[sn]mbd even if syslog only is enabled.
511 The parameter should be used
512 instead. When is set, it
513 overrides the parameter.</string>
515 <string id="POL_C2541812_F829_51FC_93D7_75BA34C1F487_Help">Samba debug log messages are timestamped by default. If you are running at a high
516 these timestamps can be distracting. This
517 boolean parameter allows timestamping to be turned off.</string>
519 <string id="POL_3B7BF4ED_04E2_5466_9368_8610A5657F8F_Help">This a full path name to a script called by smbd 8 that should stop a shutdown procedure issued by the . If the connected user possesses the SeRemoteShutdownPrivilege, right, this command will be run as root.
521 Example: /sbin/shutdown -c</string>
523 <string id="POL_7EEBACBA_ED90_5C68_826F_737212B364EF_Help">This is the full pathname to a script that will be run AS ROOT by smbd8 when a new group is requested. It will expand any %g to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. The script is free to create a group with an arbitrary name to circumvent unix group name restrictions. In that case the script must print the numeric gid of the created group on stdout.
525 Example: /usr/sbin/groupadd %g</string>
527 <string id="POL_96F9DA59_163C_56B8_9F66_40CAAD868F91_Help">This is the full pathname to a script that will be run by smbd 8 when a machine is added to Samba's domain and a Unix account matching the machine's name appended with a "$" does not already exist.
528 This option is very similar to the , and likewise uses the %u
529 substitution for the account name. Do not use the %m
530 substitution.
532 Example: /usr/sbin/adduser -n -g machines -c Machine -d /var/lib/nobody -s /bin/false %u</string>
534 <string id="POL_4AEC4EDA_3303_57E2_BC12_784F40DACA8F_Help">This is the full pathname to a script that will be run AS ROOT by smbd 8 under special circumstances described below.
535 Normally, a Samba server requires that UNIX users are created for all users accessing files on this server. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users ON DEMAND when a user accesses the Samba server.
536 When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time, smbd 8 contacts the and attempts to authenticate the given user with the given password. If the authentication succeeds then smbd attempts to find a UNIX user in the UNIX password database to map the Windows user into. If this lookup fails, and is set then smbd will call the specified script AS ROOT, expanding any %u argument to be the user name to create.
537 If this script successfully creates the user then smbd will continue on as though the UNIX user already existed. In this way, UNIX users are dynamically created to match existing Windows NT accounts.
538 See also , , .
540 Example: /usr/local/samba/bin/add_user %u</string>
542 <string id="POL_5268249C_58BD_59DA_B44F_DA9109370C58_Help">Full path to the script that will be called when a user is added to a group using the Windows NT domain administration tools. It will be run by smbd 8 AS ROOT. Any %g will be replaced with the group name and any %u will be replaced with the user name.
543 Note that the adduser command used in the example below does not support the used syntax on all systems.
545 Example: /usr/sbin/adduser %u %g</string>
547 <string id="POL_89206841_7524_5BFF_872C_444F45C82318_Help">This option controls whether the netlogon server (currently only in 'active directory domain controller' mode), will reject clients which does not support NETLOGON_NEG_STRONG_KEYS nor NETLOGON_NEG_SUPPORTS_AES.
548 This option was added with Samba 4.2.0. It may lock out clients which worked fine with Samba versions up to 4.1.x. as the effective default was "yes" there, while it is "no" now.
549 If you have clients without RequireStrongKey = 1 in the registry, you may need to set "allow nt4 crypto = yes", until you have fixed all clients.
550 "allow nt4 crypto = yes" allows weak crypto to be negotiated, maybe via downgrade attacks.
551 This option yields precedence to the 'reject md5 clients' option.</string>
553 <string id="POL_9A41AF51_88E9_5566_B12E_36DEA5C42D49_Help">When enabled, this option causes Samba (acting as an Active Directory Domain Controller) to stream authentication events across the internal message bus. Scripts built using Samba's python bindings can listen to these events by registering as the service auth_event.
554 This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature that the testsuite works around). Additionally Samba must be compiled with the jansson support for this option to be effective.
555 The authentication events are also logged via the normal logging methods when the is set appropriately.</string>
557 <string id="POL_1CAC5DAB_3CB5_586A_AB6F_84E39DDF4796_Help">This is the full pathname to a script that will be run AS ROOT by smbd 8 when a group is requested to be deleted. It will expand any %g to the group name passed. This script is only useful for installations using the Windows NT domain administration tools.</string>
559 <string id="POL_789E0632_E8D7_5FD6_86C6_0EBD079D28C4_Help">Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools. It will be run by smbd 8 AS ROOT. Any %g will be replaced with the group name and any %u will be replaced with the user name.
561 Example: /usr/sbin/deluser %u %g</string>
563 <string id="POL_A399CF3E_C0C6_594B_8F31_F2AA4A18B5AC_Help">This is the full pathname to a script that will be run by smbd 8 when managing users with remote RPC (NT) tools.
564 This script is called when a remote client removes a user from the server, normally using 'User Manager for Domains' or rpcclient.
565 This script should delete the given UNIX username.
567 Example: /usr/local/samba/bin/del_user %u</string>
569 <string id="POL_B35B056A_EEB8_5B89_9FCC_127565F4A6AC_Help">If set to yes, the Samba server will provide the netlogon service for Windows 9X network logons for the it is in. This will also cause the Samba server to act as a domain controller for NT4 style domain services. For more details on setting up this feature see the Domain Control chapter of the Samba HOWTO Collection.</string>
571 <string id="POL_3B3E3AD6_FB80_5225_8EDA_6066E5987CE1_Help">This deprecated parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either net rpc rights or one of the Windows user and group manager tools. This parameter is enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to assign privileges to users or groups which can then result in certain smbd operations running as root that would normally run under the context of the connected user.
572 An example of how privileges can be used is to assign the right to join clients to a Samba controlled domain without providing root access to the server via smbd.
573 Please read the extended description provided in the Samba HOWTO documentation.</string>
575 <string id="POL_130E1C0E_9AED_52F5_B1AB_20FD88C999E8_Help">This parameter specifies a delay in milliseconds for the hosts configured for delayed initial samlogon with .</string>
577 <string id="POL_EEBDC4C9_64BA_58DF_B7A3_C384D6972690_Help">This parameter takes a list of host names, addresses or networks for which the initial samlogon reply should be delayed (so other DCs get preferred by XP workstations if there are any).
578 The length of the delay can be specified with the parameter.
582 <string id="POL_2FCE2207_11A6_5B55_9ECC_49D171438176_Help">This parameter specifies the local path to which the home directory will be connected (see ) and is only used by NT Workstations.
583 Note that this option is only useful if Samba is set up as a logon server.
585 Example: h:</string>
587 <string id="POL_12DCA5BB_14ED_5BC6_AB9D_E6A57E943B24_Help">This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do C:\>NET USE H: /HOME
588 from a command prompt, for example.
589 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
590 This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user's home directory. This is done in the following way:
591 logon home = \\%N\%U\profile
592 This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request. Win9X clients truncate the info to \\server\share when a user does
593 net use /home but use the whole string when dealing with profiles.
594 Note that in prior versions of Samba, the was returned rather than logon home. This broke net use /home but allowed profiles outside the home directory. The current implementation is correct, and can be used for profiles if you use the above trick.
595 Disable this feature by setting "" - using the empty string.
596 This option is only useful if Samba is set up as a logon server.
598 Example: \\remote_smb_server\%U</string>
600 <string id="POL_6C04D9F3_27E3_51A9_82B5_BEB5265E1236_Help">This parameter specifies the directory where roaming profiles (Desktop, NTuser.dat, etc) are stored. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles. To find out how to handle roaming profiles for Win 9X system, see the parameter.
601 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. It also specifies the directory from which the "Application Data", desktop, start menu, network neighborhood, programs and other folders, and their contents, are loaded and displayed on your Windows NT client.
602 The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories. Thereafter, the directories and any of the contents can, if required, be made read-only. It is not advisable that the NTuser.dat file be made read-only - rename it to NTuser.man to achieve the desired effect (a MANdatory profile).
603 Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in. Therefore, it is vital that the logon path does not include a reference to the homes share (i.e. setting this parameter to \\%N\homes\profile_path will cause problems).
604 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
605 Do not quote the value. Setting this as \\%N\profile\%U will break profile handling. Where the tdbsam or ldapsam passdb backend is used, at the time the user account is created the value configured for this parameter is written to the passdb backend and that value will over-ride the parameter value present in the smb.conf file. Any error present in the passdb backend account record must be edited using the appropriate tool (pdbedit on the command-line, or any other locally provided system tool).
606 Note that this option is only useful if Samba is set up as a domain controller.
607 Disable the use of roaming profiles by setting the value of this parameter to the empty string. For example, "". Take note that even if the default setting in the smb.conf file is the empty string, any value specified in the user account settings in the passdb backend will over-ride the effect of setting this parameter to null. Disabling of all roaming profile use requires that the user account settings must also be blank.
608 An example of use is:
610 logon path = \\PROFILESERVER\PROFILE\%U</string>
612 <string id="POL_D354C217_6C18_5AD8_B0A2_DDC89463D0C6_Help">This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS style CR/LF line endings. Using a DOS-style editor to create the file is recommended. The script must be a relative path to the service. If the [netlogon] service specifies a of /usr/local/samba/netlogon, and STARTUP.BAT, then the file that will be downloaded is:
613 /usr/local/samba/netlogon/STARTUP.BAT
615 The contents of the batch file are entirely your choice. A suggested command would be to add NET TIME \\SERVER /SET /YES, to force every machine to synchronize clocks with the same time server. Another use would be to add NET USE U: \\SERVER\UTILS for commonly used utilities, or
617 NET USE Q: \\SERVER\ISO9001_QA
618 for example.
619 Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached.
620 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
621 This option is only useful if Samba is set up as a logon server in a classic domain controller role.
622 If Samba is set up as an Active Directory domain controller, LDAP attribute scriptPath
623 is used instead. For configurations where ldapsam is in use,
624 this option only defines a default value in case LDAP attribute sambaLogonScript
625 is missing.
627 Example: scripts\%U.bat</string>
629 <string id="POL_0AABECB8_5A60_50DA_973A_7EED1138DB0C_Help">This option controls whether the netlogon server (currently only in 'active directory domain controller' mode), will reject clients which does not support NETLOGON_NEG_SUPPORTS_AES.
630 You can set this to yes if all domain members support aes. This will prevent downgrade attacks.
631 This option takes precedence to the 'allow nt4 crypto' option.</string>
633 <string id="POL_68A94D8F_DA35_5CEC_90E6_4FB245FF32D3_Help">Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups. This script sets the primary group in the unix user database when an administrator sets the primary group from the windows user manager or when fetching a SAM with net rpc vampire. %u will be replaced with the user whose primary group is to be set. %g will be replaced with the group to set.
635 Example: /usr/sbin/usermod -g '%g' '%u'</string>
637 <string id="POL_5CDF89E1_F318_5495_BEA0_DA44F0542D49_Help">This a full path name to a script called by smbd
638 8 that should start a shutdown procedure.
639 If the connected user possesses the SeRemoteShutdownPrivilege, right, this command will be run as root.
640 The %z %t %r %f variables are expanded as follows: %z will be substituted with the shutdown message sent to the server. %t will be substituted with the number of seconds to wait before effectively starting the shutdown procedure. %r will be substituted with the switch -r. It means reboot after shutdown for NT. %f will be substituted with the switch -f. It means force the shutdown even if applications do not respond for NT.
641 Shutdown script example:
643 #!/bin/bash
645 time=$2
652 Shutdown does not return so we need to launch it in background.
654 Example: /usr/local/samba/sbin/shutdown %m %t %r %f</string>
656 <string id="POL_3F1B0630_F3F0_5FDE_B66B_1A315CC059B3_Help">Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The add share command is used to define an external program or script which will add a new service definition to smb.conf.
657 In order to successfully execute the add share command, smbd requires that the administrator connects using a root account (i.e. uid == 0) or has the SeDiskOperatorPrivilege. Scripts defined in the add share command parameter are executed as root.
658 When executed, smbd will automatically invoke the add share command with five parameters.
659 configFile - the location of the global smb.conf file.
660 shareName - the name of the new share.
661 pathName - path to an **existing** directory on disk.
662 comment - comment string to associate with the new share.
663 max connections Number of maximum simultaneous connections to this share.
664 This parameter is only used to add file shares. To add printer shares, see the .
666 Example: /usr/local/bin/addshare</string>
668 <string id="POL_66A8EC32_6235_5E7C_A085_189166239268_Help">This parameter controls the lifetime of tokens that the AFS fake-kaserver claims. In reality these never expire but this lifetime controls when the afs client will forget the token.
671 <string id="POL_78946CAB_73BD_507E_96D5_C643814290D0_Help">If you are using the fake kaserver AFS feature, you might want to hand-craft the usernames you are creating tokens for. For example this is necessary if you have users from several domain in your AFS Protection Database. One possible scheme to code users as DOMAIN+User as it is done by winbind with the + as a separator.
672 The mapped user name must contain the cell name to log into, so without setting this parameter there will be no token.
674 Example: %u@afs.samba.org</string>
676 <string id="POL_DEF84B6C_B415_56EB_B3E7_1ED683BFEDE5_Help">In normal operation the option which allows the server to follow symlinks outside of a share path is automatically disabled when are enabled on a Samba server. This is done for security purposes to prevent UNIX clients creating symlinks to areas of the server file system that the administrator does not wish to export. Setting to true disables the link between these two parameters, removing this protection and allowing a site to configure the server to follow symlinks (by setting to "true") even when is turned on. It is not recommended to enable this option unless you fully understand the implications of allowing the server to follow symbolic links created by UNIX clients. For most normal Samba configurations this would be considered a security hole and setting this parameter is not recommended. This option was added at the request of sites who had deliberately set Samba up in this way and needed to continue supporting this functionality without having to patch the Samba code.</string>
678 <string id="POL_8539DC0B_8971_5145_8173_C77681F13A94_Help">If set to no (the default), smbd checks at startup if other smbd versions are running in the cluster and refuses to start if so. This is done to protect data corruption in internal data structures due to incompatible Samba versions running concurrently in the same cluster. Setting this parameter to yes disables this safety check.</string>
680 <string id="POL_A05EAA54_C6F4_567A_8DE6_7541F9B11046_Help">This parameter specifies whether Samba should fork the async smb echo handler. It can be beneficial if your file system can block syscalls for a very long time. In some circumstances, it prolongs the timeout that Windows uses to determine whether a connection is dead. This parameter is only for SMB1. For SMB2 and above TCP keepalives can be used instead.</string>
682 <string id="POL_087EEAB6_7F83_50CF_A3D0_97B4C6F94F67_Help">This is a list of services that you want to be automatically added to the browse lists. This is most useful for homes and printers services that would otherwise not be visible.
683 Note that if you just want all printers in your printcap file loaded then the option is easier.
685 Example: fred lp colorlp</string>
687 <string id="POL_5518624A_7DB9_51BA_A891_F00A40152354_Help">Usually, most of the TDB files are stored in the lock directory. Since Samba 3.4.0, it is possible to differentiate between TDB files with persistent data and TDB files with non-persistent data using the state directory and the cache directory options.
688 This option specifies the directory for storing TDB files containing non-persistent data that will be kept across service restarts. The directory should be placed on persistent storage, but the data can be safely deleted by an administrator.
690 Example: /var/run/samba/locks/cache</string>
692 <string id="POL_3E23F826_A699_511F_9370_F79DBB4977A9_Help">This parameter specifies whether Samba should reply to a client's file change notify requests.
693 You should never need to change this parameter</string>
695 <string id="POL_3EF254FF_4CC2_58A5_9A1B_4E0655610DCA_Help">Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server
696 Manager. The change share command is used to define an external
697 program or script which will modify an existing service definition in smb.conf.
698 In order to successfully execute the change share command, smbd requires that the administrator connects using a root account (i.e. uid == 0) or has the SeDiskOperatorPrivilege. Scripts defined in the change share command parameter are executed as root.
699 When executed, smbd will automatically invoke the change share command with six parameters.
700 configFile - the location of the global smb.conf file.
701 shareName - the name of the new share.
702 pathName - path to an **existing** directory on disk.
703 comment - comment string to associate with the new share.
704 max connections Number of maximum simultaneous connections to this share.
705 CSC policy - client side caching policy in string form. Valid values are: manual, documents, programs, disable.
706 This parameter is only used to modify existing file share definitions. To modify printer shares, use the "Printers..." folder as seen when browsing the Samba host.
708 Example: /usr/local/bin/changeshare</string>
710 <string id="POL_93ADB149_A45A_56A2_9462_0BE437084E47_Help">With this parameter you can add additional addresses that nmbd will register with a WINS server. Similarly, these addresses will be registered by default when net ads dns register is called with yes configured.
714 <string id="POL_306A8E87_1400_5208_8ABF_B9802BFA685B_Help">This parameter specifies whether Samba should contact ctdb for accessing its tdb files and use ctdb as a backend for its messaging backend.
715 Set this parameter to yes only if you have a cluster setup with ctdb running.</string>
717 <string id="POL_2D29302D_8AD7_5BC3_B681_8C54D0A61E68_Help">This allows you to override the config file to use, instead of the default (usually smb.conf). There is a chicken and egg problem here as this option is set in the config file!
718 For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file.
719 This option takes the usual substitutions, which can be very useful.
720 If the config file doesn't exist then it won't be loaded (allowing you to special case the config files of just a few clients).
722 Example: /usr/local/samba/lib/smb.conf.%m</string>
724 <string id="POL_3838911B_D4E6_50BD_B168_85F113E29165_Help">If you set clustering=yes, you need to tell Samba where ctdbd listens on its unix domain socket. The default path as of ctdb 1.0 is /tmp/ctdb.socket which you have to explicitly set for Samba in smb.conf.
726 Example: /tmp/ctdb.socket</string>
728 <string id="POL_57D6924C_3F94_5C29_8F63_39808A84FA0F_Help">In a cluster environment using Samba and ctdb it is critical that locks on central ctdb-hosted databases like locking.tdb are not held for long. With the current Samba architecture it happens that Samba takes a lock and while holding that lock makes file system calls into the shared cluster file system. This option makes Samba warn if it detects that it has held locks for the specified number of milliseconds. If this happens, smbd will emit a debug level 0 message into its logs and potentially into syslog. The most likely reason for such a log message is that an operation of the cluster file system Samba exports is taking longer than expected. The messages are meant as a debugging aid for potential cluster problems.
731 <string id="POL_6392B974_5997_5E87_916F_FCDCCCCA6069_Help">This parameter specifies a timeout in milliseconds for the connection between Samba and ctdb. It is only valid if you have compiled Samba with clustering and if you have set clustering=yes. When something in the cluster blocks, it can happen that we wait indefinitely long for ctdb, just adding to the blocking condition. In a well-running cluster this should never happen, but there are too many components in a cluster that might have hickups. Choosing the right balance for this value is very tricky, because on a busy cluster long service times to transfer something across the cluster might be valid. Setting it too short will degrade the service your cluster presents, setting it too long might make the cluster itself not recover from something severely broken for too long. Be aware that if you set this parameter, this needs to be in the file smb.conf, it is not really helpful to put this into a registry configuration (typical on a cluster), because to access the registry contact to ctdb is required. Setting ctdb timeout to n makes any process waiting longer than n milliseconds for a reply by the cluster panic. Setting it to 0 (the default) makes Samba block forever, which is the highly recommended default.</string>
733 <string id="POL_65E02D5E_EC95_5CD1_9976_6FF4E023ADDD_Help">This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found. Note that the square brackets are NOT given in the parameter value (see example below).
734 There is no default value for this parameter. If this parameter is not given, attempting to connect to a nonexistent service results in an error.
735 Typically the default service would be a , service. Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like %S to make a wildcard service.
736 Note also that any "_" characters in the name of the service used in the default service will get mapped to a "/". This allows for interesting things.
738 Example: pub</string>
740 <string id="POL_6CD86A19_3EBF_5E3B_A686_462CA044C5D8_Help">Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The delete share command is used to define an external program or script which will remove an existing service definition from smb.conf.
741 In order to successfully execute the delete share command, smbd requires that the administrator connects using a root account (i.e. uid == 0) or has the SeDiskOperatorPrivilege. Scripts defined in the delete share command parameter are executed as root.
742 When executed, smbd will automatically invoke the delete share command with two parameters.
743 configFile - the location of the global smb.conf file.
744 shareName - the name of the existing service.
745 This parameter is only used to remove file shares. To delete printer shares, see the .
747 Example: /usr/local/bin/delshare</string>
749 <string id="POL_EA272781_6D7D_5FD5_96BF_069193C67F65_Help">When enabled, this option causes Samba (acting as an Active Directory Domain Controller) to stream Samba database events across the internal message bus. Scripts built using Samba's python bindings can listen to these events by registering as the service dsdb_event.
750 This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature that the testsuite works around).
751 The Samba database events are also logged via the normal logging methods when the is set appropriately.</string>
753 <string id="POL_560BC356_6AEC_5D1A_9859_6479FE0F97C0_Help">When enabled, this option causes Samba (acting as an Active Directory Domain Controller) to stream group membership change events across the internal message bus. Scripts built using Samba's python bindings can listen to these events by registering as the service dsdb_group_event.
754 This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature that the testsuite works around).
755 The group events are also logged via the normal logging methods when the is set appropriately.</string>
757 <string id="POL_2CF8E791_3F03_5CE3_AC93_0B8078E9667D_Help">When enabled, this option causes Samba (acting as an Active Directory Domain Controller) to stream password change and reset events across the internal message bus. Scripts built using Samba's python bindings can listen to these events by registering as the service password_event.
758 This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature that the testsuite works around).
759 The password events are also logged via the normal logging methods when the is set appropriately.</string>
761 <string id="POL_C8A040D9_B798_5FE4_A736_BAD9C81CE976_Help">Path to a file specifying metadata attribute mappings in JSON format. Use
762 by the Elasticsearch backend of the Spotlight RPC service.
764 Example: /usr/share/foo/mymappings.json</string>
766 <string id="POL_66C9072D_C818_5DFB_AB72_5EDDD4CAE999_Help">When enabled, Samba's File Server Remote VSS Protocol (FSRVP) server checks all FSRVP initiated snapshots on startup, and removes any corresponding state (including share definitions) for nonexistent snapshot paths.
768 Example: yes</string>
770 <string id="POL_A7F4325A_910F_5437_B911_6D94050EF882_Help">The File Server Remote VSS Protocol (FSRVP) server includes a message sequence timer to ensure cleanup on unexpected client disconnect. This parameter overrides the default timeout between FSRVP operations. FSRVP timeouts can be completely disabled via a value of 0.
774 <string id="POL_529A6287_1697_57CA_A6D0_811F61A441A0_Help">If is yes, and smbd 8 is also acting as a Win95/98 logon server then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted. At present, only the Sun auto.home map format is understood. The form of the map is:
776 username server:/some/file/system
777 and the program will extract the servername from before the first ':'. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps. A working NIS client is required on the system for this option to work.
779 Example: amd.homedir</string>
781 <string id="POL_3EE25C0A_C920_54B4_8B7B_D0A91CF3E3F1_Help">This parameter specifies whether Samba should ask the kernel for change notifications in directories so that SMB clients can refresh whenever the data on the server changes.
782 This parameter is only used when your kernel supports change notification to user programs using the inotify interface.</string>
784 <string id="POL_15EAB330_0CF4_537E_AD96_8FCECB55194F_Help">This option specifies the directory where lock files will be placed. The lock files are used to implement the option.
785 Note: This option can not be set inside registry configurations. The files placed in this directory are not required across service restarts and can be safely placed on volatile storage (e.g. tmpfs in Linux)
787 Example: /var/run/samba/locks</string>
789 <string id="POL_A53007F8_7951_51F3_9753_B6FA4B38B9B7_Help">When the network connection between a CIFS client and Samba dies, Samba has no option but to simply shut down the server side of the network connection. If this happens, there is a risk of data corruption because the Windows client did not complete all write operations that the Windows application requested. Setting this option to "yes" makes smbd log with a level 0 message a list of all files that have been opened for writing when the network connection died. Those are the files that are potentially corrupted. It is meant as an aid for the administrator to give him a list of files to do consistency checks on.</string>
791 <string id="POL_7DD9B43E_A2B8_59F8_9927_2B56698E65B6_Help">This specifies what command to run when the server receives a WinPopup style message.
792 This would normally be a command that would deliver the message somehow. How this is to be done is up to your imagination.
793 An example is:
795 message command = csh -c 'xedit %s;rm %s' &
797 This delivers the message using xedit, then removes it afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).
798 All messages are delivered as the global guest user. The command takes the standard substitutions, although %u won't work (%U may be better in this case).
799 Apart from the standard substitutions, some additional ones apply. In particular:
800 %s = the filename containing the message. %t = the destination that the message was sent to (probably the server name).
801 %f = who the message is from.
802 You could make this command send mail, or whatever else takes your fancy. Please let us know of any really interesting ideas you have.
803 Here's a way of sending the messages as mail to root:
805 message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
807 If you don't have a message command then the message won't be delivered and Samba will tell the sender there was an error. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered.
808 If you want to silently delete it then try:
810 message command = rm %s
814 <string id="POL_3BDFEE33_A965_5CA9_BC8C_7E5FDA1BB1D5_Help">This option allows you to control what address Samba will send NBT client packets from, and process replies using, including in nmbd. Setting this option should never be necessary on usual Samba servers running only one nmbd.
815 By default Samba will send UDP packets from the OS default address for the destination, and accept replies on 0.0.0.0. This parameter is deprecated. See Yes and for the previous behaviour of controlling the normal listening sockets.
819 <string id="POL_C4D98472_F115_59FD_A3E6_A7984D662B99_Help">This directory will hold a series of named pipes to allow RPC over inter-process communication. This will allow Samba and other unix processes to interact over DCE/RPC without using TCP/IP. Additionally a sub-directory 'np' has restricted permissions, and allows a trusted communication channel between Samba processes
821 Example: /var/run/samba/ncalrpc</string>
823 <string id="POL_4308D035_8B4B_575A_8984_BAC33A169EBA_Help">Get the home share server from a NIS map. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server.
824 When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS). This can be very slow.
825 This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server. When Samba is returning the home share to the client, it will consult the NIS map specified in and return the server listed there.
826 Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server.</string>
828 <string id="POL_359CDEF8_9711_56A5_8621_C50718A5B8A1_Help">This option causes nmbd 8 to explicitly bind to the broadcast address of the local subnets. This is needed to make nmbd work correctly in combination with the option. You should not need to unset this option.</string>
830 <string id="POL_23418947_2DAF_54B3_812C_D9B43F49CFCB_Help">This is a Samba developer option that allows a system command to be called when either smbd 8 or nmbd 8 crashes. This is usually used to draw attention to the fact that a problem occurred.
834 <string id="POL_C5C3267E_6E80_5311_96A5_B492C8C3C0AF_Help">This parameter specifies the perfcount backend to be used when monitoring SMB operations. Only one perfcount module may be used, and it must implement all of the apis contained in the smb_perfcount_handler structure defined in smb.h.</string>
836 <string id="POL_02EAE588_9ED7_589C_A454_5B168B65A48A_Help">This option specifies the directory where pid files will be placed.
838 Example: /var/run/</string>
840 <string id="POL_77C5FC2D_BBFA_5B4E_906F_ED49B11BF069_Help">This turns on or off support for share definitions read from registry. Shares defined in smb.conf take precedence over shares with the same name defined in registry. See the section on registry-based configuration for details.
841 Note that this parameter defaults to no, but it is set to yes when config backend is set to registry.
843 Example: yes</string>
845 <string id="POL_0FB22970_94A4_5403_888E_3CF8242A955C_Help">This option allows you to setup nmbd 8 to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name.
846 This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
847 For example:
850 the above line would cause nmbd to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name, then the one given in the parameter is used instead.
851 The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable.
852 See the chapter on Network Browsing in the Samba-HOWTO book.</string>
854 <string id="POL_B570A06A_7945_5818_B81D_D27007986548_Help">This option allows you to setup nmbd 8 to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This is done in a manner that does not work with any non-Samba servers.
855 This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
856 For example:
858 remote browse sync = 192.168.2.255 192.168.4.255
859 the above line would cause nmbd to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server.
860 The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment.
861 The may be used on networks where there is no WINS server, and may be used on disjoint networks where each network has its own WINS server.</string>
863 <string id="POL_BA134175_B8C1_5781_9585_AF3A47C44354_Help">This boolean option controls whether an incoming SMB1 session setup should kill other connections coming from the same IP. This matches
864 the default Windows 2003 behaviour.
865 Setting this parameter to yes becomes necessary when you have a flaky network and windows decides to reconnect while the old connection still has files with share modes open. These files become inaccessible over the new connection.
866 The client sends a zero VC on the new connection, and Windows 2003 kills all other connections coming from the same IP. This way the locked files are accessible again.
867 Please be aware that enabling this option will kill connections behind a masquerading router, and will not trigger for clients that only use SMB2 or SMB3.</string>
869 <string id="POL_F0071286_C011_5F1C_A520_2DD14DF7682C_Help">Defines whether to use the embedded code or start a separate daemon for the defined rpc services. The rpc_daemon prefix must be followed by the server name, and a value.
870 Two possible values are currently supported: disabled fork
871 The classic method is to run rpc services as internal daemons embedded in smbd, therefore the external daemons are disabled by default.
872 Choosing the fork option will cause samba to fork a separate process for each daemon configured this way. Each daemon may in turn fork a number of children used to handle requests from multiple smbds and direct tcp/ip connections (if the Endpoint Mapper is enabled). Communication with smbd happens over named pipes and require that said pipes are forward to the external daemon (see ).
873 Forked RPC Daemons support dynamically forking children to handle connections. The heuristics about how many children to keep around and how fast to allow them to fork and also how many clients each child is allowed to handle concurrently is defined by parametrical options named after the daemon. Five options are currently supported: prefork_min_children prefork_max_children prefork_spawn_rate prefork_max_allowed_clients prefork_child_min_life
874 To set one of these options use the following syntax: daemonname:prefork_min_children = 5
875 Samba includes separate daemons for spoolss, lsarpc/lsass, netlogon, samr, FSRVP and mdssvc(Spotlight). Currently five daemons are available and they are called: epmd lsasd spoolssd fssd mdssd Example: rpc_daemon:spoolssd = fork</string>
877 <string id="POL_820BF686_A78C_5314_A371_3633A8448DC2_Help">With this option you can define if a rpc service should be running internal/embedded in smbd or should be redirected to an external daemon like Samba4, the endpoint mapper daemon, the spoolss daemon or the new LSA service daemon. The rpc_server prefix must be followed by the pipe name, and a value.
878 This option can be set for each available rpc service in Samba. The following list shows all available pipe names services you can modify with this option.
879 epmapper - Endpoint Mapper winreg - Remote Registry Service srvsvc - Remote Server Services lsarpc - Local Security Authority samr - Security Account Management netlogon - Netlogon Remote Protocol netdfs - Settings for Distributed File System dssetup - Active Directory Setup wkssvc - Workstation Services spoolss - Network Printing Spooler svcctl - Service Control ntsvcs - Plug and Play Services eventlog - Event Logger initshutdown - Init Shutdown Service mdssvc - Spotlight
880 Three possible values currently supported are: embedded external disabled
881 The classic method is to run every pipe as an internal function embedded in smbd. The defaults may vary depending on the service.
882 Choosing the external option allows one to run a separate daemon or even a completely independent (3rd party) server capable of interfacing with samba via the MS-RPC interface over named pipes.
883 Currently in Samba3 we support four daemons, spoolssd, epmd, lsasd and mdssd. These daemons can be enabled using the rpc_daemon option. For spoolssd you have to enable the daemon and proxy the named pipe with:
884 Examples: rpc_daemon:lsasd = fork rpc_server:lsarpc = external rpc_server:samr = external rpc_server:netlogon = external
885 rpc_server:spoolss = external rpc_server:epmapper = disabled
886 rpc_daemon:mdssd = fork rpc_server:mdssvc = external
887 There is one special option which allows you to enable rpc services to listen for ncacn_ip_tcp connections too. Currently this is only used for testing and doesn't scale!
888 rpc_server:tcpip = yes</string>
890 <string id="POL_70434A64_4979_53D2_80EE_09FBF1562741_Help">This parameter allows the administrator to enable profiling support. Possible values are off, count and on.
892 Example: on</string>
894 <string id="POL_9598A191_3D22_5B49_8188_8D6901A5B4CE_Help">Usually, most of the TDB files are stored in the lock directory. Since Samba 3.4.0, it is possible to differentiate between TDB files with persistent data and TDB files with non-persistent data using the state directory and the cache directory options.
895 This option specifies the directory where TDB files containing important persistent data will be stored.
897 Example: /var/run/samba/locks/state</string>
899 <string id="POL_73FD8B56_579A_5BC6_A49A_4000BE94A02F_Help">This parameter controls whether user defined shares are allowed to be accessed by non-authenticated users or not. It is the equivalent of allowing people who can create a share the option of setting guest ok = yes in a share definition. Due to its security sensitive nature, the default is set to off.</string>
901 <string id="POL_A0CE47E8_AE8A_5602_8265_1C8D3AEC6064_Help">This parameter specifies the number of user defined shares that are allowed to be created by users belonging to the group owning the usershare directory. If set to zero (the default) user defined shares are ignored.</string>
903 <string id="POL_411611B5_93F6_546F_B68B_05167A064628_Help">This parameter controls whether the pathname exported by a user defined shares must be owned by the user creating the user defined share or not. If set to True (the default) then smbd checks that the directory path being shared is owned by the user who owns the usershare file defining this share and refuses to create the share if not. If set to False then no such check is performed and any directory path may be exported regardless of who owns it.</string>
905 <string id="POL_DD97B40A_CB2A_5818_8D39_F94911EB3F13_Help">This parameter specifies the absolute path of the directory on the filesystem used to store the user defined share definition files. This directory must be owned by root, and have no access for other, and be writable only by the group owner. In addition the "sticky" bit must also be set, restricting rename and delete to owners of a file (in the same way the /tmp directory is usually configured). Members of the group owner of this directory are the users allowed to create usershares. For example, a valid usershare directory might be /usr/local/samba/lib/usershares, set up as follows. ls -ld /usr/local/samba/lib/usershares/ drwxrwx--T 2 root power_users 4096 2006-05-05 12:27 /usr/local/samba/lib/usershares/ In this case, only members of the group "power_users" can create user defined shares.</string>
907 <string id="POL_4AAFAB11_EB55_5600_A574_08E074B5DC28_Help">This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions. If the pathname to be exported doesn't start with one of the strings in this list, the user defined share will not be allowed. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares. If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation.
909 Example: /home /data /space</string>
911 <string id="POL_1D783E13_3E5A_5FEB_B1C0_486FF385960E_Help">This parameter specifies a list of absolute pathnames the root of which are NOT allowed to be exported by user defined share definitions. If the pathname exported starts with one of the strings in this list the user defined share will not be allowed. Any pathname not starting with one of these strings will be allowed to be exported as a usershare. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares. If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation.
913 Example: /etc /dev /private</string>
915 <string id="POL_2974E59A_2225_59CA_A4C8_C967FDB0E588_Help">User defined shares only have limited possible parameters such as path, guest ok, etc. This parameter allows usershares to "cloned" from an existing share. If "usershare template share" is set to the name of an existing share, then all usershares created have their defaults set from the parameters set on this share. The target share may be set to be invalid for real file sharing by setting the parameter "-valid = False" on the template share definition. This causes it not to be seen as a real exported share but to be able to be used as a template for usershares.
917 Example: template_share</string>
919 <string id="POL_99ADA47F_F025_52B8_B8F5_DDFA0EEFEF31_Help">This boolean parameter is only available if Samba has been configured and compiled with the option --with-utmp. If set to yes then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.
920 Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user. Enabling this option creates an n^2 algorithm to find this number. This may impede performance on large installations.</string>
922 <string id="POL_21565354_4253_5482_97D2_9C2558461C47_Help">This parameter is only available if Samba has been configured and compiled with the option --with-utmp. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually /var/run/utmp on Linux).
924 Example: /var/run/utmp</string>
926 <string id="POL_4F8E9BC0_CFAB_52F8_9C49_B8BB7400E60A_Help">This parameter is only available if Samba has been configured and compiled with the option --with-utmp. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server. The difference with the utmp directory is the fact that user info is kept after a user has logged out. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually /var/run/wtmp on Linux).
928 Example: /var/log/wtmp</string>
930 <string id="POL_83F826D3_2069_552C_8376_C0512E99728D_Help">Samba 3.0.23 introduced support for adding printer ports remotely using the Windows "Add Standard TCP/IP Port Wizard". This option defines an external program to be executed when smbd receives a request to add a new Port to the system. The script is passed two parameters:
931 port name device URI
933 The deviceURI is in the format of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>.
935 Example: /etc/samba/scripts/addport.sh</string>
937 <string id="POL_B4BE84FF_FB13_5496_AC34_B15BF764F654_Help">With the introduction of MS-RPC based printing
939 Printer Wizard (APW) icon is now also available in the
941 allows for printers to be add remotely to a Samba or Windows
942 NT/2000 print server.
943 For a Samba host this means that the printer must be
944 physically added to the underlying printing system.
945 The addprinter command
946 defines a script to be run which
947 will perform the necessary operations for adding the printer
948 to the print system and to add the appropriate service definition
949 to the smb.conf file in order that it can be
950 shared by smbd
951 8.
952 The addprinter command is
953 automatically invoked with the following parameter (in
954 order):
955 printer name share name port name driver name location Windows 9x driver location
957 All parameters are filled in from the PRINTER_INFO_2 structure sent
959 driver location" parameter is included for backwards compatibility
960 only. The remaining fields in the structure are generated from answers
961 to the APW questions.
963 Once the addprinter command has
964 been executed, smbd will reparse the
965 smb.conf to determine if the share defined by the APW
966 exists. If the sharename is still invalid, then smbd
967 will return an ACCESS_DENIED error to the client.
970 The addprinter command program
971 can output a single line of text,
972 which Samba will set as the port the new printer is connected to.
973 If this line isn't output, Samba won't reload its printer shares.
975 Example: /usr/bin/addprinter</string>
977 <string id="POL_D9D048A2_779C_5D85_A26E_131535508B70_Help">This parameter is only applicable if is set to cups.
981 If set, this option specifies the number of seconds that smbd will wait
982 whilst trying to contact to the CUPS server. The connection will fail
983 if it takes longer than this number of seconds.
987 <string id="POL_AB9D00A2_AB72_5D21_94C6_8EC1238F2793_Help">This parameter is only applicable if is set to cups and if you use CUPS newer than 1.0.x.It is used to define whether or not Samba should use encryption when talking to the CUPS server. Possible values are auto, yes and no
988 When set to auto we will try to do a TLS handshake on each CUPS connection setup. If that fails, we will fall back to unencrypted operation.</string>
990 <string id="POL_CDEAD263_A87A_550A_A067_3FF8C0C60986_Help">This parameter is only applicable if is set to cups.
994 If set, this option overrides the ServerName option in the CUPS client.conf. This is
995 necessary if you have virtual samba servers that connect to different CUPS daemons.
998 Optionally, a port can be specified by separating the server name and port number with a colon. If no port was specified, the default port for IPP (631) will be used.
1000 Example: mycupsserver
1004 <string id="POL_7CC90037_633A_5C8D_99C5_380E6B2E1EF0_Help">With the introduction of MS-RPC based printer
1006 possible to delete a printer at run time by issuing the
1007 DeletePrinter() RPC call.
1008 For a Samba host this means that the printer must be
1009 physically deleted from the underlying printing system. The
1010 defines a script to be run which
1011 will perform the necessary operations for removing the printer
1012 from the print system and from smb.conf.
1014 The is
1015 automatically called with only one parameter: .
1016 Once the has
1017 been executed, smbd will reparse the
1018 smb.conf to check that the associated printer no longer exists.
1019 If the sharename is still valid, then smbd
1020 will return an ACCESS_DENIED error to the client.
1022 Example: /usr/bin/removeprinter</string>
1024 <string id="POL_60B548F0_E8B3_576F_B520_D4954AF3ED8E_Help">Enabling this parameter will disable Samba's support
1025 for the SPOOLSS set of MS-RPC's and will yield identical behavior
1027 Lanman style printing commands. Windows 9x/ME will be unaffected by
1028 the parameter. However, this will also disable the ability to upload
1029 printer drivers to a Samba server via the Windows NT Add Printer
1030 Wizard or by using the NT printer properties dialog window. It will
1031 also disable the capability of Windows NT/2000 clients to download
1032 print drivers from the Samba host upon demand.
1033 Be very careful about enabling this parameter.</string>
1037 <string id="POL_88C2E1AE_E15B_561A_83B3_A7A7610CB3A2_Help">The concept of a "port" is fairly foreign
1038 to UNIX hosts. Under Windows NT/2000 print servers, a port
1039 is associated with a port monitor and generally takes the form of
1040 a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
1041 (i.e. LPD Port Monitor, etc...). By default, Samba has only one
1043 Windows NT/2000, all printers must have a valid port name.
1044 If you wish to have a list of ports displayed (smbd
1045 does not use a port name for anything) other than
1047 can define enumports command to point to
1048 a program which should generate a list of ports, one per line,
1049 to standard output. This listing will then be used in response
1052 Example: /usr/bin/listports</string>
1054 <string id="POL_5247D3AE_60E1_526B_B3A0_956818E2EA49_Help">This parameter is only applicable if is set to iprint.
1058 If set, this option overrides the ServerName option in the CUPS client.conf. This is
1059 necessary if you have virtual samba servers that connect to different CUPS daemons.
1061 Example: MYCUPSSERVER</string>
1063 <string id="POL_A6ACC104_2480_55A0_A53C_D38DFF7A093B_Help">A boolean variable that controls whether all
1064 printers in the printcap will be loaded for browsing by default.
1065 See the section for
1066 more details.</string>
1068 <string id="POL_5CC89C3B_45B2_5C52_ADE0_79FB968E5EDE_Help">This controls how long lpq info will be cached for to prevent the lpq command being called too often. A separate cache is kept for each variation of the lpq command used by the system, so if you use different lpq commands for different users then they won't share cache information.
1069 The cache files are stored in /tmp/lpq.xxxx where xxxx is a hash of the lpq command in use.
1070 The default is 30 seconds, meaning that the cached results of a previous identical lpq command will be used if the cached data is less than 30 seconds old. A large value may be advisable if your lpq command is very slow.
1072 A value of 0 will disable caching completely.
1076 <string id="POL_45819251_B577_5069_AA0C_AD798BFDC903_Help">The parameter is used to define the absolute
1077 path to a file containing a mapping of Windows NT printer driver
1078 names to OS/2 printer driver names. The format is:
1080 For example, a valid entry using the HP LaserJet 5
1081 printer driver would appear as HP LaserJet 5L = LASERJET.HP
1082 LaserJet 5L.
1084 The need for the file is due to the printer driver namespace problem described in
1085 the chapter on Classical Printing in the Samba3-HOWTO book. For more
1086 details on OS/2 clients, please refer to chapter on other clients in the Samba3-HOWTO book.</string>
1088 <string id="POL_40CAC79E_549A_5AAA_8FD3_DDF6FDC3EF35_Help">This option specifies the number of seconds before the printing
1089 subsystem is again asked for the known printers.
1092 Setting this parameter to 0 disables any rescanning for new
1093 or removed printers after the initial startup.
1097 <string id="POL_A0530959_BE77_53B1_82AC_B3E11CA6D2D8_Help">This parameter may be used to override the compiled-in default printcap name used by the server (usually /etc/printcap). See the discussion of the [printers] section above for reasons why you might want to do this.
1099 To use the CUPS printing interface set printcap name = cups . This should be supplemented by an additional setting cups in the [global] section. printcap name = cups will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file.
1102 On System V systems that use lpstat to
1103 list available printers you can use printcap name = lpstat
1104 to automatically obtain lists of available printers. This
1105 is the default for systems that define SYSV at configure time in
1106 Samba (this includes most System V based systems). If
1107 printcap name is set to lpstat on
1108 these systems then Samba will launch lpstat -v and
1109 attempt to parse the output to obtain a printer list.
1111 A minimal printcap file would look something like this:
1113 print1|My Printer 1
1114 print2|My Printer 2
1115 print3|My Printer 3
1116 print4|My Printer 4
1117 print5|My Printer 5
1119 where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba that it's a comment.
1121 Under AIX the default printcap name is /etc/qconfig. Samba will assume the file is in AIX qconfig format if the string qconfig appears in the printcap filename.
1123 Example: /etc/myprintcap</string>
1125 <string id="POL_73B2297D_6138_544A_BAF8_A31CC8192C22_Help">With the introduction of MS-RPC based printing support
1127 appear on Samba hosts in the share listing. Normally this folder will
1128 contain an icon for the MS Add Printer Wizard (APW). However, it is
1129 possible to disable this feature regardless of the level of privilege
1130 of the connected user.
1131 Under normal circumstances, the Windows NT/2000 client will
1132 open a handle on the printer server with OpenPrinterEx() asking for
1133 Administrator privileges. If the user does not have administrative
1134 access on the print server (i.e is not root or has granted the
1135 SePrintOperatorPrivilege), the OpenPrinterEx()
1136 call fails and the client makes another open call with a request for
1137 a lower privilege level. This should succeed, however the APW
1138 icon will not be displayed.
1139 Disabling the show add printer wizard
1140 parameter will always cause the OpenPrinterEx() on the server to fail. Thus the APW icon will never be displayed.
1142 This does not prevent the same user from having administrative privilege on an individual printer.</string>
1144 <string id="POL_3CD8EF2C_23D9_58C5_A92C_3E1C2E4F3A4A_Help">Windows spoolss print clients only allow association of server-side drivers with printers when the driver architecture matches the advertised print server architecture. Samba's spoolss print server architecture can be changed using this parameter.
1146 Example: Windows x64</string>
1148 <string id="POL_DE5BD97B_EB5B_571A_98EE_814B2C006262_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 5.0.2195 (Windows 2000). The example is 6.1.7601 (Windows 2008 R2).
1152 <string id="POL_5EB4315D_6DDE_50E9_A228_2F5062CB23B9_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 5.0.2195 (Windows 2000). The example is 6.1.7601 (Windows 2008 R2).
1156 <string id="POL_FEE2B5DC_E367_5173_8A6A_43EB82F22680_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 5.0.2195 (Windows 2000). The example is 6.1.7601 (Windows 2008 R2).
1160 <string id="POL_6E7AC428_65F6_5006_97A7_B985AE445E43_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 6.1.7007 (Windows 7 and Windows Server 2008 R2).</string>
1162 <string id="POL_732E108C_5701_547E_903E_6112EDF3E999_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 6.1.7007 (Windows 7 and Windows Server 2008 R2).</string>
1164 <string id="POL_CBC8563A_7BEB_54F3_8554_74815EF130DF_Help">Windows might require a new os version number. This option allows to modify the build number. The complete default version number is: 6.1.7007 (Windows 7 and Windows Server 2008 R2).</string>
1166 <string id="POL_A51777A2_FA82_5D61_B7E1_9B223537A750_Help">This option controls the port used by the CLDAP protocol.
1170 <string id="POL_E2162FCB_2AF4_5BED_8254_84C87787CAA8_Help">The value of the parameter (a string) is the highest
1171 protocol level that will be supported for IPC$ connections as DCERPC transport.
1173 Normally this option should not be set as the automatic
1174 negotiation phase in the SMB protocol takes care of choosing
1175 the appropriate protocol.
1177 The value default refers to the latest
1178 supported protocol, currently SMB3_11.
1180 See for a full list
1181 of available protocols. The values CORE, COREPLUS, LANMAN1, LANMAN2
1182 are silently upgraded to NT1.
1184 Example: SMB2_10</string>
1186 <string id="POL_86DD41DB_D3AE_5445_8E2D_335E8182ECDF_Help">This setting controls the minimum protocol version that the will be attempted to use for IPC$ connections as DCERPC transport.
1187 Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.
1188 The value default refers to the higher value of NT1 and the effective value of .
1189 See for a full list of available protocols. The values CORE, COREPLUS, LANMAN1, LANMAN2 are silently upgraded to NT1.
1191 Example: SMB3_11</string>
1193 <string id="POL_8E18914D_E4D5_5B9E_8641_02F84DEA8092_Help">The value of the parameter (a string) is the highest
1194 protocol level that will be supported by the client.
1196 Possible values are :
1197 CORE: Earliest version. No concept of user names. COREPLUS: Slight improvements on CORE for efficiency.
1198 LANMAN1: First modern version of the protocol. Long filename support.
1199 LANMAN2: Updates to Lanman1 protocol.
1200 NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
1201 SMB2: Re-implementation of the SMB protocol. Used by Windows Vista and later versions of Windows. SMB2 has sub protocols available. SMB2_02: The earliest SMB2 version. SMB2_10: Windows 7 SMB2 version. By default SMB2 selects the SMB2_10 variant.
1202 SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols available. SMB3_00: Windows 8 SMB3 version. SMB3_02: Windows 8.1 SMB3 version. SMB3_11: Windows 10 SMB3 version. By default SMB3 selects the SMB3_11 variant.
1205 Normally this option should not be set as the automatic
1206 negotiation phase in the SMB protocol takes care of choosing
1207 the appropriate protocol.
1209 The value default refers to SMB3_11.
1211 IPC$ connections for DCERPC e.g. in winbindd, are handled by the
1212 option.
1214 Example: LANMAN1</string>
1216 <string id="POL_277C30D1_A2C2_5AB4_8748_A9ECC063AE91_Help">This setting controls the minimum protocol version that the client will attempt to use.
1217 Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol unless you connect to a legacy SMB1-only server.
1218 See client max protocol for a full list of available protocols.
1219 IPC$ connections for DCERPC e.g. in winbindd, are handled by the option.
1220 Note that most command line tools support --option='client min protocol=NT1', so it may not be required to enable SMB1 protocols globally in smb.conf.
1222 Example: NT1</string>
1224 <string id="POL_89A40B64_721B_55DF_841D_C3481F32C2FF_Help">This variable controls whether Samba clients will try
1225 to use Simple and Protected NEGOtiation (as specified by rfc2478) with
1226 supporting servers (including WindowsXP, Windows2000 and Samba
1227 3.0) to agree upon an authentication
1228 mechanism. This enables Kerberos authentication in particular.
1230 When is also set to
1231 yes extended security (SPNEGO) is required
1232 in order to use NTLMv2 only within NTLMSSP. This behavior was
1235 <string id="POL_FCF4AF88_1B2D_5A6E_B630_7E88FA13F4EB_Help">Specifies which DCE/RPC endpoint servers should be run.
1237 Example: rpcecho</string>
1239 <string id="POL_73CE9581_7CF3_5CD8_ABBD_3DD273E7ED10_Help">Windows allows specifying how a file will be shared with other processes when it is opened. Sharing violations occur when a file is opened by a different process using options that violate the share settings specified by other processes. This parameter causes smbd to act as a Windows server does, and defer returning a "sharing violation" error message for up to one second, allowing the client to close the file causing the violation in the meantime.
1240 UNIX by default does not have this behaviour.
1241 There should be no reason to turn off this parameter, as it is designed to enable Samba to more correctly emulate Windows.</string>
1243 <string id="POL_951C9DAC_2C21_58B0_8B22_D9D2CCEB1755_Help">Specifies which ports the server should listen on for NetBIOS datagram traffic.</string>
1245 <string id="POL_401F735E_7E1F_5EBC_A3E3_9642A9F023DA_Help">Enabling this parameter will disable netbios support
1246 in Samba. Netbios is the only available form of browsing in
1247 all windows versions except for 2000 and XP.
1249 Clients that only support netbios won't be able to
1250 see your samba server when netbios support is disabled.</string>
1252 <string id="POL_6BB5884D_D948_5765_B165_FCB496E3A64A_Help">Hosts running the "Advanced Server for Unix (ASU)" product
1253 require some special accommodations such as creating a builtin [ADMIN$]
1254 share that only supports IPC connections. The has been the default
1255 behavior in smbd for many years. However, certain Microsoft applications
1256 such as the Print Migrator tool require that the remote server support
1257 an [ADMIN$] file share. Disabling this parameter allows for creating
1258 an [ADMIN$] file share in smb.conf.</string>
1260 <string id="POL_D389B35D_C2C8_5971_A195_FBD8C0AAC94C_Help">This option defines a list of log names that Samba will
1261 report to the Microsoft EventViewer utility. The listed
1262 eventlogs will be associated with tdb file on disk in the
1263 $(statedir)/eventlog.
1267 The administrator must use an external process to parse the normal
1268 Unix logs such as /var/log/messages
1269 and write then entries to the eventlog tdb files. Refer to the
1270 eventlogadm(8) utility for how to write eventlog entries.
1272 Example: Security Application Syslog Apache</string>
1274 <string id="POL_04CE2D0D_386E_5CA3_B450_F1BC9FC9CC9B_Help">This parameter determines whether or not
1275 smbd
1277 streaming read and write variant SMB requests introduced with
1279 this requires Samba to be running on a 64-bit capable operating
1280 system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve
1281 performance by 10% with Windows 2000 clients. Defaults to on. Not as tested as some other Samba code paths.</string>
1283 <string id="POL_63F5048E_6174_5012_8637_738DD79034E5_Help">Setting this deprecated option will allow the RPC server in the AD DC to answer the LSARPC interface on the \pipe\netlogon IPC pipe.
1284 When enabled, this matches the behaviour of Microsoft's Windows, due to their internal implementation choices.
1285 If it is disabled (the default), the AD DC can offer improved performance, as the netlogon server is decoupled and can run as multiple processes.</string>
1287 <string id="POL_87E8C778_F6AC_5666_8855_D40F11853504_Help">This option controls the maximum number of
1288 outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.</string>
1291 8 what the default 'time to live'
1292 of NetBIOS names should be (in seconds) when nmbd is
1293 requesting a name using either a broadcast packet or from a WINS server. You should never need to change this parameter. The default is 3 days.</string>
1295 <string id="POL_0AAACA11_DE41_5664_A306_F44D752598C5_Help">This option controls the maximum packet size
1296 that will be negotiated by Samba's
1297 smbd8
1298 for the SMB1 protocol. The default is 16644, which
1300 You should never need to change this parameter from its default value.
1304 <string id="POL_24E58521_FFD2_5ADE_A9C8_4050EE408BC2_Help">This option changes the behavior of smbd
1305 8 when processing SMBwriteX calls. Any incoming
1306 SMBwriteX call on a non-signed SMB/CIFS connection greater than this value will not be processed in the normal way but will
1307 be passed to any underlying kernel recvfile or splice system call (if there is no such
1308 call Samba will emulate in user space). This allows zero-copy writes directly from network
1309 socket buffers into the filesystem buffer cache, if available. It may improve performance
1310 but user testing is recommended. If set to zero Samba processes SMBwriteX calls in the
1311 normal way. To enable POSIX large write support (SMB/CIFS writes up to 16Mb) this option must be
1313 Note this option will have NO EFFECT if set on a SMB signed connection.
1314 The default is zero, which disables this option.</string>
1316 <string id="POL_1DDE423B_1CCB_5179_87D3_1FEE7D4CA621_Help">This option is used by the programs in the Samba
1317 suite to determine what naming services to use and in what order
1318 to resolve host names to IP addresses. Its main purpose to is to
1319 control how netbios name resolution is performed. The option takes a space
1320 separated string of name resolution options.
1324 resolved as follows:
1326 lmhosts : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the manpage for lmhosts for details) then any name type matches for lookup.
1327 host : Do a standard host name to IP address resolution, using the system /etc/hosts , NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.conf file. Note that this method is used only if the NetBIOS name type being queried is the 0x20 (server) name type or 0x1c (domain controllers). The latter case is only useful for active directory domains and results in a DNS query for the SRV RR entry matching _ldap._tcp.domain.
1328 wins : Query a name with the IP address listed in the wins server parameter. If no WINS server has been specified this method will be ignored.
1329 bcast : Do a broadcast on each of the known local interfaces listed in the parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
1332 The example below will cause the local lmhosts file to be examined
1333 first, followed by a broadcast attempt, followed by a normal
1334 system hostname lookup.
1336 When Samba is functioning in ADS security mode (security = ads)
1337 it is advised to use following settings for name resolve order:
1339 name resolve order = wins bcast
1341 DC lookups will still be done via DNS, but fallbacks to netbios names will not inundate your DNS servers with needless queries for DOMAIN<0x1c> lookups.
1343 Example: lmhosts bcast host</string>
1345 <string id="POL_B1C3F6FC_E4FB_58A7_9CE4_50090EF8FF17_Help">Specifies which port the server should use for NetBIOS over IP name services traffic.</string>
1347 <string id="POL_E2A4C01A_1EFC_5826_9D3A_A4AD065518EF_Help">This boolean parameter controls whether
1348 smbd
1349 8 will allow Windows NT
1350 clients to connect to the NT SMB specific IPC$
1351 pipes. This is a developer debugging option and can be left alone.</string>
1353 <string id="POL_C1F0941D_67B4_55EA_A915_6F5E9A945E57_Help">This boolean parameter controls whether smbd
1354 8 will negotiate NT specific status
1355 support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone.
1356 If this option is set to no then Samba offers
1357 exactly the same DOS error codes that versions prior to Samba 2.2.3
1358 reported.
1360 You should not need to ever disable this parameter.</string>
1363 because this feature is incompatible with raw read SMB requests
1365 If enabled, raw reads allow reads of 65535 bytes in
1366 one packet. This typically provides a major performance benefit for some very, very old clients.
1369 However, some clients either negotiate the allowable
1370 block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads.
1372 In general this parameter should be viewed as a system tuning tool and left severely alone.</string>
1374 <string id="POL_F9AD06B5_1870_5BE4_87A9_08E3821667E4_Help">Setting this option will force the RPC client and server to transfer data in big endian.
1375 If it is disabled, data will be transferred in little endian.
1376 The behaviour is independent of the endianness of the host machine.</string>
1378 <string id="POL_380E7843_58D7_505E_9092_392FE1FC4BA2_Help">Specifies which port the server should listen on for DCE/RPC over TCP/IP traffic. This controls the default port for all protocols, except for NETLOGON. If unset, the first available port from is used, e.g. 49152. The NETLOGON server will use the next available port, e.g. 49153. To change this port use (eg) rpc server port:netlogon = 4000. Furthermore, all RPC servers can have the port they use specified independenty, with (for example) rpc server port:drsuapi = 5000.
1379 This option applies currently only when samba 8 runs as an active directory domain controller.
1382 <string id="POL_D910FC29_975B_5105_97C8_BD75D68FDC5F_Help">The value of the parameter (a string) is the highest
1383 protocol level that will be supported by the server.
1385 Possible values are :
1386 LANMAN1: First modern version of the protocol. Long filename support.
1387 LANMAN2: Updates to Lanman1 protocol.
1388 NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
1389 SMB2: Re-implementation of the SMB protocol. Used by Windows Vista and later versions of Windows. SMB2 has sub protocols available. SMB2_02: The earliest SMB2 version. SMB2_10: Windows 7 SMB2 version. By default SMB2 selects the SMB2_10 variant.
1390 SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols available. SMB3_00: Windows 8 SMB3 version. SMB3_02: Windows 8.1 SMB3 version. SMB3_11: Windows 10 SMB3 version. By default SMB3 selects the SMB3_11 variant.
1393 Normally this option should not be set as the automatic
1394 negotiation phase in the SMB protocol takes care of choosing
1395 the appropriate protocol.
1397 Example: LANMAN1</string>
1399 <string id="POL_98D56061_466A_5DDE_BFF3_8A194DE5FE2E_Help">This setting controls the minimum protocol version that the server will allow the client to use.
1400 Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol unless you have legacy clients which are SMB1 capable only.
1401 See server max protocol for a full list of available protocols.
1403 Example: NT1</string>
1405 <string id="POL_2A034462_D418_5914_B24C_6535DD368A66_Help">This is needed to support some special application that makes QFSINFO calls to check whether we set the SPARSE_FILES bit (0x40). If this bit is not set that particular application refuses to work against Samba. With 64 the SPARSE_FILES file system capability flag is set. Use other decimal values to specify the bitmask you need to fake.</string>
1407 <string id="POL_A3F9ABC7_494B_5007_B5A1_1DA0B9FC345D_Help">This option controls the maximum number of outstanding simultaneous SMB2 operations
1408 that Samba tells the client it will allow. This is similar to the
1409 parameter for SMB1. You should never need to set this parameter.
1413 <string id="POL_209C2DE8_5843_50FC_9B61_A3F3EBFE95B5_Help">This option specifies the protocol value that smbd
1414 8 will return to a client, informing the client of the largest
1415 size that may be returned by a single SMB2 read call.
1418 Please note that the default is 8MiB, but it's limit is based on the
1422 <string id="POL_0696582B_7928_558B_B4DA_9A0C647CFBB8_Help">This option specifies the protocol value that smbd
1423 8 will return to a client, informing the client of the largest
1424 size of buffer that may be used in querying file meta-data via QUERY_INFO and related SMB2 calls.
1427 Please note that the default is 8MiB, but it's limit is based on the
1431 <string id="POL_DA17FE47_6637_50D0_9AD1_A95AAA49F717_Help">This option specifies the protocol value that smbd
1432 8 will return to a client, informing the client of the largest
1433 size that may be sent to the server by a single SMB2 write call.
1436 Please note that the default is 8MiB, but it's limit is based on the
1440 <string id="POL_97C2005C_F45B_5675_B450_75842A4139F0_Help">Specifies which ports the server should listen on for SMB traffic.</string>
1442 <string id="POL_5B8B1A0B_AC6B_5E89_8FDE_4CBE538A9CB8_Help">This option defines a list of init scripts that smbd
1443 will use for starting and stopping Unix services via the Win32
1444 ServiceControl API. This allows Windows administrators to
1445 utilize the MS Management Console plug-ins to manage a
1446 Unix server running Samba.
1448 The administrator must create a directory
1449 name svcctl in Samba's $(libdir)
1450 and create symbolic links to the init scripts in
1451 /etc/init.d/. The name of the links
1452 must match the names given as part of the svcctl list.
1454 Example: cups postfix portmap httpd</string>
1457 8 advertises itself as a time server to Windows
1458 clients.</string>
1460 <string id="POL_B8322D3C_E4C4_5EAD_AE99_B912C35C56C8_Help">Specifies whether the server and client should support unicode.
1461 If this option is set to false, the use of ASCII will be forced.</string>
1463 <string id="POL_4A31BF60_B9E4_5E35_B979_A1C15754CA9A_Help">This boolean parameter controls whether Samba
1464 implements the CIFS UNIX extensions, as defined by HP.
1465 These extensions enable Samba to better serve UNIX CIFS clients
1466 by supporting features such as symbolic links, hard links, etc...
1467 These extensions require a similarly enabled client, and are of
1468 no current use to Windows clients.
1470 Note if this parameter is turned on, the
1471 parameter will automatically be disabled.
1474 See the parameter
1475 if you wish to change this coupling between the two parameters.</string>
1478 because this feature is incompatible with raw write SMB requests
1480 If enabled, raw writes allow writes of 65535 bytes in
1481 one packet. This typically provides a major performance benefit for some very, very old clients.
1484 However, some clients either negotiate the allowable
1485 block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw writes.
1487 In general this parameter should be viewed as a system tuning tool and left severely alone.</string>
1489 <string id="POL_585034D0_C9E6_568C_AF40_354A01C24E02_Help">This boolean parameter controls whether
1490 smbd
1491 8 will support
1492 SMB3 multi-channel.
1494 This parameter was added with version 4.4.
1496 Warning: Note that this feature is still considered experimental.
1497 Use it at your own risk: Even though it may seem to work well in testing,
1498 it may result in data corruption under some race conditions.
1499 Future releases may improve this situation.
1502 Due to dependencies to kernel APIs of Linux or FreeBSD, it's only possible
1503 to use this feature on Linux and FreeBSD for now. For testing this restriction
1504 can be overwritten by specifying force:server multi channel support=yes
1505 in addition.</string>
1506 <string id="POL_4553EC0B_4966_52CE_83C6_948DAC67A281">smb2 disable lock sequence checking</string>
1507 <string id="POL_4553EC0B_4966_52CE_83C6_948DAC67A281_Help">This boolean parameter controls whether
1508 smbd
1509 8 will disable
1510 lock sequence checking even for multi-channel connections
1511 as well as durable handles.
1514 The [MS-SMB2] specification (under 3.3.5.14 Receiving an SMB2 LOCK Request)
1515 documents that a server should do lock sequence if Open.IsResilient or Open.IsDurable
1516 or Open.IsPersistent is TRUE or if Connection.Dialect belongs to the SMB 3.x dialect
1517 family and Connection.ServerCapabilities includes SMB2_GLOBAL_CAP_MULTI_CHANNEL.
1520 But Windows Server (at least up to v2004) only does these checks
1521 for the Open.IsResilient and Open.IsPersistent.
1522 That means they do not implement the behavior specified
1523 in [MS-SMB2].
1525 By default Samba behaves according to the specification
1526 and sends smb2 oplock break notification retries.
1528 Warning: Only enable this option if existing clients can't
1529 handle lock sequence checking for handles without Open.IsResilient and Open.IsPersistent.
1530 And it turns out that the Windows Server behavior is required.
1532 Note: it's likely that this option will be removed again
1533 if future Windows versions change their behavior.
1535 Note: Samba does not implement Open.IsResilient and Open.IsPersistent yet.
1537 Example: yes</string>
1539 <string id="POL_690A701E_D101_57E5_A180_30E9E54B8B38_Help">This boolean parameter controls whether
1540 smbd
1541 8 will trigger
1542 smb2 oplock break notification retries when using
1543 yes.
1546 The [MS-SMB2] specification documents that a server should
1547 send smb2 oplock break notification retries on all available channel
1548 to the given client.
1550 But Windows Server versions (at least up to 2019) do not send
1551 smb2 oplock break notification retries on channel failures.
1552 That means they do not implement the behavior specified
1553 in [MS-SMB2].
1555 By default Samba behaves according to the specification
1556 and send smb2 oplock break notification retries.
1558 Warning: Only enable this option if existing clients can't
1559 handle possible retries and it turns out that the Windows Server
1560 behavior is required.
1562 Note: it's likely that this option gets removed again
1563 if future Windows versions change their behavior.
1565 Note: this only applies to oplocks and not SMB2 leases.
1567 Example: yes</string>
1569 <string id="POL_7564C5C4_88AA_576B_A9E8_091901A3D6E0_Help">This parameter tells the RPC server which port range it is allowed to use to create a listening socket for LSA, SAM, Netlogon and others without wellknown tcp ports. The first value is the lowest number of the port range and the second the highest. This applies to RPC servers in all server roles.</string>
1571 <string id="POL_8D3A68BB_46F0_55A8_B53F_A4AA70C39B46_Help">This determines how Samba will use its
1572 algorithmic mapping from uids/gid to the RIDs needed to construct
1573 NT Security Identifiers.
1576 Setting this option to a larger value could be useful to sites
1577 transitioning from WinNT and Win2k, as existing user and
1578 group rids would otherwise clash with system users etc.
1581 All UIDs and GIDs must be able to be resolved into SIDs for
1582 the correct operation of ACLs on the server. As such the algorithmic
1583 mapping can't be 'turned off', but pushing it 'out of the way' should
1584 resolve the issues. Users and groups can then be assigned 'low' RIDs
1585 in arbitrary-rid supporting backends.
1589 <string id="POL_4A36DCFC_E9DB_5CD6_A67B_F94F3D95224F_Help">This option controls whether DCERPC services are allowed to be used with DCERPC_AUTH_LEVEL_CONNECT, which provides authentication, but no per message integrity nor privacy protection.
1590 Some interfaces like samr, lsarpc and netlogon have a hard-coded default of no and epmapper, mgmt and rpcecho have a hard-coded default of yes.
1591 The behavior can be overwritten per interface name (e.g. lsarpc, netlogon, samr, srvsvc, winreg, wkssvc ...) by using 'allow dcerpc auth level connect:interface = yes' as option.
1592 This option yields precedence to the implementation specific restrictions. E.g. the drsuapi and backupkey protocols require DCERPC_AUTH_LEVEL_PRIVACY. The dnsserver protocol requires DCERPC_AUTH_LEVEL_INTEGRITY.
1594 Example: yes</string>
1596 <string id="POL_F3A8A539_E774_5498_B8B7_5D295841A159_Help">This option only takes effect when the option is set to
1597 server, domain or ads.
1598 If it is set to no, then attempts to connect to a resource from
1599 a domain or workgroup other than the one which smbd is running
1600 in will fail, even if that domain is trusted by the remote server
1601 doing the authentication.
1602 This is useful if you only want your Samba server to
1603 serve resources to users in the domain it is a member of. As
1604 an example, suppose that there are two domains DOMA and DOMB. DOMB
1605 is trusted by DOMA, which contains the Samba server. Under normal
1606 circumstances, a user with an account in DOMB can then access the
1607 resources of a UNIX account with the same account name on the
1608 Samba server even if they do not have an account in DOMA. This
1609 can make implementing a security boundary difficult.</string>
1611 <string id="POL_DF7112E5_5322_5A42_A1AD_45085CB6EC86_Help">This parameters defines the directory samba will use to store the configuration
1612 files for bind, such as named.conf.
1614 NOTE: The bind dns directory needs to be on the same mount point as the private
1615 directory!</string>
1617 <string id="POL_41C0408D_BF8C_5BA3_992E_6D58CF58FF84_Help">The name of a program that can be used to check password
1618 complexity. The password is sent to the program's standard input.
1620 The program must return 0 on a good password, or any other value
1621 if the password is bad.
1622 In case the password is considered weak (the program does not return 0) the
1623 user will be notified and the password change will fail.
1625 In Samba AD, this script will be run AS ROOT by
1626 samba 8
1627 without any substitutions.
1629 Note that starting with Samba 4.11 the following environment variables are exported to the script:
1631 SAMBA_CPS_ACCOUNT_NAME is always present and contains the sAMAccountName of user, the is the same as the %u substitutions in the none AD DC case.
1632 SAMBA_CPS_USER_PRINCIPAL_NAME is optional in the AD DC case if the userPrincipalName is present.
1633 SAMBA_CPS_FULL_NAME is optional if the displayName is present.
1636 Note: In the example directory is a sample program called crackcheck
1637 that uses cracklib to check the password quality.
1639 Example: /usr/local/sbin/crackcheck</string>
1641 <string id="POL_9869726F_8F58_512B_A708_C7360AC9146F_Help">This controls whether the client is allowed or required to use SMB signing for IPC$
1642 connections as DCERPC transport. Possible values
1643 are auto, mandatory
1644 and disabled.
1647 When set to mandatory or default, SMB signing is required.
1649 When set to auto, SMB signing is offered, but not enforced and if set
1650 to disabled, SMB signing is not offered either.
1652 Connections from winbindd to Active Directory Domain Controllers
1653 always enforce signing.</string>
1655 <string id="POL_309DB173_58D7_5326_B21D_8DF044225CB9_Help">This parameter determines whether or not smbclient
1656 8 and other samba client
1657 tools will attempt to authenticate itself to servers using the
1658 weaker LANMAN password hash. If disabled, only server which support NT
1659 password hashes (e.g. Windows NT/2000, Samba, etc... but not
1662 The LANMAN encrypted response is easily broken, due to its
1663 case-insensitive nature, and the choice of algorithm. Clients
1665 this option.
1667 Disabling this option will also disable the client plaintext auth option.
1669 Likewise, if the client ntlmv2
1670 auth parameter is enabled, then only NTLMv2 logins will be
1671 attempted.</string>
1673 <string id="POL_0F39ED01_BB64_5653_839C_CB26A70EC531_Help">This parameter determines whether or not smbclient
1674 8 will attempt to
1675 authenticate itself to servers using the NTLMv2 encrypted password
1676 response.
1678 If enabled, only an NTLMv2 and LMv2 response (both much more
1679 secure than earlier versions) will be sent. Older servers
1681 NTLMv2 when not in an NTLMv2 supporting domain
1683 Similarly, if enabled, NTLMv1, client lanman auth and client plaintext auth
1684 authentication will be disabled. This also disables share-level
1685 authentication.
1687 If disabled, an NTLM response (and possibly a LANMAN response)
1688 will be sent by the client, depending on the value of client lanman auth.
1690 Note that Windows Vista and later versions already use
1691 NTLMv2 by default, and some sites (particularly those following
1692 'best practice' security polices) only allow NTLMv2 responses, and
1693 not the weaker LM or NTLM.
1695 When is also set to
1696 yes extended security (SPNEGO) is required
1697 in order to use NTLMv2 only within NTLMSSP. This behavior was
1700 <string id="POL_94342D11_937E_5F14_BBEA_C9B370F6A523_Help">Specifies whether a client should send a plaintext password if the server does not support encrypted passwords.</string>
1702 <string id="POL_DCB591D5_0F63_58EC_A0BB_F5F81064B714_Help">This option is deprecated with Samba 4.8 and will be removed in future. At the same time the default changed to yes, which will be the hardcoded behavior in future.
1706 This controls whether the client offers or even demands the use of the netlogon schannel.
1707 no does not offer the schannel,
1708 auto offers the schannel but does not
1709 enforce it, and yes denies access
1710 if the server is not able to speak netlogon schannel.
1713 Note that for active directory domains this is hardcoded to
1714 yes.
1716 This option yields precedence to the option.
1718 Example: auto</string>
1720 <string id="POL_F35419AB_2114_5382_8060_B1AAED24F2A1_Help">This controls whether the client is allowed or required to use SMB signing. Possible values
1721 are auto, mandatory
1722 and disabled.
1725 When set to auto or default, SMB signing is offered, but not enforced.
1727 When set to mandatory, SMB signing is required and if set
1728 to disabled, SMB signing is not offered either.
1730 IPC$ connections for DCERPC e.g. in winbindd, are handled by the
1731 option.</string>
1733 <string id="POL_F761A7A7_2852_560C_B6D7_A50C613C5431_Help">This parameter determines whether or not
1734 smbclient
1735 8 and other samba components
1736 acting as a client will attempt to use the server-supplied
1737 principal sometimes given in the SPNEGO exchange.
1739 If enabled, Samba can attempt to use Kerberos to contact
1740 servers known only by IP address. Kerberos relies on names, so
1741 ordinarily cannot function in this situation.
1743 This is a VERY BAD IDEA for security reasons, and so this
1744 parameter SHOULD NOT BE USED. It will be removed in a future
1745 version of Samba.
1747 If disabled, Samba will use the name used to look up the
1748 server when asking the KDC for a ticket. This avoids situations
1749 where a server may impersonate another, soliciting authentication
1750 as one principal while being known on the network as another.
1753 Note that Windows XP SP2 and later versions already follow
1754 this behaviour, and Windows Vista and later servers no longer
1755 supply this 'rfc4178 hint' principal on the server side.
1757 This parameter is deprecated in Samba 4.2.1 and will be removed
1758 (along with the functionality) in a later release of Samba.</string>
1760 <string id="POL_158C42B4_685B_5FDE_BF9D_C42504E8C09C_Help">This option will make the smbd server and client code using
1761 libsmb (smbclient, smbget, smbspool, ...) dump the Session Id,
1762 the decrypted Session Key, the Signing Key, the Application Key,
1763 the Encryption Key and the Decryption Key every time an SMB3+
1764 session is established. This information will be printed in logs
1765 at level 0.
1768 Warning: access to these values enables the decryption of any
1769 encrypted traffic on the dumped sessions. This option should
1770 only be enabled for debugging purposes.</string>
1772 <string id="POL_8853D1A2_6482_58E1_9748_192D92523750_Help">Specifies the absolute path to the kerberos keytab file when is set to "dedicated keytab".
1774 Example: /usr/local/etc/krb5.keytab</string>
1776 <string id="POL_3C1941B5_4894_501A_A7FD_F0C6BCE77DA9_Help">This parameter has been deprecated since Samba 4.11 and
1777 support for plaintext (as distinct from NTLM, NTLMv2
1778 or Kerberos authentication)
1779 will be removed in a future Samba release.
1780 That is, in the future, the current default of
1781 encrypt passwords = yes
1782 will be the enforced behaviour.
1783 This boolean controls whether encrypted passwords
1784 will be negotiated with the client. Note that Windows NT 4.0 SP3 and
1785 above and also Windows 98 will by default expect encrypted passwords
1786 unless a registry entry is changed. To use encrypted passwords in
1791 MS Windows clients that expect Microsoft encrypted passwords and that
1792 do not have plain text password support enabled will be able to
1793 connect only to a Samba server that has encrypted password support
1794 enabled and for which the user accounts have a valid encrypted password.
1795 Refer to the smbpasswd command man page for information regarding the
1796 creation of encrypted passwords for user accounts.
1800 The use of plain text passwords is NOT advised as support for this feature
1801 is no longer maintained in Microsoft Windows products. If you want to use
1802 plain text passwords you must set this parameter to no.
1805 In order for encrypted passwords to work correctly
1806 smbd
1807 8 must either
1808 have access to a local smbpasswd
1809 5 file (see the smbpasswd
1810 8 program for information on how to set up
1811 and maintain this file), or set the [domain|ads] parameter which
1812 causes smbd to authenticate against another server.</string>
1814 <string id="POL_99472FC1_E6CE_5476_9EC3_EB2EF52862AE_Help">This is a username which will be used for access
1815 to services which are specified as (see below). Whatever privileges this
1816 user has will be available to any client connecting to the guest service.
1817 This user must exist in the password file, but does not require
1819 for this parameter.
1823 be able to print. Use another account in this case. You should test
1824 this by trying to log in as your guest user (perhaps by using the
1825 su - command) and trying to print using the
1826 system print command such as lpr(1) or
1827 lp(1).
1829 This parameter does not accept % macros, because
1830 many parts of the system require this value to be constant for correct operation.
1832 Example: ftp</string>
1834 <string id="POL_75BBDBCB_46D1_55DE_9A7C_9EEA7DD026BF_Help">This parameter determines the encryption types to use when operating
1835 as a Kerberos client. Possible values are all,
1836 strong, and legacy.
1839 Samba uses a Kerberos library (MIT or Heimdal) to obtain Kerberos
1840 tickets. This library is normally configured outside of Samba, using
1841 the krb5.conf file. This file may also include directives to configure
1842 the encryption types to be used. However, Samba implements Active Directory
1843 protocols and algorithms to locate a domain controller. In order to
1844 force the Kerberos library into using the correct domain controller,
1845 some Samba processes, such as
1846 winbindd
1847 8 and
1848 net
1849 8, build a private krb5.conf
1850 file for use by the Kerberos library while being invoked from Samba.
1851 This private file controls all aspects of the Kerberos library operation,
1852 and this parameter controls how the encryption types are configured
1853 within this generated file, and therefore also controls the encryption
1854 types negotiable by Samba.
1857 When set to all, all active directory
1858 encryption types are allowed.
1861 When set to strong, only AES-based encryption
1862 types are offered. This can be used in hardened environments to prevent
1863 downgrade attacks.
1866 When set to legacy, only RC4-HMAC-MD5
1867 is allowed. Avoiding AES this way has one a very specific use.
1868 Normally, the encryption type is negotiated between the peers.
1869 However, there is one scenario in which a Windows read-only domain
1870 controller (RODC) advertises AES encryption, but then proxies the
1871 request to a writeable DC which may not support AES encryption,
1872 leading to failure of the handshake. Setting this parameter to
1873 legacy would cause samba not to negotiate AES
1874 encryption. It is assumed of course that the weaker legacy
1875 encryption types are acceptable for the setup.</string>
1877 <string id="POL_4AE746EE_4A10_55CC_8934_7E4FEF028E4D_Help">Controls how kerberos tickets are verified.
1878 Valid options are: secrets only - use only the secrets.tdb for ticket verification (default)
1879 system keytab - use only the system keytab for ticket verification
1880 dedicated keytab - use a dedicated keytab for ticket verification
1881 secrets and keytab - use the secrets.tdb first, then the system keytab
1882 The major difference between "system keytab" and "dedicated keytab" is that the latter method relies on kerberos to find the correct keytab entry instead of filtering based on expected principals.
1883 When the kerberos method is in "dedicated keytab" mode, must be set to specify the location of the keytab file.</string>
1885 <string id="POL_C0E75830_A92F_5E76_A2CF_8E864DF58497_Help">Specifies which ports the Kerberos server should listen on for password changes.</string>
1887 <string id="POL_37987863_7B25_5531_81BE_8EB427F3D0E1_Help">Specifies which port the KDC should listen on for Kerberos traffic.</string>
1889 <string id="POL_91CB69F0_B95B_565D_B50D_0BC441ED9E34_Help">This parameter has been deprecated since Samba 4.11 and
1890 support for LanMan (as distinct from NTLM, NTLMv2 or
1891 Kerberos authentication)
1892 will be removed in a future Samba release.
1893 That is, in the future, the current default of
1894 lanman auth = no
1895 will be the enforced behaviour.
1897 This parameter determines whether or not smbd
1898 8 will attempt to
1899 authenticate users or permit password changes
1900 using the LANMAN password hash. If disabled, only clients which support NT
1901 password hashes (e.g. Windows NT/2000 clients, smbclient, but not
1903 connect to the Samba host.
1905 The LANMAN encrypted response is easily broken, due to its
1906 case-insensitive nature, and the choice of algorithm. Servers
1908 this option.
1910 When this parameter is set to no this
1911 will also result in sambaLMPassword in Samba's passdb being
1912 blanked after the next password change. As a result of that
1913 lanman clients won't be able to authenticate, even if lanman
1914 auth is re-enabled later on.
1916 Unlike the encrypt
1917 passwords option, this parameter cannot alter client
1918 behaviour, and the LANMAN response will still be sent over the
1919 network. See the client lanman
1920 auth to disable this for Samba's clients (such as smbclient)
1922 This parameter is overridden by ntlm
1923 auth, so unless that it is also set to
1924 ntlmv1-permitted or yes,
1925 then only NTLMv2 logins will be permitted and no LM hash will be
1926 stored. All modern clients support NTLMv2, and but some older
1927 clients require special configuration to use it.</string>
1929 <string id="POL_89CBBE4F_9104_594C_88D1_F9C11246B21F_Help">This option can be set to a command that will be called when new nt tokens are created.
1930 This is only useful for development purposes.</string>
1932 <string id="POL_6BE3D165_D5BE_5252_A0A2_31CD0E777478_Help">This parameter can take four different values, which tell
1933 smbd
1934 8 what to do with user
1935 login requests that don't match a valid UNIX user in some way.
1937 The four settings are :
1939 Never - Means user login requests with an invalid password are rejected. This is the default. Bad User - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the .
1940 Bad Password - Means user logins with an invalid password are treated as a guest login and mapped into the . Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong. Helpdesk services will hate you if you set the map to guest parameter this way :-). Bad Uid - Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account. This was the default behavior of Samba 2.x releases. Note that if a member server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS via the Name Service Switch interface.
1944 share services. This is because in these modes the name of the resource being
1945 requested is not sent to the server until after
1946 the server has successfully authenticated the client so the server
1947 cannot make authentication decisions at the correct time (connection
1950 Example: Bad User</string>
1952 <string id="POL_56EEE2C2_6458_524A_95A8_C59B86A453E0_Help">This option specifies the path to the MIT kdc binary.
1954 If the KDC is not installed in the default location and wasn't
1955 correctly detected during build then you should modify this variable and
1956 point it to the correct binary.
1958 Example: /opt/mit/sbin/krb5kdc</string>
1960 <string id="POL_E82BE4E4_3F51_5B03_9809_03101186CE80_Help">This parameter determines whether or not smbd
1961 8 will attempt to
1962 authenticate users using the NTLM encrypted password response for
1963 this local passdb (SAM or account database).
1965 If disabled, both NTLM and LanMan authentication against the
1966 local passdb is disabled.
1968 Note that these settings apply only to local users,
1969 authentication will still be forwarded to and NTLM authentication
1970 accepted against any domain we are joined to, and any trusted
1971 domain, even if disabled or if NTLMv2-only is enforced here. To
1972 control NTLM authentiation for domain users, this must option must
1973 be configured on each DC.
1975 By default with ntlm auth set to
1976 ntlmv2-only only NTLMv2 logins will be
1977 permitted. All modern clients support NTLMv2 by default, but some older
1978 clients will require special configuration to use it.
1980 The primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x.
1982 The available settings are:
1986 ntlmv1-permitted (alias yes) - Allow NTLMv1 and above for all clients.
1987 This is the required setting for to enable the lanman auth parameter.
1992 ntlmv2-only (alias no) - Do not allow NTLMv1 to be used, but permit NTLMv2.
1996 mschapv2-and-ntlmv2-only - Only
1997 allow NTLMv1 when the client promises that it is providing
1998 MSCHAPv2 authentication (such as the ntlm_auth tool).
2002 disabled - Do not accept NTLM (or
2003 LanMan) authentication of any level, nor permit
2004 NTLM password changes.
2009 The default changed from yes to
2010 no with Samba 4.5. The default changed again
2011 to ntlmv2-only with Samba 4.7, however the
2012 behaviour is unchanged.</string>
2014 <string id="POL_BEB01EAD_B60E_5832_BDD5_5C8ACE276FD4_Help">This setting controls the location of the socket that the NTP daemon uses to communicate with Samba for signing packets.
2015 If a non-default path is specified here, then it is also necessary to make NTP aware of the new path using the ntpsigndsocket directive in ntp.conf.</string>
2017 <string id="POL_C04AB7ED_DBC2_50A6_8082_AD0D6CCB758A_Help">Allow or disallow client access to accounts that have null passwords.
2021 <string id="POL_E305251F_7C82_54A6_8F9D_CFBB7934B1DF_Help">When Samba 3.0 is configured to enable PAM support
2022 (i.e. --with-pam), this parameter will control whether or not Samba
2023 should obey PAM's account and session management directives. The
2024 default behavior is to use PAM for clear text authentication only
2025 and to ignore any account or session management. Note that Samba
2026 always ignores PAM for authentication in the case of yes. The reason
2027 is that PAM modules cannot support the challenge/response
2028 authentication mechanism needed in the presence of SMB password encryption.</string>
2030 <string id="POL_DD8E3C33_F1AE_59CB_B2B6_3358FFBF41AF_Help">Number of minutes to permit an NTLM login after a password change or reset using the old password. This allows the user to re-cache the new password on multiple clients without disrupting a network reconnection in the meantime.
2032 This parameter only applies when is set to Active Directory Domain Controller</string>
2034 <string id="POL_B65F086B_4235_5646_8C8B_AF4C16B6E4AD_Help">With the addition of better PAM support in Samba 2.2,
2035 this parameter, it is possible to use PAM's password change control
2036 flag for Samba. If enabled, then PAM will be used for password
2037 changes when requested by an SMB client instead of the program listed in
2038 .
2039 It should be possible to enable this without changing your
2040 parameter for most setups.</string>
2042 <string id="POL_755D3500_5D11_5DF0_82AC_E5E964C7707B_Help">This option allows the administrator to chose which backend
2043 will be used for storing user and possibly group information. This allows
2044 you to swap between different storage mechanisms without recompile.
2046 The parameter value is divided into two parts, the backend's name, and a 'location'
2047 string that has meaning only to that particular backed. These are separated
2048 by a : character.
2050 Available backends can include: smbpasswd - The old plaintext passdb backend. Some Samba features will not work if this passdb backend is used. Takes a path to the smbpasswd file as an optional argument. tdbsam - The TDB based password storage
2051 backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
2052 in the directory. ldapsam - The LDAP based passdb
2053 backend. Takes an LDAP URL as an optional argument (defaults to
2054 ldap://localhost) LDAP connections should be secured where possible. This may be done using either
2055 Start-TLS (see ) or by
2056 specifying ldaps:// in
2057 the URL argument.
2059 Multiple servers may also be specified in double-quotes. Whether multiple servers are supported or not and the exact syntax depends on the LDAP library you use.
2062 Examples of use are:
2064 passdb backend = tdbsam:/etc/samba/private/passdb.tdb
2066 or multi server LDAP URL with OpenLDAP library:
2070 or multi server LDAP URL with Netscape based LDAP library:
2074 <string id="POL_2F42A35D_FAD2_545A_9ACE_84CD88BEBDB4_Help">This parameter controls whether Samba substitutes %-macros in the passdb fields if they are explicitly set. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user's primary group.</string>
2076 <string id="POL_87D22064_A317_506A_8057_62D7EB06E246_Help">This string controls the "chat"
2077 conversation that takes places between smbd
2078 8 and the local password changing
2079 program to change the user's password. The string describes a
2080 sequence of response-receive pairs that smbd
2081 8 uses to determine what to send to the
2082 and what to expect back. If the expected output is not
2083 received then the password is not changed.
2085 This chat sequence is often quite site specific, depending
2086 on what local methods are used for password control (such as NIS
2087 etc).
2089 Note that this parameter only is used if the parameter is set to yes. This sequence is
2090 then called AS ROOT when the SMB password in the
2091 smbpasswd file is being changed, without access to the old password
2092 cleartext. This means that root must be able to reset the user's password without
2093 knowing the text of the previous password. In the presence of
2094 NIS/YP, this means that the must
2095 be executed on the NIS master.
2098 The string can contain the macro %n which is substituted
2099 for the new password. The old password (%o) is only available when
2100 has been disabled.
2101 The chat sequence can also contain the standard macros
2102 \n, \r, \t and \s to give line-feed, carriage-return, tab
2103 and space. The chat sequence string can also contain
2104 a '*' which matches any sequence of characters. Double quotes can
2105 be used to collect strings with spaces in them into a single
2106 string.
2108 If the send string in any part of the chat sequence is a full
2110 expect string is a full stop then no string is expected.
2112 If the parameter is set to yes, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output. The \n macro is ignored for PAM conversions.
2114 Example: "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"</string>
2116 <string id="POL_FB5B5BAF_88EA_547F_B6C1_C26EF698C89B_Help">This boolean specifies if the passwd chat script
2117 parameter is run in debug mode. In this mode the
2118 strings passed to and received from the passwd chat are printed
2119 in the smbd
2120 8 log with a
2122 of 100. This is a dangerous option as it will allow plaintext passwords
2123 to be seen in the smbd log. It is available to help
2124 Samba admins debug their passwd chat scripts
2125 when calling the passwd program and should
2126 be turned off after this has been done. This option has no effect if the
2127 parameter is set. This parameter is off by default.</string>
2129 <string id="POL_885CA09B_77E8_5E63_85E8_108397557B0B_Help">This integer specifies the number of seconds smbd will wait for an initial
2130 answer from a passwd chat script being run. Once the initial answer is received
2131 the subsequent answers must be received in one tenth of this time. The default it
2132 two seconds.</string>
2134 <string id="POL_E710453F_700A_5430_BE8D_5364117F7E85_Help">The name of a program that can be used to set
2135 UNIX user passwords. Any occurrences of %u
2136 will be replaced with the user name. The user name is checked for
2137 existence before calling the password changing program.
2139 Also note that many passwd programs insist in reasonable
2140 passwords, such as a minimum length, or the inclusion
2141 of mixed case chars and digits. This can pose a problem as some clients
2142 (such as Windows for Workgroups) uppercase the password before sending
2143 it.
2145 Note that if the unix
2146 password sync parameter is set to yes
2147 then this program is called AS ROOT
2148 before the SMB password in the smbpasswd
2149 file is changed. If this UNIX password change fails, then
2150 smbd will fail to change the SMB password also
2151 (this is by design).
2153 If the unix password sync parameter
2154 is set this parameter MUST USE ABSOLUTE PATHS
2155 for ALL programs called, and must be examined
2156 for security implications. Note that by default unix
2157 password sync is set to no.
2159 Example: /bin/passwd %u</string>
2161 <string id="POL_77F6400F_03D4_53F9_AB7B_E0464F72E61F_Help">If samba is running as an active directory domain controller, it is possible to store the cleartext password of accounts in a PGP/OpenGPG encrypted form.
2162 You can specify one or more recipients by key id or user id. Note that 32bit key ids are not allowed, specify at least 64bit.
2163 The value is stored as 'Primary:SambaGPG' in the supplementalCredentials attribute.
2164 As password changes can occur on any domain controller, you should configure this on each of them. Note that this feature is currently available only on Samba domain controllers.
2165 This option is only available if samba was compiled with gpgme support.
2166 You may need to export the GNUPGHOME environment variable before starting samba. It is strongly recommended to only store the public key in this location. The private key is not used for encryption and should be only stored where decryption is required.
2167 Being able to restore the cleartext password helps, when they need to be imported into other authentication systems later (see samba-tool user getpassword) or you want to keep the passwords in sync with another system, e.g. an OpenLDAP server (see samba-tool user syncpasswords).
2168 While this option needs to be configured on all domain controllers, the samba-tool user syncpasswords command should run on a single domain controller only (typically the PDC-emulator).
2170 Example: 4952E40301FAB41A
2172 Example: selftest@samba.example.com
2175 <string id="POL_5EA8345D_5B61_554F_AAF5_2C069A37DFCA">password hash userPassword schemes</string>
2176 <string id="POL_5EA8345D_5B61_554F_AAF5_2C069A37DFCA_Help">This parameter determines whether or not
2177 samba
2178 8 acting as an Active
2179 Directory Domain Controller will attempt to store additional
2180 passwords hash types for the user
2182 The values are stored as 'Primary:userPassword' in the
2183 supplementalCredentials
2184 attribute. The value of this option is a hash type.
2186 The currently supported hash types are:
2189 CryptSHA256
2192 CryptSHA512
2196 Multiple instances of a hash type may be computed and stored.
2197 The password hashes are calculated using the
2198 crypt
2199 3 call.
2200 The number of rounds used to compute the hash can be specified by adding
2201 ':rounds=xxxx' to the hash type, i.e. CryptSHA512:rounds=4500 would calculate
2202 an SHA512 hash using 4500 rounds. If not specified the Operating System
2203 defaults for
2204 crypt
2205 3 are used.
2208 As password changes can occur on any domain controller,
2209 you should configure this on each of them. Note that this feature is
2210 currently available only on Samba domain controllers.
2212 Currently the NT Hash of the password is recorded when these hashes
2213 are calculated and stored. When retrieving the hashes the current value of the
2214 NT Hash is checked against the stored NT Hash. This detects password changes
2215 that have not updated the password hashes. In this case
2216 samba-tool user will ignore the stored
2217 hash values.
2220 Being able to obtain the hashed password helps, when
2221 they need to be imported into other authentication systems
2222 later (see samba-tool user
2223 getpassword) or you want to keep the passwords in
2224 sync with another system, e.g. an OpenLDAP server (see
2225 samba-tool user
2226 syncpasswords).
2228 unix password sync
2230 Example: CryptSHA256
2232 Example: CryptSHA256 CryptSHA512
2236 <string id="POL_1D36B51B_8AB7_593A_95D8_93B12C9F9EFA_Help">By specifying the name of a domain controller with this option,
2237 and using security = [ads|domain]
2238 it is possible to get Samba
2239 to do all its username/password validation using a specific remote server.
2241 Ideally, this option
2242 should not be used, as the default '*' indicates to Samba
2243 to determine the best DC to contact dynamically, just as all other hosts in an
2244 AD domain do. This allows the domain to be maintained (addition
2245 and removal of domain controllers) without modification to
2246 the smb.conf file. The cryptographic protection on the authenticated RPC calls
2247 used to verify passwords ensures that this default is safe.
2249 It is strongly recommended that you use the
2250 default of '*', however if in your particular
2251 environment you have reason to specify a particular DC list, then
2252 the list of machines in this option must be a list of names or IP
2253 addresses of Domain controllers for the Domain. If you use the
2254 default of '*', or list several hosts in the password server option then smbd will try each in turn till it
2255 finds one that responds. This is useful in case your primary
2256 server goes down.
2258 If the list of servers contains both names/IP's and the '*'
2259 character, the list is treated as a list of preferred
2260 domain controllers, but an auto lookup of all remaining DC's
2261 will be added to the list as well. Samba will not attempt to optimize
2262 this list by locating the closest DC.
2263 If parameter is a name, it is looked up using the
2264 parameter and so may resolved
2265 by any method and order described in that parameter.
2267 Example: NT-PDC, NT-BDC1, NT-BDC2, *
2271 <string id="POL_4605CA34_85F3_51DB_8BCE_C56B51AA39BF_Help">This is a list of paths to modules that should be loaded into smbd before a client connects. This improves the speed of smbd when reacting to new connections somewhat.
2273 Example: /usr/lib/samba/passdb/mysql.so</string>
2275 <string id="POL_5103CDE2_436D_5FB9_8633_6BB5EBB59406_Help">This parameters defines the directory
2276 smbd will use for storing such files as smbpasswd
2277 and secrets.tdb.</string>
2279 <string id="POL_7DB136EF_7DAD_5A4F_8C40_F3079FCB925F_Help">This parameter determines whether or not smbd
2280 8 will allow SMB1 clients without
2281 extended security (without SPNEGO) to use NTLMv2 authentication.
2283 If this option, lanman auth
2284 and ntlm auth are all disabled,
2285 then only clients with SPNEGO support will be permitted.
2286 That means NTLMv2 is only supported within NTLMSSP.</string>
2288 <string id="POL_E4D542FC_3D67_5397_9AC3_3868BB017F03_Help">This is the full pathname to a script that will be run as root by smbd 8 under special circumstances described below.
2289 When a user with admin authority or SeAddUserPrivilege rights renames a user (e.g.: from the NT4 User Manager for Domains), this script will be run to rename the POSIX user. Two variables, %uold and %unew, will be substituted with the old and new usernames, respectively. The script should return 0 upon successful completion, and nonzero otherwise.
2290 The script has all responsibility to rename all the necessary data that is accessible in this posix method. This can mean different requirements for different backends. The tdbsam and smbpasswd backends will take care of the contents of their respective files, so the script is responsible only for changing the POSIX username, and other data that may required for your circumstances, such as home directory. Please also consider whether or not you need to rename the actual home directories themselves. The ldapsam backend will not make any changes, because of the potential issues with renaming the LDAP naming attribute. In this case the script is responsible for changing the attribute that samba uses (uid) for locating users, as well as any data that needs to change for other applications using the same directory.</string>
2292 <string id="POL_7D42E3F0_DE0E_57E0_8EAF_F56111560EA3_Help">The setting of this parameter determines whether SAMR and LSA DCERPC services can be accessed anonymously. This corresponds to the following Windows Server registry options:
2293 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\RestrictAnonymous
2294 The option also affects the browse option which is required by legacy clients which rely on Netbios browsing. While modern Windows version should be fine with restricting the access there could still be applications relying on anonymous access.
2295 Setting 1 will disable anonymous SAMR access.
2296 Setting 2 will, in addition to restricting SAMR access, disallow anonymous connections to the IPC$ share in general. Setting yes on any share will remove the security advantage.</string>
2299 Change its root directory) to this directory on startup. This is
2300 not strictly necessary for secure operation. Even without it the
2301 server will deny access to files not in one of the service entries.
2302 It may also check for, and deny access to, soft links to other
2304 to access other directories (depending on the setting of the parameter).
2307 Adding a root directory entry other
2309 absolutely ensures that no access is given to files not in the
2310 sub-tree specified in the root directory
2311 option, including some files needed for
2312 complete operation of the server. To maintain full operability
2313 of the server you will need to mirror some system files
2314 into the root directory tree. In particular
2315 you will need to mirror /etc/passwd (or a
2316 subset of it), and any binaries or configuration files needed for
2317 printing (if required). The set of files that must be mirrored is
2318 operating system dependent.
2320 Example: /homes/smb</string>
2322 <string id="POL_9218F54E_BE22_57C0_BEF2_489F89B7D3BA_Help">This option specifies the path to the Samba KCC command. This script is used for replication topology replication.
2323 It should not be necessary to modify this option except for testing purposes or if the samba_kcc was installed in a non-default location.
2325 Example: /usr/local/bin/kcc</string>
2327 <string id="POL_86AEEBA8_5181_54A2_A436_FD35443F7C03_Help">This option affects how clients respond to
2328 Samba and is one of the most important settings in the
2329 smb.conf file.
2331 The default is security = user, as this is
2332 the most common setting, used for a standalone file server or a DC.
2334 The alternatives are
2335 security = ads or security = domain
2336 , which support joining Samba to a Windows domain
2338 You should use security = user and
2339 if you
2340 want to mainly setup shares without a password (guest shares). This
2341 is commonly used for a shared printer server.
2342 The different settings will now be explained.
2345 SECURITY = AUTO
2347 This is the default security setting in Samba, and causes Samba to consult
2348 the parameter (if set) to determine the security mode.
2350 SECURITY = USER
2352 If is not specified, this is the default security setting in Samba.
2354 valid username and password (which can be mapped using the
2355 parameter). Encrypted passwords (see the parameter) can also
2356 be used in this security mode. Parameters such as and if set are then applied and
2357 may change the UNIX user to use on this connection, but only after
2358 the user has been successfully authenticated.
2360 Note that the name of the resource being
2361 requested is not sent to the server until after
2362 the server has successfully authenticated the client. This is why
2363 guest shares don't work in user level security without allowing
2364 the server to automatically map unknown users into the .
2365 See the parameter for details on doing this.
2367 SECURITY = DOMAIN
2369 This mode will only work correctly if net
2370 8 has been used to add this
2371 machine into a Windows NT Domain. It expects the parameter to be set to yes. In this
2372 mode Samba will try to validate the username/password by passing
2373 it to a Windows NT Primary or Backup Domain Controller, in exactly
2374 the same way that a Windows NT Server would do.
2376 Note that a valid UNIX user must still
2377 exist as well as the account on the Domain Controller to allow
2378 Samba to have a valid UNIX account to map file access to.
2380 Note that from the client's point
2381 of view security = domain is the same
2382 as security = user. It only
2383 affects how the server deals with the authentication,
2384 it does not in any way affect what the client sees.
2386 Note that the name of the resource being
2387 requested is not sent to the server until after
2388 the server has successfully authenticated the client. This is why
2389 guest shares don't work in user level security without allowing
2390 the server to automatically map unknown users into the .
2391 See the parameter for details on doing this.
2393 See also the parameter and the parameter.
2394 SECURITY = ADS In this mode, Samba will act as a domain member in an ADS realm. To operate in this mode, the machine running Samba will need to have Kerberos installed and configured and Samba will need to be joined to the ADS realm using the net utility. Note that this mode does NOT make Samba operate as a Active Directory Domain Controller.
2395 Note that this forces yes and yes for the primary domain.
2396 Read the chapter about Domain Membership in the HOWTO for details.
2398 Example: DOMAIN</string>
2400 <string id="POL_925F9081_BDD3_5BE8_BB73_89EBE3A0A8F0_Help">This option determines the basic operating mode of a Samba
2401 server and is one of the most important settings in the smb.conf file.
2403 The default is server role = auto, as causes
2404 Samba to operate according to the setting, or if not
2405 specified as a simple file server that is not connected to any domain.
2407 The alternatives are
2408 server role = standalone or server role = member server
2409 , which support joining Samba to a Windows domain, along with server role = domain controller, which run Samba as a Windows domain controller.
2411 You should use server role = standalone and
2412 if you
2413 want to mainly setup shares without a password (guest shares). This
2414 is commonly used for a shared printer server.
2415 SERVER ROLE = AUTO
2417 This is the default server role in Samba, and causes Samba to consult
2418 the parameter (if set) to determine the server role, giving compatible behaviours to previous Samba versions.
2420 SERVER ROLE = STANDALONE
2422 If is also not specified, this is the default security setting in Samba.
2424 valid username and password (which can be mapped using the
2425 parameter) stored on this machine. Encrypted passwords (see the parameter) are by default
2426 used in this security mode. Parameters such as and if set are then applied and
2427 may change the UNIX user to use on this connection, but only after
2428 the user has been successfully authenticated.
2430 SERVER ROLE = MEMBER SERVER
2432 This mode will only work correctly if net
2433 8 has been used to add this
2434 machine into a Windows Domain. It expects the parameter to be set to yes. In this
2435 mode Samba will try to validate the username/password by passing
2436 it to a Windows or Samba Domain Controller, in exactly
2437 the same way that a Windows Server would do.
2439 Note that a valid UNIX user must still
2440 exist as well as the account on the Domain Controller to allow
2441 Samba to have a valid UNIX account to map file access to. Winbind can provide this.
2443 SERVER ROLE = CLASSIC PRIMARY DOMAIN CONTROLLER
2445 This mode of operation runs a classic Samba primary domain
2446 controller, providing domain logon services to Windows and Samba
2447 clients of an NT4-like domain. Clients must be joined to the domain to
2448 create a secure, trusted path across the network. There must be
2449 only one PDC per NetBIOS scope (typically a broadcast network or
2450 clients served by a single WINS server).
2452 SERVER ROLE = CLASSIC BACKUP DOMAIN CONTROLLER
2454 This mode of operation runs a classic Samba backup domain
2455 controller, providing domain logon services to Windows and Samba
2456 clients of an NT4-like domain. As a BDC, this allows
2457 multiple Samba servers to provide redundant logon services to a
2458 single NetBIOS scope.
2460 SERVER ROLE = ACTIVE DIRECTORY DOMAIN CONTROLLER
2462 This mode of operation runs Samba as an active directory
2463 domain controller, providing domain logon services to Windows and
2464 Samba clients of the domain. This role requires special
2465 configuration, see the Samba4
2466 HOWTO
2468 Example: ACTIVE DIRECTORY DOMAIN CONTROLLER</string>
2470 <string id="POL_6B0930DB_3CC7_57DB_8798_A6B6D3AF05B9_Help">This option is deprecated with Samba 4.8 and will be removed in future. At the same time the default changed to yes, which will be the hardcoded behavior in future. If you have the need for the behavior of "auto" to be kept, please file a bug at https://bugzilla.samba.org.
2473 This controls whether the server offers or even demands the use of the netlogon schannel. no does not offer the schannel, auto offers the schannel but does not enforce it, and yes denies access if the client is not able to speak netlogon schannel. This is only the case for Windows NT4 before SP4.
2475 Please note that with this set to no, you will have to apply the WindowsXP WinXP_SignOrSeal.reg registry patch found in the docs/registry subdirectory of the Samba distribution tarball.
2477 Example: auto</string>
2479 <string id="POL_6DC4F5E8_3493_5D3C_8E35_D928C38C2604_Help">This controls whether the client is allowed or required to use SMB1 and SMB2 signing. Possible values
2480 are default, auto, mandatory
2481 and disabled.
2484 By default, and when smb signing is set to
2485 default, smb signing is required when
2486 is active directory
2487 domain controller and disabled otherwise.
2489 When set to auto, SMB1 signing is offered, but not enforced.
2490 When set to mandatory, SMB1 signing is required and if set
2491 to disabled, SMB signing is not offered either.
2493 For the SMB2 protocol, by design, signing cannot be disabled. In the case
2494 where SMB2 is negotiated, if this parameter is set to disabled,
2495 it will be treated as auto. Setting it to mandatory
2496 will still require SMB2 clients to use signing.</string>
2498 <string id="POL_7C0D1957_E0F4_5B60_805D_FBA7399D8737_Help">This option sets the path to the encrypted smbpasswd file. By
2499 default the path to the smbpasswd file is compiled into Samba.
2502 An example of use is:
2504 smb passwd file = /etc/samba/smbpasswd</string>
2506 <string id="POL_94D60BE2_185E_5EC1_8E58_146C4B17C1E7_Help">This option can be set to a file (PEM format) containing CA certificates of root CAs to trust to sign certificates or intermediate CA certificates. This path is relative to if the path does not start with a /.</string>
2508 <string id="POL_A9FA5D2E_2052_5A81_812D_83A2952DF38B_Help">This option can be set to a file (PEM format) containing the RSA certificate. This path is relative to if the path does not start with a /.</string>
2510 <string id="POL_C3E30BBB_123E_55E6_9693_7FF6CCF7488D_Help">This option can be set to a file containing a certificate revocation list (CRL). This path is relative to if the path does not start with a /.</string>
2512 <string id="POL_ABFC90A0_6AA2_5372_85E6_FCD989E458EE_Help">This option can be set to a file with Diffie-Hellman parameters which will be used with DH ciphers. This path is relative to if the path does not start with a /.</string>
2514 <string id="POL_0F91E806_ADD5_59A1_B4FA_E99A51FED659_Help">If this option is set to yes, then Samba will use TLS when possible in communication.</string>
2516 <string id="POL_D245CE57_C525_5967_A452_F28BFDB9509B_Help">This option can be set to a file (PEM format) containing the RSA private key. This file must be accessible without a pass-phrase, i.e. it must not be encrypted. This path is relative to if the path does not start with a /.</string>
2518 <string id="POL_6DB833DB_F8B8_5A20_8E2A_6B7D8E298B9D_Help">This controls if and how strict the client will verify the peer's certificate and name. Possible values are (in increasing order): no_check, ca_only, ca_and_name_if_available, ca_and_name and as_strict_as_possible.
2519 When set to no_check the certificate is not verified at all, which allows trivial man in the middle attacks.
2520 When set to ca_only the certificate is verified to be signed from a ca specified in the option. Setting to a valid file is required. The certificate lifetime is also verified. If the option is configured, the certificate is also verified against the ca crl.
2521 When set to ca_and_name_if_available all checks from ca_only are performed. In addition, the peer hostname is verified against the certificate's name, if it is provided by the application layer and not given as an ip address string.
2522 When set to ca_and_name all checks from ca_and_name_if_available are performed. In addition the peer hostname needs to be provided and even an ip address is checked against the certificate's name.
2523 When set to as_strict_as_possible all checks from ca_and_name are performed. In addition the needs to be configured. Future versions of Samba may implement additional checks.</string>
2525 <string id="POL_82913C09_64C3_59C3_8303_3A815661F70E_Help">This boolean parameter controls whether Samba
2526 attempts to synchronize the UNIX password with the SMB password
2527 when the encrypted SMB password in the smbpasswd file is changed.
2528 If this is set to yes the program specified in the passwd
2529 program parameter is called AS ROOT -
2530 to allow the new UNIX password to be set without access to the
2531 old UNIX password (as the SMB password change code has no
2532 access to the old password cleartext, only the new).
2534 This option has no effect if samba
2535 is running as an active directory domain controller, in that case have a
2536 look at the option and the
2537 samba-tool user syncpasswords command.</string>
2539 <string id="POL_37EE4890_B571_50D5_B6D7_3462FF89BCE1_Help">This option helps Samba to try and 'guess' at
2540 the real UNIX username, as many DOS clients send an all-uppercase
2541 username. By default Samba tries all lowercase, followed by the
2542 username with the first letter capitalized, and fails if the
2543 username is not found on the UNIX machine.
2545 If this parameter is set to non-zero the behavior changes.
2546 This parameter is a number that specifies the number of uppercase
2547 combinations to try while trying to determine the UNIX user name. The
2548 higher the number the more combinations will be tried, but the slower
2549 the discovery of usernames will be. Use this parameter when you have
2550 strange usernames on your UNIX machine, such as AstrangeUser
2551 .
2553 This parameter is needed only on UNIX systems that have case
2554 sensitive usernames.
2558 <string id="POL_086EBC7E_1D72_5C67_9447_F5F6E36EFA8F_Help">This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they can more easily share files.
2560 Please note that for user mode security, the username map is applied prior to validating the user credentials. Domain member servers (domain or ads) apply the username map after the user has been successfully authenticated by the domain controller and require fully qualified entries in the map table (e.g. biddle = DOMAIN\foo).
2562 The map file is parsed line by line. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group. The special client name '*' is a wildcard and matches any name. Each line of the map file may be up to 1023 characters long.
2564 The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left. Processing then continues with the next line.
2566 If any line begins with a '#' or a ';' then it is ignored.
2568 If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line. Otherwise mapping continues with every line being processed. Using '!' is most useful when you have a wildcard mapping line later in the file.
2570 For example to map from the name admin or administrator to the UNIX name root you would use:
2572 root = admin administrator
2573 Or to map anyone in the UNIX group system to the UNIX name sys you would use:
2575 sys = @system
2578 You can have as many mappings as you like in a username map file.
2581 If your system supports the NIS NETGROUP option then the netgroup database is checked before the /etc/group database for matching groups.
2583 You can map Windows usernames that have spaces in them by using double quotes around the name. For example:
2587 would map the windows username "Andrew Tridgell" to the unix username "tridge".
2589 The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the
2590 '!' to tell Samba to stop processing if it gets a match on that line:
2592 !sys = mary fred
2593 guest = *
2597 Note that the remapping is applied to all occurrences of usernames. Thus if you connect to \\server\fred and fred is remapped to mary then you will actually be connecting to \\server\mary and will need to supply a password suitable for mary not fred. The only exception to this is the username passed to a Domain Controller (if you have one). The DC will receive whatever username the client supplies without modification.
2600 Also note that no reverse mapping is done. The main effect this has is with printing. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.
2602 Samba versions prior to 3.0.8 would only support reading the fully qualified username (e.g.: DOMAIN\user) from the username map when performing a kerberos login from a client. However, when looking up a map entry for a user authenticated by NTLM[SSP], only the login name would be used for matches. This resulted in inconsistent behavior sometimes even on the same server.
2606 The following functionality is obeyed in version 3.0.8 and later:
2610 When performing local authentication, the username map is applied to the login name before attempting to authenticate
2611 the connection.
2615 When relying upon a external domain controller for validating authentication requests, smbd will apply the username map
2616 to the fully qualified username (i.e. DOMAIN\user) only after the user has been successfully authenticated.
2620 An example of use is:
2622 username map = /usr/local/samba/lib/users.map</string>
2624 <string id="POL_0FE7956E_5744_5658_A2ED_8433C45918D7_Help">Mapping usernames with the or features of Samba can be relatively expensive. During login of a user, the mapping is done several times. In particular, calling the can slow down logins if external databases have to be queried from the script being called.
2625 The parameter controls a mapping cache. It specifies the number of seconds a mapping from the username map file or script is to be efficiently cached. The default of 0 means no caching is done.
2629 <string id="POL_7C2B49D9_45DE_5D97_B844_9F509F86D211_Help">This script is a mutually exclusive alternative to the parameter. This parameter specifies and external program or script that must accept a single command line option (the username transmitted in the authentication request) and return a line on standard output (the name to which the account should mapped). In this way, it is possible to store username map tables in an LDAP or NIS directory services.
2631 Example: /etc/samba/scripts/mapusers.sh</string>
2633 <string id="POL_22AAB8AC_4E62_5B51_BC38_C9340E8AC56E_Help">This option can be set to a string describing the TLS protocols
2634 to be supported in the parts of Samba that use GnuTLS, specifically
2635 the AD DC.
2637 The string is appended to the default priority list of GnuTLS.
2638 The valid options are described in the
2639 GNUTLS
2640 Priority-Strings documentation at http://gnutls.org/manual/html_node/Priority-Strings.html
2642 The SSL3.0 protocol will be disabled.</string>
2644 <string id="POL_08DDB9FE_1D88_5264_BEB0_6D60420CE12B_Help">The integer parameter specifies the maximum number of
2645 threads each smbd process will create when doing parallel asynchronous IO
2646 calls. If the number of outstanding calls is greater than this
2647 number the requests will not be refused but go onto a queue
2648 and will be scheduled in turn as outstanding requests complete.
2651 aio read size
2652 aio write size</string>
2654 <string id="POL_0F98F240_9B2D_5788_AC7C_7B2ECDAE60A2_Help">The value of the parameter (a decimal integer)
2655 represents the number of minutes of inactivity before a connection
2656 is considered dead, and it is disconnected. The deadtime only takes
2657 effect if the number of open files is zero.
2658 This is useful to stop a server's resources being
2659 exhausted by a large number of inactive connections.
2661 Most clients have an auto-reconnect feature when a
2662 connection is broken so in most cases this parameter should be
2663 transparent to users.
2665 Using this parameter with a timeout of a few minutes
2666 is recommended for most systems.
2668 A deadtime of zero indicates that no auto-disconnection should be performed.
2672 <string id="POL_BAC6D3CB_A32D_5702_93FD_289B714016C3_Help">This is a tuning option. When this is enabled a
2673 caching algorithm will be used to reduce the time taken for getwd()
2674 calls. This can have a significant impact on performance, especially
2675 when the parameter is set to no.</string>
2677 <string id="POL_0FB07FB9_33B4_5ECF_9725_9B7A38F863AF_Help">Specifies whether samba should use (expensive)
2678 hostname lookups or use the ip addresses instead. An example place
2679 where hostname lookups are currently used is when checking
2680 the hosts deny and hosts allow.
2682 Example: yes</string>
2684 <string id="POL_C2D014CF_45D1_5A08_9727_3F2B500A4D58_Help">The value of the parameter (an integer) represents
2685 the number of seconds between keepalive
2686 packets. If this parameter is zero, no keepalive packets will be
2687 sent. Keepalive packets, if sent, allow the server to tell whether
2688 a client is still present and responding.
2690 Keepalives should, in general, not be needed if the socket
2691 has the SO_KEEPALIVE attribute set on it by default. (see ).
2692 Basically you should only use this option if you strike difficulties.
2694 Please note this option only applies to SMB1 client connections, and
2695 has no effect on SMB2 clients.
2699 <string id="POL_AF4738EE_230C_5D39_A4CE_F270B28FE9AB_Help">This option allows you to put an upper limit
2700 on the apparent size of disks. If you set this option to 100
2701 then all shares will appear to be not larger than 100 MB in
2702 size.
2704 Note that this option does not limit the amount of
2705 data you can put on the disk. In the above case you could still
2706 store much more than 100 MB on the disk, but if a client ever asks
2707 for the amount of free disk space or the total disk size then the
2708 result will be bounded by the amount specified in max
2709 disk size.
2711 This option is primarily useful to work around bugs
2712 in some pieces of software that can't handle very large disks,
2713 particularly disks over 1GB in size.
2715 A max disk size of 0 means no limit.
2719 <string id="POL_21C3BE22_42E5_544F_97AB_732B2163839B_Help">This parameter limits the maximum number of
2720 open files that one smbd
2721 8 file
2722 serving process may have open for a client at any one time.
2723 This parameter can be set very high (16384) as Samba uses
2724 only one bit per unopened file. Setting this parameter lower than
2725 16384 will cause Samba to complain and set this value back to
2727 open file handles being available.
2729 The limit of the number of open files is usually set
2730 by the UNIX per-process file descriptor limit rather than
2731 this parameter so you should never need to touch this parameter.</string>
2733 <string id="POL_67BA8388_A439_54EA_8A1B_B6D2CCD8BB9B_Help">This parameter limits the maximum number of smbd
2734 8 processes concurrently running on a system and is intended
2735 as a stopgap to prevent degrading service to clients in the event that the server has insufficient
2736 resources to handle more than this number of connections. Remember that under normal operating
2737 conditions, each user will have an smbd
2738 8 associated with him or her to handle connections to all
2739 shares from a given host.
2741 For a Samba ADDC running the standard process model this option
2742 limits the number of processes forked to handle requests.
2743 Currently new processes are only forked for ldap and netlogon
2744 requests.
2748 <string id="POL_7CB978B4_3314_5AE7_9821_574DC024294B_Help">Specifies the number of seconds it takes before
2749 entries in samba's hostname resolve cache time out. If
2750 the timeout is set to 0. the caching is disabled.
2754 <string id="POL_93A78BFD_8C1E_5643_8329_A90FF5CE5A6B_Help">Modern server operating systems are tuned for high
2755 network performance in the majority of situations; when you set socket
2756 options you are overriding those settings. Linux in particular has an
2757 auto-tuning mechanism for buffer sizes that will be disabled if you
2758 specify a socket buffer size. This can potentially cripple your
2759 TCP/IP stack.
2761 Getting the socket options correct can make a big difference to
2762 your performance, but getting them wrong can degrade it by just as
2763 much. As with any other low level setting, if you must make changes
2764 to it, make small changes and test the effect
2765 before making any large changes.
2769 This option allows you to set socket options
2770 to be used when talking with the client.
2772 Socket options are controls on the networking layer
2773 of the operating systems which allow the connection to be
2774 tuned.
2776 This option will typically be used to tune your Samba server
2777 for optimal performance for your local network. There is no way
2778 that Samba can know what the optimal parameters are for your net,
2779 so you must experiment and choose them yourself. We strongly
2780 suggest you read the appropriate documentation for your operating
2781 system first (perhaps man
2782 setsockopt will help).
2784 You may find that on some systems Samba will say
2786 either incorrectly typed it or you need to add an include file
2787 to includes.h for your OS. If the latter is the case please
2788 send the patch to
2789 samba-technical@lists.samba.org.
2791 Any of the supported socket options may be combined
2792 in any way you like, as long as your OS allows it.
2794 This is the list of socket options currently settable
2795 using this option:
2798 SO_KEEPALIVE
2799 SO_REUSEADDR
2800 SO_BROADCAST
2801 TCP_NODELAY TCP_KEEPCNT * TCP_KEEPIDLE * TCP_KEEPINTVL *
2802 IPTOS_LOWDELAY
2803 IPTOS_THROUGHPUT SO_REUSEPORT
2804 SO_SNDBUF *
2805 SO_RCVBUF *
2806 SO_SNDLOWAT *
2807 SO_RCVLOWAT * SO_SNDTIMEO * SO_RCVTIMEO * TCP_FASTACK * TCP_QUICKACK TCP_NODELAYACK TCP_KEEPALIVE_THRESHOLD * TCP_KEEPALIVE_ABORT_THRESHOLD * TCP_DEFER_ACCEPT * TCP_USER_TIMEOUT *
2810 Those marked with a '*' take an integer
2812 or disable the option, by default they will be enabled if you
2815 To specify an argument use the syntax SOME_OPTION = VALUE
2816 for example SO_SNDBUF = 8192. Note that you must
2817 not have any spaces before or after the = sign.
2819 If you are on a local network then a sensible option
2820 might be:
2822 socket options = IPTOS_LOWDELAY
2824 If you have a local network then you could try:
2826 socket options = IPTOS_LOWDELAY TCP_NODELAY
2828 If you are on a wide area network then perhaps try
2829 setting IPTOS_THROUGHPUT.
2831 Note that several of the options may cause your Samba server to fail completely. Use these options with caution!
2833 Example: IPTOS_LOWDELAY</string>
2835 <string id="POL_3FD02174_8A27_5426_848C_B3123EA8C4C3_Help">This global parameter determines if the tdb internals of Samba can
2836 depend on mmap working correctly on the running system. Samba requires a coherent
2837 mmap/read-write system memory cache. Currently only OpenBSD and HPUX do not have such a
2838 coherent cache, and on those platforms this parameter is overridden internally
2839 to be effectively no. On all systems this parameter should be left alone. This
2840 parameter is provided to help the Samba developers track down problems with
2841 the tdb internal code.</string>
2843 <string id="POL_77FC1090_5D4B_587E_BD3B_DAE9F7A9682F_Help">The get quota command should only be used whenever there is no operating system API available from the OS that samba can use.
2844 This option is only available Samba was compiled with quotas support.
2845 This parameter should specify the path to a script that queries the quota information for the specified user/group for the partition that the specified directory is on.
2846 Such a script is being given 3 arguments:
2847 directory type of query uid of user or gid of group
2848 The directory is actually mostly just "." - It needs to be treated relatively to the current working directory that the script can also query.
2849 The type of query can be one of:
2850 1 - user quotas 2 - user default quotas (uid = -1) 3 - group quotas 4 - group default quotas (gid = -1)
2851 This script should print one line as output with spaces between the columns. The printed columns should be:
2852 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced) 2 - number of currently used blocks 3 - the softlimit number of blocks 4 - the hardlimit number of blocks 5 - currently used number of inodes 6 - the softlimit number of inodes 7 - the hardlimit number of inodes 8 (optional) - the number of bytes in a block(default is 1024)
2854 Example: /usr/local/sbin/query_quota</string>
2856 <string id="POL_B093DF52_6C77_5327_AC90_AAC6AF6CB126_Help">If set to yes, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server.
2857 See also the share level parameter. For more information on setting up a Dfs tree on Samba, refer to the MSFDS chapter in the book Samba3-HOWTO.</string>
2859 <string id="POL_6B9A8C91_49AF_58C8_931C_0304B60491D2_Help">The set quota command should only be used whenever there is no operating system API available from the OS that samba can use.
2860 This option is only available if Samba was compiled with quota support.
2861 This parameter should specify the path to a script that can set quota for the specified arguments.
2862 The specified script should take the following arguments:
2863 1 - path to where the quota needs to be set. This needs to be interpreted relative to the current working directory that the script may also check for. 2 - quota type 1 - user quotas 2 - user default quotas (uid = -1) 3 - group quotas 4 - group default quotas (gid = -1) 3 - id (uid for user, gid for group, -1 if N/A) 4 - quota state (0 = disable, 1 = enable, 2 = enable and enforce) 5 - block softlimit 6 - block hardlimit 7 - inode softlimit 8 - inode hardlimit 9(optional) - block size, defaults to 1024
2864 The script should output at least one line of data on success. And nothing on failure.
2866 Example: /usr/local/sbin/set_quota</string>
2868 <string id="POL_6A683A86_8075_55FF_B1E6_D7874A3539AA_Help">This option controls whether winbind will execute the gpupdate command defined in on the Group Policy update interval. The Group Policy update interval is defined as every 90 minutes, plus a random offset between 0 and 30 minutes. This applies Group Policy Machine polices to the client or KDC and machine policies to a server.
2870 Example: yes</string>
2872 <string id="POL_0471CC71_51D5_58F6_A00A_6E8B283C3AF5_Help">Setting this parameter to no prevents winbind from creating custom krb5.conf files. Winbind normally does this because the krb5 libraries are not AD-site-aware and thus would pick any domain controller out of potentially very many. Winbind is site-aware and makes the krb5 libraries use a local DC by creating its own krb5.conf files. Preventing winbind from doing this might become necessary if you have to add special options into your system-krb5.conf that winbind does not see.</string>
2874 <string id="POL_46FF92BD_F484_5B2C_A639_ACBE73F15F3A_Help">The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables.
2875 This option specifies the default backend that is used when no special configuration set, but it is now deprecated in favour of the new spelling .</string>
2877 <string id="POL_309434B4_68BA_53E0_BDF9_CA589711EA29_Help">This parameter specifies the number of seconds that Winbind's idmap interface will cache positive SID/uid/gid query results. By
2878 default, Samba will cache these results for one week.</string>
2880 <string id="POL_066B06D4_3BC0_5CFA_80A9_D2B1C046B5B0_Help">The idmap gid parameter specifies the range of group ids for the default idmap configuration. It is now deprecated in favour of .
2881 See the option.
2885 <string id="POL_9B5D009F_1EBE_5E94_A46B_8644157A6061_Help">This parameter specifies the number of seconds that Winbind's idmap interface will cache negative SID/uid/gid query results.</string>
2887 <string id="POL_37D1856A_CAF9_5395_AC8E_8E0F3E9C03E4_Help">The idmap uid parameter specifies the range of user ids for the default idmap configuration. It is now deprecated in favour of .
2888 See the option.
2892 <string id="POL_283F0A5F_5841_5D1D_8EE3_D2715805A463_Help">Setting this parameter to no will prevent winbind to include the system /etc/krb5.conf file into the krb5.conf file it creates. See also . This option only applies to Samba built with MIT Kerberos.</string>
2894 <string id="POL_61C9E6AE_96EF_5E8D_9AB8_7598584D391E_Help">This option controls whether winbindd sends the NETLOGON_NEG_NEUTRALIZE_NT4_EMULATION flag in order to bypass the NT4 emulation of a domain controller.
2895 Typically you should not need set this. It can be useful for upgrades from NT4 to AD domains.
2896 The behavior can be controlled per netbios domain by using 'neutralize nt4 emulation:NETBIOSDOMAIN = yes' as option.</string>
2898 <string id="POL_D8459DE9_6E91_58A6_8E4E_83BFBB41AE4E_Help">This option controls whether winbindd requires support for aes support for the netlogon secure channel.
2899 The following flags will be required NETLOGON_NEG_ARCFOUR, NETLOGON_NEG_SUPPORTS_AES, NETLOGON_NEG_PASSWORD_SET2 and NETLOGON_NEG_AUTHENTICATED_RPC.
2900 You can set this to yes if all domain controllers support aes. This will prevent downgrade attacks.
2901 The behavior can be controlled per netbios domain by using 'reject md5 servers:NETBIOSDOMAIN = yes' as option.
2902 This option takes precedence to the option.</string>
2904 <string id="POL_E3A88031_AF89_5D12_9F48_5BD36B25F58C_Help">This option controls whether winbindd requires support for md5 strong key support for the netlogon secure channel.
2905 The following flags will be required NETLOGON_NEG_STRONG_KEYS, NETLOGON_NEG_ARCFOUR and NETLOGON_NEG_AUTHENTICATED_RPC.
2906 You can set this to no if some domain controllers only support des. This might allows weak crypto to be negotiated, may via downgrade attacks.
2907 The behavior can be controlled per netbios domain by using 'require strong key:NETBIOSDOMAIN = no' as option.
2908 Note for active directory domain this option is hardcoded to 'yes'
2909 This option yields precedence to the option.
2910 This option takes precedence to the option.</string>
2912 <string id="POL_D55FF104_CF84_512D_9962_D01784923C49_Help">When filling out the user information for a Windows NT user, the winbindd 8 daemon uses this parameter to fill in the home directory for that user. If the string %D is present it is substituted with the user's Windows NT domain name. If the string %U is present it is substituted with the user's Windows NT user name.</string>
2914 <string id="POL_A317595E_2C79_5B73_9043_CEB7525F6692_Help">When filling out the user information for a Windows NT user, the winbindd 8 daemon uses this parameter to fill in the login shell for that user.</string>
2916 <string id="POL_F8F9B8BF_2D26_5079_928E_7168BBCA91BE_Help">This parameter specifies the number of seconds the winbindd 8 daemon will cache user and group information before querying a Windows NT server again.
2918 This does not apply to authentication requests, these are always evaluated in real time unless the option has been enabled.</string>
2920 <string id="POL_07E24EA1_B340_5215_BDBB_5248537F9540_Help">This setting controls the location of the winbind daemon's socket. Except within automated test scripts, this should not be altered, as the client tools (nss_winbind etc) do not honour this parameter. Client tools must then be advised of the altered path with the WINBINDD_SOCKET_DIR environment variable.</string>
2922 <string id="POL_8FEAD8B9_8097_5BA2_BD78_7BB0AA8691C1_Help">On large installations using winbindd 8 it may be necessary to suppress the enumeration of groups through the setgrent(), getgrent() and endgrent() group of system calls. If the winbind enum groups parameter is no, calls to the getgrent() system call will not return any data.
2924 Turning off group enumeration may cause some programs to behave oddly.</string>
2926 <string id="POL_FAB1BAAD_85CD_5FE6_B0AA_AC48B77ACCCC_Help">On large installations using winbindd 8 it may be necessary to suppress the enumeration of users through the setpwent(), getpwent() and endpwent() group of system calls. If the winbind enum users parameter is no, calls to the getpwent system call will not return any data.
2928 Turning off user enumeration may cause some programs to behave oddly. For example, the finger program relies on having access to the full user list when searching for matching usernames.</string>
2930 <string id="POL_2B331ECE_5A4A_5DE9_8DBF_EFBCE108F070_Help">This option controls the maximum depth that winbindd
2931 will traverse when flattening nested group memberships of Windows domain groups. This is different from the option
2932 which implements the Windows NT4 model of local group nesting. The "winbind expand groups"
2933 parameter specifically applies to the membership of domain groups.
2934 This option also affects the return of non nested group memberships of Windows domain users. With the new default "winbind expand groups = 0" winbind does not query group memberships at all.
2935 Be aware that a high value for this parameter can result in system slowdown as the main parent winbindd daemon must perform the group unrolling and will be unable to answer incoming NSS or authentication requests during this time.
2936 The default value was changed from 1 to 0 with Samba 4.2. Some broken applications (including some implementations of newgrp and sg) calculate the group memberships of users by traversing groups, such applications will require "winbind expand groups = 1". But the new default makes winbindd more reliable as it doesn't require SAMR access to domain controllers of trusted domains.</string>
2938 <string id="POL_7F3A4DCD_923C_5586_AFFB_1BA559F399CB_Help">Allows one to enter a list of trusted domains winbind should
2939 ignore (untrust). This can avoid the overhead of resources from
2940 attempting to login to DCs that should not be communicated with.
2942 Example: DOMAIN1, DOMAIN2</string>
2944 <string id="POL_FE5A1763_2311_55A2_AB2E_10D92C3A7FC4_Help">This parameter specifies the maximum number of clients the winbindd 8 daemon can connect with. The parameter is not a hard limit. The winbindd 8 daemon configures itself to be able to accept at least that many connections, and if the limit is reached, an attempt is made to disconnect idle clients.</string>
2946 <string id="POL_57855ED8_E596_52E6_A8F8_B710E76BD0F6_Help">This parameter specifies the maximum number of simultaneous connections that the winbindd 8 daemon should open to the domain controller of one domain. Setting this parameter to a value greater than 1 can improve scalability with many simultaneous winbind requests, some of which might be slow. Note that if is set to Yes, then only one DC connection is allowed per domain, regardless of this setting.
2950 <string id="POL_6C096F2D_4DB1_5E05_84BB_9E9E3E0708BB_Help">If set to yes, this parameter activates the support for nested
2951 groups. Nested groups are also called local groups or
2952 aliases. They work like their counterparts in Windows: Nested
2953 groups are defined locally on any machine (they are shared
2954 between DC's through their SAM) and can contain users and
2955 global groups from any trusted SAM. To be able to use nested
2956 groups, you need to run nss_winbind.</string>
2958 <string id="POL_7C9859FE_6BA0_526D_A308_9454D3063550_Help">This parameter controls whether winbindd will replace whitespace in user and group names with an underscore (_) character. For example, whether the name "Space Kadet" should be replaced with the string "space_kadet". Frequently Unix shell scripts will have difficulty with usernames contains whitespace due to the default field separator in the shell. If your domain possesses names containing the underscore character, this option may cause problems unless the name aliasing feature is supported by your nss_info plugin.
2960 This feature also enables the name aliasing API which can be used to make domain user and group names to a non-qualified version. Please refer to the manpage for the configured idmap and nss_info plugin for the specifics on how to configure name aliasing for a specific configuration. Name aliasing takes precedence (and is mutually exclusive) over the whitespace replacement mechanism discussed previously.
2962 Example: yes</string>
2964 <string id="POL_3D3D280A_1D60_58AA_A7BD_54D13DDBE1A6_Help">This parameter is designed to control how Winbind retrieves Name Service Information to construct a user's home directory and login shell. Currently the following settings are available:
2965 template - The default, using the parameters of template shell and template homedir)
2966 <sfu | sfu20 | rfc2307 > - When Samba is running in security = ads and your Active Directory Domain Controller does support the Microsoft "Services for Unix" (SFU) LDAP schema, winbind can retrieve the login shell and the home directory attributes directly from your Directory Server. For SFU 3.0 or 3.5 simply choose "sfu", if you use SFU 2.0 please choose "sfu20". Note that for the idmap backend idmap_ad you need to configure those settings in the idmap configuration section. Make sure to consult the documentation of the idmap backend that you are using.
2968 Example: sfu</string>
2970 <string id="POL_34B48F10_7723_5E77_A57B_AE606BBB43B7_Help">This parameter is designed to control whether Winbind should allow one to login with the pam_winbind module using Cached Credentials. If enabled, winbindd will store user credentials from successful logins encrypted in a local cache.
2972 Example: yes</string>
2974 <string id="POL_05A14875_99EE_5000_A1E2_100D2F7B079F_Help">This parameter specifies the number of seconds the winbindd 8 daemon will wait between attempts to contact a Domain controller for a domain that is determined to be down or not contactable.</string>
2976 <string id="POL_98A94538_AA09_51C8_A96D_ACB0B314F5F4_Help">This parameter is designed to control whether Winbind should refresh Kerberos Tickets retrieved using the pam_winbind module.
2978 Example: yes</string>
2980 <string id="POL_96B1E9F8_5418_5EA0_8B87_614B45822D92_Help">This parameter specifies the number of seconds the winbindd 8 daemon will wait before disconnecting either a client connection with no outstanding requests (idle) or a client connection with a request that has remained outstanding (hung) for longer than this number of seconds.</string>
2982 <string id="POL_FEC015B1_6B0B_5D76_B23D_71363578FAF7_Help">Setting this parameter to yes forces winbindd to use RPC instead of LDAP to retrieve information from Domain
2983 Controllers.</string>
2985 <string id="POL_412B470E_EC88_556F_B9DE_1952C70E45B1_Help">This option only takes effect when the option is set to
2986 domain or ads.
2987 If it is set to yes (the default), winbindd periodically tries to scan for new
2988 trusted domains and adds them to a global list inside of winbindd.
2989 The list can be extracted with wbinfo --trusted-domains --verbose.
2990 This matches the behaviour of Samba 4.7 and older.
2992 The construction of that global list is not reliable and often
2993 incomplete in complex trust setups. In most situations the list is
2994 not needed any more for winbindd to operate correctly.
2995 E.g. for plain file serving via SMB using a simple idmap setup
2996 with autorid, tdb or ad.
2997 However some more complex setups require the list, e.g.
2998 if you specify idmap backends for specific domains.
2999 Some pam_winbind setups may also require the global list.
3001 If you have a setup that doesn't require the global list, you should set
3002 no.</string>
3004 <string id="POL_6247DEB4_05CC_51B8_A8CB_1FF7DEDA741C_Help">This option controls whether any requests from winbindd to domain controllers pipe will be sealed. Disabling sealing can be useful for debugging purposes.
3005 The behavior can be controlled per netbios domain by using 'winbind sealed pipes:NETBIOSDOMAIN = no' as option.</string>
3007 <string id="POL_7E1E179F_7E0D_5CB4_BDAA_B8EDF41428CC_Help">This parameter allows an admin to define the character used when listing a username of the form of DOMAIN \user. This parameter is only applicable when using the pam_winbind.so and nss_winbind.so modules for UNIX services.
3008 Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group.
3010 Example: +</string>
3012 <string id="POL_1780A1A5_0535_5D0B_8105_2129879E3C40_Help">This parameter specifies whether the winbindd 8 daemon should operate on users without domain component in their username. Users without a domain component are treated as is part of the winbindd server's own domain. While this does not benefit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system. This option should be avoided if possible. It can cause confusion about responsibilities for a user or group. In many situations it is not clear whether winbind or /etc/passwd should be seen as authoritative for a user, likewise for groups.
3014 Example: yes</string>
3015 <string id="POL_71A1842A_9526_5BF9_A0FC_07322D2C6C81">winbind use krb5 enterprise principals</string>
3016 <string id="POL_71A1842A_9526_5BF9_A0FC_07322D2C6C81_Help">winbindd is able to get kerberos tickets for pam_winbind with krb5_auth or wbinfo -K/--krb5auth=.
3017 winbindd (at least on a domain member) is never be able to have a complete picture of the trust topology (which is managed by the DCs). There might be uPNSuffixes and msDS-SPNSuffixes values, which don't belong to any AD domain at all.
3018 With no winbindd don't even get an incomplete picture of the topology.
3019 It is not really required to know about the trust topology. We can just rely on the [K]DCs of our primary domain (e.g. PRIMARY.A.EXAMPLE.COM) and use enterprise principals e.g. upnfromB@B.EXAMPLE.COM@PRIMARY.A.EXAMPLE.COM and follow the WRONG_REALM referrals in order to find the correct DC. The final principal might be userfromB@INTERNALB.EXAMPLE.PRIVATE.
3020 With yes winbindd enterprise principals will be used.
3022 Example: yes</string>
3024 <string id="POL_B05D0593_B0CE_52A9_977C_E7A897EEA307_Help">Specifies that nmbd 8 when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client.
3025 Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum.
3026 nmbd spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action.</string>
3029 8 when acting as a WINS server (yes) what the maximum
3030 'time to live' of NetBIOS names that nmbd
3031 will grant will be (in seconds). You should never need to change this parameter. The default is 6 days (518400 seconds).</string>
3034 8
3035 when acting as a WINS server (yes) what the minimum 'time to live'
3036 of NetBIOS names that nmbd will grant will be (in
3037 seconds). You should never need to change this parameter. The default
3040 <string id="POL_890DE0DC_C0FC_565A_A1D3_AD06EFAC41ED_Help">Normally queries for 0x1C names (all logon servers for a domain) will return the first address of the 0x1B names (domain master browser and PDC) as first address in the result list. As many client only use the first address in the list by default, all clients will use the same server (the PDC). Windows servers have an option to disable this behavior (since Windows 2000 Service Pack 2).</string>
3042 <string id="POL_06F0FFB1_F595_57BB_B964_6D419A02F468_Help">Normally queries for 0x1C names will return the addresses in the same order as they're stored in the database, that means first all addresses which have been directly registered at the local wins server and then all addresses registered at other servers. Windows servers have an option to change this behavior and randomize the returned addresses. Set this parameter to "yes" and Samba will sort the address list depending on the client address and the matching bits of the addresses, the first address is randomized based on depending on the "nbtd:wins_randomize1Clist_mask" parameter.</string>
3044 <string id="POL_F63D2A1E_D6BA_516E_995D_F9FEE05D49DB_Help">If the "nbtd:wins_randomize1Clist" parameter is set to "yes", then randomizing of the first returned address is based on the specified netmask. If there are addresses which are in the same subnet as the client address, the first returned address is randomly chosen out them. Otherwise the first returned address is randomly chosen out of all addresses.</string>
3046 <string id="POL_D0A83CCC_07AF_553B_84AE_4824377AE692_Help">This specifies the address that is stored in the winsOwner attribute, of locally registered winsRecord-objects. The default is to use the ip-address of the first network interface.</string>
3048 <string id="POL_06442D20_4739_5DE0_820F_516416AD0ECF_Help">This parameter disables fsync() after changes of the WINS database.</string>
3050 <string id="POL_F7271C08_2949_53E0_809D_9B976AB9DE2E_Help">When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS.
3051 The wins hook parameter specifies the name of a script or executable that will be called as follows:
3052 wins_hook operation name nametype ttl IP_list
3053 The first argument is the operation and is one of "add", "delete", or "refresh". In most cases the operation can be ignored as the rest of the parameters provide sufficient information. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add.
3054 The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods.
3055 The third argument is the NetBIOS name type as a 2 digit hexadecimal number.
3056 The fourth argument is the TTL (time to live) for the name in seconds. The fifth and subsequent arguments are the IP addresses currently registered for that name. If this list is empty then the name should be deleted.
3057 An example script that calls the BIND dynamic DNS update program nsupdate is provided in the examples directory of the Samba source code.</string>
3059 <string id="POL_A1E6C0E7_38BA_5583_816D_73C91FCAADB4_Help">This is a boolean that controls if nmbd 8 will respond to broadcast name queries on behalf of other hosts. You may need to set this to yes for some older clients.</string>
3061 <string id="POL_31C40FB1_1B0A_5AA3_80F9_7914AC38FD99_Help">This specifies the IP address (or DNS name: IP address for preference) of the WINS server that nmbd 8 should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.
3062 You should point this at your WINS server if you have a multi-subnetted network.
3063 If you want to work in multiple namespaces, you can give every wins server a 'tag'. For each tag, only one (working) server will be queried for a name. The tag should be separated from the ip address by a colon.
3064 You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly. See the chapter in the Samba3-HOWTO on Network Browsing.
3071 <string id="POL_44517D2D_845B_5F7B_90F2_F7BD0DA063A9_Help">This boolean controls if the nmbd 8 process in Samba will act as a WINS server. You should not set this to yes unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server. Note that you should NEVER set this to yes on more than one machine in your network.</string>
3073 <string id="POL_8A035569_9C85_59DC_9BF8_241994D4E947_Help">This maximum interval in seconds between 2 periodically scheduled runs where we check for wins.ldb changes and do push notifications to our push partners. Also wins_config.ldb changes are checked in that interval and partner configuration reloads are done.</string>
3074 <string id="POL_186864AE_CE31_5628_BA4E_6B9F06F087E5">wreplsrv:propagate name releases</string>
3075 <string id="POL_186864AE_CE31_5628_BA4E_6B9F06F087E5_Help">If this parameter is enabled, then explicit (from the client) and implicit (via the scavenging) name releases are propagated to the other servers directly, even if there are still other addresses active, this applies to SPECIAL GROUP (2) and MULTIHOMED (3) entries. Also the replication conflict merge algorithm for SPECIAL GROUP (2) entries discards replica addresses where the address owner is the local server, if the address was not stored locally before. The merge result is propagated directly in case an address was discarded. A Windows servers doesn't propagate name releases of SPECIAL GROUP (2) and MULTIHOMED (3) entries directly, which means that Windows servers may return different results to name queries for SPECIAL GROUP (2) and MULTIHOMED (3) names. The option doesn't have much negative impact if Windows servers are around, but be aware that they might return unexpected results.</string>
3077 <string id="POL_8DC9CC59_A490_5F52_8C69_A9EEC802C48C_Help">This is the interval in s between 2 scavenging runs which clean up the WINS database and changes the states of expired name records. Defaults to half of the value of wreplsrv:renew_interval.</string>
3078 <string id="POL_DB737BF2_9B47_5895_A3F8_D51BBD764222">wreplsrv:tombstone_extra_timeout</string>
3079 <string id="POL_DB737BF2_9B47_5895_A3F8_D51BBD764222_Help">This is the time in s the server needs to be up till we'll remove tombstone records from our database. Defaults to 3 days.</string>
3081 <string id="POL_30D1C3B2_BDCD_5A5C_A131_11E1E6DA2A76_Help">This is the interval in s till released records of the WINS server become tombstone. Defaults to 6 days.</string>
3083 <string id="POL_F19C445A_AFD5_51B6_B87A_E42499C3C5D8_Help">This is the interval in s till tombstone records are deleted from the WINS database. Defaults to 1 day.</string>
3085 <string id="POL_8CF1FEA3_BD3E_53C0_9F73_34050187A91E_Help">This is the interval in s till we verify active replica records with the owning WINS server. Unfortunately not implemented yet. Defaults to 24 days.</string>
3088 <string id="POL_38DA04F0_3FD6_4425_8924_1CEEA685FD07_Help"> The contents of /etc/motd are displayed after a successful login but just before it executes the login shell.</string>
3090 <string id="POL_68E9155C_CB49_428E_AFE0_B89316FFD948_Help"> The issue file may contain certain escape codes to display the system name, date, time etc. All escape codes consist of a backslash (\) immediately followed by one of the characters listed below.
3093 Insert the IPv4 address of the specified network interface (for example: \4{eth0}). If the interface argument is not specified, then select the first fully configured (UP, non-LOCALBACK, RUNNING) interface. If not any configured interface is found, fall back to the IP address of the machine's hostname.
3096 The same as \4 but for IPv6.
3098 b Insert the baudrate of the current line.
3100 d Insert the current date.
3102 e or e{name}
3103 Translate the human-readable name to an escape sequence and insert it (for example: \e{red}Alert text.\e{reset}). If the name argument is not specified, then insert \033. The currently supported names are: black, blink, blue, bold, brown, cyan, darkgray, gray, green, halfbright, lightblue, lightcyan, lightgray, lightgreen, lightmagenta, lightred, magenta, red, reset, reverse, and yellow. All unknown names are silently ignored.
3105 s Insert the system name (the name of the operating system). Same as 'uname -s'. See also the \S escape code.
3107 S or S{VARIABLE}
3108 Insert the VARIABLE data from /etc/os-release. If this file does not exist then fall back to /usr/lib/os-release. If the VARIABLE argument is not specified, then use PRETTY_NAME from the file or the system name (see \s). This escape code allows to keep /etc/issue distribution and release independent. Note that \S{ANSI_COLOR} is converted to the real terminal escape sequence.
3110 l Insert the name of the current tty line.
3112 m Insert the architecture identifier of the machine. Same as 'uname -m'.
3114 n Insert the nodename of the machine, also known as the hostname. Same as 'uname -n'.
3116 o Insert the NIS domainname of the machine. Same as 'hostname -d'.
3118 O Insert the DNS domainname of the machine.
3120 r Insert the release number of the OS. Same as 'uname -r'.
3122 t Insert the current time.
3124 u Insert the number of current users logged in.
3126 U Insert the string "1 user" or "<n> users" where <n> is the number of current users logged in.
3128 v Insert the version of the OS, that is, the build-date and such.</string>
3131 <string id="POL_ADABE9E0_FFF9_4FFE_A105_03E646C79978_Help">A list of zones to create. Existing zones on the host will be unaffected.
3133 Rule creation for zones is handled in the Rules setting.</string>
3135 <string id="POL_B21F349F_4BF6_473E_8452_047D714F156C_Help">A JSON dictionary, containing zones paired with a list of rules.
3137 For example, to create rules for the Work and Home zones, specify the following JSON:
3139 {
3140 "work": [
3141 {"rule": {"family": "ipv4"}, "source address": "172.25.1.7", "service name": "ftp", "reject": {}},
3143 ],
3144 "home": [
3146 {"rule": {"family": "ipv4"}, "source address": "192.168.1.2/32", "service name": "telnet", "accept": {"limit value": "1/m"}}
3147 ]
3148 }
3150 An improperly formatted JSON will be ignored.
3152 The rule structure loosely follows the Firewalld Rich Language Documentation.
3154 General rule structure:
3155 {
3156 "rule": {
3159 },
3163 "port": {
3166 }
3169 "Masquerade": true|false,
3171 "forward-port": {
3176 },
3177 "source-port": {
3180 },
3181 "log": {
3185 },
3186 "audit": {
3188 },
3189 "accept" : {
3191 } | "reject": {
3194 } | "drop": {
3196 } | "mark": {
3199 }
3200 }</string>
3201 </stringTable>
3202 <presentationTable>
3205 </presentation>
3208 </presentation>
3211 </presentation>
3214 </presentation>
3217 </presentation>
3221 </textBox>
3222 </presentation>
3225 </presentation>
3230 </textBox>
3231 </presentation>
3235 </textBox>
3236 </presentation>
3238 <checkBox defaultChecked="true" refId="CHK_A51834ED_BBB9_52C3_A7C5_A566ABE7AB3D">enable core files</checkBox>
3239 </presentation>
3244 </textBox>
3245 </presentation>
3247 <checkBox defaultChecked="true" refId="CHK_03FFDBD4_C185_5951_954F_189B0D4C40DA">multicast dns register</checkBox>
3248 </presentation>
3252 </textBox>
3253 </presentation>
3257 </textBox>
3258 </presentation>
3262 </textBox>
3263 </presentation>
3266 </presentation>
3269 </presentation>
3272 </presentation>
3276 </textBox>
3277 </presentation>
3281 <defaultValue>s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate, dns</defaultValue>
3282 </textBox>
3283 </presentation>
3288 </textBox>
3289 </presentation>
3294 </textBox>
3295 </presentation>
3300 </textBox>
3301 </presentation>
3306 </textBox>
3307 </presentation>
3311 </textBox>
3312 </presentation>
3314 <checkBox defaultChecked="true" refId="CHK_1D40EF50_9DF5_5D95_B5EF_406C4F3774B8">browse list</checkBox>
3315 </presentation>
3320 </textBox>
3321 </presentation>
3323 <checkBox defaultChecked="true" refId="CHK_7A02FE2C_82BF_50CE_91F0_14B1191E7258">enhanced browsing</checkBox>
3324 </presentation>
3329 </textBox>
3330 </presentation>
3333 </presentation>
3335 <checkBox defaultChecked="true" refId="CHK_CFD7EF58_DD73_5465_B0CE_4C6B4E35F416">local master</checkBox>
3336 </presentation>
3339 </presentation>
3344 </textBox>
3345 </presentation>
3350 </textBox>
3351 </presentation>
3355 </textBox>
3356 </presentation>
3361 </textBox>
3362 </presentation>
3365 </presentation>
3370 </textBox>
3371 </presentation>
3374 </presentation>
3379 </textBox>
3380 </presentation>
3385 </textBox>
3386 </presentation>
3389 </presentation>
3394 </textBox>
3395 </presentation>
3398 </presentation>
3400 <checkBox defaultChecked="true" refId="CHK_45471F8A_D0BD_53A3_B51F_393DE6CC03D2">stat cache</checkBox>
3401 </presentation>
3406 </textBox>
3407 </presentation>
3411 </textBox>
3412 </presentation>
3415 </presentation>
3418 </presentation>
3423 </textBox>
3424 </presentation>
3429 </textBox>
3430 </presentation>
3434 </textBox>
3435 </presentation>
3439 </textBox>
3440 </presentation>
3444 </textBox>
3445 </presentation>
3448 </presentation>
3453 </textBox>
3454 </presentation>
3457 </presentation>
3462 </textBox>
3463 </presentation>
3468 </textBox>
3469 </presentation>
3474 </textBox>
3475 </presentation>
3480 </textBox>
3481 </presentation>
3484 </presentation>
3488 </textBox>
3489 </presentation>
3492 </presentation>
3496 </textBox>
3497 </presentation>
3500 </presentation>
3503 </presentation>
3506 </presentation>
3509 </presentation>
3512 </presentation>
3514 <checkBox defaultChecked="true" refId="CHK_8649286E_DE5D_5DE7_A836_AA15E736A911">smb2 leases</checkBox>
3515 </presentation>
3518 </presentation>
3520 <checkBox defaultChecked="true" refId="CHK_ADDEF100_7619_5056_B632_ECEF204DBEC8">debug hires timestamp</checkBox>
3521 </presentation>
3524 </presentation>
3527 </presentation>
3530 </presentation>
3533 </presentation>
3536 </presentation>
3540 </textBox>
3541 </presentation>
3545 </textBox>
3546 </presentation>
3551 </textBox>
3552 </presentation>
3555 </presentation>
3558 </presentation>
3561 </presentation>
3563 <checkBox defaultChecked="true" refId="CHK_16FD7E9E_1FCF_58D9_940E_42D45860825B">timestamp logs</checkBox>
3564 </presentation>
3569 </textBox>
3570 </presentation>
3574 </textBox>
3575 </presentation>
3579 </textBox>
3580 </presentation>
3584 </textBox>
3585 </presentation>
3589 </textBox>
3590 </presentation>
3593 </presentation>
3596 </presentation>
3600 </textBox>
3601 </presentation>
3605 </textBox>
3606 </presentation>
3610 </textBox>
3611 </presentation>
3614 </presentation>
3616 <checkBox defaultChecked="true" refId="CHK_A6532133_05F0_5D5F_983E_8924AB2334D5">enable privileges</checkBox>
3617 </presentation>
3620 </presentation>
3624 </textBox>
3625 </presentation>
3629 </textBox>
3630 </presentation>
3635 </textBox>
3636 </presentation>
3641 </textBox>
3642 </presentation>
3646 </textBox>
3647 </presentation>
3650 </presentation>
3654 </textBox>
3655 </presentation>
3659 </textBox>
3660 </presentation>
3664 </textBox>
3665 </presentation>
3668 </presentation>
3672 </textBox>
3673 </presentation>
3675 <checkBox refId="CHK_AC4E2E8E_74FE_5FD1_B6F4_3637B4582348">allow insecure wide links</checkBox>
3676 </presentation>
3678 <checkBox refId="CHK_D36441A8_7E2F_5174_8483_4DFE0503C16D">allow unsafe cluster upgrade</checkBox>
3679 </presentation>
3682 </presentation>
3686 </textBox>
3687 </presentation>
3691 </textBox>
3692 </presentation>
3694 <checkBox defaultChecked="true" refId="CHK_1A966B04_20C5_5E97_8C75_71519DB4783C">change notify</checkBox>
3695 </presentation>
3699 </textBox>
3700 </presentation>
3704 </textBox>
3705 </presentation>
3708 </presentation>
3712 </textBox>
3713 </presentation>
3717 </textBox>
3718 </presentation>
3721 </presentation>
3724 </presentation>
3728 </textBox>
3729 </presentation>
3733 </textBox>
3734 </presentation>
3737 </presentation>
3739 <checkBox refId="CHK_F76A8EFA_4388_54E3_B283_976BA2DD2A2E">dsdb group change notification</checkBox>
3740 </presentation>
3742 <checkBox refId="CHK_4B61A9A1_8E18_56CF_9B9E_6904A78328A0">dsdb password event notification</checkBox>
3743 </presentation>
3748 </textBox>
3749 </presentation>
3752 </presentation>
3755 </presentation>
3759 </textBox>
3760 </presentation>
3762 <checkBox defaultChecked="true" refId="CHK_F273132D_C805_596F_A0E1_B6ECB4752ADB">kernel change notify</checkBox>
3763 </presentation>
3767 </textBox>
3768 </presentation>
3770 <checkBox refId="CHK_EB18668D_E754_524B_B2D7_CC74BA90421D">log writeable files on exit</checkBox>
3771 </presentation>
3775 </textBox>
3776 </presentation>
3781 </textBox>
3782 </presentation>
3786 </textBox>
3787 </presentation>
3790 </presentation>
3792 <checkBox defaultChecked="true" refId="CHK_49457A99_B4CF_594B_B796_916B9AB74838">nmbd bind explicit broadcast</checkBox>
3793 </presentation>
3797 </textBox>
3798 </presentation>
3802 </textBox>
3803 </presentation>
3807 </textBox>
3808 </presentation>
3811 </presentation>
3815 </textBox>
3816 </presentation>
3820 </textBox>
3821 </presentation>
3824 </presentation>
3829 </textBox>
3830 </presentation>
3835 </textBox>
3836 </presentation>
3841 </textBox>
3842 </presentation>
3846 </textBox>
3847 </presentation>
3850 </presentation>
3853 </presentation>
3855 <checkBox defaultChecked="true" refId="CHK_950CF79D_4898_55EB_A6A8_24F2A6867B1D">usershare owner only</checkBox>
3856 </presentation>
3861 </textBox>
3862 </presentation>
3866 </textBox>
3867 </presentation>
3871 </textBox>
3872 </presentation>
3876 </textBox>
3877 </presentation>
3880 </presentation>
3884 </textBox>
3885 </presentation>
3889 </textBox>
3890 </presentation>
3894 </textBox>
3895 </presentation>
3899 </textBox>
3900 </presentation>
3903 </presentation>
3908 </textBox>
3909 </presentation>
3914 </textBox>
3915 </presentation>
3919 </textBox>
3920 </presentation>
3923 </presentation>
3925 <checkBox defaultChecked="true" refId="CHK_76C31A1A_3CCA_54F4_A09B_01ED9C31465A">enable spoolss</checkBox>
3926 </presentation>
3930 </textBox>
3931 </presentation>
3936 </textBox>
3937 </presentation>
3939 <checkBox defaultChecked="true" refId="CHK_01150395_D329_542B_8848_2D352BA599CA">load printers</checkBox>
3940 </presentation>
3943 </presentation>
3947 </textBox>
3948 </presentation>
3951 </presentation>
3956 </textBox>
3957 </presentation>
3959 <checkBox defaultChecked="true" refId="CHK_21859C56_D5DA_5C2E_9215_BA75864C9B4B">show add printer wizard</checkBox>
3960 </presentation>
3965 </textBox>
3966 </presentation>
3969 </presentation>
3972 </presentation>
3975 </presentation>
3978 </presentation>
3981 </presentation>
3984 </presentation>
3987 </presentation>
3992 </textBox>
3993 </presentation>
3998 </textBox>
3999 </presentation>
4004 </textBox>
4005 </presentation>
4010 </textBox>
4011 </presentation>
4013 <checkBox defaultChecked="true" refId="CHK_5549EDCC_940D_5AEA_8465_B771FEE013BC">client use spnego</checkBox>
4014 </presentation>
4018 <defaultValue>epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver</defaultValue>
4019 </textBox>
4020 </presentation>
4022 <checkBox defaultChecked="true" refId="CHK_AA0DA4CF_4431_509C_8E2D_27BD0DD5CCAB">defer sharing violations</checkBox>
4023 </presentation>
4026 </presentation>
4029 </presentation>
4032 </presentation>
4036 </textBox>
4037 </presentation>
4039 <checkBox defaultChecked="true" refId="CHK_21EE7A7A_DF8F_56F7_85FB_6EC5DD083DD6">large readwrite</checkBox>
4040 </presentation>
4043 </presentation>
4046 </presentation>
4049 </presentation>
4052 </presentation>
4055 </presentation>
4060 </textBox>
4061 </presentation>
4064 </presentation>
4066 <checkBox defaultChecked="true" refId="CHK_DAAC7C86_8FD9_55BF_9125_9C95E2D52AFE">nt pipe support</checkBox>
4067 </presentation>
4069 <checkBox defaultChecked="true" refId="CHK_95DD62AA_03E3_5679_AD11_D5616CD25255">nt status support</checkBox>
4070 </presentation>
4072 <checkBox defaultChecked="true" refId="CHK_B11F35D5_3196_5D92_9B1D_9C746F9162FA">read raw</checkBox>
4073 </presentation>
4076 </presentation>
4079 </presentation>
4084 </textBox>
4085 </presentation>
4090 </textBox>
4091 </presentation>
4096 </textBox>
4097 </presentation>
4100 </presentation>
4103 </presentation>
4106 </presentation>
4109 </presentation>
4114 </textBox>
4115 </presentation>
4119 </textBox>
4120 </presentation>
4123 </presentation>
4125 <checkBox defaultChecked="true" refId="CHK_2280B94E_EB17_5A5E_80F0_B48BE0CBC2CB">unicode</checkBox>
4126 </presentation>
4128 <checkBox defaultChecked="true" refId="CHK_E429FAE8_6D3B_5B56_8EFF_B3B7C25B3DE1">unix extensions</checkBox>
4129 </presentation>
4131 <checkBox defaultChecked="true" refId="CHK_4FD77295_65FD_5553_AB18_D6CF04394DAB">write raw</checkBox>
4132 </presentation>
4134 <checkBox refId="CHK_82B2446C_9CAB_5880_AF33_2803AE49B294">server multi channel support</checkBox>
4135 </presentation>
4137 <checkBox refId="CHK_B6B60597_42F0_58D3_98BB_DB6B75D07112">smb2 disable lock sequence checking</checkBox>
4138 </presentation>
4140 <checkBox refId="CHK_B83E6646_94FD_5882_B57A_15B4BA0AABFD">smb2 disable oplock break retry</checkBox>
4141 </presentation>
4146 </textBox>
4147 </presentation>
4150 </presentation>
4152 <checkBox refId="CHK_EAA911EE_CB2D_5459_AF50_DC1CA4719686">allow dcerpc auth level connect</checkBox>
4153 </presentation>
4155 <checkBox defaultChecked="true" refId="CHK_83FBBE91_8F41_5C06_BD1D_9A47A10B07FE">allow trusted domains</checkBox>
4156 </presentation>
4160 </textBox>
4161 </presentation>
4165 </textBox>
4166 </presentation>
4171 </textBox>
4172 </presentation>
4175 </presentation>
4177 <checkBox defaultChecked="true" refId="CHK_B6DB6C5E_8C6F_5288_B469_0C54B947EA2F">client NTLMv2 auth</checkBox>
4178 </presentation>
4181 </presentation>
4186 </textBox>
4187 </presentation>
4192 </textBox>
4193 </presentation>
4195 <checkBox refId="CHK_E5D1CBBE_5B07_5559_8885_E8F6DBA75A18">client use spnego principal</checkBox>
4196 </presentation>
4199 </presentation>
4203 </textBox>
4204 </presentation>
4206 <checkBox defaultChecked="true" refId="CHK_EC390E59_1CA4_5C42_960E_B0EEA3B0C1F4">encrypt passwords</checkBox>
4207 </presentation>
4212 </textBox>
4213 </presentation>
4218 </textBox>
4219 </presentation>
4224 </textBox>
4225 </presentation>
4228 </presentation>
4231 </presentation>
4234 </presentation>
4238 </textBox>
4239 </presentation>
4244 </textBox>
4245 </presentation>
4249 </textBox>
4250 </presentation>
4255 </textBox>
4256 </presentation>
4260 </textBox>
4261 </presentation>
4264 </presentation>
4267 </presentation>
4270 </presentation>
4273 </presentation>
4278 </textBox>
4279 </presentation>
4282 </presentation>
4287 </textBox>
4288 </presentation>
4291 </presentation>
4294 </presentation>
4298 </textBox>
4299 </presentation>
4303 </textBox>
4304 </presentation>
4308 </textBox>
4309 </presentation>
4314 </textBox>
4315 </presentation>
4319 </textBox>
4320 </presentation>
4324 </textBox>
4325 </presentation>
4328 </presentation>
4332 </textBox>
4333 </presentation>
4336 </presentation>
4340 </textBox>
4341 </presentation>
4346 </textBox>
4347 </presentation>
4352 </textBox>
4353 </presentation>
4358 </textBox>
4359 </presentation>
4364 </textBox>
4365 </presentation>
4370 </textBox>
4371 </presentation>
4375 </textBox>
4376 </presentation>
4381 </textBox>
4382 </presentation>
4387 </textBox>
4388 </presentation>
4392 </textBox>
4393 </presentation>
4397 </textBox>
4398 </presentation>
4400 <checkBox defaultChecked="true" refId="CHK_FBD1856B_6C06_5CF4_9A53_DDF372A2250F">tls enabled</checkBox>
4401 </presentation>
4406 </textBox>
4407 </presentation>
4412 </textBox>
4413 </presentation>
4416 </presentation>
4419 </presentation>
4423 </textBox>
4424 </presentation>
4427 </presentation>
4431 </textBox>
4432 </presentation>
4437 </textBox>
4438 </presentation>
4441 </presentation>
4444 </presentation>
4446 <checkBox defaultChecked="true" refId="CHK_18CC19EE_D0BD_5776_9816_F100799183AB">getwd cache</checkBox>
4447 </presentation>
4450 </presentation>
4453 </presentation>
4456 </presentation>
4459 </presentation>
4462 </presentation>
4465 </presentation>
4470 </textBox>
4471 </presentation>
4473 <checkBox defaultChecked="true" refId="CHK_AE0F9277_9994_5245_9AF5_2FE2694EADB3">use mmap</checkBox>
4474 </presentation>
4478 </textBox>
4479 </presentation>
4481 <checkBox defaultChecked="true" refId="CHK_D8B6A576_57BD_5C1B_8503_D7514BF9A79A">host msdfs</checkBox>
4482 </presentation>
4486 </textBox>
4487 </presentation>
4490 </presentation>
4492 <checkBox defaultChecked="true" refId="CHK_4D19E247_9D41_57FC_A81B_7AAA3DA70D22">create krb5 conf</checkBox>
4493 </presentation>
4498 </textBox>
4499 </presentation>
4502 </presentation>
4506 </textBox>
4507 </presentation>
4510 </presentation>
4514 </textBox>
4515 </presentation>
4517 <checkBox defaultChecked="true" refId="CHK_09A137C2_9429_5D4A_A327_A5F475E367AE">include system krb5 conf</checkBox>
4518 </presentation>
4521 </presentation>
4524 </presentation>
4526 <checkBox defaultChecked="true" refId="CHK_C103A13B_7017_50F6_A337_C2A90DAE4419">require strong key</checkBox>
4527 </presentation>
4532 </textBox>
4533 </presentation>
4538 </textBox>
4539 </presentation>
4542 </presentation>
4546 </textBox>
4547 </presentation>
4550 </presentation>
4553 </presentation>
4556 </presentation>
4560 </textBox>
4561 </presentation>
4564 </presentation>
4567 </presentation>
4569 <checkBox defaultChecked="true" refId="CHK_EE309E41_F404_5CE1_AC86_5E795D0C979A">winbind nested groups</checkBox>
4570 </presentation>
4573 </presentation>
4578 </textBox>
4579 </presentation>
4582 </presentation>
4585 </presentation>
4588 </presentation>
4591 </presentation>
4594 </presentation>
4596 <checkBox defaultChecked="true" refId="CHK_3CAC88EA_556D_5AA8_8A29_282B574B2743">winbind scan trusted domains</checkBox>
4597 </presentation>
4599 <checkBox defaultChecked="true" refId="CHK_E93252A7_06C7_566B_B7E6_8D4D7AADFB8D">winbind sealed pipes</checkBox>
4600 </presentation>
4605 </textBox>
4606 </presentation>
4608 <checkBox refId="CHK_BF4DA096_841C_5A0D_A5E3_CD564122C924">winbind use default domain</checkBox>
4609 </presentation>
4611 <checkBox refId="CHK_7E9390CD_05D9_570F_A761_7B5A605BA1F9">winbind use krb5 enterprise principals</checkBox>
4612 </presentation>
4614 <checkBox defaultChecked="true" refId="CHK_243E92BD_CBA1_50BC_BD4D_87B750B6FABB">dns proxy</checkBox>
4615 </presentation>
4618 </presentation>
4621 </presentation>
4626 </textBox>
4627 </presentation>
4632 </textBox>
4633 </presentation>
4638 </textBox>
4639 </presentation>
4643 </textBox>
4644 </presentation>
4649 </textBox>
4650 </presentation>
4654 </textBox>
4655 </presentation>
4658 </presentation>
4662 </textBox>
4663 </presentation>
4666 </presentation>
4671 </textBox>
4672 </presentation>
4677 </textBox>
4678 </presentation>
4682 </textBox>
4683 </presentation>
4688 </textBox>
4689 </presentation>
4694 </textBox>
4695 </presentation>
4700 </textBox>
4701 </presentation>
4706 </textBox>
4707 </presentation>
4711 </textBox>
4712 </presentation>
4717 </textBox>
4718 </presentation>
4721 </presentation>
4726 </textBox>
4727 </presentation>
4728 </presentationTable>
4729 </resources>
4730 </policyDefinitionResources>