Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


Why a chrooted bind need to mknod dev/null and dev/random ?

Howto say it's necessary but without explain reasons, I administrate chrooted bind servers without theses options, and all seems to work perfectly ...

Thanks for your answers.

share|improve this question
up vote 1 down vote accepted

Many programs and libraries open /dev/null, /dev/zero, or /dev/random. If whatever you're running in the chrooted jail needs those pseudo-devices, they need to be present inside the jail. If they are not included, an application may work for a while and then die (when the pseudo device open fails).

You can check your binaries (including dynamic libraries) and see if the devices are mentioned. From a security standpoint, it's difficult to see any negative implications from /dev/null or /dev/zero. If I was being paranoid, or doing covert channel analysis (not that there's that much difference), I'd want to look at the specific implementation of /dev/random.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.