1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

V10 B68 problems with ftp

Discussion in 'Support' started by Steve Fabian, Jun 24, 2009.

  1. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    1/ IIRC, earlier builds allowed "relative path" specification of the
    location of FTP.CFG, i.e., ftpcfg=.\FTP.CFG was accepted as a file in the
    TCC's startup directory. Current build interprets the path dynamically, and
    if it finds no such file in the current directory, it creates an empty one.
    This makes using an FTP.CFG file from a portable drive very cumbersome (I
    must first CD to the right FTPCFG directory, execute IFTP, and return - my
    future work around is an IFTP alias to do that). A better solution would be
    to allow specifying the FTP.CFG file using either an environment variable,
    or a directory alias. BTW: are directory aliases allowed in .INI files?

    2/ If the ftp connection times out, an attempt to perform a new ftp action
    performs an implied IFTP in the current directory, with the same issues as
    above attempting to locate FTP.CFG. A simple solution for this problem would
    be that any successful IFTP command would save the username and password
    information; however, this may result in a security compromise.

    3/ Attempting to download the content of an ftp site using the command
    copy/s/[d-400] ftp:* .
    (where copy is an alias : *copy/[!descript.ion]/efgrhv/net) failed to copy
    any files. Both DIR and PDIR with similar selection options worked well. I
    got my current task done by editing the DIR command output, and downloading
    the individual files in a loop.

    --
    Steve
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,860
    Likes Received:
    83
    Steve Fábián wrote:

    No version of TCC/4NT has ever supported relative paths for any
    directive in the .INI, and it is not planned for any future version.
    (For several architectural reasons which we've discussed in the past
    when you've requested this.)


    A rather MAJOR security compromise!


    Not reproducible here. But date ranges can be highly problematic on FTP
    sites, because the date format returned varies wildly (and is sometimes
    missing altogether).

    Rex Conn
    JP Software
     

Share This Page