-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have said it before and I will say it again. Linux is not Windows. The basic philosophy is that you can tie together a bunch of small applications that do their job well, as opposed to one large program that does a number of things in a mediocre way.
Most user management for FTP is tied to the system. So adding users to ftp is no different than adding users to your system (via the command line or a graphic util). Directory permissions are handled the same way, either via the command line (chmod/chown) or via a graphic tool like konqueror or gnome equivalent. Now you can back end the user database into SQL or LDAP (or flat text files), the flexibility far exceeds what you are probably used to in the windows world, or even what you need. This does come at a cost. The command line can be daunting, but is far more flexible and powerful than any GUI tool. Likely your ftp daemon is not allowing root to login, which is a good thing, as ftp is not secure, and you do not want your root login credentials passed in the clear over the network. DO NOT underestimate this security risk! You WILL get hacked. The filezilla client supports sftp which is supported by your ssh daemon. You can lock this down more (ie. have users be able to transfer files via sftp but not get a local shell), but you do not need to worry about that at this point. Having said that, you can install a web based gui such as webmin, but its limitations frustrate me (mind you I do manage a number of servers, with users numbering between 15 and 350+ depending on the client, so I have fairly demanding needs). It is also interesting to note that the Microsoft team in charge of hotmail has mandated that all management be scriptable from the command line. So even Microsoft needs the command line :) So the big take home message, is that while there are some applications that are essentially identical to their windows counterparts, there are lots of cases where there is no direct equivalent application. This is not a bad thing, it is simply a different way of doing things. Mitchell Brown wrote: > I do understand FTP. I run an ftp server on my Windows box and have a > graphical front end to manage it. In fact, its all graphical. It's > Filezilla Server. A client is used to connect to it. You should know > that the FileZilla Server portion can be used to connect to OTHER > servers on port 14147 to administer them. Weird, I know. > > On 4/18/06, *Shawn* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > On Tuesday 18 April 2006 19:31, Mitchell Brown wrote: > > This is all very confuzzling for me. > > > > I refuse to believe there is not a graphical FTP daemon out there for > > Linux. > > I can tell you don't have a proper understanding of what FTP > is. Some of the > questions you are asking are clearly confusing the difference > between an FTP > server, and an FTP client. > > The graphical tool you are looking for is the client - something > like CuteFTP. > You use the client tool to connect to a server and transfer files > to/from > said server. > > The server is totally different. It provides the environment that > allows > connections to it, and enforces permissions. > > The easiest way to set up an ftp server is to use shell > accounts. So, once > you have vsftp, or proftp, or XXXftp setup, anyone with a local > shell account > (i.e. Linux username/password), can connect to access either shared > files, of > personal files depending on how you set it up. Of course, this just > scratches the surface of what is possible. > > Part of the delay getting the information you need, is because you > seem to be > unclear on the correct questions to ask. (not dis'ing you, just > observing) > Take the time to read through the various how-to's, guides and > manuals for > the various ftp servers out there. It'll pay off in the long > run. But, you > are asking questions, and based on your efforts and the responses > you'll get, > you'll start asking the "right" questions as a result. > > As for graphical tools to manage an ftp server - could could always > try webmin > - but you need to take care to set that up correctly so as not to > open your > network to attack. Not to mention that will also require properly > understanding more than just ftp. > > I agree with the others who suggest simply using scp, or > sftp. These are part > of the OpenSSH libraries, and if you are running an SSH server you > already > have these at your fingertips with no additional setup. I host a few > websites on my server, and I absolutely refuse to give them raw ftp > access - > they use sftp via the winscp client (that runs on windows). > > HTH. > > Shawn > > > _______________________________________________ > clug-talk mailing list > [email protected] <mailto:[email protected]> > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines ( http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > > > > ------------------------------------------------------------------------ > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFERcE7wRXgH3rKGfMRAtqJAKCkDWVYVIZkNZREXDxl8JghoLjNOACfX68X D/LrxunyTIPf4vuy+4636v0= =5y8P -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
