Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
This video is a continuation of another video on the Samba server. In that video we briefly described the default version of the Samba configuration file, etc slash samba slash smb dot conf through the default home share. Continuing on in the Samba configuration file, what comes next is the default printer share, and the default printer stanza includes an error. There is no usr slash spool slash samba directory. You should change that to var slash spool slash samba, otherwise printers you configure through this server won't print, and that's not good. Note how browseable is set to no. But remember, we saw shared printers with the smbclient dash L local host command in the previous video. That was made possible due to the printcap name directive, which shares printers listed in the etc slash printcap configuration file. As it's a global directive, it overrides settings in the printer share. Now, look at some of the stanzas that follow. Note the comment characters. There are two different comment characters. This one here, the hash mark, sometimes also known as the pound sign, or the number sign, and the semi-colon. If the semi-colon is removed from the stanza, this activates the tmp directory as defined by this path as a global share accessible tool and writable by all users. Let's say I wanted to configure this stanza with these kinds of permissions on another directory. I get a hint here because the tmp diretory has full read slash write slash execute permissions, and the sticky bit, all set on that directory, which corresponds to writability by all users, so to configure the same sort of permissions on a new directory, say, the test directory, I'd have to set the sticky bit in full read slash write slash execute permissions for all users. And note the result here. We have the same permissions as well as the same sticky bit, set for both the tmp and test directories. You also need to know how to limit access to shared directories in Samba. The stanza which follows assumes that write access is limited to members of the staff group. The "at" sign means that Samba looks for staff in the local etc slash group configuration file, so while this means the home slash samba directory is readable by all, it's only writable by those users who are listed as members of the staff directory in etc slash group, and also happen to have passwords in the Samba password database, which we discussed in a previous video. Let's jump down a bit to a share associated with user Fred. Specifically, as commented, access to Fred's service is limited to the user name Fred, and at the end of the file there's a similar share stanza available. It's a slightly different directory, but access is limited to users Mary and Fred. You can also limit access by IP address, host name, or domain name. For example, the following directive, this hostallow directive, limits access first to the local host system, which corresponds to the 127 dot IPv4 address, you can substitute a local host for that address. The ten dot address, which corresponds to the 10 dot 0 dot 0 dot 0 NETwork address, and all systems on the example dot net domain. For example, ns dot example dot net would have access to this particular share. When I share with Samba, I start with the template available from the default Samba configuration file, and now you should be able to do so as well. Yes, there's more security for Samba related to Firewalls and SELinux, and we'll discuss that in another video.
| Course: | Red Hat Certified Engineer |
| Author: | Michael Jang |
| SKU: | 33845 |
| ISBN: | 1-934743-47-X |
| Release Date: | 2008-01-18 |
| Duration: | 6.5 hrs / 94 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |