You can use -oUserKnownHostsFile=/home/user/.ssh/known_hosts to share the known_hosts as well.
--
Sean Porterfield
-----Original Message-----
From: Chris Bipes
Sent: Friday, January 27, 2012 10:38
To: 'MIDRANGE-L@xxxxxxxxxxxx'
Subject: RE: SFTP Keys
Yes. But all these users will be signing on as the same person if you do that. You may not want your developers using the production logon to the production folder. Look at the contents of the key pair files. You will see the user ID within it. The user id is at the very end of the string.
There is also a way to put the known_host file into a root directory for all users, if my memory serves me today. I remember reading about it but not the details.
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: Gord Hutchinson
Sent: Friday, January 27, 2012 7:20 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: SFTP Keys
I am just beginning to follow Jeff down the SFTP trail.
We have a userid which is only used to run EDI in batch. In production, this will be the only user for SFTP. In addition, we have two EDI developers who may need to use the connection, especially during startup. In addition to that, we have a test and a development system.
After creating the key pairs can the .ssh folder be copied to the /home directory for different users and on different systems?
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
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.