At 03:03 PM 2/20/2004, you wrote:
I'll skip past the fact that you _really_ don't want to run any of the "r"
commands (rsh, rexec, etc.) since they're so completely insecure. (SSH
would be a much better option.)
The rap against rexec is that passwords and
data are send "in the clear".
But, if an MVS REXEC client talks to
a mainframe Linux rexecd daemon via HiperSockets,
who else is going to see the packets?
As long as the Linux box doesn't identify
trusted hosts, and as long as a firewall
blocks inbound REXEC traffic from outside
the mainframe box, can this traffic be
considered "secure"?
