Browsing Estonian translation

61.

<emphasis>security = ADS:</emphasis> allows the <application>Samba</application> server to join an <trademark class="registered">Active Directory</trademark> domain as a native member. See <xref linkend="samba-ad-integration"/> for details.

62.

<emphasis>security = server:</emphasis> this mode is left over from before <application>Samba</application> could become a member server, and, due to some security issues, should not be used. See the <ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/ServerType. html#id349531">Server Security</ulink> section of the <application>Samba</application> guide for more details.

64.

The preferred security mode depends on the environment and what the <application>Samba</application> server needs to accomplish.

66.

This section will reconfigure the <application>Samba</application> file and print server, from <xref linkend="samba-fileserver"/> and the <ulink type="help" url="help:/kubuntu/printing/"> Print Server</ulink>, to require authentication.

67.

First, install the <application>libpam-smbpass</application> package, which will sync the system users to the <application>Samba</application> user database:

69.

If the <emphasis><application>Samba</application> Server</emphasis> task was chosen during installation, <application>libpam-smbpass</application> is already installed.

72.

Finally, restart <application>Samba</application> for the new settings to take effect:

74.

To map a network drive to the share, <quote>Reconnect at Logon</quote> should be checked, which will require the username and password to be entered just once &mdash; at least until the password changes.

76.

There are several options available to increase the security for each shared directory. Using the <emphasis>[share]</emphasis> example, this section will cover some common options.

78.

Groups define a collection of computers or users who have a common level of access to particular network resources and offer a level of granularity in controlling access to such resources. For example, if a group <emphasis role="italic">qa</emphasis> is defined and contains the users <emphasis role="italic">freda</emphasis>, <emphasis role="italic">danika</emphasis>, and <emphasis role="italic">rob</emphasis>, and a second group <emphasis role="italic">support</emphasis> is defined and consists of users <emphasis role="italic">danika</emphasis>, <emphasis role="italic">jeremy</emphasis>, and <emphasis role="italic">vincent</emphasis>, then certain network resources configured to allow access by the <emphasis role="italic">qa</emphasis> group will subsequently enable access by freda, danika, and rob, but not jeremy or vincent. Since the user <emphasis role="italic">danika</emphasis> belongs to both the <emphasis role="italic">qa</emphasis> and <emphasis role="italic">support</emphasis> groups, she will be able to access resources configured for access by both groups, whereas all other users will have only access to resources explicitly allowing the group they are part of.