Quote:
Originally Posted by Zer0Racer
ioFTPD v5.x can only receive ssl fxp, not send. So when you fxp from ioFTPD v6.x to v5.x it should be encrypted - but when you do it the other way around (and have "Secure Site To Site Transfers" enabled for both) you will get that error message since v5.x cannot initiate the ssl transfer (just receive).
When the fxp works from v5.x to v6.x the data is not encrypted.
/ZR
|
So to be clear. I need v6 on both sides to be able to encrypt data transfers both ways and only v6 can fxp to v5 not the opposite way.
I change the settings in ioftpd.ini on the v6-site so it forces everyone to use SSL3 when transfering data, so it should be impossible to transfer unencrypted data. Here is what happens.
Impossible to fxp from v6 to v5 from now on.
Any ideas? and is it only me that are haveing problems getting ssl-fxp to work on v6?
Here is the log:
Code:
[01:46:30] TYPE I
[01:46:30] 200 Type set to I.
[01:46:30] TYPE I
[01:46:30] 200 Type set to I.
[01:46:30] SSCN ON
[01:46:30] 200 SSCN:CLIENT METHOD
[01:46:30] PASV
[01:46:30] 227 Entering Passive Mode (000,000,000,000,117,65)
[01:46:30] PORT 000,000,000,000,117,65
[01:46:30] 200 PORT command successful.
[01:46:30] STOR file.r22
[01:46:30] 150 Opening BINARY mode data connection for file.r22.
[01:46:30] RETR file.r22
[01:46:30] 150 Opening BINARY mode data connection for file.r22.
[01:46:30] 426 Connection closed: The specified network name is no longer available.
[01:46:30] ABOR
[01:46:30] 426 Connection closed: Incorrect function.
[01:46:30] 226 ABOR command successful.
[01:46:30] ABOR
[01:46:30] 226 ABOR command successful.
[01:46:31] Transfer Failed!