Changeset View
Changeset View
Standalone View
Standalone View
documentation/content/en/books/arch-handbook/jail/_index.adoc
Context not available. | |||||
:icons: font | :icons: font | ||||
:sectnums: | :sectnums: | ||||
:sectnumlevels: 6 | :sectnumlevels: 6 | ||||
:sectnumoffset: 4 | |||||
:partnums: | |||||
:source-highlighter: rouge | :source-highlighter: rouge | ||||
:experimental: | :experimental: | ||||
:skip-front-matter: | :images-path: books/arch-handbook/ | ||||
:xrefstyle: basic | |||||
:relfileprefix: ../ | |||||
:outfilesuffix: | |||||
:sectnumoffset: 4 | |||||
include::shared/mirrors.adoc[] | ifdef::env-beastie[] | ||||
ifdef::backend-html5[] | |||||
:imagesdir: ../../../../images/{images-path} | |||||
endif::[] | |||||
ifndef::book[] | |||||
include::shared/authors.adoc[] | include::shared/authors.adoc[] | ||||
include::shared/mirrors.adoc[] | |||||
include::shared/releases.adoc[] | include::shared/releases.adoc[] | ||||
include::shared/en/mailing-lists.adoc[] | include::shared/attributes/attributes-{{% lang %}}.adoc[] | ||||
include::shared/en/teams.adoc[] | include::shared/{{% lang %}}/teams.adoc[] | ||||
include::shared/en/urls.adoc[] | include::shared/{{% lang %}}/mailing-lists.adoc[] | ||||
include::shared/{{% lang %}}/urls.adoc[] | |||||
toc::[] | |||||
endif::[] | |||||
ifdef::backend-pdf,backend-epub3[] | |||||
include::../../../../../shared/asciidoctor.adoc[] | |||||
endif::[] | |||||
endif::[] | |||||
ifndef::env-beastie[] | |||||
toc::[] | toc::[] | ||||
include::../../../../../shared/asciidoctor.adoc[] | |||||
endif::[] | |||||
On most UNIX(R) systems, `root` has omnipotent power. This promotes insecurity. If an attacker gained `root` on a system, he would have every function at his fingertips. In FreeBSD there are sysctls which dilute the power of `root`, in order to minimize the damage caused by an attacker. Specifically, one of these functions is called `secure levels`. Similarly, another function which is present from FreeBSD 4.0 and onward, is a utility called man:jail[8]. Jail chroots an environment and sets certain restrictions on processes which are forked within the jail. For example, a jailed process cannot affect processes outside the jail, utilize certain system calls, or inflict any damage on the host environment. | On most UNIX(R) systems, `root` has omnipotent power. This promotes insecurity. If an attacker gained `root` on a system, he would have every function at his fingertips. In FreeBSD there are sysctls which dilute the power of `root`, in order to minimize the damage caused by an attacker. Specifically, one of these functions is called `secure levels`. Similarly, another function which is present from FreeBSD 4.0 and onward, is a utility called man:jail[8]. Jail chroots an environment and sets certain restrictions on processes which are forked within the jail. For example, a jailed process cannot affect processes outside the jail, utilize certain system calls, or inflict any damage on the host environment. | ||||
Jail is becoming the new security model. People are running potentially vulnerable servers such as Apache, BIND, and sendmail within jails, so that if an attacker gains `root` within the jail, it is only an annoyance, and not a devastation. This article mainly focuses on the internals (source code) of jail. For information on how to set up a jail see the link:{handbook}#jails/[handbook entry on jails]. | Jail is becoming the new security model. People are running potentially vulnerable servers such as Apache, BIND, and sendmail within jails, so that if an attacker gains `root` within the jail, it is only an annoyance, and not a devastation. This article mainly focuses on the internals (source code) of jail. For information on how to set up a jail see the extref:{handbook}[handbook entry on jails, jails]. | ||||
[[jail-arch]] | [[jail-arch]] | ||||
== Architecture | == Architecture | ||||
Context not available. |