Closed
Bug 953547
Opened 12 years ago
Closed 12 years ago
Can't connect to Google Talk accounts from Google Apps.
Categories
(Chat Core :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
0.2b2
People
(Reporter: florian, Assigned: florian)
Details
(Whiteboard: [0.2-wanted])
*** Original post on bio 96 at 2008-08-11 22:39:00 UTC ***
We get the error "nss: Handshake failed (-12276)", that's SSL_ERROR_BAD_CERT_DOMAIN.
Comment 1•12 years ago
|
||
*** Original post on bio 96 by Niklas <05282 AT gmx.de> at 2008-09-15 14:16:49 UTC ***
Same thing when I'm trying to connect to my own Server. It's an openfire Installation with unsigned SSL-Certificate. (instantbird-0.1.2.1.en-US.win32)
As I'm new to instantbird and not an developer at all, is there any additional information I should provide?
| Assignee | ||
Comment 2•12 years ago
|
||
*** Original post on bio 96 at 2008-09-15 14:28:13 UTC ***
(In reply to comment #1)
> Same thing when I'm trying to connect to my own Server. It's an openfire
> Installation with unsigned SSL-Certificate. (instantbird-0.1.2.1.en-US.win32)
>
Well, it's not exactly the same bug. In the case of gtalk, the certificate is valid, but for the connect server (i.e. talk.google.com), not for the expected domain (i.e. what you have after @ in your jabber id) so I guess we can special case Google Talk.
For your specific case (own server with invalid certificate), you would need a security dialog to add an exception and trust the certificate.
> As I'm new to instantbird and not an developer at all, is there any additional
> information I should provide?
Not really, the problem is known. You can file a separate bug (an enhancement request) to add a security exception dialog if you want.
| Assignee | ||
Updated•12 years ago
|
Whiteboard: [0.2-wanted]
| Assignee | ||
Comment 3•12 years ago
|
||
*** Original post on bio 96 at 2010-02-24 18:59:14 UTC ***
FIXED: https://hg.instantbird.org/instantbird/rev/224a8b3cac90
Accounts created from the Google Talk protocol override will automatically use talk.google.com as connect server, and libpurple is now checking certificates against the connect server if it is provided (and not queried through a DNS SRV request).
Target Milestone: --- → 0.2b2
| Assignee | ||
Comment 4•12 years ago
|
||
*** Original change on bio 96 at 2010-02-24 19:01:02 UTC was without comment, so any subsequent comment numbers will be shifted ***
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•