Date: Thu, 23 May 1996 21:22:00 GMT From: cskinner@bml.ca (Chris K. Skinner) To: www@freebsd.org Subject: FTP server definite bug! Message-ID: <199605232121.RAA10225@host.igs.net> Resent-Message-ID: <4042.832888469@time.cdrom.com>
index | next in thread | raw e-mail
Hi. Greetings. Discovered something weird...
Bug title: FTP server gets and obeys an mput of "." and ".."
special files from a "stupid" LAN FTP client.
Config:
Server: January CD of FreeBSD 2.1.0 from Walnut Creek.
Client: the MS-Windows for Workgroups 3.11 Beta 1.1(?) of
Microsoft TCP/IP-32.
Scenario:
1. Within a MS WFW 3.11 system, login as a valid
unix user (Ethernet Lan connection between machines).
2. Change local Win3.11 directory to a directory with a
bunch of www html, gif, jpg files to send to the
unix host as a test of MS tcp/ip-32 FTP.
3. Set prompting off so that no interactive "y/n ?" pause
message appear within MS tcp/ip-32 when doing "mput".
4. Change remote FreeBSD unix directory to user's home
directory.
5. Make a temporary unix directory to hold the files
that will be up-loaded via MS-tcp/ip-32 ftp to the
unix user sub-directory.
6. Change into this temporary directory for doing the
upload.
7. Perform a "mput *.*" command so that Win3.11 sends files
to unix.
8. Witness that the Win3.11 FTP will attempt to send both
the "." and ".." files, and the unix machine will
have its "." and ".." directory entries corrupted.
9. Perform a "fsck" command on the unix machine to detect
and correct the corruption created by the steps above.
The unix fsck reports and corrects the directory entry
corruption of the "." and ".." directory entries that
were screwed up by the "stupid" client ftp software.
Thanks for reading this. Regards, Chris K. Skinner.
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605232121.RAA10225>