I'd venture to guess that most people are looking for ssh to replace rexec, not be a general-purpose session management tool. It'd be nice to have, but I'd settle for a decent rexec replacement as an interim step.
> But ... shucks! ... OpenVM absolutely *cried* for such a connection. One thought that occurs to me: wrt to rexec (or possibly OE), you could separate the function into two servers (the rexec controller, and the virtual machine being driven). the ssh controller could manage the TCP connection and authentication process, and couple that with a small piece of code that would be driven on AUTOLOG of the virtual machine being driven to create a LDEV or IUCV service. The controller could DIAL to that LDEV and drive it via RXLDEV or supply info via IUCV or similar gadgetry. Given that division of function, you could have the controller supply the credentials to the virtual machine being driven, and allow the stub to check whether the connection would be allowed based on user-maintained info. This would also supply OE with a trivial 8-bit clean terminal connection that would not require 3270 processing. > > -- R; > > ---------------------------------------------------------------------- > 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 > > > ** ACCEPT: CRM114 PASS Markovian Matcher ** > CLASSIFY succeeds; success probability: 1.0000 pR: 127.1510 > Best match to file #0 (nonspam.css) prob: 1.0000 pR: 127.1510 > Total features in input file: 7616 > #0 (nonspam.css): features: 6960216, hits: 2340066, prob: > 1.00e+00, pR: 127.15 > #1 (spam.css): features: 3123428, hits: 2721982, prob: > 7.06e-128, pR: -127.15 > > ---------------------------------------------------------------------- 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
