On Tue, Jun 13, 2006 at 10:24:16AM +0200, Chris Osicki wrote: > The main problem is that once the chroot() is executed you don't get > anything in the logs, unless you do some acrobatics with your > favorite syslog. I suggested some time ago a simple change to solve > this problem which was silently ignored.
The call to start logging is done after root privileges are dropped to avoid the possibility of a root compromize in the case of a bug in the logging module. Just such a bug was found (and has long since been fixed), but a root compromize was averted due to that decision having been made. It's gonna stay that way for exactly that reason. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0x81CFE75D
pgp7d2C0poAPr.pgp
Description: PGP signature
_______________________________________________ rssh-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rssh-discuss
