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

Rocketchat 1.0.3 little green OTR Key Icon is missinng #14477

Closed
himpierre opened this issue May 13, 2019 · 8 comments · Fixed by #14953
Closed

Rocketchat 1.0.3 little green OTR Key Icon is missinng #14477

himpierre opened this issue May 13, 2019 · 8 comments · Fixed by #14953

Comments

@himpierre
Copy link

Description:

Since upgrading from 0.74.3 to 1.0.3 the sweet little green key icon is missing, indicating the messages are protected by OTR. OTR itself works.

Steps to reproduce:

  1. Start OTR conversation
  2. Enter message
  3. No green key icon

Expected behavior:

Green key icon shows you are in a OTR session.

Actual behavior:

No green key icon.

Server Setup Information:

  • Version of Rocket.Chat Server: 1.0.3
  • Operating System: Linux
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Yes
  • NodeJS Version: 8.12.0
  • MongoDB Version: 3.6
@myura
Copy link

myura commented May 20, 2019

I went through the same upgrade path, and the OTR message green key icon no longer appears for me as well - hopefully this wasn't an intentional change, since having the icon is a perfect indicator for if you're sending/receiving messages in an OTR session or not.

@geekgonecrazy
Copy link
Contributor

Does this still work for e2e mode? If so might be a clue as to what’s happening

@Zuko
Copy link

Zuko commented May 23, 2019

Same issue (noticed yesterday)

@mddvul22
Copy link

mddvul22 commented Jun 3, 2019

This is impacting us, also. What needs to be done to get this addressed? While OTR is working, I believe you can argue this is a security issue, as users are losing trust in Rocket Chat to protect their OTR sessions, as they can't verify that an OTR session is actually established.

@AmShaegar13
Copy link
Contributor

This issue persists in v1.1.2.

@gdressman
Copy link

We also are seeing the same behavior

@cortex3
Copy link

cortex3 commented Jul 4, 2019

We're experiencing this issue in v1.2.1 as well.

@myura
Copy link

myura commented Jul 11, 2019

thanks @ggazzo, hopefully this gets merged into a release soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants