Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emulated Pageant not accessible for WinSCP / PuTTY #206

Closed
kamikatze13 opened this issue Dec 9, 2017 · 3 comments
Closed

Emulated Pageant not accessible for WinSCP / PuTTY #206

kamikatze13 opened this issue Dec 9, 2017 · 3 comments

Comments

@kamikatze13
Copy link

Possibly related to #193

Stumbled across this plugin and gave it a shot, since I'm using Pageant and KeePass already.

After setup of the key in Keepass / KeeAgent, both WinSCP as well as PuTTY fail with "No supported auth methods available (server sent: publickey)", as if Pageant wasn't running. Key is loaded in KeeAgent, however.

Starting Pageant while KeePass is open to add the key fails with "The already running Pageant refused to add the key". So Pageant is running, after all?

Closing KeePass and running Pageant with the same key works fine.

KeeAgent 0.8.1.0
KeePass 2.37
WinSCP 5.9.6
Putty 0.65
Windows 1709 Build 16299.64

@markschuh
Copy link

Setup works perfect for me - but with newer tool versions (execpt KeePass)

My ideas to narrow down the root cause:

Both KeePass (with KeeAgent) and PuTTY/WinSCP run under the same user - right?

What type of key have you used? Test again with a RSA 2048bit key to avoid key type caused issues.

Have you noticed, your Putty and WinSCP versions are quite outdated? I suggest you update and try again. Also the KeeAgent Beta (0.9.1.0) is worth a quick try, if an upgrade solves your problem. But to be true, I doubt your problem is caused by outdated version - AFAIK not much had happend in the Pageant communication over time.

Additionally you might play with "Client" vs "Agent" mode of KeeAgent. Of course "Agent" and full replacement of pageant by KeeAgent is the final target - but testing the different possible combinations may help to narrow down the root cause of the issue in your installation or potentially identify a workaround setup. Compare https://lechnology.com/software/keeagent/usage/options-and-settings/

@kamikatze13
Copy link
Author

Thanks for your reply, i finally managed to find time to try and fix the issue.

the problem was the key length: i went a little overboard with 4096b - 2048b worked first try.

@kamikatze13
Copy link
Author

addendum: it worked only once for some reason.

since you mentioned whether the applications run under the same user, i tried to run keepass/putty/winscp elevated - one at a time as well as all of them.

both winscp as well as putty can reliably authenticate with keeagent if they run elevated/as admin, even the 4096b key works. i am fairly sure keepass is not run as admin, though.

also, i should add, i updated all of the software mentioned to their newest stable versions:
winscp 5.13.1
putty 0.70
keepass 2.38
keeagent 0.10.1
windows 1709 build 16299.371

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants