-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fix error that invite link doesn't work inside chat #2246
Merged
Merged
Changes from 23 commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
f9f2c60
chore: added a small update and Cypress try
Silver-IT 4991725
chore: added comment and Cypress retry
Silver-IT 4eacdaf
chore: check if group-chat passes three times in a row
Silver-IT fec63dd
chore: group-chat passes 4 times in a row
Silver-IT 5afb858
chore: 5 times pass in a row means it fixes the heisenbug? maybe it's…
Silver-IT fb2fdcf
fix: error in invitelink
Silver-IT f266872
feat: update Cypress according to the updated invitelink format
Silver-IT 53a035c
fix: cypress errors according to the changes of inviteLink format
Silver-IT 073ed15
chore: added comment and Cypress retry
Silver-IT acf6cb9
chore: updated comment and Cypress retry
Silver-IT 77df8ce
fix: added cy.wait and Cypress try
Silver-IT 7b189d9
chore: added comment and Cypress retry
Silver-IT a1aa3ec
fix: removing cy.wait
Silver-IT 65ae37c
chore: updated comment and check Cypress passed 2 times in a row
Silver-IT cde5c76
chore: really passes 3 times in a row?
Silver-IT 57d7c2e
Merge branch '2226-heisenbug-in-group-chatspecjs-more-persistent-one'…
Silver-IT a4a9879
chore: updated comment and Cypress retry
Silver-IT 60ffd1c
chore: cypress retry
Silver-IT 6988a2d
chore: Cypress retry
Silver-IT 268837d
Merge branch 'master' into 2240-invite-links-not-working-reliably
Silver-IT e220d33
chore: Cypress retry
Silver-IT 7d35a2b
chore: Cypress retry
Silver-IT c5ba7fc
chore: Cypress retry
Silver-IT 9ae5dc3
fix: heisenbug in group-proposal
Silver-IT 93d4c32
feat: changed query to hash for security problem
Silver-IT 64c7ff1
fix: reverted the format of hash param
Silver-IT 6330f3d
fix: eslint error
Silver-IT 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
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
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
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
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.
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.
@corrideat Need your review on this
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.
Actually, the hash symbol
#
was not needed since we saved all the parameters inside query which lies after?
.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.
That's wrong, the
#
is needed, see f8cac66#diff-ab2099fc20649c2e08f92b0ca5b846b5073fc274c7d740b8e1baec7bcd26b92aR98There 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.
(also, if for some reason it works without a
#
, that's a bug: the query must not contain secrets)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.
@Silver-IT This PR needs to be closed while keeping this URL using a
#
.The reason we're using a hash here is because the hash prevents the server from learning about what groups the user is joining, and also prevents the invite secret from being shared with the server.
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 answered both of these questions in my reply above.
If the invite secret is shared with the server then it's not so secret anymore and the server could use it to join the group.
Regarding:
I'm not sure, perhaps it's to make it easier for using with
URLSearchParams
?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.
So do you mean the first one is good in terms of secret and the second one is bad?
And it's just the format change of invite link. There is no more changes. I can't understand what you mean by secret problem. What is the different on the server side when the user uses these two formats?
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.
Yes.
The first one sends all of that information to the server and the second one doesn't.
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.
Now, I think I understood what you mean, @taoeffect. So we should use
hash
instead ofquery
for the security reason.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.
Yep! 👍