From owner-freebsd-stable@FreeBSD.ORG Tue Jan 27 06:26:08 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B6171065674 for ; Tue, 27 Jan 2009 06:26:08 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [206.117.18.8]) by mx1.freebsd.org (Postfix) with ESMTP id 0FEA08FC1A for ; Tue, 27 Jan 2009 06:26:08 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.196] (pool-71-109-162-173.lsanca.dsl-w.verizon.net [71.109.162.173]) (authenticated bits=0) by zoom.lafn.org (8.14.2/8.14.2) with ESMTP id n0R5nLqd080354 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 26 Jan 2009 21:49:22 -0800 (PST) (envelope-from bc979@lafn.org) Message-Id: <85A5C570-5F81-4D6D-8D62-08FFC44DA5F7@lafn.org> From: Doug Hardie To: freebsd-stable Stable In-Reply-To: <200901262055.n0QKs31N054621@fire.js.berklix.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 26 Jan 2009 21:49:21 -0800 References: <200901262055.n0QKs31N054621@fire.js.berklix.net> X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on zoom.lafn.org X-Virus-Status: Clean Subject: Re: SSH problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 06:26:08 -0000 On Jan 26, 2009, at 12:54, Julian Stacey wrote: > Hi, > Reference: >> From: Xian Chen >> Date: Mon, 26 Jan 2009 13:45:56 -0500 >> Message-id: > > > > Xian Chen wrote: >> Hi All, >> >> I can use scp to move files from a linux to my Freebsd machine. >> >> But, when I try to use WinSCP under windows, it always failed. WinSCP >> errors: "Network error: Connection refused". Both scp & sftp fail >> if using >> WinSCP. >> >> Any clues for this? > > on FreeBSD: > man sftp says -v option exists > man ssh also offers -v > so try both those from Win/Lose/Mickesoft (*), > Also ref. > man sshd > try > kill -9 `cat /var/run/sshd.pid` > or hash out sshd line in /etc/inetd.conf & then > kill -HUP `cat /var/run/inetd.pid` > & then run as root > /usr/sbin/sshd -D -d > & > more /var/run/auth.log > > (*) PS I hate MS & dont use it, but doesnt invalidate debug stuff > above > though, except you might need to start ssh from a command line to > add a parameter, rather than just clicking. Here is how I have setup secure ftp for our users: LAFN now provides a ftp server that handles the ftp-ssl and ftp-tls protocols (RFC-2228). These protocols will encrypt the user id and password and can also be configured to encrypt the file contents if desired. The standard ftp port, 21, is used for both encrypted and non-encrypted ftp sessions. The older sftp, scp, and implicit ftp-ssl protocols are not supported. Obviously transfer times are longer if encryption is used. There are several Windows and Unix clients that support these protocols. The following clients are believed to work properly: CuteFTP Pro 2.0 Windows FileZilla 2.0.0 beta 5 Windows (GPL) SmartFTP 1.0 build 969 Windows WinSSLWrap 1.17 Windows WS_FTP Pro 7.5 Windows FTP Voyager Secure 9.1.0.1 Windows Lftp 2.5.2 Unix In addition there is a client available at http://bsdftpd-ssl.sc.ru that will work with Windows 9x, NT, 2000, and some Linux distributions. The only known client for Macintosh is available in the LAFN FAQ. It only works with OS-X and is the command line client from the fstftpd-ssl distribution. The client info above is a bit old, but is probably still accurate. There may be additional clients available now. On the server I use the bsdftpd-ssl port. It replaces the base ftpd. Several of the above clients are in regular use.