From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Tue, 6 Sep 2022 15:04:14 -0400 [thread overview]
Message-ID: <CAKH6PiXjw-fhCwbdyVHNiTnNX4aNkSJUOPkFbg7tjGRJ9ErjGQ@mail.gmail.com> (raw)
>> a paper appeared (in CACM?) that repeated Dennis's exercise.
> Maybe this one?
> B.P. Miller, L. Fredriksen, and B. So, "An Empirical Study of the Reliability
> of UNIX Utilities", Communications of the ACM 33, 12 (December 1990).
> http://www.paradyn.org/papers/fuzz.pdf
Probably. I had forgotten that the later effort was considerably more
elaborate than Dennis's. It created multiple random inputs that might
stumble on other things besides buffer overflow. I see a Unix parable
in the remarkable efficacy of Dennis's single-shot test.
Doug
next reply other threads:[~2022-09-06 19:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 19:04 Douglas McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-06 15:07 Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07 1:40 ` steve jenkin
2022-09-07 2:33 ` segaloco via TUHS
2022-09-07 4:08 ` Steve Jenkin
2022-09-07 13:08 ` Steffen Nurpmeso
2022-09-07 14:56 ` Larry McVoy
2022-09-07 21:27 ` Steve Jenkin
2022-09-07 22:36 ` Larry McVoy
2022-09-08 14:42 ` Paul Winalski
2022-09-08 15:02 ` Larry McVoy
2022-09-08 15:04 ` ron minnich
2022-09-08 15:52 ` Warner Losh
2022-09-08 16:47 ` Paul Winalski
2022-09-08 16:50 ` segaloco via TUHS
2022-09-08 17:58 ` ron minnich
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKH6PiXjw-fhCwbdyVHNiTnNX4aNkSJUOPkFbg7tjGRJ9ErjGQ@mail.gmail.com \
--to=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).