[Pidgin] #17029: AIM via improxy.smarsh.com results in SSL Handshake Failed
Pidgin
trac at pidgin.im
Tue May 31 11:13:10 EDT 2016
#17029: AIM via improxy.smarsh.com results in SSL Handshake Failed
----------------------+--------------------------------------------------
Reporter: aliebert | Owner: EionRobb
Type: defect | Status: new
Milestone: | Component: unclassified
Version: 2.10.12 | Keywords: improxy.smarsh.com smarsh pidgin aim
----------------------+--------------------------------------------------
So I have searched via Google for AIM via improxy.smarsh.com and found the
suggestion to use improxy.smarsh.com port 5191 and disable "Use
clientLogin." I also upgraded to the latest version 2.10.12 which seems to
have some fix applied relating to a similar problem. The end result is
with "Use clientLogin" disabled, I am "Unable to connect to authentication
server: SSL Handshake Failed."
If I enable Use clientLogin, I can connect to AIM using the
improxy.smarsh.com port 5191, but it skips over improxy.smarsh.com and
goes right to api.screenname.aol.com:443 with no proxy. I have tried with
and without a proxy of improxy.smarsh.com in SOCKS5 or HTTP and then the
default AIM settings in the Advanced tab Server slogin.oscar.aol.com but
that just stays in Connecting... but nothing happens. Not sure how to get
AIM, Pidgin, and Smarsh to all work in harmony; AIM and Pidgin work fine
but adding in Smarsh seems to be a problem and Smarsh is complaining that
none of my AIM activity is being received.
Thanks!
--
Ticket URL: <https://developer.pidgin.im/ticket/17029>
Pidgin <https://pidgin.im>
Pidgin
More information about the Tracker
mailing list