OpenSSH sshd on x86
-
Topic author - Valued Contributor
- Posts: 62
- Joined: Sun Jun 16, 2019 7:55 am
- Reputation: 6
- Location: Zurich
- Status: Offline
- Contact:
OpenSSH sshd on x86
Is there a simple-to-follow explanation of how to set up OpenSSH on OpenVMS 9.1?
I got TCP/IP working plus telnet server, but no OpenSSH so far. I don't want to experiment unless necessary.
I got TCP/IP working plus telnet server, but no OpenSSH so far. I don't want to experiment unless necessary.
Last edited by mister.moderator on Wed May 24, 2023 3:55 am, edited 3 times in total.
-
- VSI Expert
- Valued Contributor
- Posts: 55
- Joined: Wed Jul 21, 2021 9:14 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
which OpenSSH kit? (1A, 1B, 1C)
1) install kit via PRODUCT command. good idea to do this AFTER TCPIP is installed.
2) modify SYSTARTUP_VMS.COM to execute SYS$STARTUP:SSH$STARTUP. I put this immediately after the TCPIP startup.
2a) if the 1A kit, prefix the SSH$STARTUP with @SYS$STARTUP:SSH$DEFINE_ROOT. (fixed in 1B+).
3) any configuration options go into SSH_CONFIG or SSHD_CONFIG, found in SSH$ROOT:[ETC.TEMPLATES].
4) add @SSH$ROOT:[BIN]SSH$DEFINE_COMMANDS to SYLOGIN.COM or LOGIN.COM; this declares the ssh-related command symbols, superseding some from the TCPIP startup.
OpenSSH uses a [.SSH] directory for it's files. Also, public-key operations work differently; they don't use the AUTHENTICATION and IDENTIFICATION files. See openssh.org for documentation.
1) install kit via PRODUCT command. good idea to do this AFTER TCPIP is installed.
2) modify SYSTARTUP_VMS.COM to execute SYS$STARTUP:SSH$STARTUP. I put this immediately after the TCPIP startup.
2a) if the 1A kit, prefix the SSH$STARTUP with @SYS$STARTUP:SSH$DEFINE_ROOT. (fixed in 1B+).
3) any configuration options go into SSH_CONFIG or SSHD_CONFIG, found in SSH$ROOT:[ETC.TEMPLATES].
4) add @SSH$ROOT:[BIN]SSH$DEFINE_COMMANDS to SYLOGIN.COM or LOGIN.COM; this declares the ssh-related command symbols, superseding some from the TCPIP startup.
OpenSSH uses a [.SSH] directory for it's files. Also, public-key operations work differently; they don't use the AUTHENTICATION and IDENTIFICATION files. See openssh.org for documentation.
-
- Contributor
- Posts: 22
- Joined: Fri Jun 28, 2019 6:12 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Hello Support Team,
I am getting below dump post openSSH installation during configuring phase.
VSI Dump Kernel SYSBOOT Mar 8 2022 14:47:10
**** OpenVMS x86_64 Operating System E9.2 - BUGCHECK ****
** Bugcheck code = 000003C0: SSRVEXCEPT, Unexpected system service exception
** Crash Time: 15-APR-2022 15:59:13.12
** Crash CPU: 00000002 Primary CPU: 00000000 Node Name: GE2105
** Highest CPU number: 0000003F
** Active CPUs: 00000000.0000000F
** Current Process: "SSHD22_BG52"
** Current PSB ID: 00000001
** Image Name: DSA0:[SYS0.SYSCOMMON.OPENSSH.][SBIN.X86_64]SSH$SSHD.EX
E;1
** Dumping error logs to system disk shadow set member $1$DKB0:
** Error logs dumped to $1$DKB0:[SYS0.SYSEXE]SYS$ERRLOG.DMP
** (used 1028 out of 1040 available blocks)
** Dumping memory to system disk shadow set master member $1$DKB0:
**** Starting compressed selective memory dump at 15-APR-2022 15:59:18.16 ****
................................................................................
................................................................................
................................................................................
..............
** System space, key processes, and key global pages have been dumped.
** Now dumping remaining processes and global pages...
................
** Memory dumped to $1$DKB0:[SYS0.SYSEXE]SYSDUMP.DMP
** (used 249227 out of 2601808 available blocks)
**** Completed compressed selective memory dump at 15-APR-2022 15:59:39.97 ****
** Time to initiate memory dump: 5.03
** Time to write memory dump: 21.81
Please suggest.
I am getting below dump post openSSH installation during configuring phase.
VSI Dump Kernel SYSBOOT Mar 8 2022 14:47:10
**** OpenVMS x86_64 Operating System E9.2 - BUGCHECK ****
** Bugcheck code = 000003C0: SSRVEXCEPT, Unexpected system service exception
** Crash Time: 15-APR-2022 15:59:13.12
** Crash CPU: 00000002 Primary CPU: 00000000 Node Name: GE2105
** Highest CPU number: 0000003F
** Active CPUs: 00000000.0000000F
** Current Process: "SSHD22_BG52"
** Current PSB ID: 00000001
** Image Name: DSA0:[SYS0.SYSCOMMON.OPENSSH.][SBIN.X86_64]SSH$SSHD.EX
E;1
** Dumping error logs to system disk shadow set member $1$DKB0:
** Error logs dumped to $1$DKB0:[SYS0.SYSEXE]SYS$ERRLOG.DMP
** (used 1028 out of 1040 available blocks)
** Dumping memory to system disk shadow set master member $1$DKB0:
**** Starting compressed selective memory dump at 15-APR-2022 15:59:18.16 ****
................................................................................
................................................................................
................................................................................
..............
** System space, key processes, and key global pages have been dumped.
** Now dumping remaining processes and global pages...
................
** Memory dumped to $1$DKB0:[SYS0.SYSEXE]SYSDUMP.DMP
** (used 249227 out of 2601808 available blocks)
**** Completed compressed selective memory dump at 15-APR-2022 15:59:39.97 ****
** Time to initiate memory dump: 5.03
** Time to write memory dump: 21.81
Please suggest.
-
- Master
- Posts: 197
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Hi,
tried to send you a PM in this forum, but it stays in my outbox and doesn't seem to get sent...
Could you please obtain the CLUE file from this crash, see CLUE$COLLECT:CLUE$GE2105_ddmmyy_hhmm.LIS and send it to me at volker (dot) halle (at) invenate (dot) de (as an attached file)
Thanks,
Volker.
tried to send you a PM in this forum, but it stays in my outbox and doesn't seem to get sent...
Could you please obtain the CLUE file from this crash, see CLUE$COLLECT:CLUE$GE2105_ddmmyy_hhmm.LIS and send it to me at volker (dot) halle (at) invenate (dot) de (as an attached file)
Thanks,
Volker.
Last edited by volkerhalle on Sat Apr 16, 2022 9:10 am, edited 1 time in total.
-
- Contributor
- Posts: 22
- Joined: Fri Jun 28, 2019 6:12 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Hello Volker,
I did receive your private message and replied the same with enclosing requested file.![Smile :)](./images/smilies/icon_e_smile.gif)
I did receive your private message and replied the same with enclosing requested file.
![Smile :)](./images/smilies/icon_e_smile.gif)
-
- Master
- Posts: 197
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Sorry, I've read your PM, but I can't locate any 'attached file' ?!
Volker.
PS: It looks like you can attach files to PMs, but the attached files do NOT show up in the PM in the Inbox. Bug or feature ?
Volker.
PS: It looks like you can attach files to PMs, but the attached files do NOT show up in the PM in the Inbox. Bug or feature ?
Last edited by volkerhalle on Sun Apr 17, 2022 1:57 am, edited 1 time in total.
-
- Master
- Posts: 197
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Crash footprint from CLUE file:
Crash Time: 16-APR-2022 04:09:07.72
Bugcheck Type: SSRVEXCEPT, Unexpected system service exception
Node: GE2105 (Standalone)
CPU Type: VMware, Inc. VMware7,1
VMS Version: E9.2
Current Process: PCSI$0413_I0004
Current Image: GE2105$DKB0:[SYS0.SYSCOMMON.OPENSSH.][BIN.X86_64]SSH$SSH-KEYGEN.EXE;1
Failing PC: 00000000.7B3AA5B9 RMISHR+800005B9
Failing PS: 00000000.00000000
Module: RMISHR
Offset: 800005B9
Exception Frame:
Exception taken at RIP 00000000.7B3AA5B9 from Kernel mode
Trap Type 0000000E (Page Fault)
Address = 00000000.7FF7B7A0 Prev Frame = 00000000.7FF7BC20
RAX = 00000000.000005A8 RDI = 00000000.000052CA RSI = 00000000.00043586
RDX = 00000000.000005A8 RCX = 00000000.00000080 R8 = 00000000.0000047B
R9 = 00000000.00002180 RBX = 00000000.7FF7BE00 RBP = 00000000.7FF7B9E0
R10 = 00000000.000052CA R11 = 00000000.7B3C45E0 R12 = 00000000.7FF7BB38
R13 = 00000000.00000010 R14 = 00000000.7B3C4630 R15 = 00000000.00000200
RIP = 00000000.7B3AA5B9 RSP = 00000000.7FF7B980 SS = 00000000.00000010
Signal Array: 64-bit Signal Array:
Arg Count = 00000005 Arg Count = 00000005
Condition = 0000000C Condition = 00000000.0000000C
Argument #2 = 00000000 Argument #2 = 00000000.00000000
Argument #3 = 000005A8 Argument #3 = 00000000.000005A8
Argument #4 = 7B3AA5B9 Argument #4 = 00000000.7B3AA5B9
Argument #5 = 00000000 Argument #5 = 00000000.00000000
Failing Instruction:
RMISHR+800005B9: movq (%rdx),%rdx
Either a possible bug in RMISHR or a bad call from SSH$SSH-KEYGEN
As the SDA extension CLUE$SDA.EXE, which creates the CLUE file, does not (yet) support the CLUE STACK command on OpenVMS x86-64, consider to manually obtain the call summary:
$ ANALYZE/CRASH sysdump.dmp
SDA> CLUE CALL
SDA> exit
This might allow to determine, which code has called into RMISHR. Please post this information, if available.
[PERFAPI]RMISHR implements the SYS$GETRMI system service. Even if there would be a bad call to SYS$GETRMI (bad parameters etc.) from SSH$SSH-KEYGEN, the system should not crash, but return an appropriate system service error code.
Volker.
Crash Time: 16-APR-2022 04:09:07.72
Bugcheck Type: SSRVEXCEPT, Unexpected system service exception
Node: GE2105 (Standalone)
CPU Type: VMware, Inc. VMware7,1
VMS Version: E9.2
Current Process: PCSI$0413_I0004
Current Image: GE2105$DKB0:[SYS0.SYSCOMMON.OPENSSH.][BIN.X86_64]SSH$SSH-KEYGEN.EXE;1
Failing PC: 00000000.7B3AA5B9 RMISHR+800005B9
Failing PS: 00000000.00000000
Module: RMISHR
Offset: 800005B9
Exception Frame:
Exception taken at RIP 00000000.7B3AA5B9 from Kernel mode
Trap Type 0000000E (Page Fault)
Address = 00000000.7FF7B7A0 Prev Frame = 00000000.7FF7BC20
RAX = 00000000.000005A8 RDI = 00000000.000052CA RSI = 00000000.00043586
RDX = 00000000.000005A8 RCX = 00000000.00000080 R8 = 00000000.0000047B
R9 = 00000000.00002180 RBX = 00000000.7FF7BE00 RBP = 00000000.7FF7B9E0
R10 = 00000000.000052CA R11 = 00000000.7B3C45E0 R12 = 00000000.7FF7BB38
R13 = 00000000.00000010 R14 = 00000000.7B3C4630 R15 = 00000000.00000200
RIP = 00000000.7B3AA5B9 RSP = 00000000.7FF7B980 SS = 00000000.00000010
Signal Array: 64-bit Signal Array:
Arg Count = 00000005 Arg Count = 00000005
Condition = 0000000C Condition = 00000000.0000000C
Argument #2 = 00000000 Argument #2 = 00000000.00000000
Argument #3 = 000005A8 Argument #3 = 00000000.000005A8
Argument #4 = 7B3AA5B9 Argument #4 = 00000000.7B3AA5B9
Argument #5 = 00000000 Argument #5 = 00000000.00000000
Failing Instruction:
RMISHR+800005B9: movq (%rdx),%rdx
Either a possible bug in RMISHR or a bad call from SSH$SSH-KEYGEN
As the SDA extension CLUE$SDA.EXE, which creates the CLUE file, does not (yet) support the CLUE STACK command on OpenVMS x86-64, consider to manually obtain the call summary:
$ ANALYZE/CRASH sysdump.dmp
SDA> CLUE CALL
SDA> exit
This might allow to determine, which code has called into RMISHR. Please post this information, if available.
[PERFAPI]RMISHR implements the SYS$GETRMI system service. Even if there would be a bad call to SYS$GETRMI (bad parameters etc.) from SSH$SSH-KEYGEN, the system should not crash, but return an appropriate system service error code.
Volker.
Last edited by volkerhalle on Mon Apr 18, 2022 1:20 am, edited 5 times in total.
-
- Master
- Posts: 197
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
The same crash has also been seen during OpenLDAP configuration with SLAPD as the current image/process.
-
- Master
- Posts: 197
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
The problem in the SYS$GETRMI system service has been fixed (for V9.2).
The problem is triggered by the value of SMP$GL_MAX_CPUID. If that value is greater or equal 32 (hex 20), the crash will happen.
** Highest CPU number: 0000003F
Trying to reduce this number could provide a workaround. The maximum no. of possible CPUs is most likely a parameter or feature of the VM or the virtualization host software.
Volker.
The problem is triggered by the value of SMP$GL_MAX_CPUID. If that value is greater or equal 32 (hex 20), the crash will happen.
** Highest CPU number: 0000003F
Trying to reduce this number could provide a workaround. The maximum no. of possible CPUs is most likely a parameter or feature of the VM or the virtualization host software.
Volker.
-
- Contributor
- Posts: 22
- Joined: Fri Jun 28, 2019 6:12 am
- Reputation: 0
- Status: Offline
Re: OpenSSH sshd on x86
Verified on system and could see below :
System: GE2106, VMware, Inc. VMware7,1
CPU ownership sets:
Active 0-3 ----> Configured 4 vCPU in VM configuration.
Configure 0-3
CPU state sets:
Potential 0-3
Autostart 0-63 ----> Wondering from where it's picking these values. Didn't notice it with V9.1.
Powered Down None
Not Present 4-63 ---> Same here.
Hard Excluded None
Failover None
@ VSI Support,
Could you please suggest any specific changes in VM configuration file ?
Looking forward your assistance. Thank you in advance.
System: GE2106, VMware, Inc. VMware7,1
CPU ownership sets:
Active 0-3 ----> Configured 4 vCPU in VM configuration.
Configure 0-3
CPU state sets:
Potential 0-3
Autostart 0-63 ----> Wondering from where it's picking these values. Didn't notice it with V9.1.
Powered Down None
Not Present 4-63 ---> Same here.
Hard Excluded None
Failover None
@ VSI Support,
Could you please suggest any specific changes in VM configuration file ?
Looking forward your assistance. Thank you in advance.