Anyone is able to read the FTP usernames, passwords, commands and data by packet capture (sniffing) on the network. Maybe I missed a setting somewhere?Įdit: There you go - much better, winscp seems very nice.FTP (File Transfer Protocol) uses clear text for all transmissions. I am planning on playing with winscp some more - looks very promising, not as fast as SecureFX as of yet. Since they are both free, why not just winscp as your sftp file xfer client? Is there some specific feature in filezilla you are wanting? But that issue was cleared up in the end of 2003, are they still using old putty code? They seem to try and blame it on putty, etc.

I was able to squeeze a few extra K/s out it by turning off compression, this got it up to the 230's - but yeah its pretty slow for sftp. It does not seem to support key auth, and or the ability to select the cipher as with winscp, etc. I have to do some more playing with that program, first time I have used it.īut with SecureFX, to the same machine - sending the same file - ie get 6100KB/s Give me a few minutes - to grab filezilla, and give that a goĮdit: Well I had not played with filezilla and or winscp, and from the few minutes I have spent with the 2 - it is quite clear winscp is much better at secure file xfer than filezilla. 2200KB/s with Blowfish and sFTP, only around 1800KB/s with AES and sFTP. Using blowfish and SCP I was able to get like 4600KB/s with winscp. Are you using compression or not? Are the files binary or ascii?

What cipher are you using, and are you using scp or sFTP? Blowfish is going to give you less overhead, so therefor faster xfer. I just grabbed a copy of winscp - not too shabby from a quick look. I use SecureFX as my windows based sFTP client.

I'll have a to grab a copy of filezilla, and do some playing.

Filezilla sftp with ssh keys