Mark Doliner spake unto us the following wisdom: > >> And I just realized that maybe we should continue setting the connect > >> server to talk.google.com when users create Google Talk accounts > >> within Pidgin (I believe Ethan changed this a few days ago). > > > > I changed it yesterday; the reason for this is that it breaks SSL > > certificate verification for those with gmail.com Google Talk > > accounts. Why do you think it should be re-enabled? > > Because without it Google Apps accounts show the certificate mismatch > warning. This is, uh, comical.
I was afraid of that. ;-)
> When I login to talk.google.com as [EMAIL PROTECTED] the certificate
> presented is for talk.google.com.
> When I login to talk.google.com as [EMAIL PROTECTED] the
> certificate presented is for gmail.com.
> When I login to talk.google.com as [EMAIL PROTECTED] the
> certificate presented is for googlemail.com.
>
> Maybe we should do this:
> Only set the connect server to talk.google.com when a Google Talk
> account is created that is not @gmail.com or @googlemail.com
That sounds appropriate. I'll revert my previous commit and change it
to this behavior.
Ethan
--
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764
signature.asc
Description: Digital signature
_______________________________________________ Support mailing list Support@pidgin.im http://pidgin.im/cgi-bin/mailman/listinfo/support
