[OTR-dev] 4.0.0-rc3 ready to roll. Please try it out!

Ian Goldberg ian at cypherpunks.ca
Sun Sep 2 09:47:31 EDT 2012


On Sun, Sep 02, 2012 at 09:38:21AM -0400, Greg Troxel wrote:
> 
> Ian Goldberg <ian at cypherpunks.ca> writes:
> 
> > On Sun, Sep 02, 2012 at 07:58:01AM -0400, Greg Troxel wrote:
> >> > Something's jogging my memory.  There was one (beta?) version of
> >> > libgcrypt that didn't correctly handle counter-mode encryption of
> >> > messages that weren't a multiple of the block size.  When used with
> >> > libotr, it would give exactly the error you reported.  But it should
> >> > give the same error with the old libotr (3.2.x), so that doesn't seem
> >> > like it's the right explanation.
> >> >
> >> > http://lists.cypherpunks.ca/pipermail/otr-dev/2011-April/001168.html
> >> 
> >> pkgsrc (and thus my system) has 1.5.0.  There are some pkgsrc patches,
> >> but they're about other things.  And I did not rebuild libgcrypt or
> >> pidgin, just libotr and pidgin-otr.
> >
> > Can you confirm that the 1.5.0 in pkgsrc already has the above patch
> > applied to it?
> 
> No, it doesn't.   I can add it.   But I assumed 1.5.0 was a real release
> and if there was a bug there would have been another real release of
> libgcrypt.

Well that's certainly a clue.  But the 1.5.0 release I see here:

ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.5.0.tar.bz2

*does* already have the above patch applied.  Yours doesn't?  Very
odd...

   - Ian



More information about the OTR-dev mailing list