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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Communications Remarks<br />

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

S 5.82 Secure Use of SAMBA<br />

Initiation responsibility: Head of <strong>IT</strong> Section, Administrator<br />

Implementation responsibility: Administrator<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 />

If SAMBA is in use within the agency/company, the recommendations set out<br />

below should be considered.<br />

Programming errors which sometimes can induce security loopholes have<br />

been discovered in older versions of SAMBA. An up-to-date version should<br />

be used, in which as far as possible all known security-relevant errors have<br />

been eliminated.<br />

Using the file smb.conf, it is possible to configure the SAMBA server in an<br />

extremely flexible and detailed manner. However, this also makes the system<br />

somewhat complex. Before using SAMBA, it is therefore important to read<br />

the documentation thoroughly. <strong>The</strong> configuration should be carefully planned,<br />

documented and implemented through appropriate parameter settings in file<br />

smb.conf. For example, a long description of the various parameters can be<br />

viewed by entering the command man smb.conf. In the event that<br />

configuration settings are altered, checks should be performed using the<br />

documentation and appropriate tests to ensure that the change in configuration<br />

does not result in unwanted side-effects.<br />

<strong>The</strong> following parameters are particularly problematic in terms of the possible<br />

security risks associated with them. <strong>The</strong>y should therefore only be used after<br />

checking thoroughly all the possible effects on the <strong>IT</strong> security of the server.<br />

[...] command<br />

add user script<br />

delete user script<br />

fake oplocks<br />

ldap [...]<br />

panic action<br />

passwd program<br />

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

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

postexec<br />

preexec / exec<br />

root postexec<br />

root preexec<br />

smbrun<br />

unix password sync<br />

With the testparm program it is possible to check whether the settings in file<br />

smb.conf are permitted. Of course it is not possible using that program to draw<br />

any conclusions as to whether the settings do have the desired effect or<br />

security-relevant effects. Creation and maintenance of the smb.conf file can<br />

also be supported by graphical user interfaces, for example using the Samba

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

Saved successfully!

Ooh no, something went wrong!