Hi Bob,
The answer as to why ssh doesn't do translations is actually very simple.
SSH was originally meant to be a direct replacement, howbeit secure, for
rcp and rsh which are UNIX only commands. Since UNIX has no notion of a
difference between ascii and binary as it treats everything as binary a
translation feature wasn't needed. Thanks to the Windoze and doz people a
difference was made where there really wasn't a need for it.
Auto sensing is not very reliable as you pointed out, if a feature like
this was to be added a command line argument would be the way to go.
Remember most people that use this protocol don't point and click it.
Carl
On 10-Mar-01 Bob Babcock wrote:
>> Humm, very strange. SSH always transfers in binary mode, it never does
>> translations. If you are on a UNIX machine there are no CRs at the end
>> of
>> the line just LFs, the Mac uses just CRs and windoze uses a CRLF
>> sequence. SSH will not touch any of these on any platform as far as I
>> know.
>
> To be blunt, why are the programs that implement the ssh protocol so
> stupid?
> Ftp solved this problem years ago by making ascii transfers part of the
> protocol. Apparently ssh doesn't do this, but that doesn't stop an ssh
> program from doing the trivial line termination translations when it
> sends a
> file. All that would be needed are commands or checkboxes for, say,
> "binary", "to-unix", "to-dos" and "to-mac". Auto-sensing is a little
> harder,
> and I don't know if an ssh program can tell what OS is running on the
> other
> end.
------------------------------------------------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 12-Mar-01 Phone: 315-453-2912 Ex. 5336
Time: 08:44:11 Fax: 315-479-0859
Software Engineering Group -- AppliedTheory Corp.
224 Harrison Street, 6th Floor, Syracuse, NY 13202
------------------------------------------------------------------------
