summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-10-03 21:13:57 +0200
committerThomas Schwinge <thomas@schwinge.name>2011-10-03 21:13:57 +0200
commit42c9a7ee626c523a5bfe489ac4e3318c0364ce28 (patch)
tree85fdadc8a8063a49ba391272aaf4309592dbccf4 /open_issues
parent392ac32ff880baa97deae8348b2e61e1e474498d (diff)
open_issues/code_analysis: Input fuzzying/RPC fuzzying.
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/code_analysis.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index 7495221b..6cb304ef 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -96,3 +96,12 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
<vsrinivas> third, Red hat has a gdb python plugin that can instrument
glibc's heap structure. its kinda handy, might help?
<vsrinivas> MALLOC_CHECK_ was the envvar you want, sorry.
+
+ * Input fuzzying
+
+ Not a new topic; has been used (and a paper published) for early UNIX
+ tools, I[[I|tschwinge]]RC.
+
+ * <http://caca.zoy.org/wiki/zzuf>
+
+ What about some [[RPC]] fuzzying?