[OTR-dev] Seg fault in otr_parse

[Ian Goldberg]

On Mon, Aug 08, 2005 at 02:41:26PM -0400, Alex wrote:
> Try entering this into otr_parse and see what happens ;)
> 
> ?OTR:AAEDAAAAAQAAAAEAAADAQlmXvP+eeXWzF7z4UVVG5ReFFEerkfZDTEvEAEeFoghpJxQoVSp5ykTSBoO/bkB1IbRVy2d+PpU/0NBq5b99WDOgaeRfM2jAwo9TfCa0gCxcz8fWNe3aDuRkb0/291C1OoyVMC1wfAn8QafkLaGCqjpogCRs74IwCAJq0h9OvaPzIuuwhWTfGdjkGrIJiTimMhLh+3hXxEcpJgoL/PZoEr54TmF/iUyH7+M7u46shTc0mKdLOMKRWnfHycNu7HrNAAAAAAAAAAEAAAAQ/+v5ll994dU1J5KfL4Kl9kqXwAAepOvU2Lv8f+LKEKFbc7sNAAAAAQA=.
> 
> It makes an 'infinate' loop when it tries to output all of the mac's stored.

Well caught.  It was only the printing routine that was in error; it
went into an infinite loop when it encountered a malformed Data Message
with a revealed MAC key length which wasn't a multiple of 20 bytes.

Fixed in CVS.

   - Ian