search for: ssh_tty

I'm having a path problem with OpenSSH 2.5.1p1 in Solaris (7). When ssh-agent is run, environment variables aren't being passed to the spawned shell. sol# env | wc -l 23 sol# env | grep -i ssh SSH_CLIENT=10.0.1.146 1047 22 SSH_TTY=/dev/pts/0 sol# sol# ssh-agent sh sol# env | wc -l 1 sol# env SSH_AGENT_PID=12032 sol# If I set SSH_AUTH_SOCK manually, ssh-agent (and ssh-add) does function properly... sol# find /tmp -name 'agent*' -exec ls -l {} \; srwxr-xr-x 1 root...

...authentication has been set up. The second approach I have is much simpler and, except for one big issue, smoother. Instead of editing your local machine `~/.ssh/config`, you just edit the `.bashrc` on your remote machine to include the following block ``` if [[ $- =~ i ]] && [[ -n "$SSH_TTY" ]]; then shpool attach "ssh-$(basename $SSH_TTY)" fi ``` I think the equivilant for tmux is ``` if [[ $- =~ i ]] && [[ -n "$SSH_TTY" ]]; then tmux attach-session -t "ssh-$(basename $SSH_TTY)" fi ``` this works quite well, except that $SSH_TTY hol...

...log.. I''m not sure if UNICORN_FD has something to do with it? 1) starting unicorn BEFORE FORK: {"SHELL"=>"/bin/bash", "TERM"=>"xterm", "SSH_CLIENT"=>"24.23.182.32 38170 22", "OLDPWD"=>"/root", "SSH_TTY"=>"/dev/pts/5", "USER"=>"root", "SSH_AUTH_SOCK"=>"/tmp/ssh-eeoDcvH461/agent.461", "PATH"=>"/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin", "MAIL"=>"/var/mail/root", "PWD...

...ported something like Apache "virtual hosts". This would make it much more viable to host multiple installs of git on the same server, for example. More details: On the remote server, ssh already sets some environment variables: > printenv | grep SSH SSH_CLIENT=192.168.1.18 50945 22 SSH_TTY=/dev/pts/1 SSH_CONNECTION=192.168.1.18 50945 192.168.1.1 22 What about adding another, say SSH_SERVER_HOST=host1 Assuming that /etc/hosts 192.168.1.1 host1 host2 then ssh user at host1 and ssh user at host2 would lead to a shell on the same host with the same user, but SSH_SERVER_HOST would be di...

...ckey). > 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...

...low) debug1: Authentication succeeded (publickey). 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...

...sh user at server /bin/sh Interestingly, Debian 2.2's openssh (1:1.2.3-9.3) does enforce rlimits somehow, not sure if it was specifically patched to do this or perhaps the older version just does not have this problem. Just an FYI, while messing with this I also notice that the SSH_CLIENT and SSH_TTY environment variables are not being set, and no authlog message is generated. (Neither of these problems exist in the Debian build.)

...fix klibc compiles fine on sparc with newer gcc, but segfaults: titan:~# strace -vfF /usr/lib/klibc/bin/fstype execve("/usr/lib/klibc/bin/fstype", ["/usr/lib/klibc/bin/fstype"], ["SHELL=/bin/bash", "TERM=xterm", "SSH_CLIENT=[myip] 39403"..., "SSH_TTY=/dev/pts/0", "USER=root", "LS_COLORS=no=00:fi=00:di=01;34:l"..., "PATH=/usr/local/sbin:/usr/local/"..., "MAIL=/var/mail/root", "PWD=/root", "LANG=en_US.UTF-8", "PS1=\\h:\\w\\$ ", "HOME=/root", "SHLVL=2",...

...he initial shell. A "truss -aef" tells me that login is being execl'd like: 27066: execve("/bin/login", 0x080470FC, 0x0815F6CC) argc = 7 27066: argv: login -h <IP> -p -f -- phess 27066: envp: TZ=BST11 SSH_CLIENT=<IP> 1471 22 SSH_TTY=/dev/pts/31 27066: TERM=vt100 Do you have any ideas what I can define in order to fix this problem? I also found what I believe might be a bug in uidswap.c at line 88. It used to look like: ----- #ifndef SAVED_IDS_WORK_WITH_SETEUID /* Propagate the privileged gid to all...

...man:/usr/X11R6/man:/opt/gnome/share/man:/opt/c3-4/man HOSTNAME=master GNOME2_PATH=/usr/local:/opt/gnome:/usr XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB HOST=master TERM=xterm SHELL=/bin/bash PROFILEREAD=true HISTSIZE=1000 SSH_CLIENT=::ffff:10.15.1.179 51565 22 QTDIR=/usr/lib/qt3 OLDPWD=/opt/openmpi/bin SSH_TTY=/dev/pts/6 GROFF_NO_SGR=yes JRE_HOME=/usr/lib/jvm/java/jre USER=pearman LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=4 0;31:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00; 31:*.tbz=00;31:*.tgz=00;31:*.rpm=00...

