| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
| |
optionally record successful auth methods and public credentials
used in a file accessible to user sessions
feedback and ok markus@
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
in packet log messages, e.g.
Connection closed by invalid user foo 10.1.1.1 port 44056 [preauth]
ok markus@ bz#113
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
early in the protocol probably seemed reasonable in the 1990s, but
today it's clearly a bad idea in terms of both cryptography (cf.
multiple compression oracle attacks in TLS) and attack surface.
Moreover, to support it across privilege-separation zlib needed
the assistance of a complex shared-memory manager that made the
required attack surface considerably larger.
Prompted by Guido Vranken pointing out a compiler-elided security
check in the shared memory manager found by Stack
(http://css.csail.mit.edu/stack/); ok deraadt@ markus@
NB. pre-auth authentication has been disabled by default in sshd
for >10 years.
|
|
|
|
| |
for testing; ok markus@
|
|
|
|
|
|
| |
respective authentication methods are enabled in the configuration.
prompted by Solar Designer; ok markus dtucker
|
|
|
|
| |
login sessions; ok deraadt markus dtucker
|
| |
|
|
|
|
| |
behaviour on strict compilers; reported by Jakub Jelen bz#2581
|
|
|
|
|
|
|
|
|
|
|
| |
draft-ietf-curdle-ssh-kex-sha2-03
diffie-hellman-group14-sha256 (2K group)
diffie-hellman-group16-sha512 (4K group)
diffie-hellman-group18-sha512 (8K group)
based on patch from Mark D. Baushke and Darren Tucker
ok markus@
|
|
|
|
|
|
| |
sshbuf_dup_string() to replace a common idiom of
strdup(sshbuf_ptr()) with better safety checking;
feedback and ok markus@
|
|
|
|
|
|
|
| |
places that use them (authn and session code). After this, no state is
cached in canohost.c
feedback and ok markus@
|
| |
|
| |
|
|
|
|
|
| |
based on draft-rsa-dsa-sha2-256-03.txt and draft-ssh-ext-info-04.txt;
with & ok djm@
|
|
|
|
| |
ok djm@
|
|
|
|
| |
in test for multiple authentication with the same key
|
|
|
|
|
|
| |
codes being returned due to != having higher precedence than =.
ok deraadt@ markus@
|
|
|
|
| |
Discussed with tedu, millert, otto.... and ok djm
|
|
|
|
|
| |
this may have caused the monitor to refuse multiple authentications
that would otherwise have successfully completed; ok markus@
|
|
|
|
|
|
|
|
|
|
| |
we only ever use it for strlen(pattern).
Prompted by hanno AT hboeck.de pointing an out-of-bound read
error caused by an incorrect pattern length found using AFL
and his own tools.
ok markus@
|
|
|
|
|
| |
a corresponding private key authentication being applied to other
authentication methods. Reported by halex@, ok markus@
|
| |
|
|
|
|
| |
bz#278 reported by drk AT sgi.com; ok dtucker
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I accidentally changed the format of the hostkeys@openssh.com messages
last week without changing the extension name, and this has been causing
connection failures for people who are running -current. First reported
by sthen@
s/hostkeys@openssh.com/hostkeys-00@openssh.com/
Change the name of the proof message too, and reorder it a little.
Also, UpdateHostKeys=ask is incompatible with ControlPersist (no TTY
available to read the response) so disable UpdateHostKeys if it is in
ask mode and ControlPersist is active (and document this)
|
|
|
|
|
|
|
|
|
|
| |
The client will not ask the server to prove ownership of the private
halves of any hitherto-unseen hostkeys it offers to the client.
Allow UpdateHostKeys option to take an 'ask' argument to let the
user manually review keys offered.
ok markus@
|
| |
|
|
|
|
| |
obsolete SIZE_T_MAX. OK miod@ beck@
|
|
|
|
| |
ok djm markus
|
| |
|
|
|
|
|
|
|
|
| |
a) switch packet.c to buffer api and isolate per-connection info into struct ssh
b) (de)serialization of the state is moved from monitor to packet.c
c) the old packet.c API is implemented in opacket.[ch]
d) compress.c/h is removed and integrated into packet.c
with and ok djm@
|
|
|
|
| |
ok markus@
|
|
|
|
|
| |
options to allow sshd to control what public key types will be
accepted. Currently defaults to all. Feedback & ok markus@
|
|
|
|
|
|
|
|
|
| |
refuse to accept previously-used keys.
This allows AuthenticationMethods=publickey,publickey to require
that users authenticate using two _different_ pubkeys.
ok markus@
|
|
|
|
|
|
|
|
| |
may be forwarded to a local Unix domain socket and vice versa or
both ends may be a Unix domain socket. This is a reimplementation
of the streamlocal patches by William Ahern from:
http://www.25thandclement.com/~william/projects/streamlocal.html
OK djm@ markus@
|
|
|
|
|
|
|
|
|
| |
existing API is offered as a set of wrappers.
with and ok markus@
Thanks also to Ben Hawkes, David Tomaschik, Ivan Fratric, Matthew
Dempsky and Ron Bowes for a detailed review a few months ago.
|
|
|
|
|
|
| |
post-auth child. the new buffer code is more strict, and requires
buffer_init() while the old code was happy after a bzero();
originally from djm@
|
|
|
|
|
| |
reduces algorithms to curve25519, aes-ctr, chacha, ed25519;
allows us to explore further options; with and ok djm
|
| |
|
|
|
|
| |
ok djm dtucker
|
| |
|
| |
|
|
|
|
|
| |
or hostkeys on smartcards; most of the work by Zev Weiss; bz #1974
ok djm@
|
|
|
|
| |
the auth success/failure line; bz#2064, ok dtucker@
|
|
|
|
|
|
|
|
|
|
| |
and ruser is now logged in the auth success/failure message alongside
the local username, remote host/port and protocol in use. Certificates
contents and CA are logged too.
Pushing all logging onto a single line simplifies log analysis as it is
no longer necessary to relate information scattered across multiple log
entries. "I like it" markus@
|