Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMigrate legacy trust to cross-signing #12619
Closed
Comments
|
There's also a .. chick and egg problem here I think ... if I only attempt migrating once I enable cross-signing, and I am the first one of my contacts to do so, I won't be able to migrate as nobody has uploaded cross-signing keys yet. So apart from attempting it automatically when enabling cross-signing, we might also want the user to explicitly attempt migration by e.g. a button in the security settings. |
|
The time window for this has mostly passed now that cross-signing has released. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ensure that If I bootstrap SSSS after legacy verifying, my legacy verifications should be migrated to signing those users.
The JS-SDK already has some code for this, but the react-sdk isn't providing the
shouldUpgradeDeviceVerificationscallback yet. We're relying there on the device having signed the master key, which we currently only do during bootstrapping. We discussed all devices signing the master key with their device key once they start participating in cross-signing, but deemed it not worth it. So this means that you will only be able to migrate legacy trust if you had legacy verified the device on which the other user has bootstrapped cross-signing.