| 1 |
On Jan 7, 2012 11:14 AM, "Andrey Moshbear" <andrey.vul@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Fri, Jan 6, 2012 at 23:04, Pandu Poluan <pandu@××××××.info> wrote: |
| 4 |
> > |
| 5 |
> > On Jan 7, 2012 9:59 AM, "Andrey Moshbear" <andrey.vul@×××××.com> wrote: |
| 6 |
> >> |
| 7 |
> [snip] |
| 8 |
> >> |
| 9 |
> >> where exactly is the SSL problem? |
| 10 |
> >> |
| 11 |
> > |
| 12 |
> > It's not SSL problem, but SASL authentication failure. |
| 13 |
> > |
| 14 |
> > Check the following, might help : |
| 15 |
> > |
| 16 |
> > |
| 17 |
http://askubuntu.com/questions/88989/unable-to-connect-to-google-talk-using-pidgin-sasl-error |
| 18 |
> > |
| 19 |
> |
| 20 |
> Interesting how having |
| 21 |
> |
| 22 |
> 127.0.0.1 localhost |
| 23 |
> ::1 localhost |
| 24 |
> |
| 25 |
> instead of |
| 26 |
> |
| 27 |
> 127.0.0.1 localhost hostname |
| 28 |
> ::1 localhost hostname |
| 29 |
> |
| 30 |
> causes subtle issues. |
| 31 |
> |
| 32 |
> And yes, that fixed it. Thanks for the link. |
| 33 |
> |
| 34 |
|
| 35 |
I think the SASL handshake appended the hostname somewhere, and Google |
| 36 |
rejected all auth attempts from "localhosh" |
| 37 |
|
| 38 |
But that's just some speculation. |
| 39 |
|
| 40 |
Anyways, glad it helped. |
| 41 |
|
| 42 |
Rgds, |
Archives