Re: bug using STAT for list on drftpd servers
I've attached a text file that is the result of running quote STAT . lftp.out on a drftpd server. I would just like to note a few things i noticed while playing with the output: Drftpd seems to always have total 0 at the top of the list no matter what. This behavior is different from all other servers I have seen, but this happens using both STAT and LIST (which caches properly), so I doubt it is causing the issue. Other servers that I've seen using STAT for list have status of .: at the top of the list while drftpd has Status of .: (note the capital 's'). I don't know if this could be causing problems with parsing, but I thought I should mention it. Lastly, I found hardly any significant difference between the list output when using STAT vs LIST. A diff of the output from each always results in: 0a1 213- Status of .: 7a9 213 End of Status This leads me to conclude that the list IS a known UNIX ls format. Unfortunately this makes the problem more difficult to find. All others I've tested are properly caching the list for use with tab completion. Because of this I can only speculate that it may have something to do with PRET, a feature exclusive to drftpd. I no longer believe this to be true because I tried turning off FEAT so lftp didn't detect that PRET was needed, but the problem persisted. Thanks for the reply, - Kyle On Fri, Sep 4, 2009 at 10:58 AM, Alexander V. Lukyanov l...@netis.ru wrote: On Wed, Aug 26, 2009 at 06:32:25AM -0500, Kyle Thurow wrote: Also, if you repeat the steps above but use cls instead of ls you will see the following output: --- STAT . --- 213 End of Status --- PROT P --- 200 Command okay --- PRET NLST --- PASV --- NLST --- 200 OK, will use master for upcoming transfer This means that lftp could not parse all lines of STAT output. Probably there are lines which do not fit into known UNIX ls format. Please send me output of quote STAT . command and I'll try to fix it. -- Alexander.. lftp.out Description: Binary data
Re: implementation of lftp
Someone correct me if I'm wrong, but I believe this is the default behavior in modern versions of lftp. From the manual: ftp:use-site-utime (boolean) when true, lftp sends 5-argument `SITE UTIME' command to set file modification time on uploaded files. Default is true. ftp:use-site-utime2 (boolean) when true, lftp sends 2-argument `SITE UTIME' command to set file modification time on uploaded files. Default is true. If 5-argument `SITE UTIME' is also enabled, 2-argument command is tried first. - Kyle 2009/11/10 Dr Joel Abadie jaba...@femto-st.fr: Dear Alexander, I am actually using lftp. Congratulation, it is a good tool. I would like to make a suggestion. I did not find an option that preserve the time and date of the original file when doing a mirror -R. I think surch an option would be great. Sincerely _ Dr Joël ABADIE Ingénieur de recherche CoNRS en colère Automatique et Systèmes Micro-Mécatroniques (AS2M) Institut FEMTO-ST UMR CNRS 6174 - UFC / ENSMM / UTBM 24, rue Alain Savary, F-25000 Besançon (FRANCE) Tél : 03 81 40 28 07 Fax : 03 81 40 28 09 Mailto:jaba...@femto-st.fr http://www.femto-st.fr _
Re: Torrents with spaces in the filename
I tried the torrent found here: http://isohunt.com/download/138556137/ubuntu.torrent and was unable to replicate this problem. (note: it saves to file name [isoHunt] ubuntu-9.10-desktop-i386.iso.torrent) Perhaps you are entering the file name incorrectly? Keep in mind when accessing files with spaces, either the spaces need to be escaped with a backslash, or the whole file name put in double quotes. For example with the torrent file I used above you'd need one of the following commands for it to work: [lftp] :~ torrent [isoHunt]\ ubuntu-9.10-desktop-i386.iso.torrent or [lftp] :~ torrent [isoHunt] ubuntu-9.10-desktop-i386.iso.torrent If you don't do this you'll get the following error: torrent: Too many arguments. Try `help torrent' for more information. Is this what happened to you? You simply said it refused to start. In what way did it refuse? What output, if any, did lftp show? - Kyle On Mon, Dec 21, 2009 at 6:03 AM, Chris Sutcliffe ir0nh...@gmail.com wrote: On 12/21/09 3:10 AM, Alexander V. Lukyanov wrote: On Sun, Dec 20, 2009 at 07:18:36PM -0500, Chris Sutcliffe wrote: Is anybody able to get torrents the contain spaces in the filename to work? Torrents with spaces simply refuse to start, whereas torrents without spaces work fine. Can you provide a sample of such a torrent file? Pretty much any torrent I find on isohunt (for example) exhibits this behaviour. Chris -- Chris Sutcliffe ir0nh...@gmail.com
Re: Torrents with spaces in the filename
It's possible the torrents you tried simply had no seeds, or had issues with the tracker, etc. Since the drum beat file worked, I'm inclined to think this is the issue. If you really think the problem is with lftp, try any non-working torrent in another client to see if it works. - Kyle On Mon, Dec 21, 2009 at 10:23 PM, Chris Sutcliffe ir0nh...@gmail.com wrote: I tried the torrent found here: http://isohunt.com/download/138556137/ubuntu.torrent and was unable to replicate this problem. (note: it saves to file name [isoHunt] ubuntu-9.10-desktop-i386.iso.torrent) I should have mentioned, I don't think it's an issue with spaces in the filename of the torrent, more spaces in the filename of the target. I suspect that the torrent file you used produced a file called 'ubuntu-9.10-desktop-i386.iso'. Having said that, I tried another file with spaces in the target and it worked (a CreativeCommons drum beat). I'm not sure why some work and others don't. Is this what happened to you? You simply said it refused to start. In what way did it refuse? What output, if any, did lftp show? What happens is the torrent basically sits there waiting it seems. lftp will have the up / down indicators at 0. Chris -- Chris Sutcliffe http://emergedesktop.org
Re: lftp copy many files and directories at once
The 'mirror' command should be used for directories, and the get, put, mget and mput commands can be used for files. See the man page for specifics on how to use mirror, get, and put for fxp. Additionally the section on the obsolete 'ftpcopy' command has some examples using get and put. - Kyle On Tue, Dec 22, 2009 at 12:46 AM, Sameer Arora sameer.ar...@rdks.com.au wrote: Hi, I need to copy set of files and directories from one server to another using lftp what is the right command for this. Thanks Sameer
mirror's --loop option not working
Perhaps I misunderstand the purpose of the --loop option when using mirror, but it isn't behaving the way I expect. The point of --loop is: after mirroring all the files in the specified directory, lftp should re-acquire the directory's file listing and download any files that weren't listed the first time (it stops if no new files are seen). Is the above description correct? If so, it doesn't work for me. Instead it downloaded the files in the directory when mirroring began, but failed to loop and download any new files. - Kyle
Re: Stop fxp mirror
In response to your original email, if lftp backgrounds, the crude way of stopping it is killall lftp. If you'd rather lftp didn't background in the first place, I recommend adding set cmd:move-background no to ~/.lftp/rc You seem to indicate the traffic continues even if the lftp process has been killed? First of all, I think ps -ef | grep fxp isn't the best command. You should be grepping for lftp, not fxp (you won't necessarily always have fxp in your lftp commands) . Even if you manage to kill lftp, I'm not sure that you can stop the transfer from your computer because the two servers independently negotiate the tcp transfer. But I'm not too familiar with the details of fxp. If lftp changes to [Receiving data-Sending data] it probably means one or both of the servers don't allow fxp. lftp must then route the traffic through you're connection to make it work. Talk to the server admins to get fxp enabled. 2010/2/16 José Romildo Malaquias j.romi...@gmail.com:seems to be finished, the traffic continues and ps -ef | grep fxp does On Tue, Feb 16, 2010 at 12:15:37PM -0200, José Romildo Malaquias wrote: Hello. I have started using lftp a few days ago. I am using it to transfer some files from one ftp server to another ftp server using the fxp protocol, with a command like the following in a terminal: $ lftp -c mirror --verbose=3 --log=fxp.log -c ftp://user1:pass...@host1:port1/path1/file ftp://user2:pass...@host2:port2/path2/; I have another question in this context: Why sometimes lftp changes to [Receiving data-Sending data]. Clearly it stopped doing fxp, as traffic is going through my local computer. It is not enough to stop the command with control+c, as even after lftp seems to be finished, the traffic continues and ps -ef | grep fxp does not show a lftp process. So what is the best way of interrupting the ftp traffic in my local computer in this case? Romildo
Re: Re: lftp and embedded OS ftp server
None of those commands you typed into lftp were what I intended. I only put the quotes so you could distinguish what the command was. They way you tried to use it was completely self-defeating. As you can see, putting the whole thing in quotes results in an unknown command error. Additionally, putting drive2\: in quotes defeats the whole purpose! The quotes make the '\' character literal, so it tries to enter a directory literally named drive2\: My intent was for you to use cd drive2\: (but remove the quotes when you type this into lftp! Also cd drive2: might work (keep these quotes)) Also, I don't follow your server structure at all. are drive1 and drive2 directories withing root? The way you showed, they seem to be independent of the filesystem! Can you maybe connect to the ftp server, and show the output of 'ls' ? - Kyle On Wed, Feb 24, 2010 at 1:07 PM, mmoore.h...@gmail.com wrote: Thanks for the suggestions - no go so far. Pretty sure the issue is the preceding '/'. The server has the following structure: drive1: / /dir1 /dir2 drive2: / /dir1 /dir2 The FTP server defaults to drive1: and if the cd command includes the preceding '/' then it is assumed that the drive2 text is a directory (which doesnt exist). Some samples: FROM FTP: ftp cd drive2 550 'drive2': Not a directory or not accessible. ftp cd drive2: 250 CWD command - successful. FROM LFTP: lftp ad...@hostname:/ cd drive2: cd: Access failed: 550 '/drive2:': Not a directory or not accessible. lftp ad...@hostname:/ cd drive2\: Unknown command `cd drive2\:'. lftp ad...@hostnamen:/ cd drive2\: cd: Access failed: 550 '/drive2\:': Not a directory or not accessible. lftp ad...@hostname:/ cd 'drive2\:' cd: Access failed: 550 '/drive2\:': Not a directory or not accessible. lftp ad...@hostname:/ cd drive2 cd: Access failed: 550 '/drive2': Not a directory or not accessible. Thanks for the help. I just hope that I am not the only one to have run across a system like this before. Matt On Feb 24, 2010 12:28pm, Bill Dorsey bdorse...@gmail.com wrote: I was thinking the same thing. I never use a : when on ftp sites. Also, there may be a security issue. I get that a lot when my creds are lacking. On Wed, Feb 24, 2010 at 12:04 PM, Kyle Thurow krthu...@gmail.com wrote: This is just speculation. I haven't done any testing to verify, but lftp may be having a problem with the ':' character in that directory name. If possible, I would recommend naming it something else. Alternatively, you may be able to escape the character. you could try cd drive2\: - Kyle On Wed, Feb 24, 2010 at 10:51 AM, mmoore.h...@gmail.com wrote: Hi all - I hope this is not an rtfm problem - I have searched every way I know how for the answer... Am working with and embedded device that has 2 volumes served by FTP. With linux command line ftp client, I can cd to the second volume - cd drive2: When I do the same with lftp, I get the following error: cd: Access failed: 550 '/drive2:': Not a directory or not accessible. Which is right, because it is adding a leading '/' to the volume as to make it rooted at /.. Is there a way to change volumes or cd with out the leading '/'? Thanks, Matt
Re: Re: Re: lftp and embedded OS ftp server
The leading slash really shouldn't be a problem. When you first connect to the ftp server, you are in the root directory (a.k.a. /). When you try to cd into a new directory from root, the slash is implicit, so cd drive2: and cd /drive2: are actually the same thing, and both should work. After testing, I now see that lftp literally parses the \ character, so that isn't the proper way to escape. You didn't mention if you tried this (which I suggested in my last message): lftp:/ cd drive2: In this case, keep the quotes. The above command is really the only other suggestion I have. If this doesn't work I can only recommend changing the name of drive2: by removing the trailing ':' character. - Kyle On Wed, Feb 24, 2010 at 10:22 PM, mmoore.h...@gmail.com wrote: Sorry for the misunderstanding - not sure how the commands are interpreted, so messed that up pretty badly. lftp ad...@hostname:/ cd drive2\: cd: Access failed: 550 '/drive2\:': Not a directory or not accessible. see, the issue doesnt appear to be the : but the leading / You got the point with the file structure I think... There are 2 separate volumes. / of drive1: has a set of files and / of drive2: has a completely different set of files... the standard ftp command line client in centos5 or win xp lets me cd drive2: and I see / of drive2: while if I cd drive1: then I see / of drive1... Hope that helps? Thanks, Matt On Feb 24, 2010 9:53pm, Kyle Thurow krthu...@gmail.com wrote: None of those commands you typed into lftp were what I intended. I only put the quotes so you could distinguish what the command was. They way you tried to use it was completely self-defeating. As you can see, putting the whole thing in quotes results in an unknown command error. Additionally, putting drive2\: in quotes defeats the whole purpose! The quotes make the '\' character literal, so it tries to enter a directory literally named drive2\: My intent was for you to use cd drive2\: (but remove the quotes when you type this into lftp! Also cd drive2: might work (keep these quotes)) Also, I don't follow your server structure at all. are drive1 and drive2 directories withing root? The way you showed, they seem to be independent of the filesystem! Can you maybe connect to the ftp server, and show the output of 'ls' ? - Kyle On Wed, Feb 24, 2010 at 1:07 PM, mmoore.h...@gmail.com wrote: Thanks for the suggestions - no go so far. Pretty sure the issue is the preceding '/'. The server has the following structure: drive1: / /dir1 /dir2 drive2: / /dir1 /dir2 The FTP server defaults to drive1: and if the cd command includes the preceding '/' then it is assumed that the drive2 text is a directory (which doesnt exist). Some samples: FROM FTP: ftp cd drive2 550 'drive2': Not a directory or not accessible. ftp cd drive2: 250 CWD command - successful. FROM LFTP: lftp ad...@hostname:/ cd drive2: cd: Access failed: 550 '/drive2:': Not a directory or not accessible. lftp ad...@hostname:/ cd drive2\: Unknown command `cd drive2\:'. lftp ad...@hostnamen:/ cd drive2\: cd: Access failed: 550 '/drive2\:': Not a directory or not accessible. lftp ad...@hostname:/ cd 'drive2\:' cd: Access failed: 550 '/drive2\:': Not a directory or not accessible. lftp ad...@hostname:/ cd drive2 cd: Access failed: 550 '/drive2': Not a directory or not accessible. Thanks for the help. I just hope that I am not the only one to have run across a system like this before. Matt On Feb 24, 2010 12:28pm, Bill Dorsey bdorse...@gmail.com wrote: I was thinking the same thing. I never use a : when on ftp sites. Also, there may be a security issue. I get that a lot when my creds are lacking. On Wed, Feb 24, 2010 at 12:04 PM, Kyle Thurow krthu...@gmail.com wrote: This is just speculation. I haven't done any testing to verify, but lftp may be having a problem with the ':' character in that directory name. If possible, I would recommend naming it something else. Alternatively, you may be able to escape the character. you could try cd drive2\: - Kyle On Wed, Feb 24, 2010 at 10:51 AM, mmoore.h...@gmail.com wrote: Hi all - I hope this is not an rtfm problem - I have searched every way I know how for the answer... Am working with and embedded device that has 2 volumes served by FTP. With linux command line ftp client, I can cd to the second volume - cd drive2: When I do the same with lftp, I get the following error: cd: Access failed: 550 '/drive2:': Not a directory or not accessible. Which is right, because it is adding a leading '/' to the volume as to make it rooted at /.. Is there a way to change volumes or cd with out the leading
Re: Issue with lftp infinite looping on non-fatal errors
It's not a bug, it's a feature! Although I can see how this might be a problem in some circumstances, it's meant to make lftp more robust. From the man page: Every operation in lftp is reliable, that is any not fatal error is ignored and the operation is repeated. So if down- loading breaks, it will be restarted from the point automat- ically. Even if ftp server does not support REST command, lftp will try to retrieve the file from the very beginning until the file is transferred completely. - Kyle On Thu, Mar 25, 2010 at 12:27 PM, todd.gr...@shell.com wrote: Hello, We recently started using lftp and found that on some non-fatal errors we are experiencing infinite retry loop. We are using version 3.7.3. From the site http://lftp.yar.ru/lftp-man.html I wasn’t able to find any fix since then. Has there been any fix for this issue? Todd Grams Contractor Shell Canada Limited 400 4th Avenue S.W., P.O. Box 100 Station M, Calgary, Alberta T2P 2H5, Canada Tel: +1 403-384-5245 0 Email: Internet: http://www.shell.ca
Re: How to disable 'log'?
I'm not sure whether or not there's an lftp setting for it, but probably the best way is to create a symbolic link to /dev/null like so: rm ~/.lftp/log ln -s /dev/null ~/.lftp/log Everything normally saved there will instead be discarded. You can repeat this for any other log files as well. On Wed, Jul 7, 2010 at 10:25 PM, tomatotree tomatot...@gmx.net wrote: I have one more question please. I would like to disable the creation of the log: ~/.lftp/log I haven't been able to locate the setting for that. (The 3 logs - cwd_history, rl_history transfer_log I have disabled using the set no cmd.) If anyone knows, that would be great. Thank you again, Stephanie
Re: '331 Password required.' connecting to DSL router
I would guess your ftp server doesn't support FEAT (and possibly doesn't support TLS either). Try turning one or both off. set ftp:use-feat no set ftp:ssl-allow no Even if the server doesn't support these, it isn't handling them correctly, so the problem is really on the server side (even if you can fix it in lftp). 2010/7/3 Frédéric L. W. Meunier fred...@gmail.com: Hi. I don't know what's wrong with LFTP (4.0.6) or me, but it doesn't connect to my DSL router (SpeedTouch 510v6), which has no password. 'ftp' works fine. lftp u...@192.168.1.254:~ open -u user 192.168.1.254 Password: lftp u...@192.168.1.254:~ ls Connecting to 192.168.1.254 (192.168.1.254) port 21 --- 220 Inactivity timer = 120 seconds. Use 'site idle secs' to change. --- FEAT --- 331 Password required. --- AUTH TLS Peer closed connection Closing control socket Interrupt Using 'debug 9' returns the same lines.
Re: '331 Password required.' connecting to DSL router
Whichever command(s) I gave you before that worked should be added to the file ~/.lftp/rc Then it will run automatically every time lftp starts. If you want that setting to work only for this server you can use: set ftp:use-feat/server_ip_here no 2010/7/26 Frédéric L. W. Meunier fred...@gmail.com: On Mon, 26 Jul 2010, Peko wrote: 2010/7/4 Frédéric L. W. Meunier fred...@gmail.com Hi. I don't know what's wrong with LFTP (4.0.6) or me, but it doesn't connect to my DSL router (SpeedTouch 510v6), which has no password. 'ftp' works fine. Hi Frédéric, Why would you connect to your DSL router? Does it really host a ftp server ? Did you succeed to connect to your router with another ftp client program? Every time it power ups, I need to send ten commands to get a connection, since it isn't saving its configuration. But I really doubt that this brokenness is the problem I get with LFTP, because all other clients I tested worked. On Windows, the default ftp. On Linux, Midnight Commander's ftpfs, NcFTP and tnftp. All I know is that LFTP is the only with SSL support. ncftp open -u user 192.168.1.254 Connecting to 192.168.1.254... Inactivity timer = 120 seconds. Use 'site idle secs' to change. Logging in... Password requested by 192.168.1.254 for user user. SpeedTouch Password required. Password: OK Unknown command. Logged in to 192.168.1.254. ncftp / ls .: Permission denied ncftp / cd /dl Changed to /dl ncftp /dl ls mdap_upl.tmp seed.dat ncftp /dl
Re: FTPS (explicit) connection problems
lftp :~ open -u, -p ftps://..com The above line is your problem. In lftp, an 'ftps' prefix indicates implicit ssl, and your vendor requires explicit. Try changing the line to this instead: lftp :~ open -u, -p ftp://..com On Fri, Aug 20, 2010 at 11:14 AM, Joshua Hess joshua_7...@yahoo.com wrote: Greetings, I cannot connect to an ftps site using lftp, and I do not know what I am doing incorrectly. There are no firewall issues on the client side. Any help would be appreciated! Thank you! Josh 1) Vendor Instructions - We use the FTP/SSL port number of (for the control port) We only support Explicit (AUTH SSL) FTP/SSL - not Implicit SSL. We only support Passive mode transfers. The Server responds on ports to for its data channel for clients initiating FTP/SSL in Passive mode. 2) My session: lftp :~ debug 13 lftp :~ open -u, -p ftps://..com Resolving host address... 1 address found: xxx.xxx.xxx.xxx lftp x...@..com:~ ls FileCopy(0x8ed6148) enters state INITIAL FileCopy(0x8ed6148) enters state DO_COPY dns cache hit Connecting to ..com (xxx.xxx.xxx.xxx) port SSL_connect: unknown protocol Closing control socket ls: Fatal error: SSL_connect: unknown protocol 3) My lftp set -a set bmk:auto-sync yes set bmk:save-passwords no set cache:cache-empty-listings no set cache:enable yes set cache:expire 60m set cache:expire-negative 1m set cache:size 16M set cmd:at-exit set cmd:cls-completion-default -FB set cmd:cls-default -F set cmd:csh-history off set cmd:default-protocol ftp set cmd:default-title lftp \\h:\\w set cmd:fail-exit no set cmd:interactive no set cmd:long-running 30 set cmd:ls-default set cmd:move-background yes set cmd:move-background-detach yes set cmd:parallel 1 set cmd:prompt lftp \\S\\? \\...@\\h:\\w set cmd:queue-parallel 1 set cmd:remote-completion on set cmd:save-cwd-history yes set cmd:save-rl-history yes set cmd:set-term-status no set cmd:status-interval 0.8s set cmd:stifle-rl-history 500 set cmd:term-status set cmd:time-style %b %e %Y|%b %e %H:%M set cmd:trace no set cmd:verbose no set cmd:verify-host yes set cmd:verify-path yes set cmd:verify-path-cached no set color:dir-colors no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35: set color:use-color auto set dns:SRV-query no set dns:cache-enable yes set dns:cache-expire 1h set dns:cache-size 256 set dns:fatal-timeout 7d set dns:max-retries 1000 set dns:order inet set dns:use-fork yes set file:charset UTF-8 set fish:charset set fish:connect-program ssh -a -x set fish:shell /bin/sh set ftp:abor-max-wait 15s set ftp:acct set ftp:anon-pass lftp@ set ftp:anon-user anonymous set ftp:auto-passive-mode yes set ftp:auto-sync-mode set ftp:bind-data-socket yes set ftp:charset set ftp:client lftp/4.0.6 set ftp:device-prefix no set ftp:fix-pasv-address yes set ftp:fxp-force no set ftp:fxp-passive-source no set ftp:fxp-passive-sscn yes set ftp:home set ftp:ignore-pasv-address no set ftp:lang set ftp:list-empty-ok no set ftp:list-options set ftp:nop-interval 120 set ftp:passive-mode on set ftp:port-ipv4 set ftp:port-range full set ftp:prefer-epsv no set ftp:proxy set ftp:proxy-auth-type user set ftp:rest-list no set ftp:rest-stor yes set ftp:retry-530 too many|overloaded|try (again |back )?later|is restricted to|maximum number|number of connect only.*session.*allowed|more connection|already connected|simultaneous login set ftp:retry-530-anonymous Login incorrect set ftp:site-group set ftp:skey-allow yes set ftp:skey-force no set ftp:ssl-allow yes set ftp:ssl-allow-anonymous no set ftp:ssl-auth SSL set ftp:ssl-copy-sid yes set ftp:ssl-data-use-keys yes set ftp:ssl-force on set ftp:ssl-protect-data yes set ftp:ssl-protect-fxp no set ftp:ssl-protect-list on set ftp:ssl-shutdown-timeout 5 set ftp:ssl-use-ccc yes set ftp:stat-interval 1 set ftp:sync-mode on set ftp:timezone GMT set ftp:trust-feat no set ftp:use-abor yes set ftp:use-allo yes set ftp:use-feat yes set ftp:use-fxp yes set ftp:use-hftp yes set ftp:use-mdtm yes set ftp:use-mdtm-overloaded no set ftp:use-mlsd no set ftp:use-pret yes set ftp:use-quit yes set ftp:use-site-chmod yes set ftp:use-site-idle no set ftp:use-site-utime yes set ftp:use-site-utime2 yes set ftp:use-size yes set ftp:use-stat yes set ftp:use-stat-for-list no set ftp:use-telnet-iac yes set ftp:verify-address no set ftp:verify-port no set
