|
cd /home$
ls -ladrwxr-sr-x 3 adopt 0 8192 Oct 01 16:24 ADOPT
cd ADOPT$
ls -latotal 128
drwxr-sr-x 3 adopt 0 8192 Oct 01 16:24 .
drwxrwsrwx 33 qsys 0 32768 Oct 01 23:01 ..
-rw------- 1 adopt 0 624 Oct 02 09:30 .sh_history
drwx--S--- 2 adopt 0 8192 Oct 02 08:50 .ssh
cd .ssh
$
> ls -la
-rw------- 1 adopt 0 1675 Oct 02 08:50 id_rsa_user
-rw-r--r-- 1 adopt 0 408 Oct 02 08:50
id_rsa_user.pub
-rwxrwxrwx 1 craigs 0 1407 Oct 02 09:04 known_hosts
-rwxrwxrwx 1 craigs 0 741 Jan 05 2016 known_hosts2
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jack Woehr
Sent: Wednesday, October 2, 2019 10:35 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Using SSH to communicate from IBM i to Windows
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Most common problem is file permissions in/on the .ssh directory.
On Wed, Oct 2, 2019 at 8:23 AM Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:
Your log shows that it offered the key, and the server came back and said
give me something else.
--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
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: 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 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: 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: 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 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: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.