RE: Using SSH to communicate from IBM i to Windows -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Using SSH to communicate from IBM i to Windows
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 2 Oct 2019 17:36:09 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Ding! Ding! Ding!
Commenting out the two lines at the end of the sshd_config file and making them this
# Match Group administrators
# AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys
Did the trick!

Now I can get this to work:
CALL QP2TERM
ssh -T -v -v -v -i .ssh/id_rsa_user ADOPT@as2edi01 "dir >/users/ADOPT/testdirout.txt"
and it automatically dumps the directory listing to that file.

Thank you one and all!

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.