[OTR-users] malformed message loops

Paul Wouters paul at cypherpunks.ca
Thu Jan 5 17:54:40 EST 2006


On Thu, 5 Jan 2006, David Thiel wrote:

>
> (14:06:07) OTR Error: You transmitted a malformed data message
> (14:06:09) Successfully refreshed the private conversation with username.
> (14:06:09) The last message to username was resent.
> (14:06:09) OTR Error: You transmitted a malformed data message
> (14:06:10) Successfully refreshed the private conversation with username.
> (14:06:10) The last message to username was resent.
> (14:06:10) OTR Error: You transmitted a malformed data message
> (14:06:11) Successfully refreshed the private conversation with username.
> (14:06:11) The last message to username was resent.
> (14:06:11) OTR Error: You transmitted a malformed data message
>
> (and so on)
>
> I did see this once previously in older versions of gaim/otr. The person
> on the other side reported seeing "We got a malformed message from Lx".
> What is it that constitutes a malformed message? And if there is one,
> could you change it so that it won't cause a loop with the resends?

I've seen this too. I think this happens when the other user is idle, and
has a fingerprint screen to click on since you just changed machine/key,
but I haven't been able to reproduce it yet. It seems to happen only when
version 1 and 2 protocols are communicating.

Paul



More information about the OTR-users mailing list