At Wed, 22 Mar 2006 08:32:48 +0100, Guy Bormann <[EMAIL PROTECTED]> wrote: > > On Tue, 2006-03-21 at 18:01 +0100, [EMAIL PROTECTED] wrote: > [snip] > > I did not say where the user authentication happens. We (Bas, Olaf > > and I) have developed some ideas to do the authentication not in > > system code, but in user code. More on this another time (it's a > > separate discussion). But in the case of SSH, it doesn't really > > matter. Even if the authentication is done by the system, there is > > still some part of the SSH protocol that the system can not do for the > > user, for example executing a shell command. > [snip] > Why would executing a shell command be a problem once you have a user > session? Nothing prevents the client from sending the command over the > SSH channel, accepting the potential output and closing the channel
I am not talking about the client end, but about the server end. > In case a command cannot even be executed from the user session > interactively, there is no point in providing ssh functionality through > a separate protocol. I am not sure we mean the same thing by the term "user session". > Actually, it should be build into the terminal > facility from scratch as it should have been done originally (yes, I > know, there weren't that many machines back then blablabla...). In fact, I am not sure we mean the same thing with the term "terminal" either :) Thanks, Marcus _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
