Repository navigation
possible bug in initializeSenderSession #31
Description
Hi,
I wanted to run past you a possible bug I ran across in ratchet.go when debuggingg a problem I have been having with handshakes. here is a link to the specific line:
https://github.com/janimo/textsecure/blob/master/axolotl/ratchet.go#L196
when I compare against the java (and python) implementations of RatchetingsSession I see the equivalent code in those implementations using the derivedKeys.chainKey (rather than the sendingChain.chainKey):
here is a patch which changes the behavior as above and which works for me (correctly handles the cases I've been having trouble with).
I just wanted to check with you if there was any deliberate reason for deviating from how those other implementations handle it.
Thanks.
Activity
janimo commentedon Sep 7, 2016
Thanks, I'll look into this. What problem did you run into exactly?
gardenia commentedon Sep 7, 2016
Thanks. I had a personal project where I was was inter-operatinng with some java code which uses the official java axolotl library but it relied on the KeyExchangeMessage means of session building. I ported across the KeyExchangeMessage handling code to your go stuff but then found that there were cases where it didn't interoperate with the java. I found that it worked fine when in the Bob role but not in the Alice role and then eventually tracked it down to (suspected) the wrong chain having theen persisted in the code I referenced
(in case it helps at all, here is a repo which contains an acceptance testing tool I built to compare the java behavior https://github.com/gardenia/axolotl-sandbox)