no Login-Failed-dialog after entering wrong password for yahoo-account (pop)
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
People
(Reporter: dheddicke, Assigned: gds)
References
Details
Attachments
(4 files)
Comment 1•8 years ago
|
||
Comment 2•8 years ago
|
||
Comment 10•8 years ago
|
||
Comment 11•8 years ago
|
||
Reporter | ||
Comment 12•8 years ago
|
||
Comment 13•8 years ago
|
||
Comment 14•8 years ago
|
||
Comment 15•8 years ago
|
||
workaround |
Reporter | ||
Comment 16•7 years ago
|
||
Reporter | ||
Comment 17•7 years ago
|
||
Comment 18•6 years ago
|
||
Assignee | ||
Comment 19•6 years ago
|
||
Reporter | ||
Comment 20•6 years ago
|
||
Comment 21•6 years ago
|
||
Reporter | ||
Comment 22•6 years ago
|
||
Sorry for my repeatedly late reply. Yes, the problem with the login still exists and the wrong password still can't be removed via the "saved logins" dialogue.
Reporter | ||
Comment 23•6 years ago
|
||
I've tested it with version 65b4.
Assignee | ||
Comment 24•6 years ago
|
||
See the same with yahoo pop with approx. TRUNK debug build version. Works OK with my ISP pop account. With yahoo, just "try again later" and no prompt for corrected password unless you restart. Also, take quite a while (maybe a minute) before the "try again" prompt even occurs. And definitely can't be found in pwd mgr list.
Comment 25•6 years ago
|
||
Is this a repeat of any of these https://mzl.la/2ZhbJx3 ?
Assignee | ||
Comment 26•6 years ago
|
||
None look the same to me (except that this bug is in the list). I will take a look at this again when I get a chance so setting NI for me.
Comment 27•5 years ago
|
||
Can we likely attribute this to yahoo inconsistency?
(In reply to gene smith from comment #19)
(In reply to Wayne Mery (:wsmwk) from comment #18)
...
Bug 1408610 only applies to imap. Maybe pop has a similar problem on yahoo,
I thought we also fixed the pop case in the past year. But I'm not finding the bug report. Does anyone recall it?
Assignee | ||
Comment 28•5 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #27)
Can we likely attribute this to yahoo inconsistency?
I've looked at this today in detail. What's happening is we send the wrong password to yahoo and they respond (after 1 minute) with
-ERR [SYS/TEMP] Server error - Please try again later.
Yahoo supports the capability RESP-CODE but not AUTH-RESP-CODE so Yahoo doesn't send the code that tb expects, [AUTH]
, when a bad password is submitted, e.g.:
-ERR [AUTH] Bad username or password - Please try again.
When tb sees the [SYS/TEMP] response code, it assumes the username/password were accepted, so any other activity like clicking get new mail just fails and no prompt for a new password occurs since tb thinks yahoo has already accepted the credentials.
So the problem is truly a tb bug it seems.
I am working a fix for this but need to test it some more with non-Yahoo POP servers.
Updated•5 years ago
|
Assignee | ||
Comment 29•5 years ago
•
|
||
This diff changes tb so that if the the POP server's response code to a bad password is -ERR [SYS/TEMP]
tb treats it like an AUTH failure. However, yahoo take 60 seconds before it returns the [SYS/TEMP] response for the bad password. Yahoo also returns in the startup CAPA response that it supports PLAIN, LOGIN and USER. So what ends up happening is that that bad password gets sent 3 time to yahoo so the total time before a re-prompt for the correct password is about 3 minutes. I suspect a user might just go ahead and restart tb rather than wait for the 3 minutes. This wouldn't be a problem if yahoo didn't wait so long to respond to a bad password, but it does. I assume this is to slow down brute force password cracking.
Another non-yahoo POP server I have tested returns -ERR almost immediately with a bad password and only has one auth method in the CAPA response (PLAIN). It also doesn't return a "response code" at all in the password -ERR response so this bug doesn't cause a problem for it. (Response codes are an optional POP extension.) This POP server works with and without my proposed change.
In the diff I show a commented-out way to reduce the wait for yahoo response to 1 minute. But it skips over trying the other AUTH methods with the bad password and just sends PLAIN.
Edit: Note: oauth2 does work with yahoo pop, I just enabled it. So this may make this bug moot unless some users refuse to use oauth2 authentication. My proposed diff doesn't affect oauth2 since there is no way to send a "bad" password that I know of.
Comment 30•5 years ago
|
||
(In reply to gene smith from comment #29)
Edit: Note: oauth2 does work with yahoo pop, I just enabled it. So this may make this bug moot unless some users refuse to use oauth2 authentication. My proposed diff doesn't affect oauth2 since there is no way to send a "bad" password that I know of.
Yahoo will cease to accept anything but oAuth to access mail from Thunderbird in the very near future. The only non oAuth authentication currently allowed appears to be application passwords and See https://au.help.yahoo.com/kb/SLN27791.html
Perhaps we need to offer something to users who are trying to use yahoo to help them migrate. Yahoo wants then to drop mail clients, there is no advertising in them.
Comment 31•5 years ago
|
||
Assignee | ||
Comment 32•5 years ago
|
||
Yahoo will cease to accept anything but oAuth to access mail from Thunderbird in the very near future. The only non oAuth authentication currently allowed appears to be application passwords and See https://au.help.yahoo.com/kb/SLN27791.html
Not sure this means Yahoo will stop supporting TLS/Normal Password or that you should only use it in the short term. I think I saw this several years ago when debugging another yahoo issue yet plain passwords still work.
Anyhow, sounds like Magnus is saying WONTFIX. So I'll go ahead and close this as WONTFIX and see if anyone provides a counter argument that might reverse the decision.
Description
•