How to check if a FTP server supports EPSV (Extended Passive) mode
up vote
1
down vote
favorite
From this answer, I now know what is the difference between PASV
and EPSV
modes. Is there a definitive way of knowing if the FTP server supports EPSV
?
Is it enough to just check the response of the EPSV
command?
ftp
add a comment |
up vote
1
down vote
favorite
From this answer, I now know what is the difference between PASV
and EPSV
modes. Is there a definitive way of knowing if the FTP server supports EPSV
?
Is it enough to just check the response of the EPSV
command?
ftp
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
From this answer, I now know what is the difference between PASV
and EPSV
modes. Is there a definitive way of knowing if the FTP server supports EPSV
?
Is it enough to just check the response of the EPSV
command?
ftp
From this answer, I now know what is the difference between PASV
and EPSV
modes. Is there a definitive way of knowing if the FTP server supports EPSV
?
Is it enough to just check the response of the EPSV
command?
ftp
ftp
asked Nov 15 at 7:54
Anirudh Sridhar
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Send the FEAT
command. Defined in RFC 2389, it is the primary mechanism used by clients to discover supported features. IANA maintains a list of FTP commands and their FEAT codes.
If the server says that FEAT itself isn't a recognized command, it is best to assume that the FEAT-negotiated extensions such as EPSV are not supported either.
As for directly trying EPSV
(discovery by brute force), it might work in most cases but I think it also has a chance of triggering server or even router bugs, so I wouldn't use this method myself. Besides, you'll probably end up using FEAT for various other reasons anyway.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Send the FEAT
command. Defined in RFC 2389, it is the primary mechanism used by clients to discover supported features. IANA maintains a list of FTP commands and their FEAT codes.
If the server says that FEAT itself isn't a recognized command, it is best to assume that the FEAT-negotiated extensions such as EPSV are not supported either.
As for directly trying EPSV
(discovery by brute force), it might work in most cases but I think it also has a chance of triggering server or even router bugs, so I wouldn't use this method myself. Besides, you'll probably end up using FEAT for various other reasons anyway.
add a comment |
up vote
2
down vote
accepted
Send the FEAT
command. Defined in RFC 2389, it is the primary mechanism used by clients to discover supported features. IANA maintains a list of FTP commands and their FEAT codes.
If the server says that FEAT itself isn't a recognized command, it is best to assume that the FEAT-negotiated extensions such as EPSV are not supported either.
As for directly trying EPSV
(discovery by brute force), it might work in most cases but I think it also has a chance of triggering server or even router bugs, so I wouldn't use this method myself. Besides, you'll probably end up using FEAT for various other reasons anyway.
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Send the FEAT
command. Defined in RFC 2389, it is the primary mechanism used by clients to discover supported features. IANA maintains a list of FTP commands and their FEAT codes.
If the server says that FEAT itself isn't a recognized command, it is best to assume that the FEAT-negotiated extensions such as EPSV are not supported either.
As for directly trying EPSV
(discovery by brute force), it might work in most cases but I think it also has a chance of triggering server or even router bugs, so I wouldn't use this method myself. Besides, you'll probably end up using FEAT for various other reasons anyway.
Send the FEAT
command. Defined in RFC 2389, it is the primary mechanism used by clients to discover supported features. IANA maintains a list of FTP commands and their FEAT codes.
If the server says that FEAT itself isn't a recognized command, it is best to assume that the FEAT-negotiated extensions such as EPSV are not supported either.
As for directly trying EPSV
(discovery by brute force), it might work in most cases but I think it also has a chance of triggering server or even router bugs, so I wouldn't use this method myself. Besides, you'll probably end up using FEAT for various other reasons anyway.
answered Nov 15 at 8:28
grawity
227k35476539
227k35476539
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375575%2fhow-to-check-if-a-ftp-server-supports-epsv-extended-passive-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown