forward: Remove capped path retrieval for shared dialer#24
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR removes the "feature" that stopped clients from retrieving the PathUsage information when using the shared dialer. At the beginning we were concerned this brought some security issues, more concretely, gaining information on what path other potential users of the shared dialer are using. It is not clear what attacker model we are contemplating and what are the implication. Therefore and for the sake of usability, we remove this constrain. In any case, if we ever see this a security problem, we should probably force every client to use its own dialer, which is probably a more robust solution in terms of security (although we should assess the resource usage implications).