On Sunday 23 December 2001 08:36 pm, you wrote: > On Sunday 23 December 2001 08:25 pm, you wrote:
> > "David P. Schwartz" wrote:
> > > You can set your server to watch on whatever port you want. If you
> > > have a firewall or router (like a Cisco 675/8 modem), you'll probably
> > > need to enable the port(s) you want other than port 80. NOTE: this can
> > > make it appear that the ISP is blocking the ports, when in fact the
> > > block is on your end.
> > >
> > > You could also set up a basic web server on port 80 then load up some
> > > pages that allow directory browsing, which would accomplish about the
> > > same thing as an FTP server. But I'd definitely provide a login screen
> > > for such a method!
> >
> > ----
> > I was never real keen on allowing directory browsing - seems to be a
> > security risk - but I guess that if you use https, it is better than ftp
> > which transmits passwords in the clear - not much security there but if
> > you are determined to use ftp, at least you can chroot real users.
> >
> > Craig
>
> Seems that the consensus is to run a webserver with the ability to upload
> files. I have read that FTP creates many hazards and really wasn't keen on
> doing that but I am also very experienced in setting up or running any form
> of server on Linux.
> That should read "Inexperienced"
(text/plain)