Haven't been on the forum since 1.06 came out and everyone pointed out how it didn't work with secure FTP over TLS/SSL. Used a variety of clients (FileZilla, FTP Commander, etc.) and nothing. Just wondering whether anyone has had any success with that, or whether the new release fixed that, even though it's not in the release notes.
This is what I get to this day (with 1.06) when attempting a secure connection:
Status: TLS/SSL connection established.
Response: 331 User XXXXX OK. Password required
Command: PASS ******
Response: 230 OK. Current restricted directory is /
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Extensions supported:
Response: EPRT
Response: IDLE
Response: MDTM
Response: SIZE
Response: REST STREAM
Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response: MLSD
Response: ESTP
Response: PASV
Response: EPSV
Response: SPSV
Response: ESTA
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: 211 End.
Command: PBSZ 0
Response: 200 PBSZ=0
Command: PROT P
Response: 534 Fallback to [C]
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is your current location
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PASV
Response: 227 Entering Passive Mode
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Author
Topic: Any developments on whether secure FTP/SSL actually works now? (Read 4238 times)