× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't think RDi tries to use the key.

In the below you are setting up to use SSH from the IBMi to a PC. The public key gets copied from the location you are connecting from to the location you are connecting to.

On an LPAR that I didn't have keys set up, I connected with SSH, and it required me to use my password. I created a secure connection to the LPAR in RDi, and connected. If I was connected, and sshd wasn't running on the IBMi, then it prompted me to start sshd. If I was connected, and sshd was running, it just debugged normally. If I wasn't connected, and started debug, it prompted me for a user name and password. I created new keys on my PC ( running Ubuntu 20.04 ) and put the public key in my home directory on the IBMi in the .ssh/authorized_keys file. I was able to SSH from the PC to the IBM i without having to use a password. I added the key to the SSH section of RDi, and reran all my tests, and got the exact same results.


I'm not able to test from ACS because I've always gotten an error when I launch SSH from there. It tells me that one of the parms on the SSH command is invalid, but it doesn't show the command, so I don't know what it trying to do that is invalid. As I am running linux for my workstation, I almost always have a terminal up, so it hasn't been a problem for me to just manually connect.

On Tue, 2020-05-05 at 13:06 +0000, Justin Taylor wrote:

The keys are working for anything. Based on the feedback I got from the main MIDRANGE-L list, I think this might be the wrong direction overall. I removed the keys I created and contacted IBM support.


Thanks




-----Original Message-----

From: Justin Taylor [mailto:

<mailto:JUSTIN@xxxxxxxxxxxxx>

JUSTIN@xxxxxxxxxxxxx

]

Sent: Monday, May 04, 2020 12:55 PM

To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <

<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>

wdsci-l@xxxxxxxxxxxxxxxxxx



Subject: Re: [WDSCI-L] SSH for SEP debug


I went thru the steps on IBMi to create a key, and I copied the contents from IBMi (~/.ssh/id_dsa.pub) to a new file on my PC (c:\users\user_name_here\.ssh\authorized_keys). Unfortunately, it didn't make a difference. I'm still get the popup message in RDi.


Does anyone know where I went wrong?


Thanks






[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.