Moving Config folder data

[nick2016]

Hi,

I've moved users config folders from one server to another and when they try and access a SSH connection from the new server we get the following error:

debug1: Trying private key: /home/user1/.ssh/identity
debug1: Trying private key: /home/user1/.ssh/id_rsa
debug1: Trying private key: /home/user1/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
admin@blahblah password:

It works ok on the source server.

Any idea's ?

Thanks

[bgagnon]

Hello nick2016,

Are you reporting that public-key authentication is failing?

What version of SecureCRT was installed when you migrated the config folder?

If v7.3.x, did you use the new Export Settings... feature from Tools menu?

If an earlier version of SecureCRT (or you did not use Export Settings...), you will need to specifically copy the Identity (or other private key files associated with public-key authentication) since they are not in the config folder location, but instead in the .ssh directory.

You can check your upgrade eligibility at this URL.

[nick2016]

Yes, it looks like the key is failing.

We are using version 6.5.4 on both servers (We moved from Windows 2003 to Windows 2008), so it looks like the private key maybe missing, where is the .ssh directory ? Is that on the destination linux servers ?

Thanks

[bgagnon]

Hi nick2016,

Yes, .ssh is a default directory on Unix/Linux operating systems, so I am a little confused as to why you provided the (Open)SSH client debug lines.

The default location when *creating* a public/private key pair on SecureCRT/Windows varies according to OS.

You will need to look at the public-key properties of the session(s) in question to determine location of the files (see attached).

(Or Global Options / SSH2 category if defined globally.)

[nick2016]

Thanks, I'm not that familiar with the software, an end user supplied the file, but I see now how this hooks together.

I basically need to make sure they have the identity private and public key in their windows folder and also the correspsnding private key on the linux server.

[bgagnon]

Hello nick2016,

No, the *public-key file* is what is needed to configure the user's account on the remote server.

The private key file is just what the name implies. It is the private data and should be safeguarded accordingly. The *client* (ie: person/SFTP application) would retain the private key file.

[nick2016]

Oops, just noticed I got the private and public mixed up. Thanks for your help, re-generating new keys did the trick.