full-disclosure - talk.google.com

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <430E07E5.2050502@gmail.com>
Date: Thu Aug 25 19:03:36 2005
From: jftucker at gmail.com (James Tucker)
Subject: 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.

>  
>