Double "buddy add" request in 3.1.10 #84

Closed
DaniSancas opened this Issue Apr 26, 2016 · 10 comments

Projects

None yet

2 participants

@DaniSancas

First of all, I don't know if I would be able to reproduce this bug, but I tell you how it happened.

Yesterday I was using v3.1.08, and received a "buddy add" request (it was expected). I added that buddy and closed Cryptocat (we had no chat). Today I had the Update notification for the v3.1.10, I downloaded it and executed, everything ok 'till now. Then I logged in and the same "buddy add" request from yesterday appeared. I accepted it again (still no chat with the new buddy, for the record).

Is that a bug? Could be someone trying to do a MITM? (I can ask my buddy analogically to verify the fingerprints, so not big deal). Thanks!

@DaniSancas DaniSancas changed the title from Double add request after update? to Double "budy add" request after update? Apr 26, 2016
Owner
kaepora commented Apr 26, 2016

I had this today too. Also happened with a third person (a friend of mine) who privately reported it.

It seems recent. It didn't happen before. Although I don't know what could have made this issue crop up. I'll look into it.

@kaepora kaepora added the bug label Apr 26, 2016
@kaepora kaepora self-assigned this Apr 26, 2016
@kaepora kaepora changed the title from Double "budy add" request after update? to Double "buddy add" request in 3.1.10 Apr 26, 2016
Owner
kaepora commented Apr 28, 2016

I am no longer able to reproduce this and now believe it was actually due to server maintenance that was occurring around the time the bug happened. Please let me know if it happens again and I will re-open the issue.

@kaepora kaepora closed this Apr 28, 2016

I've just re-opened the application and happened again!

For the record: I haven't talked to my buddy yet, I believe that hasn't logged in since added me. Version 3.1.10

@kaepora kaepora reopened this Apr 28, 2016
Owner
kaepora commented Apr 28, 2016

I just can't reproduce this.

I've closed and re-opened the application and this time the bug didn't reproduced. I'll try later to shutdown my computer and re-open the application to see what happens. Maybe this last time was an echo lost in time... 😸

@kaepora kaepora closed this Apr 29, 2016

Happened again. I've opened Cryptocat and updated to 3.1.11, then logged in and, surprise! The message appears again.

Owner
kaepora commented Apr 29, 2016

You were right about this. I figured out the cause: it was a server misconfiguration. This will likely happen again today but will not occur again in the future. My apologies.

You're welcome, mate! I'll let you know if it happens again.

Logged in again and then the bug did NOT appeared. I think we can definitely close this issue. Thanks!

Owner
kaepora commented May 2, 2016

Great. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment