---------------------------------------------------------------------------
# lidsconf - A - o /home/httpd - j DENY
# lidsconf - A - s /usr/sbin/httpd - o /home/httpd - j READONLY
---------------------------------------------------------------------------
A simple disposition example:
---------------------------------------------------------------------------
lidsconf - Z
lidsconf - A - o /boot - j READONLY
lidsconf - A - o /lib - j READONLY
lidsconf - A - o /root - j READONLY
lidsconf - A - o /etc - j READONLY
lidsconf - A - o /sbin - j READONLY
lidsconf - A - o /usr/sbin - j READONLY
lidsconf - A - o /bin - j READONLY
lidsconf - A - o /usr/bin - j READONLY
lidsconf - A - o /usr/lib - j READONLY
---------------------------------------------------------------------------
2. disposes the LIDS protection advancement
a. cannot be killed advancement
LIDS can protect the father advancement is init(pid=1) advancement, disposes inside /etc/lids/lids.cap according to the following order the performance:
-29:CAP_INIT_KILL
b. hideaway advancement
These advancements do not look, orders with ps or also does not look inside /proc.
---------------------------------------------------------------------------
Example:
lidsconf - A - s /usr/sbin/httpd - o CAP_HIDDEN - j GRANT
---------------------------------------------------------------------------
3. protects through the establishment jurisdiction
Here jurisdiction is you give an advancement the jurisdiction. A root advancement has all performance, but also has binding the jurisdiction question. In general essence, when removes one jurisdiction from the binding centralism, only if restarts anybody not to be able to begin using this jurisdiction. The LIDS revision jurisdiction enables the user to be possible to cut willfully among these jurisdictions. Is captured visit to /proc/sys/kernel/cap_bset, initiation safe warning.
System's jurisdiction value saves in /etc/lids/lids.cap. Edits it to be possible to meet your need.
For example:
If the CAP_SYS_RAWIO item opens, we may allow to visit /dev/port,/dev/mem,/dev/kmem, as well as to primitive block equipment (/dev/[sh]d?? ) visit.
When we cancel this jurisdiction, may enable the movement to visit the primitive block equipment on system's all advancements, for instance moves lilo. But, some advancement's movement needs these jurisdictions, for instance XF86_SVGA.
For instance, CAP_NET_ADMIN, this jurisdiction may obtain the following ability again: The connection disposition, the IP firewall, camouflage and the cost management, establishes the sockets debugging option, the revision routing list, the establishment random advancement or the advancement group to the sockets property rights, ties up the address for the transparent proxy proxy, the establishment service type, the establishment mix pattern, broadcasts, assigns the register to the equipment to carry on the read-write and so on. Stemming from the security concern, we must cancel this jurisdiction, permissible variation network settings, also has forbidden the firewall rule change.
Other pages: : <<Prev * 1 * 2 * 3 * 4 * 5 * 6 * 7 * 8 * 9 * 10 * 11 * 12 * 13 * 14 * Next>>
|