[Pidgin] #11281: Yahoo: Account locked

Pidgin trac at pidgin.im
Wed Feb 3 01:43:10 EST 2010 

#11281: Yahoo: Account locked
-----------------------+----------------------------------------------------
 Reporter:  alasdairm  |        Owner:  rekkanoryo  
     Type:  defect     |       Status:  pending     
Milestone:             |    Component:  unclassified
  Version:  2.6.5      |   Resolution:              
 Keywords:             |  
-----------------------+----------------------------------------------------
Changes (by rekkanoryo):

  * status:  new => pending


Old description:

> full text of error message is: "Account locked: Too many failed login
> attempts. Logging into the Yahoo! website may fix this."
>
> logging into the yahoo website (http://webmessenger.yahoo.com/) fixes
> this about 1 time in 8.
>
> if my account is locked, why does logging in with the web messenger fix
> it?
>
> debug log:
>
> (21:48:07) jabber: jabber_actions: have pep: NO
> (21:48:07) account: Connecting to account alimanson.
> (21:48:07) connection: Connecting. gc = 02634178
> (21:48:07) util: Writing file C:\Documents and Settings\Ali.LENOVO-
> 84C1570F\Application
> Data\.purple\icons\03eb7735eb4c84537b29f604b2cb9d9368e9df96.png
> (21:48:07) yahoo: Calculated buddy icon checksum: 14614050
> (21:48:07) yahoo: buddy icon is up to date. Not reuploading.
> (21:48:07) dnsquery: Performing DNS lookup for scsa.msg.yahoo.com
> (21:48:07) dnsquery: IP resolved for scsa.msg.yahoo.com
> (21:48:07) proxy: Attempting connection to 68.180.217.15
> (21:48:07) proxy: Connecting to scsa.msg.yahoo.com:5050 with no proxy
> (21:48:07) proxy: Connection in progress
> (21:48:07) proxy: Connecting to scsa.msg.yahoo.com:5050.
> (21:48:07) proxy: Connected to scsa.msg.yahoo.com:5050.
> (21:48:07) yahoo: 98 bytes to read, rxlen is 118
> (21:48:07) yahoo: Yahoo Service: 0x57 Status: 1
> (21:48:07) yahoo: Authentication: In yahoo_auth16_stage1
> (21:48:07) util: requesting to fetch a URL
> (21:48:07) dnsquery: Performing DNS lookup for login.yahoo.com
> (21:48:07) dnsquery: IP resolved for login.yahoo.com
> (21:48:07) proxy: Attempting connection to 209.191.92.114
> (21:48:07) proxy: Connecting to login.yahoo.com:443 with no proxy
> (21:48:07) proxy: Connection in progress
> (21:48:07) proxy: Connecting to login.yahoo.com:443.
> (21:48:07) proxy: Connected to login.yahoo.com:443.
> (21:48:08) nss: subject=CN=login.yahoo.com,OU=Yahoo,O=Yahoo! Inc.,L=Santa
> Clara,ST=California,C=US issuer=OU=Equifax Secure Certificate
> Authority,O=Equifax,C=US
> (21:48:08) nss: subject=OU=Equifax Secure Certificate
> Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate
> Authority,O=Equifax,C=US
> (21:48:08) certificate/x509/tls_cached: Starting verify for
> login.yahoo.com
> (21:48:08) certificate/x509/tls_cached: Checking for cached cert...
> (21:48:08) certificate/x509/tls_cached: ...Found cached cert
> (21:48:08) nss/x509: Loading certificate from C:\Documents and
> Settings\Ali.LENOVO-84C1570F\Application
> Data\.purple\certificates\x509\tls_peers\login.yahoo.com
> (21:48:08) certificate/x509/tls_cached: Peer cert matched cached
> (21:48:08) nss/x509: Exporting certificate to C:\Documents and
> Settings\Ali.LENOVO-84C1570F\Application
> Data\.purple\certificates\x509\tls_peers\login.yahoo.com
> (21:48:08) util: Writing file C:\Documents and Settings\Ali.LENOVO-
> 84C1570F\Application
> Data\.purple\certificates\x509\tls_peers\login.yahoo.com
> (21:48:08) certificate: Successfully verified certificate for
> login.yahoo.com
> (21:48:08) util: request constructed
> (21:48:08) util: Response headers: 'HTTP/1.1 200 OK
>
> Date: Wed, 03 Feb 2010 05:48:06 GMT
>
> Set-Cookie: B=donnga55mi3gm&b=3&s=v5; expires=Tue, 03-Feb-2012 20:00:00
> GMT; path=/; domain=.yahoo.com
>
> P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR
> ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi
> IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"
>
> Cache-Control: private
>
> Pragma: no-cache
>
> Expires: Thu, 05 Jan 1995 22:00:00 GMT
>
> Connection: close
>
> Transfer-Encoding: chunked
>
> Content-Type: text/html
>

>
> '
> (21:48:08) yahoo: Authentication: In yahoo_auth16_stage1_cb
> (21:48:08) yahoo: Authentication error: Account locked: Too many failed
> login attempts.  Logging into the Yahoo! website may fix this.. Code 1213
> (21:48:08) connection: Connection error on 02634178 (reason: 16
> description: Account locked: Too many failed login attempts.  Logging
> into the Yahoo! website may fix this.)
> (21:48:08) jabber: jabber_actions: have pep: NO
> (21:48:08) account: Disconnecting account alimanson (00CA4230)
> (21:48:08) connection: Disconnecting connection 02634178
> (21:48:08) jabber: jabber_actions: have pep: NO
> (21:48:08) connection: Destroying connection 02634178
>

>
> thanks
>
> alasdair

New description:

 full text of error message is: "Account locked: Too many failed login
 attempts. Logging into the Yahoo! website may fix this."

 logging into the yahoo website (http://webmessenger.yahoo.com/) fixes this
 about 1 time in 8.

 if my account is locked, why does logging in with the web messenger fix
 it?

 debug log:

 {{{
 (21:48:07) jabber: jabber_actions: have pep: NO
 (21:48:07) account: Connecting to account xxxxxxxxx.
 (21:48:07) connection: Connecting. gc = 02634178
 (21:48:07) util: Writing file C:\Documents and Settings\Ali.LENOVO-
 84C1570F\Application
 Data\.purple\icons\03eb7735eb4c84537b29f604b2cb9d9368e9df96.png
 (21:48:07) yahoo: Calculated buddy icon checksum: 14614050
 (21:48:07) yahoo: buddy icon is up to date. Not reuploading.
 (21:48:07) dnsquery: Performing DNS lookup for scsa.msg.yahoo.com
 (21:48:07) dnsquery: IP resolved for scsa.msg.yahoo.com
 (21:48:07) proxy: Attempting connection to 68.180.217.15
 (21:48:07) proxy: Connecting to scsa.msg.yahoo.com:5050 with no proxy
 (21:48:07) proxy: Connection in progress
 (21:48:07) proxy: Connecting to scsa.msg.yahoo.com:5050.
 (21:48:07) proxy: Connected to scsa.msg.yahoo.com:5050.
 (21:48:07) yahoo: 98 bytes to read, rxlen is 118
 (21:48:07) yahoo: Yahoo Service: 0x57 Status: 1
 (21:48:07) yahoo: Authentication: In yahoo_auth16_stage1
 (21:48:07) util: requesting to fetch a URL
 (21:48:07) dnsquery: Performing DNS lookup for login.yahoo.com
 (21:48:07) dnsquery: IP resolved for login.yahoo.com
 (21:48:07) proxy: Attempting connection to 209.191.92.114
 (21:48:07) proxy: Connecting to login.yahoo.com:443 with no proxy
 (21:48:07) proxy: Connection in progress
 (21:48:07) proxy: Connecting to login.yahoo.com:443.
 (21:48:07) proxy: Connected to login.yahoo.com:443.
 (21:48:08) nss: subject=CN=login.yahoo.com,OU=Yahoo,O=Yahoo! Inc.,L=Santa
 Clara,ST=California,C=US issuer=OU=Equifax Secure Certificate
 Authority,O=Equifax,C=US
 (21:48:08) nss: subject=OU=Equifax Secure Certificate
 Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate
 Authority,O=Equifax,C=US
 (21:48:08) certificate/x509/tls_cached: Starting verify for
 login.yahoo.com
 (21:48:08) certificate/x509/tls_cached: Checking for cached cert...
 (21:48:08) certificate/x509/tls_cached: ...Found cached cert
 (21:48:08) nss/x509: Loading certificate from C:\Documents and
 Settings\Ali.LENOVO-84C1570F\Application
 Data\.purple\certificates\x509\tls_peers\login.yahoo.com
 (21:48:08) certificate/x509/tls_cached: Peer cert matched cached
 (21:48:08) nss/x509: Exporting certificate to C:\Documents and
 Settings\Ali.LENOVO-84C1570F\Application
 Data\.purple\certificates\x509\tls_peers\login.yahoo.com
 (21:48:08) util: Writing file C:\Documents and Settings\Ali.LENOVO-
 84C1570F\Application
 Data\.purple\certificates\x509\tls_peers\login.yahoo.com
 (21:48:08) certificate: Successfully verified certificate for
 login.yahoo.com
 (21:48:08) util: request constructed
 (21:48:08) util: Response headers: 'HTTP/1.1 200 OK

 Date: Wed, 03 Feb 2010 05:48:06 GMT

 Set-Cookie: B=donnga55mi3gm&b=3&s=v5; expires=Tue, 03-Feb-2012 20:00:00
 GMT; path=/; domain=.yahoo.com

 P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR
 ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi
 IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"

 Cache-Control: private

 Pragma: no-cache

 Expires: Thu, 05 Jan 1995 22:00:00 GMT

 Connection: close

 Transfer-Encoding: chunked

 Content-Type: text/html



 '
 (21:48:08) yahoo: Authentication: In yahoo_auth16_stage1_cb
 (21:48:08) yahoo: Authentication error: Account locked: Too many failed
 login attempts.  Logging into the Yahoo! website may fix this.. Code 1213
 (21:48:08) connection: Connection error on 02634178 (reason: 16
 description: Account locked: Too many failed login attempts.  Logging into
 the Yahoo! website may fix this.)
 (21:48:08) jabber: jabber_actions: have pep: NO
 (21:48:08) account: Disconnecting account xxxxxxxxx (00CA4230)
 (21:48:08) connection: Disconnecting connection 02634178
 (21:48:08) jabber: jabber_actions: have pep: NO
 (21:48:08) connection: Destroying connection 02634178
 }}}


 thanks

 alasdair

--

Comment:

 The error code 1213 shown in the debug log is being returned immediately
 by the server when we ask to authenticate.  "Too many failed login
 attempts" is the corresponding message for that error code.  To the best
 of my knowledge, there's pretty much nothing at all that we can do about
 this.  The best thing I can recommend in this case is wait a while before
 trying to connect again, but I can't say that it will help.

 I have seen this once before when a person's yahoo ID was a target in an
 attempt to take over existing valid accounts, but if you were to log into
 the My Yahoo! page or into mail (or basically any service other than web
 messenger) immediately after getting this error, you would almost
 certainly see warnings about excessive login failures if this was
 happening to you.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11281#comment:1>
Pidgin <http://pidgin.im>
Pidgin

More information about the Tracker mailing list