search for: socks4

Hi all. I was getting something working over socks5 and was trying to figure out why it kept using socks4. It wasn't, it was just a misleading debug message.... Patch applies to either OpenBSD or Portable. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually...

I love SSH's ability to dynamically forward ports using SOCKS (either -D or DynamicForward) (ie "ssh -D 1081 private.mine.net"). But the thing that has caused me some pain, is that only SOCKS4 is supported. The SOCKS4 proxy specification does not permit hostnames, but only IP addresses. This isn't much of a problem if the target host is a public Internet host or otherwise DNS resolvable target ... but frequently SSH tunneling is used to get into a private network, and the DNS whic...

This provides SOCKS4A support, which allows a SOCKS4 client to provide a host name instead of an IP address. It indicates that it's doing so by using a known-invalid IP address 0.0.0.x (where x != 0), and then appending the NUL-terminated hostname to the connection request. Although we check for the terminating NU...

...ure.sh which you will find attached :-) The one drawback that I saw when rummaging around in openssh code is that it is nicely set up to support ipv6 and the socks stuff only works for ipv4. The socks support is identical to that supplied in the pre-openssh ssh-1.2.xx stuff. I have not tested the socks4 support. Michael -------------- next part -------------- --with-socks5 patch apply the patch regenerate config.h.in autoheader configure.in > config.h.in regenerate configure autoconf configure.in > configure then build the configuration this example is for Linux #!/bin/sh CFLAGS=&qu...

http://home.t-online.de/home/Andreas.Steinmetz/windows/socks.html An utter pain to make functional under XP, but this is pretty significant for users of Dynamic Forwarding. More good stuff coming soon (as I always say). --Dan

Attached is a very small patch that allows the ssh clients to use the socks5 library. It should work with socks4 but is untested. Tested on linux only configure --with-socks configure --with-socks5 Also included is a configure option to disable scp statistics --disable-scp-stats modified files openssh-2.9.9p2/acconfig.h openssh-2.9.9p2/channels.c openssh-2.9.9p2/configure.in openssh-2.9.9p2/includes.h o...

is openssh going to ever contain socks4/5 proxy support (http://www.socks.nec.com/) the same way ssh (nonfree version) does? Without this support, openssh is completely unusable behind a firewall. Hayden A. James

Hi there, I'm Vladimir Olteanu (or just Vlad, for short), and I'm working on the SOCKSv6 protocol. It is being discussed at the IETF (https://tools.ietf.org/html/draft-olteanu-intarea-socks-6-10). The spec has matured somewhat and is currently undergoing an adoption call at the Intarea WG. I would like to get your opinion on this newer version of the protocol, in particular on how

...er of failed logins and update /etc/security/lastlog and /etc/security/failedlogins. 4) loginrestrictions - this function will determine if a user is allowed to login (ie too many failed logins, account disabled, etc). This function is used in conjunction with authenticate. 5) SOCKS5 and SOCKS4 support. 6) Support for the system random function instead of egd or /dev/urandom. There is one fix that should be put in. In sshd.c, function do_authloop, client_user needs to be set to NULL after the xfree. There is a double free happening here. *** acconfig.h.DIST Tue Jan 11 09:38:15 2000...

...what command needed for me to send the client, through 'ssh' terminal command. Interpreting Wikipedia's definitions of the SOCKS5 protocol, has revealed that I have to 'TCP/IP stream' to the proxy server. The SOCKS5 protocol is defined in RFC 1928. It is an extension of the SOCKS4 protocol. It offers more choices of authentication, adds support for IPv6 and UDP that can be used for DNS lookups. The initial handshake now consists of the following: Client connects and sends a greeting which includes a list of authentication methods supported. Server chooses one (...

Is there any plan to add socks 4 or socks 5 support to openssh like the original ssh developed in finland?? Michael Michael at bizsystems.com

