sftp client

[mouring at etoh.eviladmin.org]

On Fri, 9 Feb 2001, Damien Miller wrote:

> On Thu, 8 Feb 2001, Roumen Petrov wrote:
> 
> 
> > 3.)
> > My result is:
> > -----------------------------
> > Executing /.bashrc ...
> > /root/.bashrc
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 
> > 4.)
> > And result from 'sftp localhost' is:
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Connecting to localhost...
> > ......
> > Received message too long 1165518179
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 
> > 5.)
> > info: 1165518179 = 0x45786563 = "Exec" !!!!
> 
> This is what I have been trying to tell you, note that the above will
> also break r{sh,exec} based programs and sftp.
> 
> Your shell initialisation should not print *anything* if your shell is
> not interactive.
> 
I have to agree here.  This goes for any shell.. csh, tcsh, bash, ksh,
ksh93, etc..

I really wish we could drop the requirement for the user's shell for
subsystem and require the admin to build a sane {PREFIX}/etc/enviroment
file (and let users override things in their ~/.ssh/enviroment.  Because
the subsystems can't really use the shell for anything useful.  It just
sucks off the enviroment variables.

- Ben