This is problem-with-1.0-ftpd in view mode; [Up]
Date: Sun 09-Nov-1989 02:28:27 From: Unknown Subject: problem with 1.0 ftpd I have a system on a non-NeXT network, using NetInfo, no Yellow Pages. The ftpd isn't working right: it responds to the connection (220 ...Version 5.18...), but denies access for any user (530 User jacob access denied). The results are the same when ftp'ing from the same machine and from a different machine. The only hints I found in the on-line docs is "ftp works" :-) Has anybody run into this problem? Jacob
Date: Sun 09-Nov-1989 20:19:41 From: Unknown Subject: Re: problem with 1.0 ftpd The problem was that my shell was not listed in /etc/shells. Thanks to Morris Meyer (NeXT OS Group) for pointing this out to me. Jacob
Date: Sun 10-Nov-1989 01:51:04 From: Unknown Subject: Re: problem with 1.0 ftpd In article <130034@gore.com> jacob@gore.com (Jacob Gore) writes: I have a system on a non-NeXT network, using NetInfo, no Yellow Pages. The ftpd isn't working right: it responds to the connection (220 ...Version 5.18...), but denies access for any user (530 User jacob access denied). Are you using a shell that is not listed in /etc/shells? If you do something like install bash and set that as your shell you have to enter the pathname in /etc/shells or ftp will deny access. >From: eps@toaster.SFSU.EDU (Eric P. Scott)
Date: Sun 10-Nov-1989 05:07:26 From: Unknown Subject: Re: problem with 1.0 ftpd In article <130034@gore.com> jacob@gore.com (Jacob Gore) writes: >The only hints I found in the on-line docs is "ftp works" :-) Ours works fine except for anonymous ftp--LIST doesn't work, but NLST does so long as you don't give it a -argument (filenames are ok). 1.0's ftpd also has the % ftp -n localhost ftp> quot pasv crash-and-burn bug. -=EPS=- >From: eps@toaster.SFSU.EDU (Eric P. Scott)
Date: Sun 10-Nov-1989 05:54:25 From: Unknown Subject: Re: problem with 1.0 ftpd In article <106@toaster.SFSU.EDU> eps@cs.SFSU.EDU (Eric P. Scott) writes: >Ours works fine except for anonymous ftp--LIST doesn't work /bin/ls is linked with the shared library in 1.0. you have to copy libsys_s.B.shlib to ~ftp/usr/shlib/ (465K, ugh!) It seems silly to have a shared library used by ONE executable that doesn't get used very often. And no, I can't hard link it since ~ftp is on a different partition from /usr. Could we please have a self-sufficient ls executable in a future NeXT release? (we already have two versions of su...) -=EPS=- >From: ambi@bu-cs.BU.EDU (Michael Amirault)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.