This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Authority-discovery should be performed only by sentries #6264
Labels
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
Comments
rphmeier
added
the
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
label
Jun 6, 2020
26 tasks
As long as this isn't tackled, sentry nodes don't provide much protection. |
Yes. sentry nodes would imply the validator never even opens connections with anybody besides their sentries. |
Additionally, the validator should not perform the |
I believe that the solution is to add two small request-reponse protocols:
It should be quite easy to do that after #6634 is merged. |
Would be obsolete after #6762 |
Closing as obsolete. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
At the moment, validators publish the authority-discovery-related DHT records themselves. This is necessary because these records are signed with a key known to the validator only.
However, this reveals the validator's IP address.
Instead, the validator should send this signed record to its sentry nodes, and it's the sentry nodes that should perform the publication.
The text was updated successfully, but these errors were encountered: