From: Ralph Corderoy <ralph@inputplus.co.uk>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: A fuzzy awk.
Date: Mon, 20 May 2024 14:54:04 +0100 [thread overview]
Message-ID: <20240520135404.1B4181FB2F@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAKH6PiXQDOxRuZDMvzMVqzHbdgykMtWkdSVWNe4EeHEk9oXoxQ@mail.gmail.com>
Hi,
Doug wrote:
> I commend attention to the LangSec movement, which advocates for
> rigorously enforced separation between legal and illegal inputs.
https://langsec.org
‘The Language-theoretic approach (LangSec) regards the Internet
insecurity epidemic as a consequence of ‘ad hoc’ programming of
input handling at all layers of network stacks, and in other kinds
of software stacks. LangSec posits that the only path to
trustworthy software that takes untrusted inputs is treating all
valid or expected inputs as a formal language, and the respective
input-handling routines as a ‘recognizer’ for that language.
The recognition must be feasible, and the recognizer must match the
language in required computation power.
‘When input handling is done in ad hoc way, the ‘de facto’
recognizer, i.e. the input recognition and validation code ends up
scattered throughout the program, does not match the programmers'
assumptions about safety and validity of data, and thus provides
ample opportunities for exploitation. Moreover, for complex input
languages the problem of full recognition of valid or expected
inputs may be *undecidable*, in which case no amount of
input-checking code or testing will suffice to secure the program.
Many popular protocols and formats fell into this trap, the
empirical fact with which security practitioners are all too
familiar.
‘LangSec helps draw the boundary between protocols and API designs
that can and cannot be secured and implemented securely, and charts
a way to building truly trustworthy protocols and systems. A longer
summary of LangSec in this USENIX Security BoF hand-out, and in the
talks, articles, and papers below.’
That does look interesting; I'd not heard of it.
--
Cheers, Ralph.
next prev parent reply other threads:[~2024-05-20 13:54 UTC|newest]
Thread overview: 47+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2024-05-23 13:49 [TUHS] Re: A fuzzy awk Douglas McIlroy
2024-05-23 20:52 ` Rob Pike
2024-05-24 5:41 ` andrew
2024-05-24 7:17 ` Ralph Corderoy
2024-05-24 7:41 ` Rob Pike
2024-05-24 11:56 ` Dan Halbert
2024-05-25 0:17 ` Bakul Shah via TUHS
2024-05-25 0:57 ` G. Branden Robinson
2024-05-25 13:56 ` David Arnold
2024-05-25 17:18 ` Paul Winalski
2024-05-25 17:36 ` Tom Perrine
2024-05-20 14:09 Serissa
2024-05-21 1:56 ` Rob Pike
2024-05-21 2:47 ` Larry McVoy
2024-05-21 2:54 ` Lawrence Stewart
2024-05-21 3:36 ` Rob Pike
2024-05-21 11:59 ` Peter Weinberger (温博格) via TUHS
2024-05-21 3:53 ` George Michaelson
2024-05-21 16:59 ` Paul Winalski
2024-05-21 17:56 ` segaloco via TUHS
2024-05-21 18:12 ` Luther Johnson
2024-05-22 15:37 ` Paul Winalski
2024-05-22 18:49 ` Larry McVoy
2024-05-22 20:17 ` Larry McVoy
2024-05-22 3:26 ` Dave Horsfall
2024-05-22 5:08 ` Alexis
2024-05-22 13:12 ` Warner Losh
2024-05-19 23:08 [TUHS] The 'usage: ...' message. (Was: On Bloat...) Douglas McIlroy
2024-05-20 0:58 ` [TUHS] " Rob Pike
2024-05-20 3:19 ` arnold
2024-05-20 9:20 ` [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Ralph Corderoy
2024-05-20 13:10 ` [TUHS] " Chet Ramey
2024-05-20 13:30 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 13:48 ` Chet Ramey
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=20240520135404.1B4181FB2F@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--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).