Re: sFTP on 7.0-RELEASE no worky

2008-03-26 Thread Dan Nelson
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:
 
 [EMAIL PROTECTED] [~]$ sftp 172.20.30.12
 Connecting to 172.20.30.12...
 
 (banner snipped)
 
 Password:
 Received message too long 173305700
 [EMAIL PROTECTED] [~]$

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
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: sFTP on 7.0-RELEASE no worky

2008-03-26 Thread The MadDaemon
On Wed, Mar 26, 2008 at 3:30 PM, Dan Nelson [EMAIL PROTECTED] 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:
  
   [EMAIL PROTECTED] [~]$ sftp 172.20.30.12
   Connecting to 172.20.30.12...
  
   (banner snipped)
  
   Password:
   Received message too long 173305700
   [EMAIL PROTECTED] [~]$

  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
 [EMAIL PROTECTED]


d'oh!  I had fortunes enabled, which was the culprit.  Thanks for the
link/answer, Dan.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]