At Thu, 23 Mar 2006 19:45:11 +0100, Guy Bormann <[EMAIL PROTECTED]> wrote: > > On Wed, 2006-03-22 at 09:18 +0100, Marcus Brinkmann wrote: > > 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. > I am talking about the server side, too. Now go read again :-)
The question that I raised in my initial mail is basically what it should mean to have a "user session" in the context of SSH. So, uhm, maybe executing a shell command won't be a problem once I have a user session. So let me ask back: How do you think you get one? And what does it mean to "have" one in technical terms? Thanks, Marcus _______________________________________________ L4-hurd mailing list L4-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/l4-hurd
