Noted at about 8:50 TCT. Bug not present at 6:00 TCT.
Summary:
There appears to be a problem with the new log-in system, in that it does not correctly process some passwords.
There is a work-around by using a simpler password.
Detailed Description:
Accessing Torn from a Windows 10 PC (tried 2 browsers with the same result), the login window has changed to a pop-out dialog, This appears to be new. The new dialog allowed me to enter my password, but resulted in a failed login.
After a few attempts, I reset my password using the provided method and then logged in OK using the new dialog with the automatically-generated password from Torn.
I then reset my password back to the previous one. The subsequent login failed in the same way as first observed.
The new login system appears not to correctly process some passwords. My old password contained some special characters including an ampersand, currency symbol and a comma. Though I can still change my password back to this, subsequent logins will fail.
- I also tried disabling TornTools; this had no effect.
Summary:
There appears to be a problem with the new log-in system, in that it does not correctly process some passwords.
There is a work-around by using a simpler password.
Detailed Description:
Accessing Torn from a Windows 10 PC (tried 2 browsers with the same result), the login window has changed to a pop-out dialog, This appears to be new. The new dialog allowed me to enter my password, but resulted in a failed login.
After a few attempts, I reset my password using the provided method and then logged in OK using the new dialog with the automatically-generated password from Torn.
I then reset my password back to the previous one. The subsequent login failed in the same way as first observed.
The new login system appears not to correctly process some passwords. My old password contained some special characters including an ampersand, currency symbol and a comma. Though I can still change my password back to this, subsequent logins will fail.
- I also tried disabling TornTools; this had no effect.