search for: ssh_proxy_connect

...0 +0300 +++ openssh-4.5p1-ssh-socket/sshconnect.c 2007-01-16 14:06:31.000000000 +0200 @@ -310,8 +310,14 @@ debug2("ssh_connect: needpriv %d", needpriv); /* If a proxy command is given, connect using it. */ - if (proxy_command != NULL) - return ssh_proxy_connect(host, port, proxy_command); + if (proxy_command != NULL) { + if(strcmp(proxy_command,":socket:")) + return ssh_proxy_connect(host, port, proxy_command); + else { + packet_set_connection(3, 4); + return 0; + } + } /* No proxy command...

...+ #ifndef PROXY_NONE + #define PROXY_NONE "None\n" + #endif + static int show_other_keys(const char *, Key *); /* *************** *** 258,264 **** port = SSH_DEFAULT_PORT; } /* If a proxy command is given, connect using it. */ ! if (proxy_command != NULL) return ssh_proxy_connect(host, port, proxy_command); /* No proxy command. */ --- 262,268 ---- port = SSH_DEFAULT_PORT; } /* If a proxy command is given, connect using it. */ ! if (proxy_command != NULL && strcmp(proxy_command, PROXY_NONE)) return ssh_proxy_connect(host, port, proxy_command);...

Hello, My usage of ProxyCommand just calls the nc utility with various parameters. That in turn after the initial setup just copies copies the data from the network socket to stdin/stdout. This useless coping can be avoided if ssh has an option to receive the socket from the proxy command. I suppose it can improve network error reporting as ssh would talk directly to the network socket rather

...8,8 @@ port = SSH_DEFAULT_PORT; } /* If a proxy command is given, connect using it. */ - if (proxy_command != NULL) + if (proxy_command != NULL && + strcmp(options.proxy_command, "none") == 0) return ssh_proxy_connect(host, port, proxy_command); /* No proxy command. */ ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

#ssh -V OpenSSH_5.1p1, OpenSSL 0.9.8i 15 Sep 2008 Probably is not a real issue, because everyone should have its SHELL var defined, but as said above, when it's not, ssh with ProxyCommand will fail. I use connect.c, but with no SHELL var defined is not executed, ssh -v will give "No such file", and I'm pretty sure it refers to the shell, I read in ChangeLog that now ProxyCommand

...bsd-snprintf.c). If there are implementations which break the specification and fail to promote arguments of type short to an integer argument, it may be necessary to #ifdef around this on those platforms. Security implications: None known. Other notes: sshconnect.c line 59 (ssh_proxy_connect()) *may* suffer from the same bug: snprintf(strport, sizeof strport, "%hu", port); Please let me know if you require further details. Thanks, -- People shouldn't think that it's better to have Dan Astoorian loved and lost than never...

.../etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to somedomain.mynet.local [127.0.0.1] port 22. ... Expected result: Connection attempted on port 99 Actual result: Connection attempted on port 22. More info: The correct port is passed to ssh_connect_direct, but it is not used. ssh_proxy_connect works as expected. Attached patch just sets the port inside the addrinfo struct before trying to connect. Workaround: Port 99 ProxyCommand nc %h %p -- You are receiving this mail because: You are watching the assignee of the bug.

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

...t default port if port has not been set. */ - if (port == 0) { - sp = getservbyname(SSH_SERVICE_NAME, "tcp"); - if (sp) - port = ntohs(sp->s_port); - else - port = SSH_DEFAULT_PORT; - } /* If a proxy command is given, connect using it. */ if (proxy_command != NULL) return ssh_proxy_connect(host, port, proxy_command); -- dwmw2

...8,9 @@ int gaierr; int on = 1; int sock = -1, attempt; + int connect_port; char ntop[NI_MAXHOST], strport[NI_MAXSERV]; + const char *connect_host; struct addrinfo hints, *ai, *aitop; struct linger linger; struct servent *sp; @@ -218,14 +220,21 @@ if (proxy_command != NULL) return ssh_proxy_connect(host, port, pw, proxy_command); - /* No proxy command. */ + /* If an HTTP proxy is given, connect to it first. */ + if (options.proxy_server != NULL) { + connect_host = options.proxy_server; + connect_port = options.proxy_port; + } else { + connect_host = host; + connect_port = port; + }...

Dear OpenSSH Portable sshd developers, I'm having a problem where sshd login sessions are occasionally (as often as once a day) getting stuck indefinitely. I enabled debug messages and got a backtrace of a stuck sshd, and I think I've found the bug. I wanted to run it by the list once before filing. sshd version: OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004

In sshconnect.c there are two global variables for server_version_string client_version_string. These are used just in a few functions and can easily be passed as parameters. Also, there is a strange construct, where their memory is allocated to the global pointers, then copies of these pointers are assigned to the kex structure. The kex_free finally frees them via cleanup of the kex