| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
private key but no public counterpart; with & ok markus@
|
|
|
|
| |
patch from loic AT venez.fr, ok dtucker@
|
|
|
|
|
|
|
| |
envelope of private key files if not sidecar public key file is
present.
ok markus@
|
|
|
|
| |
ok markus@
|
|
|
|
| |
feedback and ok markus@
|
| |
|
|
|
|
| |
ok markus@
|
|
|
|
|
| |
now return SSH_ERR_KEY_BAD_PERMISSIONS in that case. Patch from
jitendra.sharma at intel.com, ok djm@
|
|
|
|
|
|
|
|
|
|
|
|
| |
enabled via "ssh-keygen -m PKCS8" on operations that save private
keys to disk.
The OpenSSH native key format remains the default, but PKCS8 is a
superior format to PEM if interoperability with non-OpenSSH software
is required, as it may use a less terrible KDF (IIRC PEM uses a single
round of MD5 as a KDF).
adapted from patch by Jakub Jelen via bz3013; ok markus
|
|
|
|
|
|
| |
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
|
|
|
|
| |
short (i.e. SSH_ERR_KEY_LENGTH). These keys will not be considered to
be "in the file". This allows key revocation lists to contain short
keys without the entire revocation list being considered invalid.
bz#2897; ok dtucker
|
| |
|
|
|
|
| |
noted by gerhard@; ok dtucker@, djm@
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
remaining bit that it still used into ssh-rsa.c; ok markus
|
|
|
|
|
|
| |
are handled safely, and there also is no need for preallocation dances.
Future changes in this area will be less error prone.
Review and one bug found by markus
|
|
|
|
|
| |
open()/close() on keyfile, prevent leak of 'pub' if 'keyp' is NULL,
replace strlcpy+cat with asprintf; ok djm@
|
|
|
|
| |
ok markus@
|
| |
|
|
|
|
|
|
|
|
|
| |
keys. This avoids implicit realloc inside the buffer code, which
might theoretically leave fragments of the key on the heap. This
doesn't appear to happen in practice for normal sized keys, but
was observed for novelty oversize ones.
Pointed out by Jann Horn of Project Zero; ok markus@
|
|
|
|
| |
key pointer arguments; ok markus@
|
|
|
|
| |
ok djm@
|
|
|
|
| |
ok djm@
|
|
|
|
| |
ok dtucker@
|
|
|
|
|
|
|
| |
- Remove unused function argument.
- Remove two unnecessary variables.
OK djm@
|
| |
|
| |
|
|
|
|
| |
this wording change was made a while ago but got accidentally reverted
|
| |
|
|
|
|
| |
from around call
|
| |
|
|
|
|
| |
ok djm markus
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interfaces. Refactor the generic key loading API to not require
pathnames to be specified (they weren't really used).
Fixes a few other things en passant:
Makes ed25519 keys work for hostbased authentication (ssh-keysign
previously used the PEM-only routines).
Fixes key comment regression bz#2306: key pathnames were being lost as
comment fields.
ok markus@
|
|
|
|
| |
Allow textfile or KRL-based revocation of hostkeys.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
reduces algorithms to curve25519, aes-ctr, chacha, ed25519;
allows us to explore further options; with and ok djm
|
|
|
|
|
| |
callers that futzing with it will futz with the actual buffer
contents
|
| |
|
| |
|
|
|
|
| |
ok djm dtucker
|
| |
|
|
|
|
|
| |
ed25519 reference code from SUPERCOP, see http://ed25519.cr.yp.to/software.html
feedback, help & ok djm@
|
|
|
|
| |
feedback and lots help from djm; ok djm@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that combines Daniel Bernstein's ChaCha20 stream cipher and Poly1305 MAC
to build an authenticated encryption mode.
Inspired by and similar to Adam Langley's proposal for TLS:
http://tools.ietf.org/html/draft-agl-tls-chacha20poly1305-03
but differs in layout used for the MAC calculation and the use of a
second ChaCha20 instance to separately encrypt packet lengths.
Details are in the PROTOCOL.chacha20poly1305 file.
Feedback markus@, naddy@; manpage bits Loganden Velvindron @ AfriNIC
ok markus@ naddy@
|
| |
|
|
|
|
|
| |
algorithms to ssh. Includes some refactoring of KEX and key type handling
to be table-driven; ok markus@
|
|
|
|
| |
ok and feedback djm@
|
|
|
|
|
|
|
| |
that change the packet format and compute the MAC over the encrypted
message (including the packet size) instead of the plaintext data;
these EtM modes are considered more secure and used by default.
feedback and ok djm@
|
| |
|
|
|
|
| |
fixes ssh-add for passphrase-protected ssh1-keys; noted by naddy@; ok djm@
|