[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Full-disclosure] talk.google.com
- To: "James Tucker" <jftucker@xxxxxxxxx>
- Subject: RE: [Full-disclosure] talk.google.com
- From: "Andre Protas" <aprotas@xxxxxxxx>
- Date: Thu, 25 Aug 2005 13:55:30 -0700
The Server does not accept plain. Actually, some clients were unable to
connect to the jabber server b/c of that. Gajim was one.
Anyone get a perl/python jabber client connecting to talk.google.com
properly?
Signed,
Andre Derek Protas
Security Researcher
eEye Digital Security
aprotas eeye com
-----Original Message-----
From: James Tucker [mailto:jftucker@xxxxxxxxx]
Sent: Thursday, August 25, 2005 11:03 AM
To: Andre Protas
Cc: My Name; Paul Melson; adityad2005@xxxxxxxxxxxxxxxxxxxxx; Full
Disclosure
Subject: Re: [Full-disclosure] talk.google.com
Andre Protas wrote:
>Also, they are doing some client-side bounds checking on their message
>sizes. But, if you connect to talk.google.com from a different client
>(gaim for instance), you can send quite a bit larger of a buffer.
Hehe,
>but then gaim was also cutting me off too the larger I went (more of a
>gtk issue than anything). I loaded up a python jabber client but got
>blocked by the new google token everyone was talking about.
>
>
The token is unimportant if you use the PLAIN mechanism. Check what
authentication mechanism that client was using.
>
>
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/