Replies: 1 comment 5 replies
-
Can you please clarify what the user would be signing and how this would change the existing payload? I'm assuming the URL. Does this need to be passed to the contract or can we allow it to be checked only by the Provider? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, we disallow duplicate provider urls to stop people from routing their provider record on the contract to someone else's running provider node.
This works, however a simple reverse proxy can get around this easily.
Given that a user has to sign a payload which has the chosen provider in, it's impossible for a reverse proxy to work as the provider would notice the commitment was not destined for them. Further, the provider would also check whether it was them selected for the captcha challenge, quickly discovering it was not.
Given these measures are already in place, I don't think we need the url duplication guard in the contract. A provider would naturally reject commitments when it isn't the chosen provider / interacting provider
Beta Was this translation helpful? Give feedback.
All reactions