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

"Wrong Security Key" despite setting in the correct key #16455

Closed
PeakPuzzle opened this issue Feb 15, 2021 · 2 comments
Closed

"Wrong Security Key" despite setting in the correct key #16455

PeakPuzzle opened this issue Feb 15, 2021 · 2 comments
Labels
A-E2EE-Cross-Signing T-Other Questions, user support, anything else

Comments

@PeakPuzzle
Copy link

Description

"Worng Security Key" Disprite setting in the correct Security key.

Steps to reproduce

  • For bugs, list the steps
  • that reproduce the bug
  • using hyphens as bullet points

Describe how what happens differs from what you expected.

Whenever I want to verify my devices, I cannot use my Security Key since i apparently entered the "Wrong" Security Key, Despite having the Correct one.

I've tried to use the Encryption Secure Backup to generate different Secure Keys as well, but I'm still denied access to verification
Screenshot_38
.

Version information

  • Platform: web (in-browser) or desktop?

For the web app: Firefox, Windows, app.element.io, riot.im

  • Browser: Chrome, Safari, Firefox? which version?
  • OS: Windows, macOS, Ubuntu, Arch Linux, etc?
  • URL: develop.element.io / app.element.io / somewhere else? If a private server, what version of Element Web?

For the desktop app: Windows, 1.7.20

  • OS: Windows, macOS, Ubuntu, Arch Linux, etc?
  • Version: 1.x.y
@jryans jryans changed the title "Worng Security Key" Disprite setting in the correct key. "Wrong Security Key" despite setting in the correct key Feb 24, 2021
@jryans
Copy link
Collaborator

jryans commented Mar 5, 2021

I recommend trying to reset cross signing and secret storage:

  1. Consider exporting room keys to a file as a backup in an existing session via top left menu -> Settings -> Security -> Export E2E room keys (but you've said you don't have encrypted rooms at the moment)
  2. If you don't have an existing develop session, it should be fine to login and skip any verification prompts
  3. Reset secure backup first (this should now succeed without confusingly asking for previous keys)
  4. Reset cross-signing keys (this may prompt for security key / phrase, it's expecting the new one you just made in step 2)
  5. On other sessions, you should be able to either verify the new session and receive new keys or go to Settings and "setup" Secure Backup (green button instead of the red "reset"), which maybe prompt for the new security key / phrase as part of downloading your keys

@jryans
Copy link
Collaborator

jryans commented Apr 12, 2021

It doesn't seem like the reporter is following this issue, and we have #16118 for the general problem.

@jryans jryans closed this as completed Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-Cross-Signing T-Other Questions, user support, anything else
Projects
None yet
Development

No branches or pull requests

2 participants