The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Rich Salz <rich.salz@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Cool talk on Unix and Sendmail history, by Eric Allman
Date: Sat, 22 Jul 2023 09:24:55 -0600	[thread overview]
Message-ID: <CANCZdfo9X3YdKS4TMvKMEfGvYkMDoKvhv7fFB+gKruQVUsbuwg@mail.gmail.com> (raw)
In-Reply-To: <CAFH29tqUNK8cC+UtznqkBtw59BhekoAGRAZjtppCo6bRi5sb6g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

On Sat, Jul 22, 2023, 8:54 AM Rich Salz <rich.salz@gmail.com> wrote:

> He says he wraps everything he uses in the standard library; "this tends
> to make my code idiosyncratic."  At some Usenix, someone once summed it up
> to me as "It is the most beautiful code that is completely unmodifiable."
> Seemed appropriate.  (Compare to procmail, where the quote was "seen the
> source? Gaah, my eyes are melting.")
>

Back in the 80s I looked at sendmail.. lots of things like strcpy written
inline. It was a mess in some ways, but ran more slowly if you cleaned all
that stuff up. It was decently well done, but had also clearly grown well
beyond its original framing...

The thing is... you don't need wrappers for standard calls. You just need
portable implementations of them for the times they are missing or broken.

I enjoyed watching this, thanks. I agree with the other comment "what,
> nothing about security?" Sendmail did enable the first Internet worm :)
>

Some of that was the times: almost nothing cared about security in a world
full of active attackers... having already forgotten the lessons of the
early v5 deployments exposing unix to lots of bored college students that
needed to do something and quickly found holes in unix's protections..
though known at the time, the stack smash wasn't believed generally to be a
severe threat. Even after the eorm, it was 10 years later openbsd started
its wide spread effort to fix them...

Gets() was the real problem that leD to the worm. The insecurity was baked
into the APIs until the 90s... and many insecure APIs weren't removed until
the last decade.

Warner

>

[-- Attachment #2: Type: text/html, Size: 2646 bytes --]

  reply	other threads:[~2023-07-22 15:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 18:53 [TUHS] " Rich Morin
2023-07-21 22:14 ` [TUHS] " Grant Taylor via TUHS
2023-07-21 22:30   ` Larry McVoy
2023-07-21 22:33     ` Grant Taylor via TUHS
2023-07-21 22:39       ` Larry McVoy
2023-07-21 23:39     ` Steve Nickolas
2023-07-22  4:37       ` John Cowan
2023-07-22  1:48     ` segaloco via TUHS
2023-07-22  1:55     ` Jon Forrest
2023-07-22  6:45     ` Lars Brinkhoff
2023-07-22 14:54 ` Rich Salz
2023-07-22 15:24   ` Warner Losh [this message]
2023-07-22 16:12     ` Arrigo Triulzi via TUHS
2023-07-22 20:52   ` Dave Horsfall
2023-07-30 17:33 Douglas McIlroy
2023-07-30 18:22 Norman Wilson
2023-07-30 21:43 ` Rob Pike
2023-07-30 23:34   ` George Michaelson
2023-07-30 23:59     ` Erik E. Fair
2023-07-31  0:26       ` Warner Losh
2023-07-31 22:57         ` Grant Taylor via TUHS
2023-07-31 23:05           ` Warner Losh
2023-08-01  2:45             ` Grant Taylor via TUHS
2023-08-01  1:51         ` Niklas Karlsson
2023-08-01  2:47           ` Grant Taylor via TUHS
2023-08-01  3:20           ` Theodore Ts'o
2023-07-31  0:41       ` segaloco via TUHS
2023-08-01  9:22       ` Marc Donner
2023-08-01 10:58         ` Erik E. Fair
2023-08-02  0:37           ` Dave Horsfall
2023-08-02 14:52             ` Ron Natalie
2023-08-02 21:14               ` Grant Taylor via TUHS
2023-08-02 22:20                 ` segaloco via TUHS
2023-08-02 22:37                   ` Warner Losh
2023-08-02 23:49                   ` Rich Salz
2023-08-02 23:33               ` Dave Horsfall

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=CANCZdfo9X3YdKS4TMvKMEfGvYkMDoKvhv7fFB+gKruQVUsbuwg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=rich.salz@gmail.com \
    --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).