-
Notifications
You must be signed in to change notification settings - Fork 264
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
Mark as verified if our own device matches keys #1348
Conversation
There seems to be some weirdness going on here with the CI, likely because the PR started out as a draft. Let's try to unwedge this. |
cd0c47a
to
4bc4a95
Compare
4bc4a95
to
9bb62bf
Compare
It was actually running a new test only present on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's please add the mentioned comment or some variation of it and we're good to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's see if @dkasak want's to take a look at this as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks generally good to me, apart from a minor suggestion.
Co-authored-by: Denis Kasak <[email protected]>
During migration we only convert private keys but not devices / identities. When we eventually query our own user and recieve current device, we will not consider it verified.
To solve this we mark current device as verified if just inserting it and we have master key stored locally.