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.

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

ChatSecure tries to initiate an OTR session even when an OMEMO session has already been established #788

Open
Spydar007 opened this Issue Jun 17, 2017 · 15 comments

Comments

Projects
None yet
8 participants
@Spydar007
Copy link

Spydar007 commented Jun 17, 2017

This is probably going to be a duplicate of something else.

I have had it confirmed from numerous contacts that, when the "Best Available" option is selected, ChatSecure keeps attempting to (so much that it spams the chat) initiate an OTR session even after an OMEMO session has been established.

To stop it, you have to change the Encryption Settings to be "OMEMO" only.

@chrisballinger chrisballinger added this to the 4.1 milestone Jun 17, 2017

@chrisballinger

This comment has been minimized.

Copy link
Member

chrisballinger commented Jun 17, 2017

Ah yes, I meant to change this default in v4.1.0 because OTRDATA file transfer is no longer needed now that we have XEP-0363. Thanks for the reminder.

@link2xt

This comment has been minimized.

Copy link

link2xt commented Jun 25, 2017

@chrisballinger XEP-0363 is just uploading files to web server and transferring a link. It is not encrypted. OTRDATA file transfer is end-to-end encrypted.

Before switching to XEP-0363 this problem should be solved, for example by encrypting files and transferring a key in message along with the link.

Edit: I see that #736 has aesgcm:// item, cool.

@afriedmanGlacier

This comment has been minimized.

Copy link
Contributor

afriedmanGlacier commented Jun 27, 2017

I pulled a file over from our server that was sent with HTTP Upload using OMEMO and it said "The file ... could not be opened" and "It may be damaged or use a file format that Preview doesn't recognize" so, I'm thinking its encrypted for us though I'm not sure if there is anything else to check

@chrisballinger

This comment has been minimized.

Copy link
Member

chrisballinger commented Jun 27, 2017

The transfers are encrypted as long as you aren't using "plaintext" mode.

@ronnicek

This comment has been minimized.

Copy link

ronnicek commented Aug 21, 2017

Hi,

yep, I see still error like in #611.

OMEMO is on on both clients and other side is getting following from me:

**Unencrypted** ?OTRv23?
<b>myjid@mydomain.tld</b> has requested an <a href="https://otr.cypherpunks.ca/">Off-the-Record private conversation</a>.  However, you do not have a plugin to support that.'
@therob84

This comment has been minimized.

Copy link

therob84 commented Oct 4, 2017

Is dropping OTR support in ChatSecure on the roadmap? I already heard this for Conversations' in some discussions thereover....CS should/could follow in this case to further minimize error causes and confusion about different encryption methods...

@chrisballinger

This comment has been minimized.

Copy link
Member

chrisballinger commented Oct 4, 2017

@therob84

This comment has been minimized.

Copy link

therob84 commented Jan 25, 2018

Mayne it is conected to this issue: between a ChatSecure contact and my gajim client (in parallel with an conversations client) frequently I get (error/notification) messages "OTR message which my client does not support" at gajim sent by chatsecure, although there is a working omemo connection...
The OTR messages (I can paste the quote tmrw) are sent "in background", means without the contact did sent any payloaded message from CS (thus due to some status/typing/chat markers or anything else going on in session establishing in CS?) . I only get this in gajim, but not in Conversations (both connected to my same account). Quite annoying.

@chrisballinger

This comment has been minimized.

Copy link
Member

chrisballinger commented Jan 26, 2018

I thought this was fixed already :(

@therob84

This comment has been minimized.

Copy link

therob84 commented Jan 26, 2018

@chrisballinger

This comment has been minimized.

Copy link
Member

chrisballinger commented Jan 26, 2018

@therob84

This comment has been minimized.

Copy link

therob84 commented Jan 26, 2018

No.
I am not using iOS (only Conversations@Android, Gajim@Windows).
I just asked some friends to use CS@iOS and thus are limited in advices to them, just helping with problems and convincing them in continue using XMPP with me :-/

@Echolon

This comment has been minimized.

Copy link

Echolon commented Feb 6, 2018

Hi, yes - I'd like to support the approach at least prevent CS to establish OTR automatically and instead enforce omemo. Furthermore, I experienced that the menu with settings for encryption is kinda hidden and not very easy to handle with all these abilities who encryption should be prioritised (for a normal user).

(The first thing leads in Conversations to the situation that it asks me all the time to verify OTR session...)

Cheers

@therob84

This comment has been minimized.

Copy link

therob84 commented Feb 12, 2018

And onother OTR issue, maybe connected to this one:

My contacts using ChatSecure (4.2.1) occasionally receiving messages like ?OTR Error:null although I definetively did not initiate any OTR sessions in Conversations & Gajim from my side. I never use OTR and the CS contacts complaining regularly about OTR-error-messages. :-/

I do hope for improvements in a coming release (any projected release-date yet, @chrisballinger?).

@jotwewe

This comment has been minimized.

Copy link

jotwewe commented Mar 27, 2018

I got the same messages as described in #788 (comment) from a client using chatsecure 4.2.1, until he switched from "best available" encryption to "OMEMO only".

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