Instructions to unsubscribe from this list at the end of the message - --------------------------------------------------------------------- This is a multi-part message in MIME format. - --------------080005070207080201030609 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit
>Apart from understanding next to nothing from the link you gave me, it >seems like an awfully long procedure to do every time an FTP user is >added. I would use proFTPd, but I can't find where to define which >users have what access etc.. from webmin. > > It's not FTP which controls access, it's Linux. FTP merely logs them in using their Linux user, and Linux takes care of the rest. Your users will have access according to file permissions, group membership etc. just as if they were directly logged in, except that you can also lock them into their home directories. The /etc/passwd file contains some information about each user. You can use UserDrake (control center) to edit this file, instead of editing it directly with an editor. One of the fields is the shell program - this is usually /bin/bash. You can change that to something like /bin/false, which effectively prevents that user from logging in directly using a shell, such as with telnet, ssh or directly from the console. They can still log in via ftp, since that doesn't use a shell. Another important field in this file is the "home directory". This is usually something like "/home/keith". You could change that directory to "/home/keith/./" to make ftp lock that user into their home directory. As you probably know, the "." directory refers to the current directory, so it won't affect the normal operations for that user. On the other hand, the ftp program will search for the "." within the home directory, and if it finds it there, will lock the user into that directory. If you're setting up a system which will have lots of users (hundreds of them), I suggest you read about the useradd command. You can supply all parameters on the command-line to create a new user with the right settings. Once you know the right settings, it's easy to create a simple shell-script which takes just the username as a parameter and does all the rest. Something like the following (must be root to run it): - ------------------------------------------------------------------------ #!/bin/sh useradd -d /home/$1/./ -s /bin/false -m $1 passwd $1 - ------------------------------------------------------------------------ If you want, you can create a "default home directory" somewhere, which would contain all the initial files for new ftp-users' home directories, and use the -k option so the new users will all start off with a basic starting directory structure. Ramon - --------------080005070207080201030609 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> <br> <blockquote type="cite" cite="[EMAIL PROTECTED]"> <pre wrap="">Apart from understanding next to nothing from the link you gave me, it seems like an awfully long procedure to do every time an FTP user is added. I would use proFTPd, but I can't find where to define which users have what access etc.. from webmin. </pre> </blockquote> It's not FTP which controls access, it's Linux. FTP merely logs them in using their Linux user, and Linux takes care of the rest. Your users will have access according to file permissions, group membership etc. just as if they were directly logged in, except that you can also lock them into their home directories.<br> <br> The /etc/passwd file contains some information about each user. You can use UserDrake (control center) to edit this file, instead of editing it directly with an editor. One of the fields is the shell program - this is usually /bin/bash. You can change that to something like /bin/false, which effectively prevents that user from logging in directly using a shell, such as with telnet, ssh or directly from the console. They can still log in via ftp, since that doesn't use a shell.<br> <br> Another important field in this file is the "home directory". This is usually something like "/home/keith". You could change that directory to "/home/keith/./" to make ftp lock that user into their home directory. As you probably know, the "." directory refers to the current directory, so it won't affect the normal operations for that user. On the other hand, the ftp program will search for the "." within the home directory, and if it finds it there, will lock the user into that directory.<br> <br> If you're setting up a system which will have lots of users (hundreds of them), I suggest you read about the useradd command. You can supply all parameters on the command-line to create a new user with the right settings. Once you know the right settings, it's easy to create a simple shell-script which takes just the username as a parameter and does all the rest. Something like the following (must be root to run it):<br> <br> <hr style="width: 100%; height: 2px;"> <pre style="color: rgb(0, 0, 153);">#!/bin/sh useradd -d /home/$1/./ -s /bin/false -m $1 passwd $1</pre> <hr style="width: 100%; height: 2px;">If you want, you can create a "default home directory" somewhere, which would contain all the initial files for new ftp-users' home directories, and use the -k option so the new users will all start off with a basic starting directory structure.<br> <br> Ramon<br> </body> </html> - --------------080005070207080201030609-- - --------------------------------------------------------------------- You received this message because you are subscribed to the linux mailing list. If you do not wish to continue receiving this mailing list, please send a mail message to [EMAIL PROTECTED] containing only the text "unsubscribe linux" containing only the text "unsubscribe $LIST"
