Displaying 20 results from an estimated 500 matches similar to: "[Patch] SSH through HTTP proxy using CONNECT"
2004 Aug 26
2
OpenSSH PATCH: OpenCommand and CloseCommand
Hi,
the attached patch adds support for the keywords "OpenCommand" and
"CloseCommand" to ssh_config. They are commands which are executed before
the connection is established (or ProxyCommand started) and after the
connection has been closed (or ProxyCommand ended).
this is usefull for stuff like portknocking or (that's what I wrote the
patch for) talking with trapdoor2
2010 Jan 14
1
ssh(1) multiplexing rewrite
Hi,
At the n2k10 OpenBSD network hackathon, I finally got some time to clean
up and rewrite the ssh(1) client multiplexing code. The attached diffs
(one for portable OpenSSH, one for OpenBSD) are the result, and they
need some testing.
The revised multiplexing code uses a better protocol between the master
and slave processes and I even bothered to write it up :) It tracks the
control sockets
2005 Jun 12
2
%h,%p,%u expansion for ControlPath
This allows me to set 'ControlPath ~/.ssh/sockets/%h.%p.%u' for example.
Have I missed a good reason why ssh_connect finds the default port
number for itself instead of just having it in options.port (like we do
for the the default in options.user)?
--- openssh-4.1p1/ssh.c~ 2005-06-12 09:47:18.000000000 +0100
+++ openssh-4.1p1/ssh.c 2005-06-12 09:40:53.000000000 +0100
@@ -604,6 +604,17
2010 Nov 28
2
[PATCH] Use canonical hostname for DNS SSHFP lookup
In the current implementation, ssh always uses the hostname supplied by
the user directly for the SSHFP DNS record lookup. This causes problems
when using the domain search path, e.g. I have "search example.com" in my
resolv.conf and then do a "ssh host", I will connect to host.example.com,
but ssh will query the DNS for an SSHFP record of "host.", not
2014 Jan 15
0
remote port forward failed because of failure resolving localhost to IP with error No such file or directory
Hi all,
I'm using openssh 5.9p1 with the remote port forwarding "ssh -R
20000:localhost:22 xxx at x.x.x.x". The tunnel is set up. But when I write
data to the tunnel, the ssh client failed to forward the data to the
localhost. The debug is below:
debug1: client_input_channel_open: ctype forwarded-tcpip rchan 2 win
131072 max 32768
debug1: client_request_forwarded_tcpip: listen
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
2001 Dec 05
1
DISPLAY=localhost
hi,
this can be applied to the latest portable CVS. by default bind sshd fake
display to localhost.
[stevesk at jenny stevesk]$ uname -sr
HP-UX B.11.11
[stevesk at jenny stevesk]$ echo $DISPLAY
localhost:14.0
[stevesk at jenny stevesk]$ netstat -an|grep 6014
tcp 0 0 127.0.0.1.6014 *.* LISTEN
this is currently controlled with sshd_config gatewayports;
2002 Feb 15
3
ssh can't resolve hostnames thru WINS
[Please CC me, I'm not on the list]
My box is on a mostly Windows-populated network.
Naturally, I set up Samba and added WINS as a name resolution option.
I found out that some programs now can use NetBIOS names, other can't.
openssh falls into latter category :-(
I found that openssh use this snippet to convert hostname to ip:
if((gaierr = getaddrinfo(host, strport, &hints,
2002 May 22
0
[PATCH] connect() timeout
Here are the new versions of this widely used patch for OpenSSH 3.2.2p1
and 3.2.3p1.
The patch avoids waiting to long when using ssh() or scp() on a down host,
it is usefull when you have to update many hosts via rsync or rdist themselves
relying upon ssh(). It enables a new option 'ConnectTimeout' to control
exactly the timeout value, so that it can be used even on slow links.
These
2012 Oct 22
1
[PATCH] Implement remote dynamic TCP forwarding
Hi all,
This is a client side only implementation of reversed dynamic (SOCKS) TCP
forwarding, which means it is compatible with any existing servers
have 'remote forward' capability.
To establish such forward, use "ssh -R [BIND_ADDRESS:]PORT ...".
The server will listen on that port and address and accept SOCKS
traffics.
Hope this will be useful for you.
There was an
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
2013 Apr 17
1
[Bug 1039] Incomplete application of HostKeyAlias in ssh
https://bugzilla.mindrot.org/show_bug.cgi?id=1039
Iain Morgan <imorgan at nas.nasa.gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |imorgan at nas.nasa.gov
--- Comment #13 from Iain Morgan <imorgan at nas.nasa.gov> ---
My apologies for
2012 Nov 24
0
ssh-keyscan continuity patch --
I apologize, this patch should have been sent awhile ago. Between a lot
of things that needed to be completed at work as a sysadmin for the
Research Computing group at Purdue University and retiring from work
after 38 years at the end of May (2012), I basically ignored it. This
patch is from a clone of my workstation that I just activated at home.
The patch was primarily written to fix the
2018 Feb 23
6
RFC 8305 Happy Eyeballs in OpenSSH
Hello,
I use hosts that are dual stack configured (IPv4 and IPv6) and it
happens that connectivity through one or the other is broken and
timeouts. In these case connection to the SSH server can take quite some
time as ssh waits for the first address to timeout before trying the
next.
So I gave a stab at implementing RFC 8305. This patch implements part of
it in sshconnect.c.
* It does not do
2001 Nov 17
0
[PATCH] Connect timeout
The attached patch adds a new 'ConnectTimeout' option (man page updated
in patch) to avoid wasting time when the target host is down. I needed that
because I was using rsync/rdist over ssh for massive files update and the
default connect() took too long for my purpose.
The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX
on Linux, Solaris and HP-UX without
2002 Apr 03
1
[PATCH] connect() timeout
Here is a version of this widely used patch specific for OpenSSH 3.1p1,
as it is still not in the main tree (perhap one day...)
The patch avoids spending too much time when doing an ssh()/scp() on a
down host, as it does not depend off the default TCP timeout used
by connect().
Patch was tested on Linux, Solaris and HP-UX.
The patch can also be found on:
2001 Jul 27
0
Updated ssh-keyscan patch for ssh2 support
In the past 2 months another change occurred in the CVS code that
broke my ssh-keyscan patch. Here's an updated version that tweaks the
changed name (in the Kex struct) and also causes an attempt to grab an
ssh2 key from an older server (without ssh2 support) to fail earlier
and without an error message (Stuart Pearlman emailed me some code for
this).
This patch is based on the BSD CVS
2018 Jan 15
0
doveadm mailbox command fails if backend has an IPv6 address
Hi,
some of my maintenance scripts weren't working as expected and I finally
found that this only happens if the user was mapped to a backend server
reachable via IPv6:
On a director:
doveadm mailbox status -u username messages Junk
returns
Junk messages=203 (if backend is connected via IPv4)
or
Lookup of host ipv6addr:542 failed: ... (if backend is connected via IPv6)
2002 Jun 11
4
ssh setuid changes.
Ok, I'm doing a heads up here.
I just applied:
- markus at cvs.openbsd.org 2002/06/11 04:14:26
[ssh.c sshconnect.c sshconnect.h]
no longer use uidswap.[ch] from the ssh client
run less code with euid==0 if ssh is installed setuid root
just switch the euid, don't switch the complete set of groups
(this is only needed by sshd). ok provos@
A few comments about
2013 Jun 20
1
ProxyCommand that returns a socket
Hello,
My usage of ProxyCommand just calls the nc utility with various
parameters. That in turn after the initial setup just copies copies
the data from the network socket to stdin/stdout. This useless coping
can be avoided if ssh has an option to receive the socket from the
proxy command. I suppose it can improve network error reporting as ssh
would talk directly to the network socket rather