Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

?OTR?v2? has requested an Off-the-Record private conversation #7

Open
xeverse opened this issue Feb 6, 2015 · 13 comments
Open

?OTR?v2? has requested an Off-the-Record private conversation #7

xeverse opened this issue Feb 6, 2015 · 13 comments

Comments

@xeverse
Copy link

xeverse commented Feb 6, 2015

?OTR?v2? ... has requested an Off-the-Record private conversation. However, you do not have a plugin to support that. See http://otr.cypherpunks.ca/ for more information.

But I do have the plugin installed and enabled.
local/libotr 4.1.0-1
@Ri0n
Copy link
Member

Ri0n commented Feb 7, 2015

can you check this with Psi on other side?
if it works then attach xml logs for both cases

@xeverse
Copy link
Author

xeverse commented Feb 7, 2015

ok. I will. Yep, some clients work fine. Others don't.
i can attach the xml console log but as far as i can see
there's nothing new. Just the same message with a bunch of xml tags.

What is it anyway? OTR proto v4 can't recognize v2 requests? and
is it the underlying system libotr or the psi-plus plugin implementation causing this?

@Ri0n
Copy link
Member

Ri0n commented Feb 9, 2015

I don't know. have to check it.

2015-02-08 2:33 GMT+05:00 xeverse notifications@github.com:

ok. Yep, some clients work fine. Others don't.
i can attach the xml console log but as far as i can see
there's nothing new. Just the same message with a bunch of xml tags.

Is it the underlying system libotr or the psi-plus plugin implementation
causing this?

—
Reply to this email directly or view it on GitHub
#7 (comment).

@tehnick
Copy link
Member

tehnick commented Feb 11, 2015

What versions of Psi+ and OTR plugin are you using? In which distro?

@xeverse
Copy link
Author

xeverse commented Feb 11, 2015

I'm on Arch liGnux.
local/psi-plus-git 0.16.441-1
local/psi-plus-plugins-git 0.15.443-1
Linux 3.18.4-1-ARCH x86_64 GNU/Linux
Psi plus installed from AUR ABS latest git.

THis is getting really weird. Sometimes i get the message --
"?OTRv23? ... has requested an Off-the-Record private conversation. However, you do not have a plugin to support that."
and then "Unverified conversation started". Like just now when i was testing pidgin & psi-plus.
Although the other day no private conversation was initiated whatsoever.

Also -- https://bugs.otr.im/issues/77

I'm gonna test some more with other clients and will update.

@tehnick
Copy link
Member

tehnick commented Feb 12, 2015

local/psi-plus-plugins-git 0.15.443-1

This is not the version of OTR plugin (or any other Psi+ plugin). Please look at:
Psi+ Options --> Plugins --> Off-the-Record Messagin Plugin --> Version

Also you may read the changelog of OTR plugin here:
https://github.com/psi-plus/plugins/blob/master/generic/otrplugin/changelog.txt

@xeverse
Copy link
Author

xeverse commented Feb 12, 2015

1.0.2

@tehnick
Copy link
Member

tehnick commented Feb 12, 2015

1.0.2

Hmm, it is strange. I don't have any troubles with using OTR for communicating with Pidgin users since 0.9.7. But I am not sure if they are using the latest version of Pidgin. This issue needs more research.

@g4jc
Copy link

g4jc commented Aug 7, 2015

I am also getting this error when chatting to pidgin users using latest pidgin. The error shows and then proceeds to work after OTR does a refresh.

@Vitozz Vitozz mentioned this issue May 18, 2016
Closed
@Ri0n Ri0n mentioned this issue Mar 21, 2018
Open
@gbougadis
Copy link

Did you guys figure this out I'm now having this issue. I realize this was a couple years ago if you even remember.

@tehnick
Copy link
Member

tehnick commented Sep 20, 2018

@gbougadis Make sure that Psi OTR plugin in built exactly with the same version of libotr with which in runs, because it has very strange runtime check of own version. In Debian we even use special patch for disabling this ugly behavior:
https://salsa.debian.org/pkg-privacy-team/libotr/blob/master/debian/patches/0001-Do-not-error-out-when-an-application-is-run-against-.patch

@Neustradamus
Copy link
Contributor

I have the problem, tested today on Windows x86 (Psi and Psi+), OTR enabled in two clients.

Generated key OK for two differrent JID in two different clients with one JID
The contact key has been verified in two client.

Request from Psi:
<message to='xxx1@xxx.xxx' type='chat'><subject></subject><body>?OTRv23? *xxx2@xxx.xxx* has requested an Off-the-Record private conversation. However, you do not have a plugin to support that. See https://otr.cypherpunks.ca/ for more information.</body></message>
[XX:XX:XX] *** Attempting to start a private conversation

Psi+:

<message xml:lang="en" to="xxx1@xxx.xxx/client" from="xxx2@xxx.xxx/client" type="chat">
<archived xmlns="urn:xmpp:mam:tmp" id="1543520254757080" by="xxx1@xxx.xxx"/>
<stanza-id xmlns="urn:xmpp:sid:0" id="1543520254757080" by="xxx1@xxx.xxx"/>
<body>?OTRv23? *xxx2@xxx.xxx* has requested an Off-the-Record private conversation.  However, you do not have a plugin to support that. See https://otr.cypherpunks.ca/ for more information.</body>
<subject/>
</message>

@Neustradamus
Copy link
Contributor

@xeverse, @g4jc, @gbougadis: Do you always use OTR?

Do you use OMEMO?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Ri0n @Neustradamus @tehnick @g4jc @xeverse @gbougadis