The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: a.phillip.garcia@gmail.com (A. P. Garcia)
Subject: [TUHS] Bugs in V6 'dcheck'
Date: Sun, 1 Jun 2014 18:48:48 -0500	[thread overview]
Message-ID: <CAFCBnZuCmDpRsFtPVw14tOr-q=OAh7SxWQpShati8K=SfUDtPQ@mail.gmail.com> (raw)
In-Reply-To: <201405312324.s4VNOvFV028181@stowe.cs.dartmouth.edu>

On May 31, 2014 6:25 PM, "Doug McIlroy" <doug at cs.dartmouth.edu> wrote:
>
> > Ken and Dennis and the other guys behind
> > the earliest UNIX code were smart guys and good programmers,
> > but they were far from perfect; and back in those days we
> > were all a lot sloppier.
>
> The observation that exploits may be able to parlay
> mundane bugs into security holes was not a commonplace
> back then--even in the Unix room. So input buffers were
> often made "bigger than ever will be needed" and left
> that way on the understanding that crashes are tolerable
> on outlandish data. In an idle moment one day, Dennis fed
> a huge line of input to most everything in /bin. To the
> surprise of nobody, including Dennis, lots of programs
> crashed. We WERE surprised a few years later, when a journal
> published this fact as a research result. Does anybody
> remember who published that deep new insight and/or where?
>
> Doug

yeah, that's not really sporting. I've always wondered about something
else, though: Were the original Unix authors annoyed when they learned that
some irascible young upstart named Richard Stallman was determined to make
a free Unix clone? Was he a gadfly, or just some kook you decided to
ignore? The fathers of Unix have been strangely silent on this topic for
many years. Maybe nobody's ever asked?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140601/e6c13cc8/attachment.html>


  parent reply	other threads:[~2014-06-01 23:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 23:24 Doug McIlroy
2014-06-01  0:17 ` Kevin Schoedel
2014-06-01 22:54   ` scj
2014-06-01 23:48 ` A. P. Garcia [this message]
2014-06-02  1:11   ` Ronald Natalie
2014-06-02  2:10     ` A. P. Garcia
2014-06-03 16:38 ` Nelson H. F. Beebe
  -- strict thread matches above, loose matches on Subject: below --
2014-06-03 17:33 Nelson H. F. Beebe
2014-06-02  3:34 Noel Chiappa
2014-06-02  4:05 ` Mary Ann Horton
2014-06-02  6:12 ` arnold
2014-06-03 12:11 ` emanuel stiebler
2014-06-02  3:18 Noel Chiappa
2014-06-02  2:14 Michael Spacefalcon
2014-06-02  2:51 ` John Cowan
2014-05-31 15:55 Noel Chiappa
2014-05-31 16:18 ` Ron Natalie
2014-05-31 14:19 Noel Chiappa
2014-05-31 13:30 Norman Wilson
2014-05-31 16:03 ` John Cowan
     [not found]   ` <20140531161620.GL28034@mcvoy.com>
2014-05-31 17:16     ` John Cowan
2014-05-31 13:15 Noel Chiappa
2014-05-31 13:23 ` Ronald Natalie
2014-05-31 18:58 ` Tim Newsham
2014-05-31 19:48 ` Clem Cole

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='CAFCBnZuCmDpRsFtPVw14tOr-q=OAh7SxWQpShati8K=SfUDtPQ@mail.gmail.com' \
    --to=a.phillip.garcia@gmail.com \
    /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).