| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Replaced by version in cli added in #894
|
|
|
|
|
|
| |
See GH #880
[ci skip]
|
| |
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
| |
For ressol this avoids very slow runtimes in situations when p
is actually a composite. This normally leads to algorithm failure
eventually but can be slow.
|
|
|
| |
(untested)
|
|
|
|
|
|
|
|
|
| |
Some attempts at reducing overhead in ECC math tests, unclear if
really changed anything for my machine but probably can't hurt.
Fix LLVM build flags
[ci skip]
|
|
|
|
|
|
|
| |
Matches how OpenSSL/BoringSSL fuzzers work which is useful because fuzzer
corpus can be cross-pollinated among implementations.
[ci skip]
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add explicit length limitations, to prevent the fuzzer from just
giving us increasingly long inputs until timeout occurs due
to non-linear algorithms.
Use LLVM fuzzer interface in all cases, and just have AFL driver
call that API when a define is set to include a main function.
OSS-Fuzz will be using the LLVM API, regardless of the fuzzing engine.
[ci skip]
|
| |
|
|
|
|
|
|
|
|
|
| |
OSS-Fuzz just gave us a gigantic input and then timed out.
In practice ressol is only called with specific primes of various
common ECC parameter sets, so limit to 768 bits max.
[ci skip]
|
|
|
|
|
|
| |
Chromium oss-fuzz bug 275
[ci skip]
|
| |
|
|
|
|
|
|
| |
Seemingly /dev/urandom not accessible in ClusterFuzz env
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the code was changed in b8966d0f89e, the offset was not changed,
so it would reject ciphertexts with exactly 8 bytes of random padding
(the required minimum).
Found by pkcs1 fuzzer which also had problems due to not having been
updated at the same time.
Add a test suite for decoding of PK decryption padding to cover the
problem cases.
|
|
|
|
|
|
| |
Makefile does all the things
[ci skip]
|
|
|
|
| |
[ci skip]
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
[ci skip]
|
|
Originally from https://github.com/randombit/botan-fuzzers but
merging to the main tree (without the corpus files, since I suspect
the corpus files in that repo are not useful anymore)
Adds --unsafe-fuzzer-mode which can be used to selectively disable
cryptographic checks which get in the way of fuzzer testing. This
setting is reflected in build.h and in the version string. Right
now it doesn't actually disable anything.
|