This is the same as user-level security, except that the Samba server uses a separate SMB server to validate users and their passwords before granting access to the share. Once authenticated, the user is given a special token that allows him or her access to any share with appropriate access rights. With this token, the PDC will not have to revalidate the user's password each time he or she attempts to access another share within the domain. Each of these security policies can be implemented with the global security option, as shown in Table 6.3 . This differs from the other modes of security in that there are no restrictions as to whom can access a share, as long as that individual knows the correct password.
Shares often have multiple passwords.
Security is maintained as long as unauthorized users do not discover the password for a share to which they shouldn't have access. This will bring up the Resource Properties dialog box. Select the Sharing tab at the top of the dialog box and enable the resource as Shared As. You might be thinking that this security model is not a good fit for Samba - and you would be right. For other shares, Samba appends the username to a list of users who are allowed access to the share.