19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Threats Catalogue Deliberate Acts Remarks<br />

____________________________________________________________________ .........................................<br />

T 2.65 Complexity of the SAMBA Configuration<br />

SAMBA is a freeware software package for UNIX operating systems which,<br />

amongst other things, provides file, print and authentication services over the<br />

Server Message Block (SMB) and Common Internet File System (CIFS)<br />

protocols. <strong>The</strong> most important examples of SMB/CIFS clients are definitely<br />

the operating systems in the Microsoft Windows family. With SAMBA it is<br />

possible, for example, for Windows 9x or Windows NT computers to access<br />

shared files on a UNIX server directly. This obviates the need to take a detour<br />

over the FTP or NFS protocols or to install additional software on the client.<br />

In the current version, SAMBA simulates a whole range of Windows NT<br />

server functions so that in many cases it is possible to use a UNIX system with<br />

SAMBA in lieu of such a server.<br />

On the server side, most of the SAMBA configuration settings are defined in<br />

the file smb.conf; in particular, the shared directories and printers are entered<br />

here together with various settings relating to authentication. A whole range of<br />

parameters are available for this purpose. <strong>The</strong>se are set in the individual<br />

sections of file smb.conf. A given function of the SAMBA server is generally<br />

controlled via a combination of several parameters. Depending on the<br />

particular instance, the interaction of these parameters can be very complex,<br />

so that there is a danger that the Administrator could incorrectly interpret the<br />

effect of a particular parameter combination. In particular, there is a danger<br />

that if one parameter is modified this could have unnoticed side-effects that<br />

compromised the security of the server.<br />

<strong>The</strong> problem described above is aggravated during configuration of directory<br />

and file permissions. Here it is necessary to consider not only the settings<br />

contained in file smb.conf, but also the access rights to the (UNIX) file system<br />

on which the directories and files are held. <strong>The</strong> actual rights which are valid<br />

for the user during access via SAMBA can be influenced by file smb.conf in<br />

two different ways. Firstly, it is possible to specify direct access restrictions<br />

for the individual shares of a SAMBA server (e.g. via the parameter valid<br />

users). Secondly, file smb.conf contains parameters (e.g. force user) by means<br />

of which it is possible to configure how directory- and file-based access<br />

restrictions affect a user's current access rights. It is easy to make a mistake in<br />

the configuration, with the result that users are given excessively wide access<br />

rights to directories and/or files.<br />

Example:<br />

<strong>The</strong> Administrator of a SAMBA server assigns directory- and file-based<br />

access rights to the local file system of the server. This entails setting<br />

appropriate permissions and ownerships for all the shared areas. However, file<br />

smb.conf contains the line<br />

force user = root<br />

. This means that the file system is accessed under the "root" user account,<br />

irrespective of which user has logged on to the server. <strong>The</strong> result is that<br />

virtually all the directory-and file-based access restrictions are ignored.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Unnoticed side-effects<br />

Directory and file access<br />

permissions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!