Open JuzBeKind opened 7 years ago
Are you able to get a capture of the debug log (Help->Debug Window) while trying to auth the buddy? Alternatively, can you try initiating an OTR conversation with me and I'll try capture that debug? It could be that OTR is trying to send a message that is too long for Steam to transmit, but will need to see the debug log to know more.
Sorry for the delay. For whatever reason, developers don't usually respond to my bug reports. Here is the log covering the time period from shortly before the authentication message was sent to my buddy til a little while (maybe a minute?) after the buddy typed and sent the correct response.
Wanted to mention that this is still an issue and also give some extra information.
Firstly, it is worth mentioning that you can manually verify the correspondent via the plugin settings, but this means that you have to have another way of verifying that the fingerprint is actually the user you expect, perhaps because that person is standing next to you. If you do this, the OTR status for the user will now be green (verified).
Secondly, it seems that, next to the verification "handshake" not being able to be completed, the OTR option to automatically initate private OTR conversations also doesn't seem to work in combination with this plugin, even if the checkbox is checked in the plugin settings. This means that you have to enable OTR manually every time you initiate a conversation with someone over Steam and also that both sides have to do this, which is a bit cumbersome.
Everything's working fine so far except OTR buddy authentication. I'm able to send the authentication message to my buddy and the prompt appears on his end, and he's able to type in & send his response, but then it just hangs on his end and my end. On both ends it says 'waiting for buddy'. Same thing happens if he sends me the authentication message instead.
OS: Windows 7 64-bit DLL's: libsteam-1.6.1.dll, libjson-glib-1.0.dll Pidgin ver: Pidgin 2.10.12 (libpurple 2.10.12) OTR ver: 4.0.1