Displaying 20 results from an estimated 1000 matches similar to: "[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport"
2005 Jan 24
17
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
------- Additional Comments From dtucker at zip.com.au 2005-01-24 14:27 -------
Created an attachment (id=782)
--> (http://bugzilla.mindrot.org/attachment.cgi?id=782&action=view)
forward-bind.sh: regression test for binding port forwards to addresses
Current limitations of test:
- no testing of IPv6
- no testing of backwards compat
2002 Nov 21
3
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sjc at makalumedia.com
------- Additional Comments From markus at openbsd.org 2002-11-22 09:48 -------
*** Bug 441 has been marked as
2004 Jun 06
2
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mohit_aron at hotmail.com
------- Additional Comments From dtucker at zip.com.au 2004-06-06 12:12 -------
*** Bug 876 has been marked
2002 Oct 11
2
[Bug 413] New: Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
Summary: Port forwarding:
[localhost:]localport:remotehost:remoteport
Product: Portable OpenSSH
Version: older versions
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: ssh
AssignedTo:
2003 Feb 03
8
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 -------
i'll look into this.
------- You are
2005 Apr 07
4
[Bug 1012] Trouble creating remote port forwarding to ssh.com 2.4.0 server.
http://bugzilla.mindrot.org/show_bug.cgi?id=1012
Summary: Trouble creating remote port forwarding to ssh.com 2.4.0
server.
Product: Portable OpenSSH
Version: 4.0p1
Platform: All
OS/Version: All
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: ssh
2009 Feb 17
2
Idea: reverse socks proxy
Hi,
Just a usecase that I'm sure has been covered before but just in case
its not an openssh solution would be very helpful.
I was trying to install software on a server that was firewalled so no
outbound http connections would work. I was also tunnelling via
another server. Outbound ssh connections also were a convenient option.
What would have been nice would be a remote version of
2000 Aug 23
1
Protocol 2 remote forwarding patch
Hi !
Here's a patch to add remote port forwarding support (protocol 2) for
openssh. I have tried to test that it works like it should but a more
thorough testing is needed. This patch adds both client/server support.
The patch should be applied to openssh-2.1.1p4 source tree.
Also included is a PortForwarding sshd_config option, new ./configure
option --disable-forwarding that should make it
2012 May 03
5
[PATCH/RFC 0/6] New mux client request to list open tcp forwardings.
These patches implement a new mux client request to list the currently opened
TCP forwardings. It also removes some todos regarding keeping the list
of forwardings in the options up-to-date.
Bert Wesarg (6):
attach the forwarding type to struct Forward
merge local and remote forward lists
generate unique ids for forwardings to be used for identification
remove closed forwardings from
2023 Dec 02
0
Feature Request: also report LocalPort in logs
I'm currently trying to set up a kind of vhost, using a second
LocalPort;
I notice that this isn't reported in auth.log yet,
thus this feature request.
Thanks!
2023 Nov 11
2
OpenSSH on Windows, ssh cannot |bind()| localport to port < 1023
Hi!
----
I'm doing some testing with the ssh client OpenSSH on Windows 10
(10.0-19045) but due to firewall restrictions I need to run my
experiments from a local port < 1024 (not negotiable).
I thought that this was no problem... but ssh |bind()| fails with
"address in use" (yes, I checked netstat, no one is there) for any
port < 1023.
Then I checked $ netstat # and $ netsh
2005 Mar 04
1
[PATCH] controlling remote port forwarding over control path
Hi,
the attached patch implements adding and canceling of remote port
forwardings by communicating with a running ssh client via a control
socket.
Thus, one can do this:
ssh -MNfS ~/.ssh/ctl remotehost
and then:
ssh -S ~/.ssh/ctl -O add-rforward 2000:forward:80 localhost
to add a new remote forwarding or
ssh -S ~/.ssh/ctl -O cancel-rforward localhost:2000 localhost
to remove it.
The
2012 Sep 15
2
ssh(1) documentation for -L and -R
I found that the documentation for -L and -R was hard to understand.
So I made some changes to try to make it clearer. I started with Revision
1.328 from http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ssh.1
Comments welcome.
================ ssh.1.patch ================
--- ssh.1 2012/09/15 16:08:48 1.1
+++ ssh.1 2012/09/15 20:23:35
@@ -51,13 +51,13 @@
.Op Fl F Ar configfile
.Op Fl I
2009 Jan 19
1
Bug CVE-2005-2797
Hi Everyone,
I am using openssh 4.0 in a product, which is affected by
CVE-2005-2797 (If DynamicForward option is activated, GatewayPorts is
also unconditionally enabled). I am trying to backport the fix for
this from 4.2 to 4.0. I have been finding the difference between 4.2
and 4.1 and the only change that looks relevant to this bug, to me is
the changes made in the file readconf.c with the
2002 Mar 07
11
[Bug 146] OpenSSH 3.1p1 will not build on BSD/OS 4.2/4.1/4.01
http://bugzilla.mindrot.org/show_bug.cgi?id=146
------- Additional Comments From mouring at eviladmin.org 2002-03-08 07:38 -------
I just went through someone with this problem. And HAVE_BOGUS_SYS_QUEUE_H
worked for them. However you must have BOTH HAVE_SYS_QUEUE_H and
HAVE_BOGUS_SYS_QUEUE_H set.
As for INADDR_LOOPBACK. I'd like to know where on BSD/OS that is defined
so we can
2005 May 11
5
[Bug 1037] Man page for -L and -R should mention -g
http://bugzilla.mindrot.org/show_bug.cgi?id=1037
Summary: Man page for -L and -R should mention -g
Product: Portable OpenSSH
Version: 4.0p1
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P5
Component: Documentation
AssignedTo: bitbucket at mindrot.org
ReportedBy:
2005 Mar 10
6
[Bug 996] Fatal error in xfree() when scp invokes ssh with a LocalForward config
http://bugzilla.mindrot.org/show_bug.cgi?id=996
Summary: Fatal error in xfree() when scp invokes ssh with a
LocalForward config
Product: Portable OpenSSH
Version: 4.0p1
Platform: All
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo:
2005 Mar 05
2
[Bug 993] adding and removing forwardings via the control connection
http://bugzilla.mindrot.org/show_bug.cgi?id=993
Summary: adding and removing forwardings via the control
connection
Product: Portable OpenSSH
Version: 4.0p1
Platform: All
OS/Version: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: ssh
2004 Aug 05
1
LocalForward and RemoteForward bind patch
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
2015 Jun 11
2
[PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix
from: Jeff Sloan <jeff_sloan at selinc.com>
Update UEFI PXE proxyDHCP handling.
This patch is based on commit ID 8a00e49
Modify two files to specify valid ip addresses. These files are efi/pxe.c
and efi/udp.c.
In efi/pxe.c: In net_parse_dhcp function.
If ProxyOffer has been received, start with DhcpAck packet since it is the
most complete. This requires a minimum of changes to the