-
-
Notifications
You must be signed in to change notification settings - Fork 605
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
Sign in with QR (MSC3906) compatibility with Rust Crypto #3761
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
081c1c2
Make MSC3906 implementation compatible with Rust Crypto
hughns c8790c3
Verify using CryptoApi but no cross-signing (yet)
hughns ed4f49b
Use new crossSignDevice() function
hughns 5cc344f
Mock crossSignDevice() function
hughns 87322a6
Fix type of parameter in mock
hughns 577d5ad
Merge branch 'develop' into hughns/msc3906-rust-crypto
BillCarsonFr bce3112
review: cleaning
BillCarsonFr 2ee3f9e
review: Remove unneeded defensive coding
BillCarsonFr df74bd5
Merge branch 'develop' into hughns/msc3906-rust-crypto
BillCarsonFr 5eeab19
review: fix outdated documentation
BillCarsonFr 0e9d3df
QR login: review, cleaning
BillCarsonFr a7ab4af
Merge branch 'develop' into hughns/msc3906-rust-crypto
BillCarsonFr 1f8bce0
QR login | review: use getSafeUserId
BillCarsonFr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I'm not entirely convinced this is useful. As I understand it, this doesn't actually do much at the typescript level (ie, it won't complain if you end up using a
DeviceID
where it wanted aUserID
), so the only purpose of such type aliasing is documentation... and frankly, I'd prefer to see documentation done as comments rather than as types.I'm not going to insist on changing anything here: rather sharing a thought for future reference.