18 ms·
These look fun; in particular the "Attack Lab". Dockerfiles might be helpful and easy to keep updated. Alpine Linux or just busybox are probably sufficient?
by westurner 8y ago
These look fun; in particular the "Attack Lab".
Dockerfiles might be helpful and easy to keep updated. Alpine Linux or just busybox are probably sufficient?
The instructor set could extend FROM the assignment image and run a few tests with e.g. testinfra (pytest)
You can also test code written in C with gtest.
I haven't read through all of the materials: are there suggested (automated) fuzzing tools? Does OSS-Fuzz solve?
Are there references to CWE and/or the SEI CERT C Coding Standard rules?
https://wiki.sei.cmu.edu/confluence/plugins/servlet/mobile?contentId=87152044#content/view/87152044 https://wiki.sei.cmu.edu/confluence/plugins/servlet/mobile?c...
"How could we have changed our development process to catch these bugs/vulns before release?"
"If we have 100% [...] test coverage, would that mean we've prevented these vulns?"
What about 200%?
- yjftsjthsd-h 8y agoWhat on earth would 200% test coverage mean?
- sk0g 8y agoCoverage for all the code that was written, and all the code that has yet to be typed, of course. All thanks to quantum computing :)
- westurner 8y ago⟨100%| + |100%⟩ = 200%! (Even code with 100% branch coverage may have common weaknesses like those that these (great) labs have students exploit)