WIP: Initial FXP RFC with Secure FXP (SSCN) and IPv6 support#512
Open
tsautier wants to merge 1 commit intodrftpd-ng:masterfrom
Open
WIP: Initial FXP RFC with Secure FXP (SSCN) and IPv6 support#512tsautier wants to merge 1 commit intodrftpd-ng:masterfrom
tsautier wants to merge 1 commit intodrftpd-ng:masterfrom
Conversation
2418ba6 to
5df9f24
Compare
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
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.
Problem
The current FXP (Server-to-Server) implementation lacks a defined standard for security enforcement. Specifically, the data connection between slaves is not mutually authenticated, leaving it vulnerable to "confused deputy" attacks. Additionally, IPv6 support (EPRT/EPSV) is missing.
Solution
Created an initial Request for Comments (RFC) document to propose a standard for "Secure FXP" within DrFTPD.
Changes Made
EPRTandEPSVcommands (RFC 2428).