Branton Campbell writes:
: Sami Lehtinen wrote:
:
: >There has been opinions that this could be chacked in the users
: >.cshrc, which I don't doubt, but I think this addition could reduce
: >the load of our support and sysadmins worldwide. Maybe. On a good day.
: >
: >Anyways, what do you think? (apply by going to your
: >ssh-secure-shell-2.1.0 directory, and giving the command
: >% patch -p 0 < /path/to/this/patch
: >)
:
: When will this fix work it's way into the Windows binaries
: available for download? I can see that I have the same problem
: that others have had.
That patch, which add AllowCshrcSourcingWithSubsystems, changes only
the way the server works. So this is not useful in your case (unless
your unix administrator decides to apply that patch).
You should try to clean your shell initialization scripts, so that
nothing get printed to stderr/stdout when you connect to the server.
You can try it out in the unix end. Try a command like
% ssh your_server sleep 0
If anything get's printed, then your shell initialization scripts are
messing the data stream (note: with ssh-2.2.0 (to be released) there
is a configuration parameter AuthenticationSuccessMsg, which defines
whether the client should tell the user that the authentication was
successful. This message won't be in the data stream when using ssh2
as the transport layer, so it is nothing to be worried about.)
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Corp http://www.ssh.com/]
