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

Tried to self-cross-sign using legacy verif; failed with sig error #12858

Closed
ara4n opened this issue Mar 24, 2020 · 4 comments
Closed

Tried to self-cross-sign using legacy verif; failed with sig error #12858

ara4n opened this issue Mar 24, 2020 · 4 comments

Comments

@ara4n
Copy link
Member

ara4n commented Mar 24, 2020

Having failed to cross-sign my new RiotX from Riot/Web develop due to #12681, I tried to do it via legacy verification. This also failed, with a surprisingly overdetailed error message:

Screenshot 2020-03-24 at 23 29 49

https://github.com/matrix-org/riot-web-rageshakes/issues/2448

@ara4n ara4n added the T-Defect label Mar 24, 2020
@ara4n
Copy link
Member Author

ara4n commented Mar 24, 2020

(I did, in theory, upgrade to symmetric SSSS earlier today, in case it's relevant)

@bwindels
Copy link
Contributor

bwindels commented Mar 25, 2020

This appears to be because of element-hq/element-android#1170

@jryans
Copy link
Collaborator

jryans commented Mar 26, 2020

I'll track this for now, but it seems likely it will be resolved by Android side.

@jryans
Copy link
Collaborator

jryans commented Mar 31, 2020

I'm assuming this key rotation issue is fixed by element-hq/element-android#1172. As for too much detail in the error dialog, I filed #12942.

@jryans jryans closed this as completed Mar 31, 2020
t3chguy pushed a commit that referenced this issue Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants