How long should we wait until you answer this one ;-)
Sorry.
Is it becuase you are running in SSH1 compatability mode? Is the '-D' option available
in the SSH1 version?
It appears that when you issue the '-h', it tells you the SSH2 mode, since your only
asking for help and not actually doing something.
I'm new to this and it was just a thought.
Best of Luck,
Robert
Robert P. MacDonald, Network Engineer
Gordon Food Service
Voice: 616.261.7987 email: [EMAIL PROTECTED]
>>> "Auteria Wally Winzer Jr." <[EMAIL PROTECTED]> 11/09/99 12:30AM >>>
I figured this one out also.
I need to add the "-1" option exclusively to scp.
It worked like a charm.
Now another unusual problem:
When I try to add the "-D 3" or "-D 4" option to scp,
it complains that this option is wrong, yet it shows in
the man pages the -D is a valid option.
What gives?
This is how I'm using it:
scp -D 4 -1 * [EMAIL PROTECTED]:/export/home1/wwinzer/solaris2.6/rpm
warning: Executing scp1 compatibility.
scp: illegal option -- D
usage: scp [-qQaAprvBCL] [-S path-to-ssh] [-o ssh-options] [-P port] [-c cipher] [-i
identity] f1 f2; or: scp [options] f1 ... fn directory
But, when I type scp -h:
usage: scp [-D debug_level_spec] [-d] [-p] [-n] [-u] [-v] [-1]
[-c cipher] [-S ssh2-path] [-h] [-P ssh2-port]
[[user@]host[#port]:]file ...
[[user@]host[#port]:]file_or_dir
Options:
-D debug_level_spec Set debug level.
-d Force target to be a directory.
-q Make scp quiet (doesn't show progress indicator).
-p Preserve file attributes and timestamps.
-n Show what would've been done without actually copying
any files.
-u Remove source-files after copying.
-v Verbose mode; equal to `-D 2'.
-1 Engage scp1 compatibility.
-c cipher Select encryption algorithm. Multiple -c options are
allowed and a single -c flag can have only one cipher.
-S ssh2-path Tell scp2 where to find ssh2.
-P ssh2-port Tell scp2 which port sshd2 listens on the remote machine.
-h Display this help.
So, the -D option is supposed to be valid.
Thanks.
- WWinzer Jr.
"Auteria Wally Winzer Jr." wrote:
> I'm using ssh2 exclusively in ssh1 compatibility mode.
> When I try to scp to another system running 1.2.27,
> I get the following error:
>
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[0] = ssh2
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[1] = -l
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[2] = wwinzer
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[3] = -v
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[4] = -o
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[5] = passwordprompt
> %U@%H's password:
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[6] = -o
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[7] = nodelay yes
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[8] = wahleewhirl.com
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[9] = -s
> debug: Scp2/scp2.c:1364/scp_open_remote_connection: argv[10] = sftp
> debug: connecting to wahleewhirl.com...
> debug: ssh_client_wrap: creating transport protocol
> debug: ssh_client_wrap: creating userauth protocol
> debug: entering event loop
> debug: Ssh2Transport/trcommon.c:592/ssh_tr_input_version: Remote version:
> SSH-1.5-1.2.27
> debug: Remote version: SSH-1.5-1.2.27
> Executing /usr/local/bin/ssh1 for ssh1 compatibility.
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[0] = ssh
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[1] = -l
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[2] = wwinzer
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[3] = -v
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[4] = -o
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[5] =
> passwordprompt %U@%H's password:
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[6] = -o
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[7] = nodelay
> yes
> debug: Ssh2Client/sshclient.c:425/ssh_client_version_check: args[8] =
> wahleewhirl.com
> SSH Version 1.2.27 [sparc-sun-solaris2.6], protocol version 1.5.
> Compiled with RSAREF.
> command-line line 0: Bad configuration option.
> debug: ssh_sigchld_real_callback
> debug: ssh_sigchld_process_pid: calling handler pid 714 code 255
> debug: ssh_pipe_sigchld_handler: pid 714 status 255
> debug: ssh_pipe_sigchld_do_callback
> debug: ssh_pipe_stream_read: faking eof after sigchld
> Connection lost.
>
> Where is the "command-line line 0: Bad configuration option." error coming from?
>
> I checked both ssh1 and ssh2 on the system sending the data as well
> as the system receiving the data and I can not find any errors within
> the config files.
>
> Thanks. In the meantime I'll use scp1.
>
> But, I can scp from another system using version 1 onto the SSH server
> running version 2 with no problems as long as the server running SSH2
> is in SSH1 compatibility mode.
>
> - Wally Winzer Jr.
