Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Jun 1999 19:19:28 -0400
From:      Tom Embt <tom@embt.com>
To:        mwlucas@exceptionet.com
Cc:        freebsd-stable@freebsd.org
Subject:   Re: ftpd: some clients can list, some cannot
Message-ID:  <3.0.3.32.19990624191928.00aab0cc@mail.embt.com>
In-Reply-To: <199906242207.SAA09263@easeway.com>

next in thread | previous in thread | raw e-mail | index | archive | help
At 06:07 PM 6/24/99 -0400, you wrote:
>Hello,
>
>I have a strange problem with a 3.2-stable ftpd, cvsuped last Monday.
>
>I've compiled ftpd with INTERNAL_LS=true.  When a user is listed in
>/etc/ftpchroot, they may or may not be able to list the contents of their
>home directory.
>
>The -stable and -current FreeBSD client cannot list the directory.
>
>wsftp cannot list the directory.
>
>Oddly, OSF1 can, in particular (from uname -a):
>
>OSF1 saturn2.acs.oakland.edu V3.2 148 alpha
>
>Now, I want the user to be able to list their home directory, but not get
>out of it.  Obviously, there's something I'm missing that would generate
>consistent results.  Any advice would be appreciated.
>
>Thanks,
>==ml

Lately anytime I open my mouth on a mailing list it is in error, so take
this with a grain of salt...

AFAIK, there are five files which are "supposed" to be available in a
chrooted environment.

/bin/ls
/bin/date
/etc/group
/etc/pwd.db
/etc/passwd

Compiling with INTERNAL_LS took care of the first one, but it is possible
that some clients need some/all of the other files.

If you're interested I can describe the layout of hardlinks and symlinks I
use to make these files available.  There's a good chance it's not the
Right Way(tm) to do it, but it has worked for me.



Tom Embt
tom@embt.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19990624191928.00aab0cc>