dgamelaunch binary should not be in chroot

[leaf-node]

according to the following site, placing a wrapper program that starts as root, chroots, and then drops privileges should not be placed in the chrooted directory:

http://unixwiz.net/techtips/chroot-practices.html

Limit non-jail running of jailed binaries For systems that do not have a command-line option for running chroot, the only alternative is to create a wrapper program. This wrapper will perform the key chroot operation, give up root permission, and then execute the jailed binary. The wrapper must be run as root (only chroot can perform this operation), but the wrapper itself must not be found in the jail. Otherwise an intruder could quietly compromise the wrapper, and the next time the system is launched, the intruder's program would be run as root in a non-jailed environment. This is complete compromise.

I tried moving the dgamelaunch binary and its symlink out of the chroot environment, into the parent folder, and it still works.

I wonder whether having the banner files, etc. in the chroot dir could pose a potential risk as well. I think that maybe it's not as big of a deal, if those files are only read by the program once root privileges have been dropped.

[leaf-node]

also, i forgot to mention that the dgamelaunch.conf file probably shouldn't be in there, since it specifies the directory to chroot into.

[leaf-node]

Actually, with some more testing, I see that the dgamelaunch program, as it currently is built, is needed in the chrooted directory, in order to watch games.

Maybe it could be split into the chrooting wrapper, and the part that is not run as root?

or dgamelaunch could be buit to not chroot at all, and leave the chrooting up to xinetd.