> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Malcolm Beattie
> Sent: Tuesday, February 20, 2007 12:25 PM
> To: [email protected]
> Subject: Re: scp question.
<snip>
> Here's some more rather surprising behaviour, using just ssh:
> thinkpad% echo -n ABC | ssh zos 'od -t x1'
> 0000000000 C1 C2 C3
> 0000000003
> So the three bytes (0x41, 0x42, 0x43) sent by the ssh client end up
> being read on stdin by od as 0xc1, 0xc2, 0xc3, i.e. converted from
> ASCII to EBCDIC. There's no scp there, just a stream of bytes to move
> around.
>
> --Malcolm
Erin Farr of IBM has answered the question: "Why?" over on MVS-OE.
<quote>
sftp treats all files as binary by default so that should work for
you. There are a handful of places we are forced to be different than
the
rest of the world thanks to the nature of handling EBCDIC. The IETF
SSH
RFC's and drafts did not have to be concerned with data conversion.
OpenSSH doesn't doc anything about it because they didn't have to be
concerned with it either. So, scp calls ssh with an "exec" channel,
which
is also used for remote command execution with ssh. The RFCs don't
allow
us to convert for one and not the other. Not doing ascii-ebcdic
conversion
for remote command execution is the worse of two evils, especially when
binary transfer is available with sftp. Maybe we need a section in the
book to better doc these differences.
-Erin
Unix System Services and Ported Tools Development
</quote>
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