Hi, Some programs, which requires network, do not support proxy mechanism such as SOCKS5. There is a tool called proxychains (http://proxychains.sf.net) which provides us to redirect all of the network traffic to a defined server can be SOCKS4, 5, or others. For instance, I can use proxychains wget http://www.google.com to download the homepage of google if I am behind the proxy. This is quiet useful, it even works with java too. But I dont have any luck to use it with wine, anyone else wants to give it a try ? or...find a workaround...

...the server-side, for a channel type of SSH_CHANNEL_RPORT_LISTENER, c->host_port is 0 and therefore, per the above code, nextstate == SSH_CHANNEL_DYNAMIC and port_open_helper() is not called. I am not sure what the function of SSH_CHANNEL_DYNAMIC is but it looks like it has something to do with socks4 (from looking at channel_pre_dynamic()) and probably doesn't apply to the SSH_CHANNEL_RPORT_LISTENER case. I suspect that nextstate should be SSH_CHANNEL_OPENING in order to call port_open_helper(). I tried to make the change : nextstate = (c->type == SSH_CHANNEL_RPORT_LISTENER) ?...

Hello list, I wonder why tinc tries to resolve host names before connection even with configured (socks5) proxy which fails behind restrictive firewalls. Is there any "workaround"? Thanks in advance! Regards Uwe -------------- n?chster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL:

...: @@ -635,6 +639,7 @@ channel_open_message(void) case SSH_CHANNEL_OPENING: case SSH_CHANNEL_CONNECTING: case SSH_CHANNEL_DYNAMIC: + case SSH_CHANNEL_RDYNAMIC: case SSH_CHANNEL_OPEN: case SSH_CHANNEL_X11_OPEN: case SSH_CHANNEL_INPUT_DRAINING: @@ -1033,14 +1038,23 @@ channel_decode_socks4(Channel *c, fd_set *readset, fd_set *writeset) u_int16_t dest_port; struct in_addr dest_addr; } s4_req, s4_rsp; + Buffer *input, *output; + + if (c->type == SSH_CHANNEL_RDYNAMIC) { + input = &c->output; + output = &c->input; + } else { + input = &c->input; + outp...

...orithms server options ClientAliveInterval and ClientAliveCountMax tty mode passing general: gid swapping in sshd (fixes access to /home/group/user based directory structures) Dan Kaminsky <dankamin at cisco.com> contributed an experimental SOCKS4 proxy to the ssh client (yes, client not the server). Use 'ssh -D 1080 server' if you want to try this out. server option PrintLastLog improvements for scp > 2GB improved ListenAddress option. You can now use ListenAddress host:port improved interoperability (bug detecti...

...orithms server options ClientAliveInterval and ClientAliveCountMax tty mode passing general: gid swapping in sshd (fixes access to /home/group/user based directory structures) Dan Kaminsky <dankamin at cisco.com> contributed an experimental SOCKS4 proxy to the ssh client (yes, client not the server). Use 'ssh -D 1080 server' if you want to try this out. server option PrintLastLog improvements for scp > 2GB improved ListenAddress option. You can now use ListenAddress host:port improved interoperability (bug detecti...

...cks. bz#2184 * ssh(1): avoid unnecessary hostname lookups when canonicalisation is disabled. bz#2205 * sshd(8): avoid sandbox violation crashes in GSSAPI code by caching the supported list of GSSAPI mechanism OIDs before entering the sandbox. bz#2107 * ssh(1): fix possible crashes in SOCKS4 parsing caused by assumption that the SOCKS username is nul-terminated. * ssh(1): fix regression for UsePrivilegedPort=yes when BindAddress is not specified. * ssh(1), sshd(8): fix memory leak in ECDSA signature verification. * ssh(1): fix matching of 'Host' directives in ssh_co...

On Tue, Oct 27, 2015 at 12:33:35PM +0000, Uwe Werler wrote: > I wonder why tinc tries to resolve host names before connection even > with configured (socks5) proxy which fails behind restrictive firewalls. You are right that it shouldn't be necessary to do this with SOCKS5. With SOCKS4, it needs to know the exact address, and then I just used that for SOCKS5 as well. > Is there any "workaround"? The workaround is to do resolve the hostnames yourself and replace the hostnames in the Address statements with numeric addresses. I'll try to change tinc so it will al...

...15 at 12:33:35PM +0000, Uwe Werler wrote: > > > I wonder why tinc tries to resolve host names before connection even > > with configured (socks5) proxy which fails behind restrictive firewalls. > You are right that it shouldn't be necessary to do this with SOCKS5. > With SOCKS4, it needs to know the exact address, and then I just used > that for SOCKS5 as well. > > > Is there any "workaround"? > The workaround is to do resolve the hostnames yourself and replace the > hostnames in the Address statements with numeric addresses. I'll try to...