| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
available currently. In the client this is via %i, in the server %U
(since %i was already used in the client in some places for this, but
used for something different in the server);
bz#2870, ok dtucker@
|
| |
|
|
| |
bz2831, feedback and ok dtucker@
|
| | |
|
| |
|
|
| |
with codespell tool (https://github.com/lucasdemarchi/codespell)
|
| |
|
|
|
|
|
| |
The code is not compiled in by default (see WITH_XMSS in Makefile.inc)
Joint work with stefan-lukas_gazdag at genua.eu
See https://tools.ietf.org/html/draft-irtf-cfrg-xmss-hash-based-signatures-12
ok djm@
|
| |
|
|
|
|
|
|
|
|
|
| |
to ssh(1) that directs it to bind its outgoing connection to the
address of the specified network interface.
BindInterface prefers to use addresses that aren't loopback or link-
local, but will fall back to those if no other addresses of the
required family are available on that interface.
Based on patch by Mike Manning in bz#2820, ok dtucker@
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The signal handlers from the original ssh1 code on which OpenSSH
is based assume unreliable signals and reinstall their handlers.
Since OpenBSD (and pretty much every current system) has reliable
signals this is not needed. In the unlikely even that -portable
is still being used on such systems we will deal with it in the
compat layer. ok deraadt@
|
| |
|
|
|
|
|
|
|
|
| |
ssh.com <=2.* and OpenSSH <= 3.*.
These versions were all released in or before 2001 and predate the
final SSH RFCs. The hacks in question aren't necessary for RFC-
compliant SSH implementations.
ok markus@
|
| |
|
|
|
|
| |
instead canonicalise them through getnameinfo/getaddrinfo to remove
ambiguities (e.g. ::0001 => ::1) before they are matched against
known_hosts; bz#2763, ok dtucker@
|
| |
|
|
| |
and reported by Alf Schlichting
|
| | |
|
| |
|
|
|
| |
/dev/null to fd 1. This allows propagation of remote stdout close to
the local side; reported by David Newall, ok markus@
|
| |
|
|
|
|
|
|
|
|
|
| |
At the client, the device may be obtained from a new %T expansion
for LocalCommand.
At the server, the allocated devices will be listed in a
SSH_TUNNEL variable exposed to the environment of any user sessions
started after the tunnel forwarding was established.
ok markus
|
| |
|
|
|
|
|
| |
or sftp://user@host/path. The connection parameters described in
draft-ietf-secsh-scp-sftp-ssh-uri-04 are not implemented since the
ssh fingerprint format in the draft uses md5 with no way to specify
the hash function type. OK djm@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(-D) with remote forwarding (-R) where the remote-forwarded port
expects SOCKS-requests.
The SSH server code is unchanged and the parsing happens at the SSH
clients side. Thus the full SOCKS-request is sent over the forwarded
channel and the client parses c->output. Parsing happens in
channel_before_prepare_select(), _before_ the select bitmask is
computed in the pre[] handlers, but after network input processing
in the post[] handlers.
help and ok djm@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move static state to a "struct ssh_channels" that is allocated at
runtime and tracked as a member of struct ssh.
Explicitly pass "struct ssh" to all channels functions.
Replace use of the legacy packet APIs in channels.c.
Rework sshd_config PermitOpen handling: previously the configuration
parser would call directly into the channels layer. After the refactor
this is not possible, as the channels structures are allocated at
connection time and aren't available when the configuration is parsed.
The server config parser now tracks PermitOpen itself and explicitly
configures the channels code later.
ok markus@
|
| |
|
|
|
|
|
|
| |
completely; previous behaviour would not prevent further options
appearing after the hostname (ssh has a supported options after the
hostname for >20 years, so that's too late to change).
ok deraadt@
|
| |
|
|
|
|
|
| |
file instead of giving it on the client's command line. This command
will be executed on the remote host. The feature allows to automate
tasks using ssh config.
OK markus@
|
| | |
|
| | |
|
| |
|
|
| |
ok markus@
|
| |
|
|
| |
ok markus@
|
| | |
|
| |
|
|
| |
ok markus@
|
| |
|
|
| |
ok markus@
|
| |
|
|
| |
ok markus@
|
| |
|
|
| |
sshd(8). bz#2705, patch from erahn at arista.com, ok djm@
|
| |
|
|
|
| |
excluding SHA2 RSA signature methods. bz#2680, patch from Nuno
Goncalves; ok dtucker@
|
| |
|
|
|
| |
characters can confuse some shells (e.g. zsh).
Reported by Lauri Tirkkonen via bugs@
|
| |
|
|
| |
literal IPv6 addresses. From Dick Visser; ok dtucker@
|
| |
|
|
|
|
|
| |
corresponding bare public key. E.g. just a private id_rsa and certificate
id_rsa-cert.pub (and no id_rsa.pub).
bz#2617 ok dtucker@
|
| |
|
|
|
|
|
|
|
| |
- mux client speaks the ssh-packet protocol directly over unix-domain socket.
- mux server acts as a proxy, translates channel IDs and relays to the server.
- no filedescriptor passing necessary.
- combined with unix-domain forwarding it's even possible to run mux client
and server on different machines.
feedback & ok djm@
|
| |
|
|
|
| |
Reported by mb AT smartftp.com in bz#2547 and (independantly)
Ron Frederick; ok markus@
|
| |
|
|
|
|
| |
safe fmprintf printer; bz#2058
feedback schwarze@ ok dtucker@
|
| |
|
|
|
|
|
| |
- formatting fixes
- update usage()
ok djm
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
command-line flag to allow simplified indirection through a
SSH bastion or "jump host".
These options construct a proxy command that connects to the
specified jump host(s) (more than one may be specified) and uses
port-forwarding to establish a connection to the next destination.
This codifies the safest way of indirecting connections through SSH
servers and makes it easy to use.
ok markus@
|
| |
|
|
| |
using ssh -W (but still default to yes in that case). bz#2577, ok djm@.
|
| |
|
|
| |
This will make future changes a bit easier. ok djm@
|
| | |
|
| | |
|
| |
|
|
|
| |
debug mode or when logging to a file or syslog.
bz#1988 ok dtucker
|
| |
|
|
|
|
|
| |
places that use them (authn and session code). After this, no state is
cached in canohost.c
feedback and ok markus@
|
| |
|
|
| |
deraadt@, something similar has been in the snaps for a while.
|
| | |
|
| |
|
|
|
|
| |
disabled/gutted for years already, but this aspect was surprisingly
forgotten.
Thanks for report from Qualys
|
| |
|
|
|
| |
forwarding when the X server disables the SECURITY extension;
Reported by Thomas Hoger; ok deraadt@
|
| |
|
|
| |
support. From Iain Morgan bz#2505
|
| |
|
|
| |
ok dtucker@
|
| |
|
|
|
| |
ssh_connect_direct() to print an uninitialised stack variable;
bz#2500 reported by dvw AT phas.ubc.ca
|