Ask a Question

Rebex FTP/SSL: working with drftpd servers

0 votes
by (120 points) 

var fp = new Ftp
{
    LogWriter = new ConsoleLogWriter(LogLevel.Debug),
    Passive = true,
    Settings = {UseLargeBuffers = true},
    Timeout = 30000,
    SecureTransfers = true,
};
fp.Settings.SslAllowedSuites = TlsCipherSuite.All;
fp.Settings.SslAllowedVersions = TlsVersion.TLS12;
fp.Connect(host, port, securityMode);
fp.Login(username, password);
fp.ChangeDirectory("/Stats/");
var files = fp.GetList();

Applies to: Rebex FTP/SSL

1 Answer

0 votes
by (150k points)
edited by

by (120 points)
log file has been sent to support@rebex.net
by (150k points)
We asked for additional information using e-mail on Tuesday, but received no reply so far.

The relevant reply to PASV command looked like this: "227 Entering Passive Mode (xxx)"
There are two possibilities. If this was in fact in the original log, it would explain the issue - "xxx" is definitely not an IP address, which makes this reply unparsable.
However, it seems more likely that the original log contained something else, which you replaced in order not to disclose sensitive data.
Unfortunately, doing this would have made it impossible for us to figure out what is going on.

Is this actually what the server sent? If not, would it be possible to send us a slightly more faithful representation of the original response?
by (120 points)
Yes, I replaced sensitive data such as user, password and ip with xxx
by (150k points)
This turned out to be caused by a bug in Rebex FTP/SSL. Sorry for inconvenience, and thanks for bringing this to our attention. Please download the hotfix and give it a try: http://www.rebex.net/getfile/4f111cd006bd44a5934acfc27cf0c761/RebexFtpSsl-HotfixBuild6321-Trial-Binaries.zip
by (120 points)
The fix works
by (150k points)
We just published version 2017 R3 that incorporates this fix: http://www.rebex.net/total-pack/history.aspx#2017R3 Thanks for bringing this issue to our attention.
...