From owner-freebsd-stable Thu Jun 24 19: 2:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (silver234.mminternet.com [209.241.149.234]) by hub.freebsd.org (Postfix) with ESMTP id 422EE14E25 for ; Thu, 24 Jun 1999 19:02:10 -0700 (PDT) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id TAA19619; Thu, 24 Jun 1999 19:02:02 -0700 (PDT) (envelope-from boing) Message-Id: <199906250202.TAA19619@kusanagi.boing.com> Date: Thu, 24 Jun 1999 19:02:02 -0700 (PDT) From: Geff Hanoian Subject: Re: ftpd: some clients can list, some cannot To: gnb@itga.com.au Cc: mwlucas@exceptionet.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <199906242344.JAA09470@lightning.itga.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message