[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] tftp (0.60.1)
From:       Glenn McGrath <bug1 () optushome ! com ! au>
Date:       2001-09-17 7:02:10
[Download RAW message or body]

On Mon, 17 Sep 2001 22:33:26 +1000
Glenn McGrath <bug1@optushome.com.au> wrote:

> On 17 Sep 2001 10:44:24 +0200
> Thomas Dahl <td@baekgaardholding.dk> wrote:
> 
> > Hi,
> > 
> > I'm having some timeout problems with the tftp client in busybox
0.60.1.
> > 
> > Busybox is compiled against libc5 and kernel 2.0.36.
> > 
> > Using the tftp client from the Redhat 4.2 distribution don't give me
> > these timeouts.
> > 
> > Others out there experience these problems with the tftp client?
> > 
> 
> Busybox tftp does work for me with atftpd, i was gettign timeout errors
> before i realised i hadnt restarted inetd (which starts atftpd).
> 
> What tftp server are you connecting to, i know of tftpd atftpd and
> tftp-hpa, there may be compatability problem with servers other that
atftp
> ill do some more tests and try and reproduce your problem
> 
> 
> Glenn
> 

It works with all three tftp servers i mention above.

One trap is the path name to the file, with debian, the default is for

atftpd chroots to /tftpboot to look for files
tftpd looks for files relative to /
tftp-hpa looks for files relative to / unless the -s <dir> is passed when
it chroots to that dir.

I dont like the idea that a file that is o+r _anywhere_ on your filesystem
is accessable by anyone via tftp, so i think caution is advised if you use
tftpd or tftp-hpa without -s


Glenn



[prev in list] [next in list] [prev in thread] [next in thread]