scp/sftp weirdness
Damien Miller
djm at mindrot.org
Fri Jul 7 12:58:24 EST 2006
I told you: your sftp and scp binaries are using the wrong ssh binary.
sftp and ssh set a number of options when invoking ssh. PermitLocalCommand
is one of them.
On Thu, 6 Jul 2006, Erich Weiler wrote:
> Also the "PermitLocalCommand" option doesn't appear anywhere in my ssh_config
> or sshd_config... What could be specifying that option I wonder?
>
> ciao, erich
>
> Erich Weiler wrote:
> > As a matter of fact I do have 2 versions of OpenSSH lurking around (but no
> > Sun SSH, I didn't install it). Maybe the new sftp is trying to reference
> > the old ssh? I did a 'which ssh' and 'which sftp' and they are both in the
> > right place... Does sftp reference anything else but ssh? sftp-server
> > maybe?
> >
> > The reason I have 2 versions is that my older Solaris clients are using the
> > old one and the newer Solaris 10 boxes are (trying to) using the new one.
> >
> > ciao, erich
> >
> > Damien Miller wrote:
> > > On Thu, 6 Jul 2006, Erich Weiler wrote:
> > >
> > > > Hi ya'll-
> > > >
> > > > I'm having this weird problem with the new version of OpenSSH compiled
> > > > on Solaris, version 4.3p2. SSH and SSHD work fine, all is well. But
> > > > when I try to sftp or scp something I get this:
> > > >
> > > > % sftp bullitt
> > > > Connecting to bullitt...
> > > > command-line: line 0: Bad configuration option: PermitLocalCommand
> > > > Connection closed
> > >
> > > It looks like you have your scp/sftp out of sync with your ssh binary.
> > > Perhaps OpenSSH scp/sftp are picking up Solaris' default ssh binary
> > > because it is first in your $PATH?
> > >
> > > -d
> >
>
> --
> ===================================
> Erich Weiler
> UNIX Systems Administrator
> School of Engineering
> University of California Santa Cruz
> weiler at soe.ucsc.edu
> ===================================
>
More information about the openssh-unix-dev
mailing list