...ore-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 1767 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env SSH_CLIENT debug3: Ignored env SSH_TTY debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env MAIL debug3: Ignored env PATH debug3: Ignored env PWD debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env LOGNAME debug3: Ignored env SSH_CONNECTION debug3: Ignored env LESSOPEN debug3: Ignored env LESSCLO...

...ask show_env executing "env" servers: ["foo.dartmouth.edu"] processing command [foo.dartmouth.edu] executing command [out :: foo.dartmouth.edu] TERM=xterm [out :: foo.dartmouth.edu] SHELL=/bin/bash [out :: foo.dartmouth.edu] SSH_CLIENT=x.x.x.x 55394 22 [out :: foo.dartmouth.edu] SSH_TTY=/dev/ttyp0 [out :: foo.dartmouth.edu] USER=brianvh [out :: foo.dartmouth.edu] MAIL=/var/mail/brianvh [out :: foo.dartmouth.edu] PATH=/usr/bin:/bin:/usr/sbin:/sbin [out :: foo.dartmouth.edu] PWD=/Users/brianvh [out :: foo.dartmouth.edu] SHLVL=1 [out :: foo.dartmouth.edu] HOME=/Users/brianvh [out ::...

On 12/08/15 16:23, sandy.napoles at eccmg.cupet.cu wrote: > when I type 'env' I have > > TERM=xterm > SHELL=/bin/bash > XDG_SESSION_COOKIE=a1d519cf22cd431fb15180d000000351-1439393059.403089-1335452928 > SSH_CLIENT=172.18.68.6 60620 22 > SSH_TTY=/dev/pts/0 > USER=root > MAIL=/var/mail/root > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > PWD=/root > LANG=en_US.UTF-8 > SHLVL=1 > HOME=/root > LOGNAME=root > SSH_CONNECTION=172.18.68.6 60620 172.18.68.8 22 > _=/usr/bin/env > > > 12 de...

...rt()); child_set_env(&env, &envsize, "SSH_CLIENT", buf); + snprintf(buf, sizeof buf, "%.50s", + get_local_ipaddr2()); + child_set_env(&env, &envsize, "SSH_LOCAL", buf); if (s->ttyfd != -1) child_set_env(&env, &envsize, "SSH_TTY", s->tty);

...ble to run commands (or scp) remotely, only login. Probably no-one will have a use for this but I thought I'd share because it shows how to run a shell as a login shell from a ForceCommand. Wout. #!/usr/bin/perl use strict; # Give the user a shell if that was their intention if (exists $ENV{SSH_TTY} && not exists $ENV{SSH_ORIGINAL_COMMAND}) { # Find out what their shell is my @pw = getpwuid($<); my $shell = $pw[8] || '/bin/sh'; # Run it as a login shell exec { $shell } '-sh' ; } else { print STDERR "Remote commands disabled, pl...

On Thu, 2 Mar 2023 at 00:12, Ethan Pailes <ethan at pailes.org> wrote: [...] > this works quite well, except that $SSH_TTY holds the path of the > remote pty rather than the local pty, so there is nothing that ensures > that you will reconnect to the same session if you ssh back into your > remote machine from the same local terminal emulator. > > First of all, can anyone think of some obvious thing I...

Hi ! I haven't found an easy solution to determine the local IP to which the remote SSH client is connected to the local SSHD. We use MC/Serviceguard which can create many Interfaces where a remote client could connect and we like to know within .profile which interface the client has connected to. I've looked at the sourcecode and maybe the following could do something I described :

...emote_port(), get_local_port()); child_set_env(&env, &envsize, "SSH_CLIENT", buf); + if (key_matching_data(NULL)) + child_set_env(&env, &envsize, "SSH_AUTHKEY", key_matching_data(NULL)); if (s->ttyfd != -1) child_set_env(&env, &envsize, "SSH_TTY", s->tty); if (s->term)

...shell. debug: Entering interactive session. Last login: Wed Sep 6 16:08:18 2000 from localhost Welcome to ThisCompanny, Inc. ! Environment: USER=a_user LOGNAME=a_user HOME=/home/a_user PATH=/usr/bin:/bin MAIL=/var/spool/mail/a_user SHELL=/bin/bash SSH_CLIENT=127.0.0.1 1157 22 SSH_TTY=/dev/pts/0 TERM=linux Connection to localhost closed. debug: Transferred: stdin 0, stdout 297, stderr 33 bytes in 0.1 seconds debug: Bytes per second: stdin 0.0, stdout 4280.2, stderr 475.6 debug: Exit status 0 -------------- next part -------------- Sep 6 16:08:28 evelyn sshd[9571]: Generating...

Hello, with OpenSSH_2.3.0p1 running in HP-UX 11.00 I noticed that the "SD commands" (like "swcopy") produce the following error when being logged in via SSH: ERROR: RPC exception: "Who are you failed (dce / rpc)" 11/29/00 11:20:18 MET Ideas? Regards, Ulrich P.S. Not subscribed to the list