|
|
39.
|
|
|
<emphasis>browsable:</emphasis> enables <trademark class="registered">Windows</trademark> clients to browse the shared directory using <application>Windows Explorer</application>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:206(para)
|
|
|
41.
|
|
|
<emphasis>read only:</emphasis> determines if the share is read only or if write privileges are granted. Write privileges are allowed only when the value is <emphasis>no</emphasis>, as is seen in this example. If the value is <emphasis>yes</emphasis>, then access to the share is read only.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:219(para)
|
|
|
42.
|
|
|
<emphasis>create mask:</emphasis> determines the permissions new files will have when created.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:195(para)
|
|
|
43.
|
|
|
Now that <application>Samba</application> is configured, the directory needs to be created and the permissions changed. From a terminal, enter:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:203(para)
|
|
|
46.
|
|
|
The <emphasis>-p</emphasis> switch tells <command>mkdir</command> to create the entire directory tree if it doesn't exist. Change the share name to fit the environment.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:212(para)
|
|
|
49.
|
|
|
The above configuration gives all access to any client on the local network. For a more secure configuration, see <xref linkend="samba-fileprint-security"/>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:229(para)
|
|
|
50.
|
|
|
From a <trademark class="registered">Windows</trademark> client, it should now be possible to browse to the <phrase>Kubuntu</phrase> file server and see the shared directory. To check that everything is working, try creating a directory from <trademark class="registered">Windows</trademark>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:278(para)
|
|
|
58.
|
|
|
There are two security levels available to the Common Internet Filesystem (<acronym>CIFS</acronym>) network protocol <emphasis>user-level</emphasis> and <emphasis>share-level</emphasis>. <application>Samba</application>'s <emphasis>security mode</emphasis> implementation allows more flexibility, providing four ways of implementing user-level security and one way to implement share-level:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:327(para)
|
|
|
59.
|
|
|
<emphasis>security = user:</emphasis> requires clients to supply a username and password to connect to shares. <application>Samba</application> user accounts are separate from system accounts, but the <application>libpam-smbpass</application> package will sync system users and passwords with the <application>Samba</application> user database.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:289(para)
|
|
|
60.
|
|
|
<emphasis>security = domain:</emphasis> this mode allows the <application>Samba</application> server to appear to <trademark class="registered">Windows</trademark> clients as a Primary Domain Controller (<acronym>PDC</acronym>), Backup Domain Controller (<acronym>BDC</acronym>), or a Domain Member Server (<acronym>DMS</acronym>). See <xref linkend="samba-dc"/> for further information.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/sharing/C/sharing.xml:347(para)
|
