Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
haven't found anything on the unification of these two protocols...
we'd like to build an ftp/sftp appliance, allowing both protocols if needed. one user can have the possibility ofg logging in via ftp, or sftp, and be chrooted in the same directory. I know this is technically possible, but would be an administrative nightmare if managed seperately.
so...has anyone heard of or implemented an integrated ftp/sftp system like what I am describing?
I forgot to note that we would preferably like to use sldap/ldap to authenticate users, which means that it should ideally be possible even to setup ftp/sftp systems seperately.... but with the same chrooted environments.....hmmm
I have not heard of this, but i am also trying to do the same.. The problem as i have seen it is that i can't have something like RSSH as a virtual shell for the users and still have them be able to login using FTP with the same name, because of the restrictions set forth by RSSH allowing only certian connections.
If there is a way to copy over or dynamically link FTP services to users while using a different shell or copying over the libs as you would do with a normal chroot enviroment, but every option that i have tried has not come up with anything useful results.. if anyone has any ideas please advise
sadly, the need for this was erased due to a file transfer appliance utilizing https being purchased.
my end conclusion was to setup chrooted ftp and ssh/scp services separately. however, both would use ldap and refer to the same directory regardless of services used to connect. this way, it would *appear* to the end user to be the same (since the chroot location would be the same either way). this would minimize management by utilizing ldap, so it's not as if user account would have to be created twice (once for ftp, once for ssh). you could us the local passwd file as well of course as an authentication source for both.
for example, if the user JohnFoo authenticated:
ftp would chroot to: /home/jail/home/$LDAP_user/
ssh would chroot to: /home/jail/home/$LDAP_user/
Last edited by TotalDefiance; 12-07-2006 at 09:47 PM.