-
Notifications
You must be signed in to change notification settings - Fork 5k
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
SIWE - Force match between origin domain and URI #16295
Comments
Based on a call with Spruce, we'll be implementing v1 with dapp request blocking when there's a mismatch of ABNF mismatch, signature validity, and domain binding. @holantonela thoughts on the below suggested revisions? Revisions
Future IterationsFor subsequent versions, we'll provide users the ability to 1) turn domain allow list on on settings saved locally, 2) add/remove domains to that allow list. |
An update from the team. We're going to bypass the user-facing alert described in #2 above. If the domain listed in the SIWE request does not match the domain the user is on, MetaMask will reject it via a dapp API method. There will be no user-facing alerts or recovery path. @skgbafa would you be able to work on the changes on the UI end? |
Closed by #16616 |
There is a concern about exposing users to a warning message when domain binding verification is not OK. This implementation has been done following EIP-4361.
The proposal is for us to force dapps to match origin request domains with the URI field in the transaction. The expected iteration rejects the transaction and exposes a warning to the dapp through the API.
Slack Ref https://consensys.slack.com/archives/CN2H44RAM/p1666368532006679
I'd like to hear positions about moving forward with this or not and also extending this enforcement to other transactions as well.
The text was updated successfully, but these errors were encountered: