Date: Mon, 02 Oct 2000 14:29:25 -0600 From: Brett Glass <brett@lariat.org> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Jordan Hubbard <jkh@winston.osd.bsdi.com>, security@FreeBSD.ORG Subject: FTP problems: Clients? Servers? Both? Message-ID: <4.3.2.7.2.20001002140904.00df5390@localhost> In-Reply-To: <20001002220120.A59204@mithrandr.moria.org> References: <4.3.2.7.2.20001002133527.00d604a0@localhost> <Message <brett@lariat.org> <4.3.2.7.2.20001002113441.04932240@localhost> <59846.970514080@winston.osd.bsdi.com> <4.3.2.7.2.20001002133527.00d604a0@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
At 02:01 PM 10/2/2000, Neil Blakey-Milner wrote: >You aren't keeping your machines up to date. This was fixed in RELENG_3 >already: > >revision 1.14.2.3 >date: 2000/06/23 14:46:54; author: ru; state: Exp; lines: +3 -3 >MFC: (rev 1.17) Get rid of segfault in a `site %s\' case. I have machines of all ages here. Remember that we are waiting for 4.2 to upgrade some machines from 3.x. >> 2) There is still some funkiness in recent FreeBSD servers too. This is >> evidenced by the fact that bad commands can generate responses which look >> like a memory dump. They also mess up the output of ps(1). See my message >> a few minutes ago to Alex, which shows problems in the server when I submit >> bad commands using the MS-DOS/Windows client. > >I don't see this with a 3.3 or 3.4 ftpd. My latest tests seem to indicate that the MS-DOS/Windows client may not be pristine either. (It is based, as I recall, on an old Berkeley release.) It may respond in an untoward manner to sequences such as %s. So, I have dropped down to the lowest common denominator and am using Telnet to fire commands at the various ftpd versions. Based on that modus operandi, I am beginning to think that the problems are mostly in clients. But there are also some odd things in servers (including FreeBSD's). The one you point out above (only fixed recently) is a good example. I also see a few minor nits (FreeBSD's ftpd seems to give double error messages in some cases, and does not trim trailing whitespace in commands) for which I'll probably submit patches once I figure out whether there's anything exploitable in the latest servers. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20001002140904.00df5390>