| Commit message (Collapse) | Author | Files | Lines |
|
joel's line of thinking about it
|
|
sigalg for MD5_SHA1 and using it as the non sigalgs default
ok jsing@
|
|
for a timing vullnerability in ECDSA signature generation (CVE-2018-0735).
Note that the blinding that we introduced back in June for ECDSA and DSA
should mitigate this and related issues. This simply adds an additional
layer of protection.
discussed with jsing
|
|
instead of 'uint16_t'
Found with llvm's static analyzer, noticed that it was also already reported in
Coverity CID 155890 and to ensure this was correct also inspected OpenSSL's
equivalent code.
OK tb@ and jsing@
|
|
From Edgar Pettijohn III
|
|
Makes connections to outlook.office365.com work
|
|
|
|
|
|
Spotted by maestre@, ok tb@
|
|
ok tb@
|
|
ok bcook
|
|
hex_encode() function and use byte arrays instead of strings to store
the expected values. Snatch and tweak hexdump() from beck's key_schedule
test to pretty-print data in case of failure.
|
|
Include check for appropriate RSA key size when used with PSS.
ok tb@
|
|
ok beck@
|
|
ok beck@
|
|
the server child could be delayed. In this case wait a second and
check again.
|
|
|
|
|
|
ok beck inoguchi
|
|
ok beck inoguchi
|
|
|
|
Used by unbound's DNS over TLS implementation to do server name
verification.
ok jsing
|
|
tweaks from jsing and myself. The SM2/SM3/SM4 algorithms are mandatory
for legal use of cryptography within China and [are] widely applied in
the country, covering identification/financial cards, contactless,
TPM 2.0 and PKI.
ok beck inoguchi jsing
|
|
|
|
This implements automatic thread support initialization in libcrypto.
This does not remove any functions from the ABI, but does turn them into
no-ops. Stub implementations of pthread_mutex_(init|lock|unlock) are
provided for ramdisks.
This does not implement the new OpenSSL 1.1 thread API internally,
keeping the original CRYTPO_lock / CRYPTO_add_lock functions for library
locking. For -portable, crypto_lock.c can be reimplemented with
OS-specific primitives as needed.
ok beck@, tb@, looks sane guenther@
|
|
Regression found by Perl module p5-IO-Socket-SSL tests.
with beck@ tb@
|
|
|
|
lightly tested, but will need sanity checks and regress test changes
before being added to any sigalgs list for real
ok jsing@ tb@
|
|
to allow for adding PSS, Nuke the now unneejded guard around the PSS
algorithms in the sigalgs table
ok jsing@ tb@
|
|
directory. Keep all log files for easier debugging. Name regress
target names consistently.
|
|
ok jsing@
|
|
|
|
all combinations of LibreSSL, OpenSSL 1.0.2, and OpenSSL 1.1. It
is currently disabled for TLS 1.3 as this needs more setup.
|
|
- Provide a tls13_handshake_active_action() function to reduce code
duplication and replace tls13_handshake_get_sender().
- Add an INVALID message_type, so we can explicitly detect invalid
conditions.
- Implement skeletons for the tls13_handshake_send_action() and
tls13_handshake_recv_action() functions.
- OR in the NEGOTIATED value at the end of recving or sending a server
hello so that we switch to the next chain in the state table.
ok tb@
|
|
|
|
From Ben L <bobsayshilol at live dot co dot uk>.
|
|
|
|
|
|
|
|
Reported by Ben L <bobsayshilol at live dot co dot uk>
|
|
just keep the sigalg around so we can remember what we actually
decided to use.
ok jsing@
|
|
|
|
ok jsing
|
|
ok jsing@
|
|
|
|
When the RFC refers to ("") for key derivation, it is referring to the
transcript hash of an empty string, not an empty string. Rename
tls13_secrets_new() to tls13_secrets_create(), make it take an EVP_MD *
and calculate the hash of an empty string so that we have it available
for the "derived" and other steps. Merge tls13_secrets_init() into
the same function, remove the EVP_MD * from other functions and use the
empty string hash at the appropriate places.
ok beck@ tb@
|
|
and "write". Use self-documenting C99 initializers.
ok bcook, jsing
|
|
While there, eliminate a flag that was only used once.
ok beck jsing mestre
|
|
ok beck jsing mestre
|
|
LibreSSL as crypto provider. When we run their regression tests,
we are actually testing our library. This is far from perfect. A
lot of LibreSSL features have not been implemented as Botan provider.
Even if provider openssl is specified, botan-test runs a lot of
non-openssl tests. This can be improved later.
|