07.06.2014 Views

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

a desktop machine is far from being as critical as one on a DNS server. Another interesting directive<br />

allows storing the mappings between IP addresses and MAC addresses (these uniquely<br />

identify a network card), so as to allow detecting ARP spoofing attacks by which a compromised<br />

machine attempts to masquerade as another such as a sensitive server.<br />

CAUTION<br />

Range of action<br />

The effectiveness of snort is limited by the traffic seen on the monitored network<br />

interface. It will obviously not be able to detect anything if it cannot<br />

observe the real traffic. When plugged into a network switch, it will therefore<br />

only monitor aacks targeting the machine it runs on, which is probably<br />

not the intention. The machine hosting snort should therefore be plugged<br />

into the “mirror” port of the switch, which is usually dedicated to chaining<br />

switches and therefore gets all the traffic.<br />

On a small network based around a network hub, there is no such problem,<br />

since all machines get all the traffic.<br />

14.4. Introduction to SELinux<br />

14.4.1. Principles<br />

SELinux (Security Enhanced Linux) is a Mandatory Access Control system built on Linux's LSM (Linux<br />

Security Modules interface. In practice, the kernel queries SELinux before each system call to<br />

know whether the process is authorized to do the given operation.<br />

SELinux uses a set of rules — collectively known as a policy — to authorize or forbid operations.<br />

Those rules are difficult to create. Fortunately, two standard policies (targeted and strict) are<br />

provided to avoid the bulk of the configuration work.<br />

With SELinux, the management of rights is completely different from traditional Unix systems.<br />

The rights of a process depend on its security context. The context is defined by the identity of<br />

the user who started the process, the role and the domain that the user carried at that time. The<br />

rights really depend on the domain, but the transitions between domains are controlled by the<br />

roles. Finally, the possible transitions between roles depend on the identity.<br />

388 The Debian Administrator's Handbook

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

Saved successfully!

Ooh no, something went wrong!