*BSD News Article 69489


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!bofh.dot!news.mathworks.com!newsfeed.internetmci.com!torn!nott!nntp.igs.net!usenet
From: cskinner@bml.ca (Chris K. Skinner)
Newsgroups: list.freebsd-bugs,comp.unix.bsd.freebsd.misc,list.freebsd-questions,local.freebsd.questions
Subject: Re: FTP server definite bug!
Date: Mon, 27 May 1996 05:10:34 GMT
Organization: Bytown Marine Limited, Nepean/Kanata, Ont, Canada
Lines: 162
Message-ID: <4obdn9$7o5@nntp.igs.net>
References: <318FA7CB.8D8@hkstar.com> <DrI7pE.pF@iquest.net> <4nlrhs$lqr@news1.halcyon.com> <4nmpun$i6@uriah.heep.sax.de> <4nrk6d$14h@Mercury.mcs.com> <31A2A83D.67A89A35@lambert.org> <31A33D9D.17035FB@nd1.tahsing.com.tw> <Pine.BSD/.3.91.960524205833.24236M-100000@Clifford.LiveNet.Net>
NNTP-Posting-Host: ttyb02.ott.igs.net
X-Newsreader: Forte Free Agent 1.0.82

>cc was given to: "Jordan K. Hubbard" <jkh@time.cdrom.com>,"Bruce Evans" <bde@zeta.org.au>, bugs@freebsd.org
Greetings.  I read a bunch of messages on this.  Sorry for
any inconvenience that I might have caused anyone
at the www@cdrom.com address.  I also posted the
bug message to the list.freebsd-bugs usenet newsgroup.
So that others can learn of some of this stuff, I've
cross-posted to a bunch of groups.  You'll tell me if this
is a bad thing?

I'm using MS-Windows for my connection to the Internet
and www, so when I went back to www.cdrom.com to look
in the handbook or FAQ or other, I was lazy when I
couldn't find where the bugs@freebsd.org spelling
for cut/paste purposes was where I thought I saw a
reference to reporting something to the www@cdrom.com.
I got an impression that one bug reporting 
method might have involved me running some 
unix program or script to package
the bug report.  Since my unix system is not connected
to the internet yet, and I am not rock solid with
unix at all, I just used MS-Windows, quickly grabbed
an e-mail address where persons with some degree of
concern might be found (not necessarily a super
high degree of concern, but... those who might be there
could pass along the info), and voila!--People with
concern seemed to have, one way or another, gotten
my "by-the-way, there's a bug I found"-type message.

To tell you the god's honest truth, I will probably
be sticking to some program development in a
Dos/Windows environment.  Sorry for the blasphemy,
but I like how many of the C/C++ development
environments there permit you to place the display 
cursor or otherwise highlight any word/phrase 
in the development environment and press 
Ctrl-F1 to launch hypertext help
on the topic.  It saves hunting through manuals.  
It's my lazy man's way of programming.  The help
topic brings up sample code that can be cut and
pasted into the environment's program development
window so that in a matter of seconds, one can
tweak the imported code into the shape one wants
to accomplish the functionality one is trying for.

If this kind of functionality is already in
X-windows, then I'll be eager to branch-out into
that development environment, otherwise,
I'll probably stick, for a while, to the stuff
that I know in Dos/Windows.  I'll aim for portability,
but that may be grasping for straws, and I'll
probably be swearing and cursing about how nothing
comes across cleanly!

Bruce, for technical reasons, I have to run one 
version of winsock.dll for dial-up networking 
on WFWG 3.11 and another version (Microsoft tcp/ip-32) 
for ethernet tcp/ip.  To switch back and forth, I 
click on an icon that runs a bat file script,
but cannot do so while the in-place DLL file is
busy--like now when I'm on-line on dial-up.

Bruce Evans <bde@zeta.org.au> suggested that I
please send him a ktrace of events.  When I
did a ps -leax|grep "ftp" I did not see any
pids output, so maybe I've got to log into
the unix box via ftp before the listing will
display anything to me that I can set for
ktrace'ing.  After I reproduce the bug,
and turn off ktrace via the -C option, I'll
have to grab the ktrace'd result file and
binary "get" it to this MS-Windows machine.
I could probably gzip it just before doing so.
Or should I do a kdump or ktracedump or
whatever with output redirected to a file?
And then should I e-mail either as an attachment
with MIME encoding or binhex or uuencode or
xxencode?  Note that the attached file(s) is/are
likely going to have an 8.3 MS-Dos filename.
But I can't do this this instant because of
the dial-up (trumpet) winsock.dll is in use
and can't (now) be switched to the MS-version.

If anyone has a suggestion
regarding getting the pid of the
ftp process for ktracing, please tell me 
_exactly_ what I should be doing.

TIA.  Happy computing.  Regards, Chris K. Skinner.

At 02:53 PM 5/23/96 -0700, "Jordan K. Hubbard"
<jkh@time.cdrom.com> wrote:
>> Hi.  Greetings.  Discovered something weird...

>Uh, why are you sending this to the web site feedback address? :-)

>This should go to bugs@freebsd.org if you think it's a genuine bug or
>questions@freebsd.org if you aren't quite sure (see
>http://www.freebsd.org for section on mailing lists and their
>charters).

>Thanks!
>					Jordan
=========== A separate message from Bruce ... ==============
>Date: Fri, 24 May 1996 23:18:50 +1000
>From: Bruce Evans <bde@zeta.org.au>
>Message-Id: <199605241318.XAA03076@godzilla.zeta.org.au>
>To: cskinner@bml.ca
>Subject: Re: FTP server definite bug!

>>Bug title:  FTP server gets and obeys an mput of "." and ".."
>> special files from a "stupid" LAN FTP client.

>Please send me output from ktrace for this.

>I broke the standard ftp client to test this but wasn't able to
>duplicate the bug.  The client sends ".", and the server attempts
>to open "." for writing as a plain file, but the open fails like
>it should.  I think your client does something to make the server
>unlink ".".

>Bruce
=========== Original bug report message follows ======
>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.