The following header lines retained to affect attribution:
|Date: Thu, 21 Jan 1999 00:42:13 -0800
|From: Joe Rhett <[EMAIL PROTECTED]>
|To: [EMAIL PROTECTED]
|Subject: Re: How do I sz/rz under an ssh connection?

|> More silly and redundant file transfer protocols.  If you're using SSH
|> then you're already using a perfectly adequate and well integrated file
|> transfer protocol (scp).  You don't need to tunnel anything.

|I think we have different definitions of adequate.

        No, we have the same definition.

        You have a defective model of how to use the tools you
        already have.

|Adequate file transfer in SSH would look something like this:

|local% scp remote:files_I_want/* .     <-- multiple file transfer

        Huh?!

        I do that frequently using scp.  The _only_ problem is that
        the * must be communicated to the other side of the connection.
        That is a _simple_ problem to solve:

        local% scp remote:files_I_want/\* .

                or

        local% scp 'remote:files_I_want/*' .


        I suggest rereading the man pages on your shell and learning
        how and when shell wildcarding (globbing) occurs.

        Even in the case that you want an entire directory tree
        (your example imples that you wanted the contents of a
        single directory with no subdirectories), it is not much
        harder:


        ssh remote 'cd directory; tar -cf - .' | tar xf -

                or

        ssh remote 'cd /; find directory-list -depth -print |
            sed -e "s/^\///" | cpio -oc' | cpio -icmud

                If you do not specify the directory list with
                leading slashes (/) or do want the files put
                at the same location on your system, then
                the sed is unnecessary.

|       or

|remote% sgrab files_I_want/*   <-- transfer files back to source of connection

|Right now, we are forced to tar/zip the files we want, then log out, scp
|the archive, and log back in (assuming a single remote login). Since we use
|challenge/response tokens, that's a 2 minute process MINIMUM.

        Sorry, that is your problem, not ssh's.

|I'm not saying that SSH couldn't provide these services --> but it doesn't
|today, so it hardly makes for "adequate".

        SSH does provide those services.  You just have to have
        a little imagination and learn to use the UNIX small
        tool model for obtaining results instead of expecting
        the program to do every for you by itself.

|Joe Rhett                                                 Systems Engineer
|[EMAIL PROTECTED]                                          ISite Services

|PGP keys and contact information:          http://www.noc.isite.net/Staff/

Randolph J. Herber, [EMAIL PROTECTED], +1 630 840 2966, CD/CDFTF PK-149F,
Mail Stop 318, Fermilab, Kirk & Pine Rds., PO Box 500, Batavia, IL 60510-0500,
USA.  (Speaking for myself and not for US, US DOE, FNAL nor URA.)  (Product,
trade, or service marks herein belong to their respective owners.)

Reply via email to