You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Query mode are currently always accessible, this leads to serious issue (totally unsecure), replying in 'proxy' mode to stuck a peer or sending 'aproxy' query in some sensitive network, and a lot of possible misuse.
Possible query mode should be configurable. We need a rules to return the allowed mode for a given dht (a simple bit mask), with obvious filtering on message reception in server.
More advanced filtering should also be based upon kind of query, so an optional parameter with &key could be added. This will be usefull with network where multiple mode are used for multiple usecases.
The text was updated successfully, but these errors were encountered:
Query mode are currently always accessible, this leads to serious issue (totally unsecure), replying in 'proxy' mode to stuck a peer or sending 'aproxy' query in some sensitive network, and a lot of possible misuse.
Possible query mode should be configurable. We need a rules to return the allowed mode for a given dht (a simple bit mask), with obvious filtering on message reception in server.
More advanced filtering should also be based upon kind of query, so an optional parameter with &key could be added. This will be usefull with network where multiple mode are used for multiple usecases.
The text was updated successfully, but these errors were encountered: