ssh - sshd

[Andi B.]

I want to set up a ssh server on my system. I've not much experience with SSH until now. I installed the openssh packages (yum install openssh-servers ..) but can't start the daemon.

I tried all combinations with or without path like p:\usr\sbin\sshd.exe or P:/usr/sbin/sshd.exe ... but I get always -

Code: [Select]

sshd re-exec requires execution with an absolute path

Anyone running successfully an ssh server on OS/2?

[David McKenna]

Hi Andi,

 Just tried it myself and got the same result (no previous experience here either). Strangely enough, the last commit by Sylvan on the 'openssh-portable' BWW github site had to do with absolute paths on OS/2 (March 9, 2021). So my guess is it wasn't enough (or not released in a binary). Probably worth filing a bug report...

Regards,

[Dave Yeo]

It seems to me that only a certain EMX build really worked, at least without too many dependencies. IIRC, EMX had better terminal support as well.

[Jan-Erik Lärka]

I do use ssh(d) on my machines to connect to/from.
Rewrote a rexx script for an earlier release for setup (installation, configuration and various program icons).
I have the new version installed, but use the previous until the new one behave as expected.

[Dave Yeo]

I do use ssh(d) on my machines to connect to/from.
Rewrote a rexx script for an earlier release for setup (installation, configuration and various program icons).
I have the new version installed, but use the previous until the new one behave as expected.

Which version are you using? ssh --version might be informative

[Jan-Erik Lärka]

ssh -v

OpenSSH_5.3p1, OpenSSL 0.9.8k 25 Mar 2009

[Edmund Wong]

I tried using Security/2 but there was a lot of stuff that didn't seem to work well.  So I am trying the openssh rpm
packages.

While I installed "openssh-server",  I too am having issues with getting it to work.
Unfortunately, a lot of the searches have brought me to *nix based solutions.

C:\usr\sbin\sshd gives me the same error as everyone; that is, "sshd re-exec requires execution with an absolute path"

Edmund

[Rick Smith]

Greetings,

I have been trying to get ssh to work for a year or so now, but it just wont behave or work correctly so I gave up on it..

Rick

[Dave Yeo]

Has anyone filed an issue at Bitwise's github? Things don't get fixed without the developers knowing there's a problem. My guess it did what the porter wanted so he was happy.

[Sean Casey]

Haven't used OpenSSH server on OS/2, but the v.5.3 client worked well as did OS/2 ZOC with Linux OpenSSH v.7 servers.   It seems OpenSSH v.8.9 server, which I'm now using on my Linux machines, no longer allows a workaround for the older key exchanges/ciphers supported by OS/2.  Was using diffie-hellman and DSA with overrides in sshd_config, but these no longer work with OpenSSH v.8 with my config overrides.

Recently installed the OS/2 v.7 OpenSSH client, but I preferred using ZOC.  I need to look into the possibility of not passing my OS/2 term environment variable "os2ansi" with SSH as this causing me issues in Linux (e.g., seeing junk characters using vi).   

Update:  I manually set ANSI for my SSH session which helped with vi, but keyboard mapping is borked while working in vi.   Keyboard mapping is on the client side, so something is off on my v.7 OS/2 SSH client. I'll come back to this in the future as I don't need SSH on OS/2. 

[SoundChaser]

Thank you Sean for sharing your results!

[Andi B.]

I just had the opportunity to test sshd on win. It shows the same message -

Code: [Select]

....apps\git\usr\bin] sshd
sshd re-exec requires execution with an absolute pathSo this seems to be
- no bug or
- cross platform bug or
- a user command error or
- a feature.

This is with latest openssh which comes with the win git version from yesterday.

Maybe we simply do not know how to install/use sshd correctly?

Probably I've stated before I've nearly no clue about all these ssh things. But in the meantime I played a bit. I did successfully connect from OS/2 to one linux box with the openssh5.3 version. But still can't get a sshd running on OS/2.

[Dave Yeo]

OK, I got further, seems it expects the directory separators to be / and it doesn't understand drive letters.

Code: [Select]

H:\tmp>sh
# w:/usr/sbin/sshd
sshd re-exec requires execution with an absolute path
# cd w:
# pwd
w:
# /usr/sbin/sshd
sshd: no hostkeys available -- exiting.
#

So use sh.exe and make sure you are on the @unixroot drive. Pwd command says your current directory

[Andi B.]

Thanks. I will make more test the next days/weeks.

Key creation works. Although I'm not sure were is the best place to keep them. %etc% (M:\mptn\etc or P:\etc - boot drive or unixroot) or %home% (E:\home\default) in my case. Have to play with this. But it clearly shows my decision to keep boot drive, rpm/%unixroot% and data separated on different drives may introduce additional problems linux guys do not have.

[Dave Yeo]

Not sure about the keys, I'd assume %HOME% or /@unixroot/etc.
sh does understand @unixroot,

Code: [Select]

H:\>sh
# /@unixroot/usr/sbin/sshd
sshd: no hostkeys available -- exiting.
and also ~ as %HOME%

Code: [Select]

# ls ~
Desktop  Downloads  FCCACHE.INI  kalendar  ml.xspf  rpmbuild  tea  vlcrc
#

Edit:  Also understands @tmpdir, as %TMP% or %TMPDIR%

Code: [Select]

# ls /@tmpdir/
dooble.exe                   etilqs_4yGYScugU0IZ2IH3MKBQ
etilqs_36wWySOaKwG594uBEuBx  runtime-root
#