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.

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

Created a room on mobile and encrypted it but it the encryption option is off on riot web #3776

Closed
Qwertie- opened this issue Apr 30, 2017 · 6 comments
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@Qwertie-
Copy link

On riot for android (fdroid 0.6.9) I created a room with another user with the button on their profile, I then enabled encryption. Everything working fine so far, both of us are talking with e2e enabled. I then loaded riot web development version and the room is full of
** Unable to decrypt: The sender's device has not sent us the keys for this message. **

Messages sent from web send unencrypted and the encryption option on web is unticked. I reloaded the page and nothing changed.

Attempting to enable encryption from web does nothing.

@lampholder lampholder added T-Defect S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-E2EE labels May 1, 2017
@lampholder
Copy link
Member

After joining from Riot web, when you (or the other user) try and send a message does it warn you that there's a new device in the room? I believe that a user with a verified device will have to verify your new device before it can send and receive encrypted messages.

That said, it sounds like there's another bug at play here - the room settings (the 'encryptedness' of the room) should be the same regardless of the device that's accessing the room.

Do you have any logs that you can share?

What do you mean by "Messages sent from web send unencrypted" - can you describe what this looks like?

Thanks!

@lampholder lampholder added the P1 label May 1, 2017
@Qwertie-
Copy link
Author

Qwertie- commented May 2, 2017

After joining from Riot web, when you (or the other user) try and send a message does it warn you that there's a new device in the room? I believe that a user with a verified device will have to verify your new device before it can send and receive encrypted messages.

I got this message and pressed send anyway on mobile and I got no message on web.

Not aware of any logs but when I send from desktop it shows up on my phone with the unlocked icon and on web I see "send a message (unencrypted)" in the text box.

@lampholder
Copy link
Member

HI @Qwertie- - if you scroll to the bottom of the global settings page (found by clicking the cog in the bottom left corner) you'll find a 'report a bug' button - clicking this will let you submit Riot logs to help with diagnosing an issue such as this.

@lampholder
Copy link
Member

Do you know if the encrypting event might have been redacted, as per https://github.com/vector-im/riot-web/issues/3498 ?

This is a little trick to verify - you might be able to see the redacted image in the timeline at a likely-looking spot in the history.

@Qwertie-
Copy link
Author

The event was not redacted. I recently reinstalled my OS so firefox's storage was wiped and when I relogged in to riot the room was showing as encrypted properly now.

@lukebarnard1
Copy link
Contributor

I can't reproduce this. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants