L.S, I was very happy to find that OpenSSH 2.3.0 now has server support for F-Secure's Win32 FTP client. A problem I have run into a few times (and maybe others before me) is: I want to allow technically unsophisticated users to update their web pages without having to resort to running something like wu-ftpd on my system. SFTPD is a great solution for that since even a casual user can understand it's user interface (The Win32 scp client is not an acceptable solution in this case). SFTPD still leaves me with a few items on my wishlist that could be solved on the server side: - I would prefer it if some users would be limited to SFTP access and not be allowed ssh interactive access or scp. (this is similar to Jos Backus' request posted earlier on this list). - It would be great if a user using SFTP could (optionally and configurable per user) be chrooted to his homedirectory (or some other directory). Any chance of implementing this? Regards, Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20001215/5b0d427f/attachment.html
Humm, I seem to remember reading something like: "HTML mail is NOT PERMITTED on this list." And yet, Peter is posting in HTML. What gives Peter? Does this mailing list have a filter to automatically bounce messages in HTML format? If not, it seems like a very handy thing to add. Mo DeJong Red Hat Inc
Mo & others: My sincere apologies for posting in HTML. I repeat my question in a civilized format (and crawl under a rock somewhere): L.S, I was very happy to find that OpenSSH 2.3.0 now has server support for F-Secure's Win32 FTP client. A problem I have run into a few times (and maybe others before me) is: I want to allow technically unsophisticated users to update their web pages without having to resort to running something like wu-ftpd on my system. SFTPD is a great solution for that since even a casual user can understand it's user interface (The Win32 scp client is not an acceptable solution in this case). SFTPD still leaves me with a few items on my wishlist that could be solved on the server side: - I would prefer it if some users would be limited to SFTP access and not be allowed ssh interactive access or scp. (this is similar to Jos Backus' request posted earlier on this list). - It would be great if a user using SFTP could (optionally and configurable per user) be chrooted to his homedirectory (or some other directory). Any chance of implementing this? Regards, Peter