-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
New cross-signing device doesn't trust itself #12884
Comments
for completeness, here's my
|
Is this reproducible on the develop branch? Cross signing is in very active development so the 1.5.13 release code is quite stale at this point. |
@dbkr Is there a place I can get a build of the dev branch? |
@tleydxdy https://riot.im/develop is the easiest way to access it. It's updated every time a change is merged. |
@jryans I was having trouble with it logging me out when ever my internet becomes bad (happened mutiple time) therefore why I tried to host it myself. maybe I should make a issue about that too |
This issue looks like it's bitrotted. I doubt it's still happening. |
#12884) * Refactor the various email/phone management UI into a single component These were basically the same component copied & pasted 3 times and tweaked to match the behaviour of each case. This de-dupes them into one component. This all could really benefit from playwright tests, but would require setting up a dummy ID server in the playwright tests. This is all legacy pre-MAS stuff so its questionable whether its worth the effort. * Basic test, remove old tests * Use different text to confirm remove & put headers back although the two texts are both 'Remove' in practice * Remove string This was never triggered anyway with sydent & synapse because they don't seem to agree on what error to return. In any case, I think it makes more sense for it to be consistent with the email path, ie. using a dialog. * Avoid nested forms * Snapshots * More snapshots * Test the hs side * Snapshots * Test IS bind/revoke * Test remove can be cancelled * Test unvalidated cases & fix phone error * Reset state between tests * Import useState directly * One more direct React import
Description
Upon starting a new session, riot didn't prompt me to enter my secret storage password, but it trusted every device I got except itself. Clicking manual verify just spins forever.
Steps to reproduce
Unclear
Logs being sent: no,
Failed to send logs: HTTP 0
Version information
For the web app:
The text was updated successfully, but these errors were encountered: