That user is able to control the access permissions of that file in terms of whether other users on the system are able to read and write to or, in the case of a script or binary, execute the file.
Consider, for example, a file located in the home directory of, and owned by, a particular user. Traditionally, Linux security has been based on the concept of allowing users to decide who has access to their files and other resources for which they have ownership. SELinux is a system integrated by default into the Linux kernel on all RHEL 8 systems and which provides an extra layer of security and protection to the operating system and user files. The “netbios name” property specifies the name by which the server will be visible to other systems on the network, while the log settings simply specify a file location into which log output is to be recorded. Before moving on to configuring the resources to be shared, a number of other parameters also need to be added to the section as follows: In addition to the workgroup setting, the other settings indicate that this is a standalone server on which the shared resources will be protected by user passwords.
For example, if the workgroup is named WORKGROUP (the default for most Windows networks): This is controlled via the workgroup = directive of the section which by default is configured as follows: workgroup = SAMBAīegin by changing this to the actual name of the workgroup.
The first task is to define the name of the Windows workgroup on which the RHEL 8 resources are to be shared. While these settings are global, each option may be overridden within other sections of the configuration file. The first section is the section where settings can be specified that apply to the entire Samba configuration. The smb.conf file is divided into sections. The first step in configuring Samba is to edit the /etc/samba/smb.conf file. More advanced configurations such as integrating Samba within an Active Directory environment are also available, though these are outside the scope of this book. This is a configuration known as a standalone Samba server. In reality, however, many of the configuration options are not needed by the typical installation, and the learning curve to set up a basic configuration is actually quite short.įor the purposes of this chapter we will look at joining a RHEL 8 system to a Windows workgroup and setting up a directory as a shared resource that can be accessed by a specific user. This flexibility can lead to the sense that Samba is overly complex to work with. Samba is a highly flexible and configurable system that provides many different options for controlling how resources are shared on Windows networks. In practice, much more can be achieved by taking the time to understand the intricacies of the smb.conf file. While the loss of system-config-samba may be mourned by those who relied on it, the tool’s simplicity actually masked many of the more advanced features of Samba. In this chapter we will look at the steps necessary to share file system resources and printers on a RHEL 8 system with remote Windows and Linux systems, and to access Windows resources from RHEL 8. In addition to providing integration between Linux and Windows systems, Samba may also be used to provide folder sharing between Linux systems (as an alternative to NFS which was covered in the previous chapter). This is achieved using technology called Samba. In order for a RHEL 8 system to serve such resources over a network to a Windows system and vice versa it must, therefore, support SMB. Windows systems share resources such as file systems and printers using a protocol known as SMB). Similarly, shared folders and printers residing on Windows systems may also need to be accessible from RHEL 8 based systems. It is a common requirement, therefore, that files on a RHEL 8 system be accessible to Linux, UNIX and Windows-based systems over network connections. It is also extremely common for RHEL and Windows systems to be used side by side in networked environments. It is not surprising therefore that RHEL 8 has the ability to act as a file server. Red Hat Enterprise Linux 8 Essentials Print and eBook (ePub/PDF/Kindle) editions contain 31 chapters and over 250 pagesĪlthough Linux has made some inroads into the desktop market, its origins and future are very much server-based.
Purchase a full copy of Red Hat Enterprise Linux 8 (RHEL 8) Essentials in eBook ($9.99) or Print ($36.99) format You are reading a sample chapter from the Red Hat Enterprise Linux 8 (RHEL 8) Essentials book.