| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The header is processed early, but when doing an amalgamation we
need to regenerate the makefile template. But we only do that
for the main makefile not the include inputs.
Should fix this but for now just just get it to work.
|
| |
| |
| |
| |
| |
| |
| | |
This removes a lot of logic that cannot be shared between the
nmake (Windows environment) and gnumake (Unix env) makefiles.
Also it cleans up inconsistencies, eg nmake's make distclean did not
remove amalgamation files, but gnumake version did.
|
|\ \ |
|
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Splits up the ar command and ar options to make this possible.
Removes support for calling `ranlib` after `ar`: testing in #1317
confirms that all platforms we support no longer need it.
See #1237. Also fixes #455
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
Allows distributor to override CFLAGS without having to worry
about what -std=c++xx options we are using. See GH #1237
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This was already caught with the policy check later but it's better
to be explicit. (And in theory an application might implement their
policy version check to be "return true", which would lead to us
actually attempting to negotiate SSLv3).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Due to an oversight in the logic, previously a client attempt to
negotiate SSLv3 would result in the server trying to negotiate
TLS v1.2. Now instead they get a protocol_error alert.
Similarly, detect the the (invalid) case of a major number <= 2,
which does not coorespond to any real TLS version. The server
would again reply as a TLS v1.2 server in that case, and now
just closes the connection with an alert.
|
| |
| |
| |
| | |
An empty extension is not allowed, but was previously accepted.
|
| |
| |
| |
| |
| |
| |
| |
| | |
In the client key exchange if the message was malformed (eg an
completely empty ECDH share) a Decoding_Error would be thrown,
then caught and a fake pre master secret generated. Move the
parsing of the message out of the try/catch block, so the correct
error is reported.
|
| |
| |
| |
| |
| | |
The previous limit of 512 bytes meant that TLS was unable to
negotiate using FFDHE-6144 or FFDHE-8192 groups.
|
| |
| |
| |
| | |
Was a copy+paste of FFDHE 3072
|
|/
|
|
| |
Avoids exposing RNG output on the wire. Cheap precaution.
|
| |
|
|\ |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
It parses just enough of an HTTP message that it can be used to
test against a browser, or tlsfuzzer.
|
|/ /
| |
| |
| |
| | |
Otherwise this ended up as an assertion failure which translated
to internal_error alert.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't send EC point format extension in server hello unless an EC
suite was negotiated *and* the client sent the extension.
Fix server FFDHE logic, this effectively disabled DHE ciphersuites
for clients without FFDHE extension.
Use unexpected_message alert in case of an unexpected message.
(Previously an internal_error alert was sent.)
|
|\ \ |
|
| | | |
|
|\ \ \ |
|
| |/ / |
|
|\ \ \
| |_|/
|/| |
| | | |
Compression_Algorithm and Decompression_Algorithm.
|
| | | |
|
| |/
| |
| |
| | |
Decompression_Algorithm.
|
| |
| |
| |
| |
| |
| | |
When finishing, bzip2 returns BZ_STREAM_END when it has produced all output.
If we end up calling the compression routine again (even with avail_in == 0),
bzip2 returns an error.
|
|/ |
|
|
|
|
|
| |
Similar to append but it only allows modfication before start_msg.
See GH #1306
|
|\ |
|
| |
| |
| |
| |
| | |
A sufficiently nested indefinite length construction would cause
stack exhaustion and a crash. Found by OSS-Fuzz - issue 4353
|
|/
|
|
| |
Just throws if --pem arg is used.
|
| |
|
|
|
|
|
|
| |
Their issuing CA seems to have some performance problems with OCSP
(https://github.com/letsencrypt/boulder/issues/1929) and it's currently
causing timeouts in the tests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixes GH #1297
This is done even on GNU make builds, since the same issue
affects MinGW
|
|
|
|
|
|
| |
Changed in #884 - we were copying the entire public key as the
public key id. Instead hash it with whatever hash we are using
to sign the certificate.
|
|
|
|
|
| |
Interleaving two blocks is 40-50% faster for any mode that supports
parallel operation.
|