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-next>] [day] [month] [year] [list]

Message-ID: <D52FCFAE57472647956CBAEDC08DA5533CA5DC@av-mail01.corp.int-eeye.com>
Date: Thu Aug 25 21:55:39 2005
From: aprotas at eeye.com (Andre Protas)
Subject: talk.google.com

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@...il.com] 
Sent: Thursday, August 25, 2005 11:03 AM
To: Andre Protas
Cc: My Name; Paul Melson; adityad2005@...rs.sourceforge.net; 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.

>  
>