From 7d74595f6fc9beb5886ff853d1391dbc685ed2cb Mon Sep 17 00:00:00 2001 From: Sam Hocevar Date: Sun, 7 Jan 2007 12:39:30 +0000 Subject: [PATCH] * Added a note about statically linked binaries and one about getc(). --- doc/zzuf.1 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/zzuf.1 b/doc/zzuf.1 index 6b2b11c..8ab9f05 100644 --- a/doc/zzuf.1 +++ b/doc/zzuf.1 @@ -232,6 +232,10 @@ processes, it will fail in the presence of any mechanism that disables preloading. For instance setuid root binaries will not be fuzzed when run as an unprivileged user. .PP +For the same reasons, \fBzzuf\fR will also not work with statically linked +binaries. Bear this in mind when using \fBzzuf\fR on the OpenBSD platform, +where \fBcat\fR, \fBcp\fR and \fBdd\fR are static binaries. +.PP Though best efforts are made, identical behaviour for different versions of \fBzzuf\fR is not guaranteed. The reproducibility for subsequent calls on different operating systems and with different target programs is only @@ -242,6 +246,10 @@ It is not yet possible to insert or drop bytes from the input, to fuzz according to the file format, to swap bytes, etc. More advanced fuzzing methods are planned. .PP +\fBZzuf\fR will not work properly with applications using \fBgetc\fR() on +platforms where it is defined as a macro, such as OpenBSD and FreeBSD, +because it is unable to intercept calls to \fBgetc\fR(). +.PP As of now, \fBzzuf\fR does not really support multithreaded applications. The behaviour with multithreaded applications where more than one thread does file descriptor operations is undefined.