What's needed in a chrooted environment to create a socket

[ReD-BaRoN]

Having this problem with dhcpd when it tries to start, and looking at the dhcpd source, it seems to be a socket creation problem.

For example, when dhcpd trys to do:

[moocha]

I suspect that's intentional behavior, to avoid breaking restrictions in a jailed environment. Grsecurity for example has something related to this.
You might want to take a look at Linux Capabilities:

[Hackeron]

To tell you the truth, I'm not 100% aware of what happened on the low level. It is really as easy as USE="chroot" emerge dhcpd, from there it was self explanatory for me.

Here are all files in /chroot/dhcpd:

./dev
./etc
./etc/dhcp
./etc/dhcp/dhclient-script.sample
./etc/dhcp/dhcpd.conf.sample
./etc/dhcp/dhcpd.conf
./etc/dhcp/dhclient.conf.sample
./var
./var/lib
./var/lib/dhcp
./var/lib/dhcp/.keep
./var/lib/dhcp/dhcpd.leases~
./var/lib/dhcp/dhcpd.leases
./var/run
./var/run/dhcp
./var/run/dhcp/dhcpd.pid
./var/state
./var/state/dhcp
./var/state/dhcp/dhcpd.leases

So as you can see, nothing in ./dev, and this was all auto created by clever gentoo.

And
8316 dhcp 19 0 2728 1532 1960 S 0.0 0.2 0:00.03 dhcpd --- notice that dhcpd is infact running as the dhcp user NOT as root!.

So koodos to gentoo for keeping my system as secure as possible


Any other info you would like to know from me? -- I cant tell you exactly what I did, I didnt really pay attention, it was just all extremely easy and portage did all the work...