On Fri, Apr 27, 2001 at 04:09:27PM -0400, Lucy Hou wrote:
> I have a concern with sftp/ssh. Sure, sftp make ftp transfer secure,
> but in order to make sftp work, ssh has to work in the first place. It
> is ok in a situation when server end "trust" the client, like corporate
> intranet. But what about when the client can't be fully trusted?
If you don't trust the clients, why do you want to let them connect
in the first place?
> But what if the
> situation requires that the client has write permisson?
If you need anonymous FTP with upload, then set that up. Don't use sftp.
Use a normal ftpd (such as the OpenBSD one), set up the anonymous account,
make sure it's chroot()ed, and that the upload directory has write
permission (and execute/search) but no read permission.
Anonymous sftp would be pointless, as far as I can see. Use sftp for
your normal users (everything except anonymous).
If I've misunderstood the nature of your problem, then please explain
in a little more detail.