Full Disclosure mailing list archives
Re: talk.google.com
From: James Tucker <jftucker () gmail com>
Date: Thu, 25 Aug 2005 19:03:17 +0100
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/
Current thread:
- Re: talk.google.com, (continued)
- Re: talk.google.com Brian Dessent (Aug 24)
- Message not available
- talk.google.com Mohit Muthanna (Aug 24)
- Re: talk.google.com Technica Forensis (Aug 25)
- Re: talk.google.com Justin Allen (Aug 25)
- Message not available
- Re: talk.google.com Justin Allen (Aug 25)
- Re: talk.google.com Daniel Margolis (Aug 25)
- Re: talk.google.com James Tucker (Aug 25)
- Re: talk.google.com James Tucker (Aug 26)
- Re: talk.google.com Ill will (Aug 26)
- Re: talk.google.com n3td3v (Aug 27)
- Re: talk.google.com Robert Wesley McGrew (Aug 27)
- Re: talk.google.com n3td3v (Aug 27)
- RE: talk.google.com y0himba (Aug 27)
- Re: talk.google.com Robert Wesley McGrew (Aug 27)