search for: launch_login

Displaying 4 results from an estimated 4 matches for "launch_login".

2003 Oct 07
0
FW: Environment passing in Solaris 8 with later versions of SSH a nd UseLogin=yes
...ebug1: Entering interactive session. > debug1: JRT-03: do_pre_login > debug1: JRT-04: do_child > Environment: > TZ=NZ > SSH_CLIENT=xxx.xx.xx.xxx 34811 2222 > SSH_CONNECTION=xxx.xx.xx.xxx 34811 xxx.xx.xx.xx 2222 > SSH_TTY=/dev/pts/6 > TERM=xterm > debug1: JRT-05: launch_login > > However, if I then query the environment of the logged in > process, none of the variables have been set properly, thus: > > user at host:~$ echo $SSH_CLIENT > > user at host:~$ echo $SSH_TTY > > user at host:~$ echo $TERM > sun > > I don't mind the...
2003 Sep 29
1
Environment passing in Solaris 8 with later versions of SSH and U seLogin=yes
...y). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: JRT-03: do_pre_login debug1: JRT-04: do_child Environment: TZ=NZ SSH_CLIENT=xxx.xx.xx.xxx 34811 2222 SSH_CONNECTION=xxx.xx.xx.xxx 34811 xxx.xx.xx.xx 2222 SSH_TTY=/dev/pts/6 TERM=xterm debug1: JRT-05: launch_login However, if I then query the environment of the logged in process, none of the variables have been set properly, thus: user at host:~$ echo $SSH_CLIENT user at host:~$ echo $SSH_TTY user at host:~$ echo $TERM sun I don't mind the loss of SSH_CLIENT and SSH_TTY; but the fact that my TERM is...
2010 Oct 22
2
Interix Port
Hi! I recently updated my now long-standing patches for openssh 5.5p1 on interix, and wondered if i ever reported those here, and whether there would be any interest in it anyway. So just to make sure, i'm sending it here, so you may do with it however you like. It would be cool to see the changes go upstream though ;) Regards, markus -------------- next part -------------- A non-text
2002 Jul 23
2
Irix UseLogin wtmp/utmp bug
...he problem existed in openssh 3.0.2 I just upgraded to 3.4 and still have the problem. Here is what I have found, if anyone has any info that would be great else I will have to live with this: The login program is execl'd in the sesssion.c file using the execl() call: ---------- static void launch_login(struct passwd *pw, const char *hostname) { char *env_init[] = {"MYENV=null", NULL}; /* Launch login(1). */ fprintf(stderr, "X11 forwarding not supported with IRIX login.\n"); fprintf(stderr, "Must enter password again to get AFS token,\n");...