[Pidgin] #9600: Yahoo still does not work through SOCKS5 Proxy

[Pidgin]

#9600: Yahoo still does not work through SOCKS5 Proxy
------------------------+---------------------------------------------------
 Reporter:  psmith2100  |        Owner:  sulabh.dev
     Type:  defect      |       Status:  pending   
Milestone:              |    Component:  Yahoo!    
  Version:  2.5.8       |   Resolution:            
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by psmith2100):

  * status:  pending => new


Old description:

> Ok as requested, I attached the screenshots as JPEG files and a debug
> file which looks to me to indicate the proxy is working like it should
> and Yahoo is refusing the connection.  Again, Trillian connects just fine
> through the proxy.
>

> I have read about the Yahoo issues, and 2.5.7 and 2.5.8 did fix my issue
> at home on my broadband connection, but not at work.  Pidgin still does
> not work through my corporate SOCKS5 proxy server since the Yahoo issues
> started, but Trillian does.
>
> Pidgin had always worked on my corporate LAN using my corporate SOCKS5
> proxy until Yahoo made all these changes and broke Pidgin, and it has
> never worked since.  2.5.7 does not work and 2.5.8 does not work with the
> SOCKS5 proxy, and I am using the same proxy and port as I always have and
> it works in Trillian.
>
> The port my proxy uses is 1080.  When I do a netstat -a when connected
> with Trillian, it shows a connection to the proxy on port 5050 which is
> the Yahoo port.
>
> A netstat -a with pidgin shows a connection to the proxy on port 1080,
> but I get an error saying the server refused connection.  Sometimes I get
> an error saying "unable to connect to login.yahoo.com: SSL handshake
> failed."  Please see attached screenshots.

New description:

 Yes, the SOCKS5 proxy allows SSL connections through it because Trillian
 works fine with the proxy.



 Ok as requested, I attached the screenshots as JPEG files and a debug file
 which looks to me to indicate the proxy is working like it should and
 Yahoo is refusing the connection.  Again, Trillian connects just fine
 through the proxy.


 I have read about the Yahoo issues, and 2.5.7 and 2.5.8 did fix my issue
 at home on my broadband connection, but not at work.  Pidgin still does
 not work through my corporate SOCKS5 proxy server since the Yahoo issues
 started, but Trillian does.

 Pidgin had always worked on my corporate LAN using my corporate SOCKS5
 proxy until Yahoo made all these changes and broke Pidgin, and it has
 never worked since.  2.5.7 does not work and 2.5.8 does not work with the
 SOCKS5 proxy, and I am using the same proxy and port as I always have and
 it works in Trillian.

 The port my proxy uses is 1080.  When I do a netstat -a when connected
 with Trillian, it shows a connection to the proxy on port 5050 which is
 the Yahoo port.

 A netstat -a with pidgin shows a connection to the proxy on port 1080, but
 I get an error saying the server refused connection.  Sometimes I get an
 error saying "unable to connect to login.yahoo.com: SSL handshake failed."
 Please see attached screenshots.

--

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