Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

msorens

Re: ppk file relocation causing minor problems

I found it :-) And, yes, that fixed it--thanks.
msorens

Re: ppk file relocation causing minor problems

Could you point me to where to remove the key stored in the session?
martin

Re: ppk file relocation causing minor problems

You probably have the private key file configured in the stored session with the old path. So it complains that it cannot use the configured file. However, then it finds it in pagent and connects with that. If you use pagent, you do not need to have the key specified in the session directly.
msorens

ppk file relocation causing minor problems

I installed WinSCP 3.5.6 sometime ago when I also installed putty and pageant. At the time I had my private key file (ppk) in one directory (let's call this dirA). Some time later I moved the ppk file to a different directory, and told pageant where the "new" key now was located (dirB). Pageant, putty, and WinSCP were all happy with that. Today I upgraded WinSCP to 3.8.2. When I started it, it complained about the ppk file being missing from dirA. And yet it was then able to connect just fine.
After a period of inactivity the session timed out. I clicked on reconnect, and again it complained, and again it connected.
So how and where do I adjust so it no longer complains and just connects?