From owner-freebsd-stable  Thu Jun 24 19:17:43 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from easeway.com (ns1.easeway.com [209.69.39.1])
	by hub.freebsd.org (Postfix) with ESMTP id A42AF14E25
	for <freebsd-stable@freebsd.org>; Thu, 24 Jun 1999 19:17:39 -0700 (PDT)
	(envelope-from mwlucas@easeway.com)
Received: (from mwlucas@localhost)
	by easeway.com (8.8.8/8.8.5) id WAA09671;
	Thu, 24 Jun 1999 22:05:55 -0400 (EDT)
Message-Id: <199906250205.WAA09671@easeway.com>
Subject: Re: ftpd: some clients can list, some cannot
In-Reply-To: <199906250202.TAA19619@kusanagi.boing.com> from Geff Hanoian at "Jun 24, 99 07:02:02 pm"
To: boing@kusanagi.boing.com (Geff Hanoian)
Date: Thu, 24 Jun 1999 22:05:55 -0400 (EDT)
Cc: freebsd-stable@freebsd.org
From: mwlucas@exceptionet.com
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I tried both ls and dir.  Neither worked.

All of the hosts involved are unprotected on the open Internet, so
firewalls shouldn't be an issue.

==ml

> On 25 Jun, Gregory Bond wrote:
> >> 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.
> > 
> > I discovered in a smilar situation on a Solaris ftpd that if I typed "ls" it
> > failed, but "dir" it worked.  Also, some ftp clients worked and some didn't.
> > The problem was that "dir" used the internal ls, but "ls" was an alias for "ls
> > -l", and that caused the ftpd to try and run the (non-existent) chroot'd /bin/
> > ls, even though it had INTERNAL_LS defined.
> > 
> > I assume a similar problem could cause the same behaviour on FreeBSD.
> 
> Have we elimited firewall configuration as a possibility?  From end to
> end of course.
> 
> Geff


-- 
Michael Lucas			|
Exceptionet, Inc.		|	www.exceptionet.com
"Exceptional Networking"	|


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