From: Richard Stallman <rms@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: mattiase@acm.org, 50136@debbugs.gnu.org,
monnier@iro.umontreal.ca, rms@gnu.org
Subject: bug#50136: 28.0.50; A problem with rx-let expansion
Date: Fri, 20 Aug 2021 23:21:00 -0400 [thread overview]
Message-ID: <E1mHHZ6-0005U2-LF@fencepost.gnu.org> (raw)
In-Reply-To: <87y28whw1b.fsf@web.de> (message from Michael Heerdegen on Fri, 20 Aug 2021 19:21:20 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Actually it's the rx `eval` form that you are looking for if you want
> > arbitrary compile-time computation. `regexp` and `literal` are
> > explicitly made for run-time expressions.
If there are variables which can hold an rx expression, we need to make
them as unsafe file variable bindings. Or else have special code
to study them and see if evaluation constructs are used.
Has this been done?
Are these constructs an insecurity?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2021-08-21 3:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 13:59 bug#50136: 28.0.50; A problem with rx-let expansion Michael Heerdegen
2021-08-20 14:50 ` Michael Heerdegen
2021-08-20 15:23 ` Mattias Engdegård
2021-08-20 17:21 ` Michael Heerdegen
2021-08-20 18:45 ` Mattias Engdegård
2021-08-21 11:45 ` Michael Heerdegen
2021-08-21 13:02 ` Mattias Engdegård
2021-08-23 10:45 ` Michael Heerdegen
2021-08-23 12:38 ` Mattias Engdegård
2021-08-23 15:20 ` Mattias Engdegård
2021-08-23 16:59 ` Michael Heerdegen
2021-08-23 18:05 ` Mattias Engdegård
2021-08-21 3:21 ` Richard Stallman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1mHHZ6-0005U2-LF@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=50136@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).