From owner-freebsd-questions@FreeBSD.ORG Fri Mar 25 16:11:50 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BDAF16A505 for ; Fri, 25 Mar 2005 16:11:50 +0000 (GMT) Received: from enterprise.thenetnow.com (enterprise.thenetnow.com [65.39.193.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D67443D1F for ; Fri, 25 Mar 2005 16:11:50 +0000 (GMT) (envelope-from gpeel@thenetnow.com) Received: from GRANT (hpeel.ody.ca [216.240.12.2])j2PGBj527457; Fri, 25 Mar 2005 11:11:45 -0500 (EST) (envelope-from gpeel@thenetnow.com) Message-ID: <004b01c53155$5ce59c60$6401a8c0@GRANT> From: "Grant Peel" To: "Eric McCoy" References: <002c01c53145$b9c64390$6401a8c0@GRANT> <4244354E.10401@haystacks.org> Date: Fri, 25 Mar 2005 11:11:51 -0500 Organization: The Net Now MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-questions@freebsd.org Subject: Re: sFTP nologin X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Grant Peel List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 16:11:50 -0000 Yes, been trying that all morning. sbin/nologin kills the connection after it prints the message. i have been tring scponly it has been less that workable so far too. -GRant ----- Original Message ----- From: "Eric McCoy" To: "Grant Peel" Cc: Sent: Friday, March 25, 2005 10:59 AM Subject: Re: sFTP nologin > Grant Peel wrote: >> Is there a quick - secure way to allow the sshd sFTP subsystem to allows >> sftp connections without allowing shell accounts? > > Create the account and set its shell to /sbin/nologin. You can safely add > that to /etc/shells: it does its name and just prints a terse message > before booting the user if he tries to connect via vanilla SSH. > >