-
## Description
nightly build to verify code that cannot do on every merge
- fuzz test
- release candidate
-
Subscribe to this issue and stay notified about new [weekly trending repos in Haskell](https://github.com/trending/haskell?since=weekly).
-
We need to clarify the scope of the Core Fellowship so that new members can know in what area of work are considered in scope.
While we have manifesto as the source of truth, but it still leaves ma…
-
Excuse me. I just tried to add GPU support to the container so that I could test my Neural Network-based fuzzer. I have managed to add GPU support in generated.mk and run_experiment.py, and the test o…
-
### Describe the bug
I performed a successful manual SQLi attack (using the Manual Explore feature). During this manual exploration, the History tab exhibits the following information regarding coo…
-
**Describe the bug**
The test fails locally ~every time.
```
test peer_manager::tests::fuzzers::random_handshake_connect_fuzzer has been running for over 60 seconds
--- STDERR: …
-
Hi!
I have played around with the fuzzers and have several variations and new fuzzers on my private repo. I wanted to file an issue here to have a discussion if and how to upstream this. I also have …
-
Hi, in order to evaluate my approach i am, in addition to open62541, testing live555 and lightftp.
For live555 i extracted some messages and added them to the corpus.
However, one of my initial inpu…
-
[Honggfuzz](http://honggfuzz.com/) looks to be a great competitor to libFuzzer and AFL.
Also, the instrumentalization procedure seems to be very similar to libFuzzer so it might be quite easy to ad…
-
> Some notes about the fuzzing outcome: As you see in the code, I randomly generate calls that may or may not be valid and bombard the pallet with these calls, and every so often I execute the entire …