Error Listing some Dirs with SSL Connection.

Hi I get this error in listing some dirs :

150 Opening ASCII data connection for ls /UPLOAD using SSL/TLS.
Connected. Exchanging encryption keys...
Session Cipher: 128 bit RC4
SSL encrypted session established.
An established connection was aborted by the software in your host machine.

when I try again same happens , and reconnect also not help .

but same dirs working fine in flashfxp for example , here is a log file :

[L] 150 Opening ASCII data connection for ls /UPLOAD using SSL/TLS.
[L] Connected. Negotiating SSL session..
[L] 226-free disk space under this directory : 108011 mb
[L] SSL negotiation successful...
[L] SSL encrypted session using cipher AES256-SHA (256 bits)
[L] 226 Transfer finished successfully. Data connection closed .
[L] List Complete: 113 bytes in 2.13 seconds (0.1 KB/s)

and listing is alot faster in FlashFXP . in SmartFTP take some 10-12sec and CPU jump to 60% usage and FlashFXP some 1-2sec and CPU usage 1-2% . looks like SSL slow down the SmartFTP alot , how to fix this ?

maybe all the problem in the Microsoft Schannel RC4 ?
how about to add external SSL like in FlashFXP ? he looks alot better 256bit and works alot faster and not use CPU so much . :roll:
please correct me if I'm mistaken :wink:

I don't have such problems as you described.

If you are connecting to a glftpd server then the problem is very likely with their product.

Regards,
-Mat

in use RaidenFTPD , tested more then 1 version .
and it cant be FTP server because other clients working always good.

Any chance that I can get a test account on the mentiond server? I run raidenftpd as well but I haven't noticed any problems.

-Mat

ok I will send you soon in PM

Done , check your PM

BTW: Can you post the full logs, including the PASV and PORT commands. Maybe the problem is related to the data connection method (PORT or PASV) and not to the SSL layer itself.

Regards
-Mat

Hello ...

I just fixed the high cpu usage when downloading files and listing directories. The problem showed up after the recent MS hotfixes. The bug was in SmartFTP though. The fix will be available in the next developer build.

Regards,
-Mat