| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
from Patrick dot Steuer at de dot ibm dot com
via OpenSSL commit 338ead0f Oct 9 12:16:34 2017 +0200.
Correct the EVP_EncryptUpdate(3) and EVP_DecryptUpdate(3) prototypes;
from FdaSilvaYY at gmail dot com
via OpenSSL commit 7bbb0050 Nov 22 22:00:29 2017 +0100.
Document the additional public function EVP_CIPHER_CTX_rand_key(3);
from Patrick dot Steuer at de dot ibm dot com
via OpenSSL commit 5c5eb286 Dec 5 00:36:43 2017 +0100.
|
|
|
|
|
| |
Mostly from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800,
tweaked by me for conciseness and accuracy.
|
|
|
|
|
|
|
|
| |
via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800,
but fixing two bugs in his description.
This commit also includes a few minor improvements to the description
of DES_fcrypt(3), also from OpenSSL, tweaked by me.
|
|
|
|
|
|
|
|
| |
These functions constitute an obvious portability nightmare,
but that's no excuse for incorrect documentation.
Pointed out by Nicolas Schodet
via OpenSSL commit b713c4ff Jan 22 14:41:09 2018 -0500.
|
|
|
|
|
| |
from Hubert Kario <hkario at redhat dot com>
via OpenSSL commit 681acb31 Sep 29 13:10:34 2017 +0200.
|
|
|
|
|
|
|
|
| |
from Rich Salz via OpenSSL commit 8162f6f5 Jun 9 17:02:59 2016 -0400.
Merging the RETURN VALUES section really wouldn't make much sense
here, it contains no additional information and i don't see any way
to reorganize the content and make it better.
|
|
|
|
|
|
|
|
|
|
| |
Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
by Paul Yang, but reworded for intelligibility and precision.
While here, also expand the description of the "ret" argument of
BIO_callback_fn(). That's a fairly complicated and alarmingly
powerful concept, but the description was so brief that is was
barely comprehensible.
|
|
|
|
|
| |
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
with tweaks by me.
|
|
|
|
| |
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
|
|
|
|
|
| |
From Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
with one tweak.
|
|
|
|
|
|
|
|
|
|
| |
accordingly. Make some statements more precise, and point out
some dangerous traps in these ill-designed interfaces.
Also do some minor polishing while here.
Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
by Paul Yang, but not using most of his wording because that is in
part redundant, in part incomplete, and in part outright wrong.
|
|
|
|
|
|
| |
as requested by jsing@, and also document six more related functions
that have already been public before that.
OpenSSL fails to document any of these.
|
| |
|
|
|
|
|
| |
that jsing@ recently exposed publicly in libcrypto.
Requested by jsing@.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The keypair pubkey hash was being generated and set in the keypair when the
TLS context was being configured. This code should not be messing around
with the keypair contents, since it is part of the config (and not the
context).
Instead, generate the pubkey hash and store it in the keypair when the
certificate is configured. This means that we are guaranteed to have the
pubkey hash and as a side benefit, we identify bad certificate content
when it is provided, instead of during the context configuration.
ok beck@
|
| |
|
|
|
|
| |
functions require the conninfo passed in to be non-NULL.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A libtls client can specify a session file descriptor (a regular file
with appropriate ownership and permissions) and libtls will manage reading
and writing of session data across TLS handshakes.
Discussed at length with deraadt@ and tedu@.
Rides previous minor bump.
ok beck@
|
| |
|
|
|
|
| |
API and are now in use by various libraries and applications.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The RI logic gets pulled up into ssl3_get_server_hello() and
ssl_parse_serverhello_tlsext() gets replaced by tlsext_client_parse(),
which allows a CBS to be passed all the way down.
This also deduplicates the tlsext_client_build() and tlsext_server_build()
code.
ok beck@
|
|
|
|
| |
ok beck@ inoguchi@
|
| |
|
|
|
|
|
| |
rolling its own certificate loading. This also means we get better error
reporting on failure.
|
| |
|
|
|
|
| |
fatal.
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by and fix from Nate Bessette <openbsd at nate dot sh> - thanks.
|
| |
|
|
|
|
|
|
| |
in multiple locations.
ok beck@
|
| |
|
|
|
|
| |
the intent is more obvious.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
passed to BIO_get_accept_socket(). This is part of the API and it
fixes "openssl ocsp -port 12345" in server mode.
from markus@; OK jsing@ beck@
|
|
|
|
| |
OK jsing@
|
|
|
|
|
|
| |
SSL_free will do this a second time.
ok jsing
|
|
|
|
|
|
|
|
|
|
| |
make OPENSSL=/usr/src/usr.bin/openssl/obj/openssl
actually does the expected thing instead of running a mixture of both the
openssl below /usr/obj and the one below /usr/bin. Found the hard way via
backtraces that made no sense whatsoever.
ok jsing
|
| |
|
|
|
|
| |
No change to generated assembly.
|