new version of openssh ?

[rdunkle]

I see a the latest version of OpenSSH is 7.3, released 1 August 2016.  The latest version for OS/2 I can find is at Hobbes  5.3p1.  Is there a newer port available ?

[Greggory Shaw]

Also, an  updated Rysnc that works over SSh would be great !

[Paul Smedley]

Also, an  updated Rysnc that works over SSh would be great !

Hey guys. openssh relies on some terminal stuff that is present in EMX but not in klibc (IIRC). I think there were also some issues with select() that may be addressed by dmik's libcx

If we can get openssh working with klibc, rsync over ssh should work. rsync built with klibc won't work with an EMX build of openssh (or vice versa)

[Paul Smedley]

Hi Guys,

Also, an  updated Rysnc that works over SSh would be great !

Hey guys. openssh relies on some terminal stuff that is present in EMX but not in klibc (IIRC). I think there were also some issues with select() that may be addressed by dmik's libcx

If we can get openssh working with klibc, rsync over ssh should work. rsync built with klibc won't work with an EMX build of openssh (or vice versa)

I found a post from Dave Saville that confirmed my recollection of the issues with porting a recent openssh. With the introduction of a select() that works with file handles in libcx, I'll try recompiling openssh again. It may not be suitable as an ssh client due to the terminal stuff, but for use with things like rsync, the terminal stuff shouldn't matter.

Cheers,

Paul

[Paul Smedley]

Hi Guys,

Also, an  updated Rysnc that works over SSh would be great !

Hey guys. openssh relies on some terminal stuff that is present in EMX but not in klibc (IIRC). I think there were also some issues with select() that may be addressed by dmik's libcx

If we can get openssh working with klibc, rsync over ssh should work. rsync built with klibc won't work with an EMX build of openssh (or vice versa)

I found a post from Dave Saville that confirmed my recollection of the issues with porting a recent openssh. With the introduction of a select() that works with file handles in libcx, I'll try recompiling openssh again. It may not be suitable as an ssh client due to the terminal stuff, but for use with things like rsync, the terminal stuff shouldn't matter.

The results don't quite match my memory.

There's an ssh.exe at http://smedley.id.au/tmp/ssh.zip

Terminal stuff is messed up, but it does appear to work.  No select() errors that I saw, if I linked it against libcx0 then I got an error connecting to the host....

I'd be interested to see if this works with rsync....

[rdunkle]

Maybe something is missing:

[c:\tmp\ssha]ssh -l testuser sky10
You don't exist, go away!

[Greggory Shaw]

Thx, Paul for the info and I'll test it out.

[Greggory Shaw]

Here is what I get:

Code: [Select]

rsync -v -e ssh e:/tmp/test.txt root@192.168.1.100:/home/root

Code: [Select]

[[E:\TMP\UNZIP\SSH]rsync -av -e "ssh" e:/tmp/test.txt root@192.168.1.100:/home/root

ssh: invalid option -- -
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-e escape_char] [-F configfile]
           [-I pkcs11] [-i identity_file]
           [-L [bind_address:]port:host:hostport]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-R [bind_address:]port:host:hostport] [-S ctl_path]
           [-W host:port] [-w local_tun[:remote_tun]]
           [user@]hostname [command]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=
3.0.9]



NOTE: using the old ssh I get the same rsync error, but ssh connects correctly.

Is there a bug with rsync 3.09 ?

https://cygwin.com/ml/cygwin/2011-12/msg00529.html


Greggory

[Paul Smedley]

Maybe something is missing:

[c:\tmp\ssha]ssh -l testuser sky10
You don't exist, go away!

I refreshed the zip that will hopefully address this...

[Paul Smedley]

Hi Greggory,

Here is what I get:

Code: [Select]

rsync -v -e ssh e:/tmp/test.txt root@192.168.1.100:/home/root

Code: [Select]

[[E:\TMP\UNZIP\SSH]rsync -av -e "ssh" e:/tmp/test.txt root@192.168.1.100:/home/root

ssh: invalid option -- -
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-e escape_char] [-F configfile]
           [-I pkcs11] [-i identity_file]
           [-L [bind_address:]port:host:hostport]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-R [bind_address:]port:host:hostport] [-S ctl_path]
           [-W host:port] [-w local_tun[:remote_tun]]
           [user@]hostname [command]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=
3.0.9]



NOTE: using the old ssh I get the same rsync error, but ssh connects correctly.

Is there a bug with rsync 3.09 ?

https://cygwin.com/ml/cygwin/2011-12/msg00529.html

No idea - I'll have to setup a rsync server on by Ubuntu box and test locally....

[Greggory Shaw]

Here's what i get from linux (the old ssh conects, but rsync still fails) :

[E:\TMP\UNZIP\SSH(1)]ssh root@159.xxxxxxxxxxx
Could not create directory '/nonexistent/.ssh'.
The authenticity of host '159.xxxxxxxxx (159.xxxxxxxxxx)' can't be established.

ECDSA key fingerprint is 57:aa:23:31:79:11:e1:31:e4:49:xxxxxx.
Are you sure you want to continue connecting (yes/no)?
[E:\TMP\UNZIP\SSH(1)]ssh root@159.xxxxxxxx
Could not create directory '/nonexistent/.ssh'.
The authenticity of host '159.xxxxxxxxx (159.xxxxxxxxxxx)' can't be established.

ECDSA key fingerprint is 57:aa:23:31:79:11:e1:31:e4:49:bcxxxxxxxxxxxx.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/nonexistent/.ssh/known_hosts
).
root@159.2xxxxxxxxxxxxx's password:
tcgetattr: Invalid argument

This is different ?
Could not create directory '/nonexistent/.ssh'.

https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/988144

[Andi B.]

Anyone found out why this ssh now wants this wrong directory /nonexistent/.ssh?

Older ssh-keygen put it in ~/.ssh which is on my system e:\\HOME\\DEFAULT/.ssh/...  Yes this strange mix of \\ and / worked with older version.

Should we create a new user nonexistent instead the old default? Or is there a new environment variable for this?

[Andi B.]

Okay found a solution for this one in the issue tracker - https://github.com/bitwiseworks/openssh-portable/issues/1

Use the klibc user manager and point the home directory of root to your usual home directory (e:\HOME\default on my machine).