data connection stealing and bounce attack mitigation #251
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 patch improve security for passive connections and fixes bounce attacks for active ones.
IPMatchRelaxed
andIPMatchTrusted
are useful for passive connections if using haproxy. We can get rid of these settings if we expose a callback for the passive connection listener, so we can provide a custom listener that decodes the proxy header and get the real client IP as we do for the control connection. ProFTPD does not recommend to enable the proxy header for data connections and I followed the same recommendation for SFTPGo until now, no problem to change if you prefer this way.See the FAQ here