Re: Openssh-portable
From: Lupe Christoph (lupe@lupe-christoph.de)
Date: 07/25/02
- Next message: Robert S. Wojciechowski Jr.: "RE: Openssh-portable"
- Previous message: Chris McCluskey: "Static built files and resolv issue"
- In reply to: Travis L. Leuthauser: "RE: Openssh-portable"
- Next in thread: Darren Pilgrim: "Re: Openssh-portable"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 25 Jul 2002 23:10:29 +0200 To: "Travis L. Leuthauser" <travis@bbipmail.com> From: lupe@lupe-christoph.de (Lupe Christoph)
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
- Next message: Robert S. Wojciechowski Jr.: "RE: Openssh-portable"
- Previous message: Chris McCluskey: "Static built files and resolv issue"
- In reply to: Travis L. Leuthauser: "RE: Openssh-portable"
- Next in thread: Darren Pilgrim: "Re: Openssh-portable"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]