search for: ssh_connection

Hello, I am testing ssh with occasional network disconnection between server and client during these days. I found ssh sometimes hangs if the disconnection happens after the connection is established but before ssh_exchange_identification completes. The ssh configuration files show that both client and server alive options are set. In /etc/ssh/ssh_config: # Send keepalive messages to the server.

Being rather aggrevated when testing at the enforced 1 second delay between each connection attempt and the useless 1 second delay done after all connection attempts have failed I wrote a patch to make the number of seconds delayed between each connection attempt configurable. Stephen -------------- next part -------------- diff -u --recursive openssh-2.3.0p1/ChangeLog

I see that support for AuthorizedKeysCommand has been added. The arguments supplied to the command is just the authenticating user. Can we add the SSH connection details (ie. source and destination IPs and ports) as well? This command seems to be the idea way of requiring one set of credentials from inside an organisation (say the user's own authorized_keys file) and another set from outside

...usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin", "MAIL"=>"/var/mail/root", "PWD"=>"/var/www/lookbook/current", "HOME"=>"/root", "SHLVL"=>"2", "LOGNAME"=>"root", "SSH_CONNECTION"=>"24.23.182.32 38170 98.158.22.100 22", "_"=>"/opt/ruby-enterprise-1.8.7-2010.02/bin/unicorn_rails", "RAILS_ENV"=>"production"} AFTER FORK: {"SHELL"=>"/bin/bash", "TERM"=>"xterm", "SS...

Here are the new versions of this widely used patch for OpenSSH 3.2.2p1 and 3.2.3p1. The patch avoids waiting to long when using ssh() or scp() on a down host, it is usefull when you have to update many hosts via rsync or rdist themselves relying upon ssh(). It enables a new option 'ConnectTimeout' to control exactly the timeout value, so that it can be used even on slow links. These

This allows me to set 'ControlPath ~/.ssh/sockets/%h.%p.%u' for example. Have I missed a good reason why ssh_connect finds the default port number for itself instead of just having it in options.port (like we do for the the default in options.user)? --- openssh-4.1p1/ssh.c~ 2005-06-12 09:47:18.000000000 +0100 +++ openssh-4.1p1/ssh.c 2005-06-12 09:40:53.000000000 +0100 @@ -604,6 +604,17

SSH doesn't seem to be responding to me. The machine I am connecting to is running Linux, and I could connect to it fine from windows running the SSH client. But now I can no longer connect. From Linux, this is the output: pc078:~$ ssh -v 208.240.199.51 SSH Version OpenSSH_2.2.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Reading configuration data

I'm running openssh-2.3.0p1 in linux. scp -P 2222 -v user at 207.224.119.73:openssh-2.3.0p1.tar /tmp/junk gives me Executing: program /usr/local/bin/ssh host 207.224.119.73, user user, command scp -v -f openssh-2.3.0p1.tar ssh_connect: getnameinfo failed I get that 3 times and then it gives up. I've changed ssh_connect as follows: if (getnameinfo(ai->ai_addr,ai->ai_addrlen,

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

Please tell me where I can ask questions on ssh's use. I installed openssh on two Linux boxes, one is RedHat 6.0 the other is RedHat 6.1. I used the rpms at ftp://thermo.stat.ncsu.edu/pub/openssh-usa/ I used the us versions, and I touched no config files whatsoever. >From one machine, I have no problems connecting to the other machine, but does not work the other way around. Here are

Attached is a patch which adds a ConnectionTimeout option, and corrects the ConnectionAttempts documentation. Previously, ssh would try to make a connection ConnectionAttempts times, sleeping 1 second between tries. But each connection attempt could take a very long time to fail if the packets die before the get to the host. So if ssh is being run in a script or what-have-you, it might be

Hello! I'm hoping that Gmail won't HTML format this mail so that I'll get flamed :) Anyway, my question relates to ssh_config. The problem I find is that the Host pattern is only applied to the argument given on the command line, as outlined in the man page: "The host is the hostname argument given on the command line (i.e. the name is not converted to a canonicalized host name

...ke 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 different, and that would al...

...eing set: ssh hostname "export" IRIX: DISPLAY=localhost:10.0 HOME=/root LOGNAME=root MAIL=/usr/mail//root PATH=/usr/sbin:/usr/bsd:/sbin:/usr/etc:/usr/bin:/usr/bin/X11:/usr/LOCAL/ssh/bin:/usr/LOCAL/bin:/usr/local/bin: PWD=/root SHELL=/bin/ksh SSH_CLIENT='xxx.xxx.xxx.xxx 53599 22' SSH_CONNECTION='xxx.xxx.xxx.xxx 53599 xxx.xxx.xxx.xxx 22' USER=root Linux: declare -x DISPLAY="localhost:11.0" declare -x HOME="/root" declare -x LOGNAME="root" declare -x MAIL="/var/mail/root" declare -x OLDPWD declare -x PATH="/usr/sbin:/usr/bsd:/sbin:/usr/...

Hello, There are environment variables SSH_CLIENT and SSH_CONNECTION with information about client of current session. I want to implement new variables with info about credentials used for session authentication. Such as: SSH_CLIENT_CERT SSH_CLIENT_CERT_ID SSH_CLIENT_CERT_PRINCIPALS SSH_CLIENT_PUBKEY SSH_CLIENT_PUBKEY_FINGERPRINT Some of that information availa...

Hi, I just ran into an interesting problem with 3.0p1 on FreeBSD 4.0 and IPv6/v4 mapped addresses. If I do "ssh -v machine", where "machine" has an IPv4 address in the DNS, everything works fine (machine is "hilbert.space.net"): debug1: Connecting to hilbert [194.59.182.6] port 22. ... Warning: This may be due to an old implementation of ssh. debug1: Received

...****** In /etc/profile file, i have placed these below 13 lines just above the "unset i" line, at bottom side: if [ -n "$SSH_CLIENT" ] then set $SSH_CLIENT echo "Your current connection coming from IP Address $1 using port $2, to this computer." else if [ -n "$SSH_CONNECTION" ] then set $SSH_CONNECTION echo "Your current connection coming from IP Address $1 using port $2, to this computer." else echo "Your current connection's IP Address & port could not be shown for now." fi fi In /etc/profile.local file, i have placed these...

On Thursday, April 5, 2001, at 02:09 , Theo de Raadt wrote: > please mail details about the bugs asap. The first bug I sent (pending/1759: 2.5.2p2 can't connect using protocol 2 to a 2.3.0p1 server), got sent back as "fixed in current" so hopefully that is taken care of (details at the bottom of this message). I'm happy to try and repro / debug these if necessary. The

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

I have a problem I can not identify. Two firewalls with OpenBSD 2.8 sshd version OpenSSH_2.3.0 I do a ssh root at 195.84.181.91 -v SSH Version OpenSSH_2.3.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /etc/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to 195.84.181.91 [195.84.181.91] port 22. debug: Allocated