Ian Goldberg <i...@cypherpunks.ca> writes: > You can paste the message into the otr_parse program that comes with > libotr. But also please send them to me in non-list email. The message > seny when you click the button should say ?OTRv23?, the reply should > start with ?OTR:AAMC, (C for "commit") the reply to that should start > with ?OTR:AAMK (K for "key"), the reply to that should start with > ?OTR:AAMR (R for "reveal"), and the last message in the AKE starts with > ?OTR:AAMS (S for "signature"). The "M" in each case indicates the OTRv3 > protocol.
I saw init, C, K, R, and I think the originator objected to the R message. There was no S message. > 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. (I sent you the actual bits off-list.)
pgpTOjMB7BRxn.pgp
Description: PGP signature
_______________________________________________ OTR-dev mailing list OTR-dev@lists.cypherpunks.ca http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
