RE: Calling a program on the i via OpenSSH -- MIDRANGE-L

Basic key security says that you should create the key on the client, not
the server. They private key should never be shared with other systems.

----- Original message -----
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: RE: Calling a program on the i via OpenSSH
Date: Mon, Feb 4, 2019 11:29 AM

The process is about the same, and as Chris pointed out as well, very
easy
if not a bit meticulous.

The trick is to create the key on the IBM i side. See:

[1]http://www-01.ibm.com/support/docview.wss?uid=nas8N1012710

You'll see almost the same process is followed. That document is a bit
old
but updated through 7.2.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Monday, February 04, 2019 10:46 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH

Doesn't this configure the HMC being the host and the iSeries being the
client? I need the other way around. The iSeries will be my host.
There
will be a Window or Linux box connecting to the iSeries.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jim
Oberholtzer
Sent: Monday, February 4, 2019 11:31 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH

There is an excellent tutorial, however while its purpose is slightly
different than your ultimate needs, the first part, setting up the SSH
is
the same.

Find the technote: "Sending HMC commands from a CL program":

[2]http://www-01.ibm.com/support/docview.wss?uid=nas8N1019126

There is specifically a section on setting up openssh in there.

Clearly the rest of it can be of interest since the HMC is a Linux
appliance. Works from Winders too.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Monday, February 04, 2019 10:02 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH

Can someone post a link that shows how to set up OpenSSH public /
private
keys with the iSeries being the server and a Windows machine being the
client? I don't understand how to configure keys (I'm definitely out of
my
league on this) and the only examples that I can find are iSeries to
iSeries
or the iSeries as a client and that's not helping me with the Windows
part.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Justin
Taylor
Sent: Monday, February 4, 2019 9:02 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH

Can't you just autostart *SSHD?

I don't have *SECOFR and I can start *SSHD.

-----Original Message-----
From: smith5646midrange@xxxxxxxxx
[[3]mailto:smith5646midrange@xxxxxxxxx]
Sent: Saturday, February 02, 2019 11:24 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH

Since STRTCPSVR *SSHD has to be run by a secofr profile (unless I am
reading
the internet incorrectly), I am looking for best practice for starting
it
when the system IPLs. Is there a reason not to add it to QSTRUP and
compile
it with a *secofr profile with adopt *owner auth? Is there some other
option that I am not finding during my research on automating it's
startup?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [4]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[5]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
[6]https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [7]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[8]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
[9]https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [10]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[11]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
[12]https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [13]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[14]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
[15]https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [16]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [17]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [18]https://amazon.midrange.com

References

Visible links
1. http://www-01.ibm.com/support/docview.wss?uid=nas8N1012710
2. http://www-01.ibm.com/support/docview.wss?uid=nas8N1019126
3. mailto:smith5646midrange@xxxxxxxxx
4. https://lists.midrange.com/mailman/listinfo/midrange-l
5. https://archive.midrange.com/midrange-l
6. https://amazon.midrange.com/
7. https://lists.midrange.com/mailman/listinfo/midrange-l
8. https://archive.midrange.com/midrange-l
9. https://amazon.midrange.com/
10. https://lists.midrange.com/mailman/listinfo/midrange-l
11. https://archive.midrange.com/midrange-l
12. https://amazon.midrange.com/
13. https://lists.midrange.com/mailman/listinfo/midrange-l
14. https://archive.midrange.com/midrange-l
15. https://amazon.midrange.com/
16. https://lists.midrange.com/mailman/listinfo/midrange-l
17. https://archive.midrange.com/midrange-l
18. https://amazon.midrange.com/