I'm not seeing any ticket request. There is no kerberos traffic at all.
Can you try the official PuTTY instead?Thanks for your reply. I'm using the putty downloaded from here:
It does.Is PuTTY using the 'native' SSPI functionality provided by Windows?
The official does not. Only the development version does (the once I've sent you link to).If I read the link on this page correctly:
The 'official' version of PuTTY doesn't support SSPI...
WinSCP used to use this implementation of Kerberos/SSPI in past. In 4.2 we switched to official PuTTY implementation, once they have it.Please see:
So if you set this option, does PuTTY work with SSPI on its own? Or do you still need to start the session using Quest PuTTY? Btw, all the option does is that it fills the username ( Connection > Data > Auto-login username) with your Windows username.So I did a diff on the registry keys and found that:
UserNameFromEnvironment must be set to 1.
Connection > Data > When username is not specified > Use system usernameIf that is configurable via the gui I cannot find it.
So just try to enter your Windows username into username field in WinSCP.WinSCP does NOT connect.
I suppose PuTTY is just getting the user name from Windows.
Not yet.Has support for auto detection of current username been completed?
You can post new topics in this forum