Date: Thu, 24 Jun 1999 22:05:55 -0400 (EDT) From: mwlucas@exceptionet.com To: boing@kusanagi.boing.com (Geff Hanoian) Cc: freebsd-stable@freebsd.org Subject: Re: ftpd: some clients can list, some cannot Message-ID: <199906250205.WAA09671@easeway.com> In-Reply-To: <199906250202.TAA19619@kusanagi.boing.com> from Geff Hanoian at "Jun 24, 99 07:02:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906250205.WAA09671>