SCP not working

6 posts / 0 new
Last post
psomers
Offline
Last seen: 6 years 5 months ago
Joined: 16.01.2012 - 21:55
SCP not working

Installed Copssh on the Windows 7 partition of a dual-boot PC. Other partition is XP.

SCP from IBM System i to server is failing. Having limited familiarity with Linux and SSH, I'm uncertain about the cause of the problem and the following client-side log entries. Also, the end of the log contains two unusual-looking entries.

Any help would be much appreciated. Let me know if any more information is needed.

Thank you.

<code>$ anonymized by tk
.....
debug1: Connection established.
.....
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9
debug1: match: OpenSSH_5.9 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 122/256
debug1: bits set: 1010/2048
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'xx.xx.xx.xx' is known and matches the RSA host key.
debug1: Found key in /HOME/xxxxx/.ssh/known_hosts:4
debug1: bits set: 1053/2048
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
.....
debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 2003c920 hint 1
debug1: read PEM private key done: type RSA
debug1: ssh-userauth2 successful: method publickey
debug1: fd 5 setting O_NONBLOCK
debug1: fd 6 setting O_NONBLOCK
debug1: channel 0: new
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
.....
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
 ]0;~
 [32mxxxxxxx  [33m~ [0m
$</code>

itefix
Online
Last seen: 2 min 7 sec ago
Joined: 01.05.2008 - 21:33
Can you send contents of

Can you send contents of etc/passwd and bin/copssh.config via the internal mailer (just click on my login and select -contact- tab). In the meantime you may also try to run Copssh in debug mode to see of some weird messages come up. Recipe is available at FAQ https://www.itefix.no/i2/node/11759.

psomers
Offline
Last seen: 6 years 5 months ago
Joined: 16.01.2012 - 21:55
Thank you for you prompt

Thank you for you prompt attention to this problem.

 

anonymized by tk

etc/passwd contents

.....

 

bin/copssh.config contents


Port=22
Compression=delayed
LogLevel=INFO
TCPKeepAlive=yes
LoginGraceTime=120
Protocol=2
MaxAuthTries=6
MaxSessions=10


Enabled=yes
SftpMode=internal-sftp
ReadOnly=no
LogLevel=INFO
LogDestination=eventlog


EventsTimeWindow=2 days


Linux shell and Sftp=-
Sftp=internal-sftp
Linux shell=/bin/bash --login -i
Windows shell=/cygdrive/c/windows/system32/cmd.exe
No shell access=/bin/false




Command=Linux shell
PasswordAuthentication=no
PubkeyAuthentication=yes
AllowTcpForwarding=yes

itefix
Online
Last seen: 2 min 7 sec ago
Joined: 01.05.2008 - 21:33
You've activated your user

You've activated your user for only bash login which doesn't support copying operations: It allows only an interactive terminal. You'll be fine if you activate your user with access type Linux shell and SFTP.

psomers
Offline
Last seen: 6 years 5 months ago
Joined: 16.01.2012 - 21:55
WORKED as advertised. Thank

WORKED as advertised. Thank you for your fine service.

Another question: Can the time in the event viewer be synced with the windows clock?

itefix
Online
Last seen: 2 min 7 sec ago
Joined: 01.05.2008 - 21:33
Fine. I close the case then.

Fine. I close the case then. Regarding eventlog timestamps, I will check if there is a bug or a feature request and register it accordingly. I will let you know then. Btw, I've anonymized your posts to avoid information leakage :-).