Date: Thu, 25 Jul 2002 23:10:29 +0200 From: lupe@lupe-christoph.de (Lupe Christoph) To: "Travis L. Leuthauser" <travis@bbipmail.com> Cc: freebsd-security@freebsd.org Subject: Re: Openssh-portable Message-ID: <20020725211029.GB18063@lupe-christoph.de> In-Reply-To: <NEBBIGMCEDGDNFGOAAFLKEFLKGAA.travis@bbipmail.com> References: <20020725145327.A404@melusine.cuivre.fr.eu.org> <NEBBIGMCEDGDNFGOAAFLKEFLKGAA.travis@bbipmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 2002-07-25 at 07:58:31 -0500, Travis L. Leuthauser wrote: > As I understand, this is a known problem with openssh-portable when using > privsep. Apparently after initiating privsep, sshd attempts to read > /etc/resolv.conf, which it can't since chrooted to /var/empty. A workaround > is to copy resolv.conf into /var/empty/etc. The only problem w/ this is > that /var/empty is intented to be empty. If there is no (chroot)/etc/resolv.conf, the resolver will try 127.0.0.1. So if you run a local named, this will work. HTH, Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | I have challenged the entire ISO-9000 quality assurance team to a | | Bat-Leth contest on the holodeck. They will not concern us again. | | http://public.logica.com/~stepneys/joke/klingon.htm | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020725211029.GB18063>