{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Eric Hall <[EMAIL PROTECTED]>
On Fri, Feb 22, 2002 at 04:35:50AM -0500, Brad Watson wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to Brad Watson <[EMAIL PROTECTED]>
>
> Below are exerts from deep within each client's official Homepage. Lines
> with a "*" in front are from two 3rd party clients who have found a way
> around the length issue.
>
> AIM IM Server limits outgoing message to 2048 bytes but the command
> length must be taken into account so a users message should be closer to
> 2000 bytes to be safe. (Server/Client-side)
>
[snip]
Well, message size appears to be the problem I'm having w/ sending
gpg encrypted messages. I've got a 4k key, and a simple 'test a'
message winds up being 2388 bytes (before adding server commands, etc.,
that's just the message body).
I can see (w/ the debugger) that the message is being properly
encrypted, but it fails to send due to the large data size
(in toc_send_printf(), toc.c:433). Unfortunately the error returned
from toc_send_printf() isn't propogated upwards by the next two
layers, so fire doesn't know it had an error.
ChatWindow.m:413 is where the encrypted data is sent:
---------
// We are done with the old form.
if(encryptedData) {
[[[MainController mainController] communicationController]
sendIMToUser:targetUser rawData:encryptedData];
free(encryptedData);
} else {
---------
I'm digging through this, and one thing I noticed is that
the gpg command includes encrypting to myself, which is really
pushing the encrypted output over the limit. I don't see a
reason to encrypt to self here, I'm about to try taking that
out and see how it goes.
I'll also (later) take a look at propogating the error
from toc_send_printf() back up so we can catch it.
-eric
{#} ----------------------------------------------------+[ fire ]+---
