From: Ben Kallus <benjamin.p.kallus.gr@dartmouth.edu>
To: Larry McVoy <lm@mcvoy.com>
Cc: John Levine <johnl@taugh.com>, tuhs@tuhs.org
Subject: [TUHS] Re: OT: LangSec (Re: A fuzzy awk.)
Date: Mon, 20 May 2024 17:00:40 -0400 [thread overview]
Message-ID: <CAB6pCSYdhxS2hxQE768Pgj62sfNqgM+gY_4L1z3fiyfDXAFPhQ@mail.gmail.com> (raw)
In-Reply-To: <20240520201122.GC27662@mcvoy.com>
What I meant was that the LangSec people reject the robustness
principle as it is commonly understood (i.e., make a "reasonable"
guess when receiving garbage), not necessarily that their view is
incompatible with Postel's original vision. This interpretation of the
principle is pretty widespread; take a look at the Nginx mailing list
if you have any doubt. I attribute this to the same phenomenon that
inverted the meaning of REST.
-Ben
next prev parent reply other threads:[~2024-05-20 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 13:06 [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Douglas McIlroy
2024-05-20 13:14 ` [TUHS] " arnold
2024-05-20 14:00 ` G. Branden Robinson
2024-05-20 13:25 ` Chet Ramey
2024-05-20 13:41 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 14:26 ` Chet Ramey
2024-05-22 13:44 ` arnold
2024-05-20 13:54 ` Ralph Corderoy
2024-05-20 15:39 ` [TUHS] OT: LangSec (Re: A fuzzy awk.) Åke Nordin
2024-05-20 16:09 ` [TUHS] " Ben Kallus
2024-05-20 20:02 ` John Levine
2024-05-20 20:11 ` Larry McVoy
2024-05-20 21:00 ` Ben Kallus [this message]
2024-05-20 21:03 ` John R Levine
2024-05-20 21:14 ` Larry McVoy
2024-05-20 21:46 ` Ben Kallus
2024-05-20 21:57 ` Larry McVoy
2024-05-20 16:06 ` [TUHS] Re: A fuzzy awk. (Was: The 'usage: ...' message.) Paul Winalski
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=CAB6pCSYdhxS2hxQE768Pgj62sfNqgM+gY_4L1z3fiyfDXAFPhQ@mail.gmail.com \
--to=benjamin.p.kallus.gr@dartmouth.edu \
--cc=johnl@taugh.com \
--cc=lm@mcvoy.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).