On 2/21/07, Alan Altmark <[EMAIL PROTECTED]> wrote:
z/OS could do the same thing, letting sftp and scp use the same translation settings. Of course, the ssh protocol is extendable and could include channel types specifically designed for file transfer, as opposed to command/response.
I have not even heard the "which ASCII" and "which EBCDIC" yet ;-) Considering that any change will impact installed base of programs and human minds, we probably need to add two additional paths for those who know what they want. With VM NFS, I simply mounted the directory twice (once with and once without translation) because I could not make the network folks to listen. And it was up to the user and/or application to take the correct path (no 00D intended). If sshd has an option to enable / disable translation, you could run one of each on different IP stacks, and allow users / applications use different host names to select translation or not. Just using a different port might be even better because that does not complicate the key issues. There's also options to specify the cipher to be used (even via the known_hosts IIIRC) but I am not sure we could come up with a cipher that also does the translation along with encrypt and decrypt. And the idea is probably so ugly that I would want to keep it secret if we could :-) Rob ---------------------------------------------------------------------- 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
