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

Cross-signing: refactor secret storage loading at startup and show user shield in member details panel #1062

Merged
merged 36 commits into from
Mar 27, 2023

Conversation

bwindels
Copy link
Contributor

@bwindels bwindels commented Mar 24, 2023

Makes the crossSigning object available on Session after load is called, so it is immediately available to the UI when first shown.
Checks all the signatures in the chain to see if a user is trusted.

image

…te store

This will make it easier to sign and verify signatures with these keys,
as the signed value needs to have the same layout when signing and
for every verification.
In order to sign and verify signatures of design keys, we need
to have them in the format as they are uploaded and downloaded
from the homeserver. So, like the cross-signing keys, we store
them in locally in the same format to avoid constant convertions.

I also renamed deviceIdentities to deviceKeys, analogue to
crossSigningKeys. In order to prevent mistakes in this refactor,
I also converted DeviceTracker to typescript.
as it ends up in the value we're signing and uploading,
corrupting the signature
as this field also reflects the tracking status of the cross-signing
keys for a given user.
always store them, if not we'll think that the user hasn't uploaded
the cross-signing keys if we don't store them in spite of invalid or
missing signature.
@bwindels bwindels marked this pull request as ready for review March 24, 2023 22:14
Copy link
Member

@MidhunSureshR MidhunSureshR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bwindels bwindels merged commit 07df6a8 into master Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants