The standard SSH and SFTP protocols (and most implementations) *only* do
binary.

z/OS OpenSSH is extended to do limited ASCII<->EBCDIC translation.
   - it automatically translates "shell" sessions, remote command
execution, scp (client and server),  and adds "ascii" and "binary" commands
to "sftp" *client* command.

Some Windows SFTP implementations also handle CRLF<->LF mappings.

On Mon, Apr 15, 2019 at 7:38 AM Allan Staller <[email protected]> wrote:

> "The ssh command performs ASCII<->EBCDIC conversion (for pedants,
> 1047<->819).  I'd expect that to be IBM-specific.  Probably not relevant to
> security, but additional code that must be supported in an IBM instance, or
> conditionally bypassed if the sources are merged."
>
> SSH defaults to binary transfer.  For the issue below (1047-819
> translation) a text mode transfer would have to be specifically requested.
> It is presumed that someone that knows enough to request a text mode
> transfer would be aware of the translation issues.
> ::DISCLAIMER::
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or may contain
> viruses in transmission. The e mail and its contents (with or without
> referred errors) shall therefore not attach any liability on the originator
> or HCL or its affiliates. Views or opinions, if any, presented in this
> email are solely those of the author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification, distribution and / or
> publication of this message without the prior written consent of authorized
> representative of HCL is strictly prohibited. If you have received this
> email in error please delete it and notify the sender immediately. Before
> opening any email and/or attachments, please check them for viruses and
> other defects.
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to