From: Warner Losh <imp@bsdimp.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] buffer overflow (Re: Happy birthday Morris worm
Date: Thu, 21 Nov 2019 13:38:37 -0700 [thread overview]
Message-ID: <CANCZdfrzei=PTDt1Jwgy-rMJe+odBK8gDZpUePOi9+QzMkM6nw@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1911220658250.33542@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Thu, Nov 21, 2019 at 1:02 PM Dave Horsfall <dave@horsfall.org> wrote:
> On Tue, 19 Nov 2019, Tony Finch wrote:
>
> > Amusingly POSIX says the C standard takes precedence wrt the details of
> > gets() (and other library functions) and C18 abolished gets(). I'm
> > slightly surprised that the POSIX committee didn't see that coming and
> > include the change in the 2018 edition...
>
> Didn't know that gets() had finally been abolished; it's possibly the most
> unsafe function (OK, macro) on the planet. I've long been tempted to
> remove gets() and see what breaks...
>
A few things actually broke when FreeBSD removed it. Apart from 'wrappers'
that needed it for various reasons, it was only a few programs in our
'ports' package that needed to be corrected.
Most people have moved on with the 20 years of warnings when it was used...
Sadly only most...
Warner
[-- Attachment #2: Type: text/html, Size: 1333 bytes --]
next prev parent reply other threads:[~2019-11-21 20:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 20:56 [TUHS] " Norman Wilson
2019-11-12 22:00 ` Dave Horsfall
2019-11-12 22:10 ` [TUHS] buffer overflow (Re: " Bakul Shah
2019-11-12 22:14 ` Larry McVoy
2019-11-12 22:41 ` Robert Clausecker
2019-11-12 22:49 ` Arthur Krewat
2019-11-12 23:45 ` Jon Steinhart
2019-11-13 0:38 ` Warren Toomey
2019-11-13 1:09 ` Arthur Krewat
2019-11-13 0:24 ` Larry McVoy
2019-11-12 22:54 ` Dave Horsfall
2019-11-12 23:22 ` Warner Losh
2019-11-12 23:27 ` Arthur Krewat
[not found] ` <alpine.DEB.2.20.1911191443530.10845@grey.csi.cam.ac.uk>
2019-11-21 20:02 ` Dave Horsfall
2019-11-21 20:38 ` Warner Losh [this message]
2019-11-21 21:04 ` Clem Cole
2019-11-21 22:06 ` Dave Horsfall
2019-11-21 21:48 ` Steffen Nurpmeso
2019-11-13 7:35 ` [TUHS] " arnold
2019-11-13 18:02 ` [TUHS] Happy birthday Morris worm [ really programming education ] Jon Steinhart
2019-11-13 18:49 ` Tyler Adams
2019-11-13 19:15 ` [TUHS] #defines and enums ron
2019-11-13 21:11 ` Warner Losh
2019-11-13 21:22 ` [TUHS] Happy birthday Morris worm [ really programming education ] Chet Ramey
2019-11-15 22:49 ` Adam Thornton
2019-11-15 23:59 ` Theodore Y. Ts'o
2019-11-12 22:39 [TUHS] buffer overflow (Re: Happy birthday Morris worm Norman Wilson
2019-11-13 1:43 ` John P. Linderman
2019-11-21 13:10 ` William Cheswick
2019-11-21 18:04 ` Steve Johnson
2019-11-21 21:51 ` John P. Linderman
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='CANCZdfrzei=PTDt1Jwgy-rMJe+odBK8gDZpUePOi9+QzMkM6nw@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=dave@horsfall.org \
--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).