similar to: [Bug 1334] New: Bind tunnels to given interface on the server

Hi, I am using the following version of OpenSSH for reference: root at proxy:/root# ssh -V OpenSSH_4.8, OpenSSL 0.9.7j 04 May 2006 root at proxy:/root# uname -a OpenBSD proxy.localdomain 4.3 GENERIC#698 i386 I am developing an application which uses on-the-fly SSH port forwarding by using the "~C" escape sequence to add local port forwards when needed (through Expect). It would

Hi, tmux author refuses to add -h, --help option, because OpenSSH does not have it [1]. I don't see why convenience features of tmux should depend on OpenSSH, but because I have no other choice (and got curious) I ask here - why OpenSSH doesn't provide -h or --help option? I use PuTTY as my client, which processes --help option, and for `ssh` binary I usually use Google + StackOverflow.

The attached patch for 4.6p1 adds a feature (-u) that will check to see if a key exists on a remote host. I use this for auditing my users transition to v2 keys very useful. If there is any interest I'll provide a patch for v2 ssh keys also. http://vapid.dhs.org/dokuwiki/doku.php?id=vapidlabs:openssh_check_key_patch -- Thanks Larry --- orig/openssh-4.6p1/sshconnect1.c 2006-11-07

On 19Oct2018 17:12, Damien Miller <djm at mindrot.org> wrote: >On Fri, 19 Oct 2018, Cameron Simpson wrote: >> The ssh command line's -L option has supported socket forwarding for >> a while, >> but as far as I can tell the ssh_config file does not, even in 7.9. > >It does, look for LocalForward Pardon me, I've been unclear. I don't mean TCP forwards

https://bugzilla.mindrot.org/show_bug.cgi?id=2592 Bug ID: 2592 Summary: -R bind_address not working, always bind 0.0.0.0 Product: Portable OpenSSH Version: 7.2p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at

FINALLY, it's here. You can now tell SSH which address to bind to for every single port forwarding option! This patch allows you to pass the following as ssh command line options: ssh -L 192.168.1.55:1234:localhost:80 -R ::11:22:aa:bb/80/localhost/80 etc. Or as normal config file options: LocalForward ::11:22:33/1234 localhost/80 RemoteForward 1.2.3.4:80 localhost:80 It will also

I have a firewall with 2 connections to the internet (eth1 and eth2) and one LAN interface. on the LAN interface, the users can connect via PPTP. those authenticating via pptp shall be masqueraded over eth2, those not authenticating should be ordinary masqueraded over eth1. as from the archives I took the configuration like in FAQ32, but this doesn''t work with the ppp+ interfaces. I

https://bugzilla.mindrot.org/show_bug.cgi?id=1572 Summary: accept SOCKS requests over the mux socket in master mode Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: unassigned-bugs

I've attached a patch to OpenSSH 3.0.2p1 that will allow the client side of local port forwarding to be bound to a single address. For my purposes, binding to 127.0.0.1 or (via GatewayPorts) all addresses would not work. I overloaded the "-b local_host" option so that it's address will be used when "-L port:remote_host:remote_port" is also specified. Today is the first

http://bugzilla.mindrot.org/show_bug.cgi?id=1077 Summary: Descriptions for "ssh -D" and DynamicForward should mention they can specify "bind_address" optionally Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority:

https://bugzilla.mindrot.org/show_bug.cgi?id=2174 Bug ID: 2174 Summary: no-pty in authorized_keys does not prevent and interactive shell Product: Portable OpenSSH Version: 6.4p1 Hardware: All OS: Linux Status: NEW Severity: security Priority: P5 Component: sshd

OpenSSH supports the -b bind_address argument for binding to a local IP address when connecting to a remote host. It's however currently not possible to specify a local port to bind to, something I've found useful at several occasions. Below is an unified diff that introduces the [-B bind_port] option to ssh(1) and a ssh_config(5) style option "BindPort bind_port". This allows

https://bugzilla.mindrot.org/show_bug.cgi?id=2324 Bug ID: 2324 Summary: remote port forward w/ empty bind_address via multiplexed connection: doc violation Product: Portable OpenSSH Version: 6.7p1 Hardware: amd64 OS: Linux Status: NEW Severity: trivial Priority: P5

This setup is rather complex, so apologies for the length of this mail. I'm also not at all sure where my problem is, so again I apologise if this is the wrong place to ask. I have a raspberry pi sitting in a remote office (hostname 'pi' below), a VPS hosted on someone's cloud (hostname 'vps' below) and my local laptop (hostname 'laptop'). The remote office then

I am have a shorewall firewall and freeswan ipsec running on a redhat 8.0 Linux gateway machine. I have one working tunnel defined, all works well. I am not clear how to define mutiple concurrent tunnels. I can not add further interface entries as all the tunnels come in on ipsec0, do I still have mutiple zone definitions? some of the tunnels will be dynamic roadwarriors and as such would need a

I use ssh tunnels extensively. recently I upgraded my linux kernel from 2.6.18 to 2.6.37 and a problem with tunnels has resulted. prior to the upgrade use of ssh tunN devices was rock solid. the problem manifests as the tunnel from the initiator end ceasing to transfer data to the remote after a quantity of data is sent. it is necessary to create a new tunnel after destroying the old to get

Hi, Currently, OpenSSH only accepts the SOCKS5 command "CONNECT": <https://anongit.mindrot.org/openssh.git/tree/channels.c#n1281> The RFC also specifies the commands "BIND" and "UDP ASSOCIATE": <https://tools.ietf.org/html/rfc1928#section-4> As a consequence, in particular, a SOCKS5 server started with "ssh -D" cannot proxify UDP packets. Are

Hi, I have two systems each with 2 two gre tunnels over ipsec. The tunnels are setup to loadbalance using ''ip route''. Using ping from one server to the other I get equal results via the two gre tunnels, but when I try a large ftp transfer the utilization of one tunnel is 90% and the other 10%. The two interfaces are both 100/full. What would be the reason for this, or would

On Fri, Sep 25, 2015 at 08:41:06AM +0200, Marcus Schopen wrote: > I'm running some tinc clients behind a NAT (masquerading, Cisco Router) > connecting to a host outside on a public IP in a different network. The > tunnels get unstable every few minutes and I see packet loss when > pinging the clients on their internal tunnel IPs from the host side. > Before putting the tinc

Hi , I am trying to set up a GRE tunnel between two linux routers. The routers have a 400 MHz Processor. Linux .2 65.0.0.2 Linux LAN1 -------- Router -------- INTERNET ---- Router ---- LAN2 10.10.10.0 .1 208.1.0.1 (Simulated) .1 .1 192.168.2.0/24 /24 Scripts to Create the tunnel ip tunnel add tun0 mode gre remote 65.0.0.1 local