Forum » Support and Bug Reports »

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

martin

Re: Two-Factor Authentication

Please attach a full WinSCP session log file showing the authentication (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
yasin

Two-Factor Authentication

I started using Google Authenticator two-step verification to access my servers. I used to be able to use it with PuTTY with the Remember session password option and now that it's two-step verification it's impossible. But I found a problem, when I try to connect to PuTTY with WinSCP, PuTTY gives an error because it tries to enter my password saved in the Google authentication code. Because now when I try to log in with PuTTY it first asks for the verification code and then my SSH password. In other words, since WinSCP thinks the verification code is the SSH password, PuTTY gives an error without doing anything. Do you think a solution can be developed for this? When I try to log in with PuTTY, I just want to access my server by entering the Google security code.

When I enable two-step verification the login sequence is as follows... 
login as: yasin

Verification code:

Password:

Last login: Tue Apr 23 13:58:29 2022 from 172.16.25.125

[root@tecmint ~]#

Documentation

Support

Associations

Follow Us