Skip to content
New issue

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

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

Already on GitHub? # to your account

Auto login failed, please try again. #70

Closed
karagi4 opened this issue Apr 1, 2021 · 19 comments
Closed

Auto login failed, please try again. #70

karagi4 opened this issue Apr 1, 2021 · 19 comments
Assignees
Labels
bug Something isn't working

Comments

@karagi4
Copy link

karagi4 commented Apr 1, 2021

WindTerm 2.0.2
Auto login failed, please try again.
2021-04-01 18-54-29 WindTerm

@karagi4
Copy link
Author

karagi4 commented Apr 1, 2021

In version 2.0.2, this error appeared and it does not go away!

@kingToolbox
Copy link
Owner

In order to fix 2FA login issue in version 2.0.2, almost the entire automatic login module was rewritten. Although rigorous testing has been performed, new errors may have been introduced :(

So, what does this automatic login include? Is it a password, a public-key, a keyboard-interactive, or a mix? Is this automatic login created by copying the profile folder from the old version, or is it generated by selecting Auto login next time when logging in in the 2.0.2 version?

In addition, please follow the steps below to see if the issue can be fixed:

  • Open the session property dialog, then click SSH - Authentication - Saved automatic authentication - Clear button to clear the auto login.
  • Restart the session and log in with Auto login next time checked.
  • Restart the session again to see if it can be automatically logged in successfully.

@karagi4
Copy link
Author

karagi4 commented Apr 1, 2021

image

I use this, the login happens, but the next time it asks for confirmation again.

@karagi4
Copy link
Author

karagi4 commented Apr 1, 2021

I also removed the session.autoLogin parameter in the user.sessions file but it doesn't help, authorization is still requested
image

@karagi4
Copy link
Author

karagi4 commented Apr 1, 2021

From version 1.9 to 2.0.1, the profile migrated well. Version 2.0.1 works and does not ask for re-confirmation

@karagi4
Copy link
Author

karagi4 commented Apr 1, 2021

On a new installation of version 2.0.2 without transferring settings, when connecting via an ssh key, auto-login also does not work :(

@kingToolbox
Copy link
Owner

If my understanding is correct, do you mean that you cannot use pageant to automatically log in? This problem does exist, I have reproduced it just now, and will fix it as soon as possible.

It just so happens that the X/Y/Z modem feature is almost finished, so I will wait for the X/Y/Z modem to be released together. The release time is expected this weekend. I will update the progress here, thank you very much!

@kingToolbox kingToolbox self-assigned this Apr 2, 2021
@kingToolbox kingToolbox added the bug Something isn't working label Apr 2, 2021
@karagi4
Copy link
Author

karagi4 commented Apr 2, 2021

Yes, thank you!

@karagi4
Copy link
Author

karagi4 commented Apr 2, 2021

Also, since we are talking about authorization, could you implement the possibility of enabling a Master password to log in to the WindTerm application?
Then I would use the built-in WindTerm authorization. I use Pageant and the master password for the key in it. If you use this in WindTerm, you have to enter the master password every time you connect.

@kingToolbox
Copy link
Owner

WindTerm already has a master password 😄 You can read master password to learn more. But if this is not what you want, you can describe your needs in more detail, and I will try to implement it.

@karagi4
Copy link
Author

karagi4 commented Apr 3, 2021

2021-04-03 15-29-52 WindTerm
Yes, this is suggested at the first launch. But if I already have downloaded sessions or I previously refused to set the master password, then I can no longer set it. Or how it can be done, maybe I don't know it?

@karagi4
Copy link
Author

karagi4 commented Apr 3, 2021

About the master password. I had in mind the possibility of setting the master password to log in to WindTerm completely, so that if I do not enter the password, I would not be able to use WindTerm and see the configured connections at all.

@karagi4
Copy link
Author

karagi4 commented Apr 3, 2021

Or the second option is an analogue of pageant Putty, so that I can enter the password on the ssh key only once and that it no longer requires confirmation of the input in each session until I restart WindTerm

@karagi4
Copy link
Author

karagi4 commented Apr 3, 2021

Thank you for your feedback!

@kingToolbox
Copy link
Owner

But if I already have downloaded sessions or I previously refused to set the master password, then I can no longer set it. Or how it can be done, maybe I don't know it?

Sorry, currently it can only be set for the first time. The method of re-setting and modification will be provided in later versions.

I had in mind the possibility of setting the master password to log in to WindTerm completely, so that if I do not enter the password, I would not be able to use WindTerm and see the configured connections at all.

Speaking of this feature, I happen to be completing a new function "lock screen", just like the "lock screen" of Windows or Linux. During use, you can lock the screen at any time, and then you must unlock it to continue operation, otherwise you cannot see the currently opened tabs, screen output, etc, which just meet some of your needs.

But this feature "lock screen" is more used to protect the current screen output to prevent others from peeping on the screen when you are not in front of the computer, and not used to protect youre session configuration, because the configuration itself 'windterm-install-path/profile/default.v10/terminal/user.sessions' is stored on the disk and is not encrypted and can be viewed at any time with a text editor. Unless encrypted, I also think it is meaningless to protect any content on the disk because it can be viewed with third-party tools. In other words, if your computer is hacked, then any information will be at risk. This is not something that WindTerm or other clients can solve.

the second option is an analogue of pageant Putty, so that I can enter the password on the ssh key only once and that it no longer requires confirmation of the input in each session until I restart WindTerm

Isn't this the current design? 😃 After the first setting, you will only be asked when WindTerm need to read encrypted information such as automatic login, and the input will be valid until WindTerm is closed.

@kingToolbox
Copy link
Owner

Sorry to keep you waiting. WindTerm_2.1.0_Prerelease_1 has finally been released and this automatically login issue has been fixed. You can download and check it now. Thank you.

X/Y/Z modem and lock screen are still under development and are not stable yet, so it will take a few days. This is also the reason why the version 2.1.0_Prerelease_1 has not been released last weekend and has been delayed so far.

@karagi4
Copy link
Author

karagi4 commented Apr 9, 2021

In Winterm v2.1.0, autologin works.
It was possible to set the master password and transfer the sessions like this: When running a clean version of WindTerm, we set the master password, and then copy the following files from the working WindTerm configuration with replacement:...\WindTerm\profiles\default.v10\global\reopen.history
…\WindTerm\profiles\default.v10\terminal
After that, your sessions and settings should be transferred to a clean WindTerm with a master password.

@kingToolbox
Copy link
Owner

Unfortunately, for security, WindTerm will generate a unique fingerprint in the profile the first time it is created, and this fingerprint will participate in all subsequent encryption. Therefore, the profile of different WindTerms are not interchangeable.

However, when developing the lock screen feature, the feature of changing the master password has been implemented. The only problem now is that the current security design makes it impossible for even WindTerm to know whether the master password to be replaced is correct.

In daily use, this is not a problem. WindTerm is responsible for decrypting using the master password given by the user and sending the decrypted authentication information to the server for judgment. WindTerm itself does not know, nor does it need to know whether the decrypted information is correct. But when changing the master password, WindTerm needs to determine whether the decrypted information is correct, otherwise after re-encrypting the wrong decrypted data with the new master password, All the user's automatic login data will be lost.

I am still thinking about how to better solve this problem, and I also hope you can share more suggestions. Thank you very much for your great advice.

@karagi4 karagi4 closed this as completed Apr 21, 2021
@kingToolbox
Copy link
Owner

The new version 2.1.0_prerelease_2 has been released, and supports locking screen and changing the master password, you can download and check it now, thank you!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants