|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
|
|
#12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: new Component: unclassified | Version: 2.7.5 Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Since today I get this error message when trying to log in to my ICQ account. When I disable "Use SSL" pidgin logs in without any problems. -- Ticket URL: <http://developer.pidgin.im/ticket/12886> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Changes (by deryni): * status: new => pending Comment: The ICQ servers are having issues today it would seem, we assume this to be related to the AIM/ICQ split. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:1> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by ViperGeek): The old standby of enabling clientLogin seems to work, at least for now: Accounts -> ICQ -> Edit Account -> Advanced -> [x] Use clientLogin - Dave -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:2> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by nealo): I already had "Use clientLogin" checked, but I still saw this issue. But it works now, after turning off clientLogin, trying to connect (failed), and then turning it back on. I rarely see anyone logged into ICQ anyway, and the ones I do see are also on some other messenger. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:3> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by tomburger): Well, it worked for me finally other way around --- I had some ICQ issues for week or so, so I realized I'm behind with Pidgin updates. After upgrade last night, the message above started to coming. Today I found this ticket, I switched the clientLogin on, and it didn't helped (but no error message), then I switched it off again and now --- it works... I hope it was just some temporary "magic" problem, here in Czech ICQ is still the mostly used IM. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:4> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by ledow): I also have had this problem since using 2.7.5. Clientlogin does has absolutely zero effect but disabling SSL does. Any way to check the SSL certificates being used? -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:5> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by ledow): The only data I could pull out of the debug window that looks wrong is: (12:56:18) nss: Handshake failed (-5928) (12:56:18) oscar: unable to connect to FLAP server of type 0x0002 (12:56:18) connection: Connection error on 03D53FD8 (reason: 0 description: Unable to connect to BOS server: SSL Handshake Failed) -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:6> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by Knight): The "Use clientLogin" worked for me as well. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:7> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by Edding8400): But this can't be the solution. I don't like to deactivate security related items and SSL Login is important. If I use clientLogin with SSL the Debug Windows says: "We haven't received a tlsCertName to use. We will not do SSL to BOS." and "We won't use SSL for FLAP [....]" -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:8> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by rekkanoryo): Replying to [comment:8 Edding8400]: > But this can't be the solution. It is. ICQ's servers were very recently split from AIM's, and most of ICQ's new servers do not support SSL. There's nothing we can do about that. The only reason clientLogin works with the "Use encryption if available" setting is that the clientLogin method gives us the information we need to determine what servers we can or cannot connect to with SSL. In effect, the only thing that uses SSL is the login process; the rest of the connection for ICQ is insecure. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:9> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: pending Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Comment(by Edding8400): Replying to [comment:9 rekkanoryo]: > It is. ICQ's servers were very recently split from AIM's, and most of ICQ's new > servers do not support SSL. There's nothing we can do about that. Thanks for fast answer explanation! Now I have a better understanding about this topic. I think it's really bad what they did. Secure Logindata-transfer is a duty. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:10> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
|
|
Re: #12886: Unable to connect to BOS server:: SSL Handshake Failed#12886: Unable to connect to BOS server:: SSL Handshake Failed
--------------------------------------------+------------------------------- Reporter: WebComPas | Owner: rekkanoryo Type: defect | Status: closed Milestone: | Component: unclassified Version: 2.7.5 | Resolution: Keywords: ssl handshake bos server login | --------------------------------------------+------------------------------- Changes (by trac-robot): * status: pending => closed Comment: This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days. -- Ticket URL: <http://developer.pidgin.im/ticket/12886#comment:11> Pidgin <http://pidgin.im> Pidgin _______________________________________________ Tracker mailing list Tracker@... http://pidgin.im/cgi-bin/mailman/listinfo/tracker |
| Free embeddable forum powered by Nabble | Forum Help |