If your users want a GUI client and they run Linux or *BSD, then they can easily configure Gftp to use sftp rather than ftp. In this scenario, you don't need to run Pureftp on your server - sftp (which uses the sshd daemon) will do the whole job.
In Gftp, you set this up by clicking FTP-Options-SSH, and on the line that says "SSH2 sftp-server path" type "/usr/libexec/sftp-server". This is the sftp-server path for FreeBSD, though note that if your users try to connect to another server that uses a different path (some Linux distros use /usr/lib/sftp-server) they'll have to change the path. Anyway, once this option is set, the only thing the user has to do is click on the "FTP" icon (upper right-hand side of Gftp screen) and select "SSH2" (as opposed to "FTP"). That's all. All of the above applies to Linux and *BSD, and maybe to OSX as well. But if your users are running Windows, I have no idea. It may be possible with some Windows ftp clients, but you'll have to research that on your own. Maybe I haven't really answered your question. best regards, Robert On Thu, 3 Jun 2004 08:26:55 -0800 "Noah" <[EMAIL PROTECTED]> wrote: > > > > > SFTP is for giving secure-ftp-access to users who also have secure- > > shell-access (SSH), so I don't think it's appropriate for your case. > > FTP-logins can be totally separated from shell-logins (with a > > separate passwords-database or even virtual users on some ftp- > > servers), so I think you better go on with your FTP-configuration, > > but then use a SSL- aware FTP-client to make secured connections to > > your server, not SFTP. > > I dont completely understand here - how can I force people with FTP > accounts to log in securely? As in - how do I force SSL authenticated > logins but still allow authentication to the accounts in Pureftp DB > file? > > thanks in advance, > > - noah _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"