From owner-freebsd-questions@FreeBSD.ORG Wed Mar 26 18:53:21 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 222511065675 for ; Wed, 26 Mar 2008 18:53:21 +0000 (UTC) (envelope-from maddaemon@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 9FAD78FC2F for ; Wed, 26 Mar 2008 18:53:20 +0000 (UTC) (envelope-from maddaemon@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so3527005fgg.35 for ; Wed, 26 Mar 2008 11:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=zU2eOCNFdSf1OMnftY55mWSZgIXXlsbNdVM4xChEKCg=; b=WHxsBdDABORo8O/7wZwWc9tk4Tz9jal314t/OGqAO0NfEcgPWMRZgJ6tB0AbVHZxk/Y0japjLgZvZv3g+HZZ5YDM6Nov4+9O1i2aVxlfDccws7zfAwl0hQ9u7XxayBauSx38Xu8LKlMB/VAbO3GzArBDQ+EiyU91wEKchEEOC6c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ryxjQ3fB5MznL49MFlyVvQ8aJfOVBi82hR6rZ5O9Mwtg/F3nMXdVBbb7qGEysbdf6sqPfYfkDhU7Q72r6xK2fpjU8I8d6Wmy893SgL54hAmjIMLj+XzRqjlcAYCRX7eZNlPRnu2yWl5WuhEa9lfkmq6BUEwCkEZufXV5A9G/68A= Received: by 10.82.170.2 with SMTP id s2mr670688bue.30.1206555959984; Wed, 26 Mar 2008 11:25:59 -0700 (PDT) Received: by 10.82.188.5 with HTTP; Wed, 26 Mar 2008 11:25:54 -0700 (PDT) Message-ID: <6c1774c50803261125ic810c32g4a97447e63c42d06@mail.gmail.com> Date: Wed, 26 Mar 2008 14:25:54 -0400 From: "The MadDaemon" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: sFTP on 7.0-RELEASE no worky X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2008 18:53:21 -0000 I have a 7.0-RELEASE box that I setup a few weeks ago for testing, and I just now tried to sftp into it and get the following: kevin@darkhorse [~]$ sftp 172.20.30.12 Connecting to 172.20.30.12... (banner snipped) Password: Received message too long 173305700 kevin@darkhorse [~]$ I can SSH into the box all day long, but I can't sFTP or scp anything to it. Here's the /etc/ssh/sshd_conf (stock config with the modified Banner line): # $OpenBSD: sshd_config,v 1.74 2006/07/19 13:07:10 dtucker Exp $ # $FreeBSD: src/crypto/openssh/sshd_config,v 1.47 2006/11/10 16:52:41 des Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value. # Note that some of FreeBSD's defaults differ from OpenBSD's, and # FreeBSD has a few additional options. #VersionAddendum FreeBSD-20061110 #Port 22 #Protocol 2 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_dsa_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 768 # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin no #StrictModes yes #MaxAuthTries 6 #RSAAuthentication yes #PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no # similar for protocol version 2 #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # Change to yes to enable built-in password authentication. #PasswordAuthentication no PasswordAuthentication yes #PermitEmptyPasswords no # Change to no to disable PAM authentication #ChallengeResponseAuthentication yes # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes # Set this to 'no' to disable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. #UsePAM yes #AllowTcpForwarding yes #GatewayPorts no #X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes PrintMotd no #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation yes #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS yes #PidFile /var/run/sshd.pid #MaxStartups 10 #PermitTunnel no # no default banner path Banner /etc/motd # override default of no subsystems Subsystem sftp /usr/libexec/sftp-server Has anyone noticed this before? I didn't have any luck with search engines.. Thanks, Kevin