From owner-freebsd-security Tue Jun 12 14:57: 5 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.wlcg.com (mail.wlcg.com [207.226.17.4]) by hub.freebsd.org (Postfix) with ESMTP id 99CFD37B401 for ; Tue, 12 Jun 2001 14:57:02 -0700 (PDT) (envelope-from rsimmons@wlcg.com) Received: from localhost (rsimmons@localhost) by mail.wlcg.com (8.11.3/8.11.3) with ESMTP id f5CLv7476548; Tue, 12 Jun 2001 17:57:07 -0400 (EDT) (envelope-from rsimmons@wlcg.com) Date: Tue, 12 Jun 2001 17:57:03 -0400 (EDT) From: Rob Simmons To: "Antoine Beaupre (LMC)" Cc: Jamie Norwood , "Antoine Beaupre (LMC)" , freebsd-security@FreeBSD.ORG Subject: Re: OT: yet another discussion FTP vs HTTP (was: IPFW almost works now.) In-Reply-To: <3B2684EC.2010205@lmc.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Tue, 12 Jun 2001, Antoine Beaupre (LMC) wrote: > Jamie Norwood wrote: > I think you misunderstood. If you need to allow ftp access, *securly*, > you must use sftp, and then, you must provide the user with a shell > account, which is by definition a higher security risk, unless you > disable the shell account and use only RSA auth. Which is completly > user-unfriendly. chroot'ing that user's ssh session to their home directory could solve this problem somewhat. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7JpAzv8Bofna59hYRAz69AJ43K3GjMNQDGyT2W7kc8iWASfZgkgCdH1ca rnCP/j1ckt2AFtUtcrG8a/E= =PrcX -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message