My fingerprint missing during OTR conversation

[ghost]

I ran fresh installs on two devices and initiated an OTR session successfully. When I call "otr:fingerprintForAccountName" I get their fingerprint as expected. But when I call "otr:activeFingerprintForUsername" to retrieve my fingerprint I get an empty string @"".

I double checked using "otr:requestAllFingerprints" and this confirms I only have the one fingerprint for the other side of the OTR conversation.

I kind of assumed "my" fingerprint would be available if OTR initiated successfully. Going through the API's nothing really stands out something I have missed. But I do seem to be missing something nevertheless.

Any help would be appreciated. I want to do the right thing but I am not sure I know what that is ;(

[chrisballinger]

Hmm that's strange, are you using the latest code from the master branch?

[ghost]

I updated 2 weeks ago and have rewiewed the latest changes but there seemed nothing to be concerned about.

So I rejigged things a bit:

I reset the App and I call: initiateEncryptionWithUsername sends off ?OTR?

Then I get get back: willStartGeneratingPrivateKeyForAccountName didFinishGeneratingPrivateKeyForAccountName showFingerprintConfirmationForTheirHash

And everything is great and I have my fingerprints / hashes.

But if I cancel and re-initiate OTR the following are not called because the Keys have been generate for that user previously. willStartGeneratingPrivateKeyForAccountName didFinishGeneratingPrivateKeyForAccountName showFingerprintConfirmationForTheirHash

I then call the following to get the fingerprints: fingerprintForAccountName activeFingerprintForUsername

My fingerprint is @“” and theirs is correct. It looks like my hash / fingerprint isn’t getting save in Libotr (guessing here)

So should I be forcing the regeneration of the keys every time I initiate OTR? How do I correctly force regeneration if I should be doing this If I generate a key for myself via “generatePrivateKeyForAccountName" is this valid, because at this point that is what seems to work.

Thanks Clay

On Jul 22, 2014, at 12:39 PM, Chris Ballinger [email protected] wrote:

Hmm that's strange, are you using the latest code from the master branch?

— Reply to this email directly or view it on GitHub.

[ghost]

What I am investigating now is that OTRKit doesn't have my AccountName so when I ask it throws up its hands. While showFingerprintConfirmationForTheirHash has complete with success it didn't know who me was at the time.

I will let you know how this goes ...

[ghost]

Closing as things around verification seems a little up in the air at the mo.

[stoyan-simov-vox]

I have the same problem. I checkout fresh working copy 2 days ago. But it seems that something is broken