similar to: [PATCH] ssh.1: Clarify remote bind_address usage

Displaying 20 results from an estimated 10000 matches similar to: "[PATCH] ssh.1: Clarify remote bind_address usage"

2016 Jun 20
2
[Bug 2592] New: -R bind_address not working, always bind 0.0.0.0
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
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
2010 Aug 14
1
bind_address ignored? as in "ssh -R [bind_address]:12491:127.0.0.1:500"
No answers on secureshell at securityfocus.com I must be doing something wrong or the server seems to ignore my bind request. Port forwarding is working it just bind to all ips and ignores my bind request. I've also tried this with an rfc1918 address opposed to a loopback and had the same results. Google and the archive haven't helped. Thanks in advance for your time and consideration.
2014 Dec 04
4
[Bug 2324] New: remote port forward w/ empty bind_address via multiplexed connection: doc violation
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
2005 Sep 01
1
[Bug 1077] Descriptions for "ssh -D" and DynamicForward should mention they can specify "bind_address" optionally
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:
2021 Jul 25
8
[Bug 3331] New: Issues with man pages
https://bugzilla.mindrot.org/show_bug.cgi?id=3331 Bug ID: 3331 Summary: Issues with man pages Product: Portable OpenSSH Version: 8.4p1 Hardware: Other OS: All Status: NEW Severity: minor Priority: P5 Component: Documentation Assignee: unassigned-bugs at mindrot.org
2014 Feb 10
0
[PATCH] Basic SCTP support for OpenSSH client and server
This patch allows the OpenSSH client to make connections over SCTP, and allows the OpenSSH server to listen for connections over SCTP. SCTP is a robust transport-layer protocol which supports, amongst other things, the changing of endpoint IPs without breaking the connection. To connect via SCTP, pass -H or set "ConnectViaSCTP yes". To listen via SCTP as well as TCP, set
2002 Jan 05
2
new feature w/ patch
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
2007 Aug 22
0
Patch to allow checking of v1 keys on remote host.
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
2010 Aug 07
7
[Bug 1804] New: ssh option -R 127.0.0.2:10443:<dest ip>:443 does not work
https://bugzilla.mindrot.org/show_bug.cgi?id=1804 Summary: ssh option -R 127.0.0.2:10443:<dest ip>:443 does not work Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:
2011 Jul 17
2
openSSH 5.8p2 BindPort patch
Hi, i have written a patch for openSSH 5.8p2 which allows the user to set the local source port. The patch is as follows: diff -rupN openssh-5.8p2//readconf.c openssh-5.8p2-srcport//readconf.c --- openssh-5.8p2//readconf.c 2010-11-20 04:19:38.000000000 +0000 +++ openssh-5.8p2-srcport//readconf.c 2011-07-17 20:57:52.385044096 +0100 @@ -125,7 +125,7 @@ typedef enum { oGlobalKnownHostsFile2,
2005 Jan 20
0
AllowUsers - proposal for useful variations on the theme
A short while ago, I looked at using the AllowUsers configuration option in openssh (v3.8p1 , but I believe this to be unchanged in 3.9p1) to restrict access such that only specific remote machines could access specific local accounts. I swiftly discovered that a) specifying wildcarded IP numbers to try to allow a useful IP range was pointless: if I specified AllowUsers joe at
2012 Feb 12
0
PATCH: multiple BindAddress
Hello all, I recently have a problem with multiple addresses and address families. Problem is simple, i have some hosts with IPv4 access only and some with IPv6 access. This wouldn't be big problem if I had a stable IP addresses. But sometimes I move to another network with complete different addresses. So I created patch which on option BindAddress accept list of addresses. With ip I solved
2007 Mar 13
0
[Bug 1297] No feedback when remote forward is localhost-only due to GatewayPorts
http://bugzilla.mindrot.org/show_bug.cgi?id=1297 ted at midg3t.net changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Remote forwards do not bind |No feedback when remote |to the selected address |forward is localhost-only |
2000 Oct 09
2
Remote port forwarding
I have the following line in the sshd_config file: GatewayPorts no If I launch the ssh client as this: ssh -l user host -R 9000:otherHost:25 the port forwarding is successful! :-( As you can see, the 'netstat -na' command shows the Secure Shell daemon listening to the port 9000. Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address
2009 Jul 09
0
[PATCH] Allow binding to a local port (OpenSSH 5.2)
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
2014 Jun 23
1
-h, --help option
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.
2003 Nov 16
1
[Bug 760] GatewayPorts clarification in _config man pages
http://bugzilla.mindrot.org/show_bug.cgi?id=760 Summary: GatewayPorts clarification in _config man pages Product: Portable OpenSSH Version: 3.7p1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Documentation AssignedTo: openssh-bugs at mindrot.org
2004 Apr 30
1
Code question (canohost.c)
On Fri, 30 Apr 2004, YOSHIFUJI Hideaki / [iso-2022-jp] $B5HF#1QL@(B wrote: > In article <Pine.BSO.4.44.0404292059520.953-100000 at etoh.eviladmin.org> (at Thu, 29 Apr 2004 21:00:26 -0500 (CDT)), Ben Lindstrom <mouring at etoh.eviladmin.org> says: > > > Be that true.. then one should review the usage of it in sshconnect.c > > which is the other place we do it. >
2003 Mar 05
0
"rsync --daemon" and IPv4/v6 dual stack
on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet does not get routed to AF_INET6 socket) rsync --daemon would accept IPv6 sessions only. open_socket_in() tries to deal with the situation, but it was not enough. here's the patch. (it is required on all *BSDs to accept both IPv4 and IPv6 connections with --daemon mode) itojun --- ? configure.lineno ? lib/dummy