windows下密码输入错误会卡很长时间。

[ssmmtt]

windows下密码输入错误会卡很长时间。

[kingToolbox]

How long do you have to wait each time? Usually several seconds or tens of seconds are normal. WindTerm uses the PBKDF2 algorithm, which makes it necessary to perform a lot of calculations every time the master password is verified to avoid being brute force cracked locally.

Depending on the performance of your machine, each calculation usually takes a few seconds, so that no more than 80,000 password combinations can be tried every day, which greatly reduces the possibility of brute force cracking.

[funkpopo]

在保证本地环境较为安全的前提下可以优先考虑使用弱密码。这将在一定程度上相对减少密码校验的时间。
The use of weak passwords can be a priority while keeping the local environment secure. This will reduce the time for password validation to some extent.

[ssmmtt]

@kingToolbox

[gooker]

I have a similar situation. I modify the virtual machine IP, then modify the IP in the window , press enter, enter the user name, and then enter the password. It will be stuck for a long time

[funkpopo]

@kingToolbox
Have just checked this problem. The new session creation works well on WindTerm 2.2.0 when using CentOS/ Kali and Ubuntu
When I tried to create a new session, the default connection has been set as "ssh: notty", as shown in the image down below. I just created a virtual machine then login with the local platform and used the newest version of WindTerm.

Regarding the above bug, after repeated testing, it was confirmed that the newly created session would be stuck after entering the password and clicking "Confirm". After clicking "Cancel", an authentication error and a new password window will pop up, and the connection cannot be successfully established at this link. Shown as the result down below.

By the way, every session that has been created successfully before the new version v2.2.0 was released can be used with no problem. And the session info which was saved into the /profiles/../terminal/user.sessions is different from the old session infos. I will paste a sample here. The "Euler OS" is a CentOS-based version of Linux.

Re-checked this morning
Found out that when I try to make the connection with CentOS 7 Linux, virtual machine and bare metal both works well, but the Euler OS ( based on CentOS), I can not establish a connection successfully due to a "ssh:notty" failure info, this may be the main reason of this issue.

Possible sources of the problem:

1. You may accidentally change the default settings of creating a new session with the unavailable "ssh:notty" that caused the establishment failure.
2. May exist some default session conflicts of the ssh settings with target systems.
3. There may be some undiscovered possible causes I have not found out yet...

[kingToolbox]

Sorry, I thought it was master password before, but when I saw the screenshot, I realized that it was the SSH session password.

It should be noted that after clicking Continue in the login wizard, WindTerm was not actually stuck, but is waiting for the server to return the login result. At this time, you can still change your password and click Continue again. If the password is correct, the login will be successful immediately.

In order to avoid this misunderstanding, I will add some tips after clicking Continue.

BTW:
When the login fails, WindTerm_2.2.0 will try to automatically log in three more times, with an interval of 500 millisecond between each login. This design is to avoid as much as possible the login failure caused by accidental network interruption. But apart from this, there is no additional overhead. All waiting time depends entirely on the processing time of the network and server.

[kingToolbox]

@funkpopo
Thank you for doing such a detailed test and giving a proper analysis.

[ssmmtt]

恩 最好是提示一下鉴权失败。

[kingToolbox]

I am happy to inform you that WindTerm_2.2.1 has been released and this issue has been fixed, now when the login fails, an error message will be displayed in time, please download and check it, thank you.

[ssmmtt]

nice,It works !

[kingToolbox]

Okey, this issue has been solved and will be closed. Welcome to continue submitting new feature requests and bugs, thank you.