search for: socks4a

...DNS resolvable target ... but frequently SSH tunneling is used to get into a private network, and the DNS which can resolve the hostname is on the wrong side of the tunnel. I don't think that SOCKS5 or anything that complex would be usefully helpful, but there is an addition to SOCKS4 (called SOCKS4A) which does permit host names to be passed in in the SOCKS4 initiation packet. See http://www.socks.nec.com/protocol/socks4a.protocol for details, and here's a brief synopsis. The SOCKS4 initiation packet looks like this: +----+----+----+----+----+----+----+----+----+----+....+---...

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 NUL...

https://bugzilla.mindrot.org/show_bug.cgi?id=1482 Summary: SOCKS4A support Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: unassigned-bugs at m...

Hi, has anybody seen a patch that provides socks version 5 support for the dynamic portforwarding feature? I?ve seen thats implemented in ssh.com?s ssh version, but found nothing about openssh. Only thing i found was a patch to provide socks4a. cu sleepi

...tput = &c->output; + } debug2("channel %d: decode socks4", c->self); - have = buffer_len(&c->input); + have = buffer_len(input); len = sizeof(s4_req); if (have < len) return 0; - p = buffer_ptr(&c->input); + p = buffer_ptr(input); need = 1; /* SOCKS4A uses an invalid IP address 0.0.0.x */ @@ -1065,12 +1079,12 @@ channel_decode_socks4(Channel *c, fd_set *readset, fd_set *writeset) } if (found < need) return 0; - buffer_get(&c->input, (char *)&s4_req.version, 1); - buffer_get(&c->input, (char *)&s4_req.command, 1);...

if I: ssh -fND localhost:6000 somebody at 192.168.56.5 -p PORTNUMBER from computer "A" to computer "B" [B = 192.168.56.5] then I can set the SOCKS proxy for e.g.: Firefox to use "localhost:6000" on computer "A". Ok. I can surf the web through "B". But: - Can anyone sniff the traffic of "A"? [e.g.: computers on same subnet as

...ather than stderr, which is useful when running daemonised (ssh -f) * The sshd_config(5) ForceCommand directive now accepts commandline arguments for the internal-sftp server. * The ssh(1) ~C escape commandline now support runtime creation of dynamic (-D) port forwards. * Support the SOCKS4A protocol in ssh(1) dynamic (-D) forwards. (bz#1482) * Support remote port forwarding with a listen port of '0'. This informs the server that it should dynamically allocate a listen port and report it back to the client. (bz#1003) * sshd(8) now supports setting PermitEmptyPasswo...

...ather than stderr, which is useful when running daemonised (ssh -f) * The sshd_config(5) ForceCommand directive now accepts commandline arguments for the internal-sftp server. * The ssh(1) ~C escape commandline now support runtime creation of dynamic (-D) port forwards. * Support the SOCKS4A protocol in ssh(1) dynamic (-D) forwards. (bz#1482) * Support remote port forwarding with a listen port of '0'. This informs the server that it should dynamically allocate a listen port and report it back to the client. (bz#1003) * sshd(8) now supports setting PermitEmptyPasswo...

...ather than stderr, which is useful when running daemonised (ssh -f) * The sshd_config(5) ForceCommand directive now accepts commandline arguments for the internal-sftp server. * The ssh(1) ~C escape commandline now support runtime creation of dynamic (-D) port forwards. * Support the SOCKS4A protocol in ssh(1) dynamic (-D) forwards. (bz#1482) * Support remote port forwarding with a listen port of '0'. This informs the server that it should dynamically allocate a listen port and report it back to the client. (bz#1003) * sshd(8) now supports setting PermitEmptyPasswo...

...en running daemonised (ssh -f) > > * The sshd_config(5) ForceCommand directive now accepts commandline > arguments for the internal-sftp server. > > * The ssh(1) ~C escape commandline now support runtime creation of > dynamic (-D) port forwards. > > * Support the SOCKS4A protocol in ssh(1) dynamic (-D) forwards. > (bz#1482) > > * Support remote port forwarding with a listen port of '0'. This > informs the server that it should dynamically allocate a listen > port and report it back to the client. (bz#1003) > > * sshd(8) now...

> Winton-- > > Excellent! Absolutely wonderful. > > I'm wondering which apps/encapsulators support 4A? This gets me > around > the DNS leakage problem quite nicely. > > Incidentally, we do need SOCKS5 support -- if for no other > reason, the > fact that there's *operating system* level support in OSX for SOCKS5 > redirection. So

OpenSSH 3.0 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. This release contains many portability bug-fixes (listed in the ChangeLog) as well as several new features (listed below). We would like to thank the