Explore >> Select a destination
|
You are here 
|
words.filippo.io | ||
| | | | |
hypothesis.works
|
|
| | | | | The Encode/Decode invariant One of the simplest types of invariant to find once you move past just fuzzing your code is asserting that two different operations should produce the same result, and one of the simplest instances of that is looking for encode/decode pairs. That is, you have some function that takes a value and encodes it as another value, and another that is supposed to reverse the process. This is ripe for testing with Hypothesis because it has a natural completely defined specification: Encoding and then decoding should be exactly the same as doing nothing. Lets look at a concrete example. Test faster, fix more | |
| | | | |
thomastrapp.com
|
|
| | | | | How to use libseccomp to reduce the attack surface within an application written in C++, providing a whitelist of permitted system calls to the seccomp interface of the Linux kernel. | |
| | | | |
guidovranken.com
|
|
| | | | | Larry Stefonic of wolfSSL contacted me after he'd noticed my project for fuzzing cryptographic libraries called Cryptofuzz. We agreed that I would write a Cryptofuzz module for wolfSSL. I activated the wolfSSL module for Cryptofuzz on Google's OSS-Fuzz, where it has been running 24/7 since. So far, Cryptofuzz has found a total of 8 bugs... | |
| | | | |
sergioprado.blog
|
|
| | | This article is going to be an introduction to embedded Linux security. | ||
