Changeset 1607 for zzufTweet

Timestamp:

Jan 7, 2007, 4:55:24 PM (14 years ago)

Author:

Sam Hocevar

Message:

• Updated manpage, fixed - to \- here and there.

File:

• zzuf/trunk/doc/zzuf.1 (modified) (9 diffs)

zzuf/trunk/doc/zzuf.1

@@ -73 +73 @@
 of the regular expressions will be ignored.
 .TP
-\fB\-F\fR, \fB\-\-max-forks\fR=\fIforks\fR
+\fB\-F\fR, \fB\-\-max\-forks\fR=\fIforks\fR
 Specify the number of simultaneous children that can be run.
 
@@ -120 +120 @@
 .RE
 .IP
-You can use \(oq\fB-\fR\(cq to specify ranges. For instance, to protect all
-bytes from \(oq\\001\(cq to \(oq/\(cq, use \(oq\fB\-P\ \(dq\\001-/\(dq\fR\(cq.
+You can use \(oq\fB\-\fR\(cq to specify ranges. For instance, to protect all
+bytes from \(oq\\001\(cq to \(oq/\(cq, use \(oq\fB\-P\ \(dq\\001\-/\(dq\fR\(cq.
 
 The statistical outcome of this option should not be overlooked: if characters
 are protected, the effect of the \(oq\fB\-r\fR\(cq flag will vary depending
 on the data being fuzzed. For instance, asking to fuzz 1% of input bits
-(\fB\-r\ 0.01\fR) and to protect lowercase characters (\fB\-P\ a-z\fR) will
+(\fB\-r\ 0.01\fR) and to protect lowercase characters (\fB\-P\ a\-z\fR) will
 result in an actual average fuzzing ratio of 0.9% with truly random data,
 0.3% with random ASCII data and 0.2% with standard English text.
@@ -193 +193 @@
 Fuzz 1% of the input bits of the \fBcat\fR program using seed 94324:
 .PP
-\fB    zzuf -s 94324 -r 0.01 cat /etc/motd\fR
+\fB    zzuf \-s 94324 \-r 0.01 cat /etc/motd\fR
 .PP
 Fuzz the input of the \fBcat\fR program but do not fuzz newline characters
 and prevent non-ASCII characters from appearing in the output:
 .PP
-\fB    zzuf -P \(aq\\n\(aq -R \(aq\\x00-\\x1f\\x7f-\\xff\(aq cat /etc/motd\fR
+\fB    zzuf \-P \(aq\\n\(aq \-R \(aq\\x00\-\\x1f\\x7f\-\\xff\(aq cat /etc/motd\fR
 .PP
 Fuzz the input of the \fBconvert\fR program, using file \fBfoo.jpeg\fR as the
@@ -205 +205 @@
 want \fBzzuf\fR to fuzz them):
 .PP
-\fB    zzuf -E \(aq\\.xml$\(aq convert -- foo.jpeg -format tga /dev/null\fR
+\fB    zzuf \-E \(aq\\.xml$\(aq convert \-\- foo.jpeg \-format tga /dev/null\fR
 .PP
 Fuzz the input of \fBVLC\fR, using file \fBmovie.avi\fR as the original input
 and restricting fuzzing to filenames that appear on the command line
-(\fB\-c\fR), then generate \fBfuzzy-movie.avi\fR which is a file that
+(\fB\-c\fR), then generate \fBfuzzy\-movie.avi\fR which is a file that
 can be read by \fBVLC\fR to reproduce the same behaviour without using
 \fBzzuf\fR:
 .PP
-\fB    zzuf -c -s 87423 -r 0.01 vlc movie.avi\fR
-\fB    zzuf -c -s 87423 -r 0.01 cp movie.avi fuzzy-movie.avi\fR
-\fB    vlc fuzzy-movie.avi\fR
+\fB    zzuf \-c \-s 87423 \-r 0.01 vlc movie.avi\fR
+\fB    zzuf \-c \-s 87423 \-r 0.01 cp movie.avi fuzzy\-movie.avi\fR
+\fB    vlc fuzzy\-movie.avi\fR
 .PP
 Fuzz 2% of \fBMPlayer\fR's input bits (\fB\-r\ 0.02\fR) with seeds 0 to 9999
@@ -223 +223 @@
 and disabling its \fBSIGSEGV\fR signal handler (\fB\-S\fR):
 .PP
-\fB    zzuf -c -r 0.02 -q -s 0:10000 -F 3 -T 60 -S \\\fR
-\fB      mplayer -- -benchmark -vo null -fps 1000 movie.avi\fR
+\fB    zzuf \-c \-r 0.02 \-q \-s 0:10000 \-F 3 \-T 60 \-S \\\fR
+\fB      mplayer \-\- \-benchmark \-vo null \-fps 1000 movie.avi\fR
 .SH RESTRICTIONS
 .PP
@@ -247 +247 @@
 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
@@ -256 +252 @@
 .SH NOTES
 In order to intercept file and network operations and signal handlers,
-\fBzzuf\fR diverts and reimplements the following functions:
+\fBzzuf\fR diverts and reimplements the following functions, which can
+be private libc symbols, too:
 .TP
 Unix file descriptor handling:
@@ -271 +268 @@
 .TP
 BSD-specific:
-\fBfgetln\fR()
+\fBfgetln\fR(), \fB__srefill()\fR()
 .TP
 Signal handling:
@@ -281 +278 @@
 such as \fBltrace(1)\fR on Linux to know the missing functions.
 .PP
-One important unimplemented function is \fBfscanf\fR(), because of its
-complexity. Missing functions will be implemented based upon user request.
+On some systems, such as FreeBSD, \fB__srefill\fR() is enough to monitor all
+standard IO streams functions. On other systems each function needs to be
+reimplemented on a case by case basis. One important unimplemented function
+is \fBfscanf\fR(), because of its complexity. Missing functions will be
+implemented based upon user request.
 .SH HISTORY
 .PP