Date: Wed, 26 Mar 2008 17:04:32 -0400 From: "The MadDaemon" <maddaemon@gmail.com> To: "Dan Nelson" <dnelson@allantgroup.com> Cc: freebsd-questions@freebsd.org Subject: Re: sFTP on 7.0-RELEASE no worky Message-ID: <6c1774c50803261404k72cad720s6f8c3b5c86ca7ddb@mail.gmail.com> In-Reply-To: <20080326193055.GB16367@dan.emsphone.com> References: <6c1774c50803261125ic810c32g4a97447e63c42d06@mail.gmail.com> <20080326193055.GB16367@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 26, 2008 at 3:30 PM, Dan Nelson <dnelson@allantgroup.com> wrote: > In the last episode (Mar 26), The MadDaemon said: > > 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 [~]$ > > 173305700 = 0x0A546F64 = "\nTod" > > Make sure you don't have any commands in your shell's startup scripts > that might print anything if the incoming session isn't interactive. > > http://www.snailbook.com/faq/sftp-corruption.auto.html > > -- > Dan Nelson > dnelson@allantgroup.com > d'oh! I had fortunes enabled, which was the culprit. Thanks for the link/answer, Dan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6c1774c50803261404k72cad720s6f8c3b5c86ca7ddb>