Had dhcpd running chrooted on "normal" gentoo. Changed to hardened toolchain, and now dhcpd does not run chrooted. If I try to run chrooted I get the following on the log: dhcpd: unable to create icmp socket: Operation not permitted dhcpd: Wrote 0 deleted host decls to leases file. dhcpd: Wrote 0 new dynamic host decls to leases file. dhcpd: Wrote 0 leases to leases file. dhcpd: Open a socket for LPF: Operation not permitted dhcpd: exiting. It runs fine on hardened if not chrooted. Reproducible: Always Portage 2.1.3.19 (hardened/x86/2.6, gcc-3.4.6, glibc-2.6.1-r0, 2.6.23-hardened-r4 i686) ================================================================= System uname: 2.6.23-hardened-r4 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz Timestamp of tree: Sun, 13 Jan 2008 02:00:01 +0000 app-shells/bash: 3.2_p17-r1 dev-lang/python: 2.4.4-r6 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.10-r5 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.61-r1 sys-devel/automake: 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=pentium4 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US" LC_ALL="en_US" LINGUAS="en pt_PT" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="berkdb cracklib crypt hardened midi nls nptl nptlonly pam pic readline ssl tcpd urandom x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en pt_PT" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #0) > Had dhcpd running chrooted on "normal" gentoo. > > Changed to hardened toolchain, and now dhcpd does not run chrooted. > > If I try to run chrooted I get the following on the log: > dhcpd: unable to create icmp socket: Operation not permitted > dhcpd: Wrote 0 deleted host decls to leases file. > dhcpd: Wrote 0 new dynamic host decls to leases file. > dhcpd: Wrote 0 leases to leases file. > dhcpd: Open a socket for LPF: Operation not permitted > dhcpd: exiting. > > It runs fine on hardened if not chrooted. This doesn't have anything to do with hardened per se. You basically need to disable CONFIG_GRKERNSEC_CHROOT in your kernel config, or maybe CONFIG_GRKERNSEC_SOCKET if you have it enabled.
Just a comment for anyone else who may run into this problem: you can leave the general CHROOT restrictions enabled, simply disable CONFIG_GRKERNSEC_CHROOT_CAPS (you can also use "echo 0 > /proc/sys/kernel/grsecurity/chroot_caps" if you have sysctl enabled for grsecurity). It's a bit annoying that grsecurity doesn't actually say that it denied the access - it's plenty verbose about everything else, after all.
