{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Eric Hall <[EMAIL PROTECTED]>
On Tue, Apr 30, 2002 at 06:03:35PM -0400, Joe Block wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to Joe Block <[EMAIL PROTECTED]>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Tuesday, April 30, 2002, at 01:51 , David B. Peterson wrote:
>
> > {#} Replies are directed back to [EMAIL PROTECTED]
> > {#} To reply to the author, write to "David B. Peterson"
> > <[EMAIL PROTECTED]>
> >
> >> after using GPG encryption for Yahoo! chats for the past few months
> >> this stopped working in the past couple of weeks. When trying to
> >> exchange keys it drops the END PGP PUBLIC KEY BLOCK line so all you
> >> see is the raw key, likewise encrypted messages are missing the end
> >> part of the key. I suspect that this is due to some change made by
> >> Yahoo!
> >>
> >> Has anyone else noticed this?
> >
> > I haven't been able to get it to work at all with Yahoo! All of the
> > messages seem to get truncated. There seems to be some ridiculously
> > low limit on how many characters you can send in one message. I
> > haven't noticed a change recently.
>
> I never was able to get encrypted chat working with Yahoo either. I
> ended up just moving to AIM.
>
> jpb
> - --
> Joe Block <[EMAIL PROTECTED]>
>
[snip]
From an earlier message by Brad Watson:
> Yahoo messages can be up to 1260 bytes in size (I'm guessing closer to
> 1200 bytes would be safer based on AOL's figures). (Server-side)
I've been poking at getting GPG encryption working w/ AIM, and
found that the standard Fire does an encrypt to self as well as
encrypt to the buddy. For me (w/ a 4k key, buddy w/ a 2k key)
a simple "test a" wound up being 2388 bytes, encrypt only to buddy
is somewhere around 940 bytes. Currently the code that preps and
sends the encrypted message isn't catching 'message to big' (or other)
errors from the lower-level sending routines. I'm working on that
right now, so at least we'll know that the encrypted message was
too big and not get a false sense that the message was properly
sent. Once I have a functional build I'll submit patches for it.
I havn't tried w/ yahoo yet, but given the smaller max message
size (~1200 bytes), I figure most gpg messages wouldn't make it
anyways.
-eric
{#} ----------------------------------------------------+[ fire ]+---
