From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
larsi@gnus.org, 44018@debbugs.gnu.org
Subject: bug#44018: Don't consider play-sound-file to be a 'safe' function
Date: Mon, 26 Oct 2020 18:38:07 +0100 [thread overview]
Message-ID: <156CF4D0-EA6C-454C-9C7D-98A2DD3BFB70@acm.org> (raw)
In-Reply-To: <83zh48ewmd.fsf@gnu.org>
26 okt. 2020 kl. 18.16 skrev Eli Zaretskii <eliz@gnu.org>:
>> What is a safe Lisp expression? Basically, it's an expression that
>> calls only built-in functions with no side effects (or only innocuous
>> ones). Innocuous side effects include displaying messages and
>> altering non-risky buffer-local variables (but not global variables).
>
> Thanks. But this seems to say 'message' should be considered safe?
What counted as 'innocuous' back then may not do so today.
Freely displaying messages to the user as if they came from a trusted system isn't necessarily harmless by modern standards of security.
next prev parent reply other threads:[~2020-10-26 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 16:55 bug#44018: Don't consider play-sound-file to be a 'safe' function Mattias Engdegård
2020-10-15 17:14 ` Lars Ingebrigtsen
2020-10-15 17:26 ` Eli Zaretskii
2020-10-15 19:01 ` Mattias Engdegård
2020-10-15 19:20 ` Eli Zaretskii
2020-10-16 9:45 ` Mattias Engdegård
2020-10-26 11:51 ` Mattias Engdegård
2020-10-26 15:29 ` Eli Zaretskii
2020-10-26 16:19 ` Mattias Engdegård
2020-10-26 17:09 ` Eli Zaretskii
2020-10-26 18:25 ` Lars Ingebrigtsen
2020-10-26 16:32 ` Stefan Kangas
2020-10-26 16:51 ` Mattias Engdegård
2020-10-16 5:39 ` Lars Ingebrigtsen
2020-10-16 6:23 ` Eli Zaretskii
2020-10-26 17:05 ` Basil L. Contovounesios
2020-10-26 17:16 ` Eli Zaretskii
2020-10-26 17:38 ` Mattias Engdegård [this message]
2020-10-26 18:28 ` Eli Zaretskii
2020-10-26 20:36 ` Mattias Engdegård
2020-10-31 8:06 ` Eli Zaretskii
2020-10-31 13:33 ` Mattias Engdegård
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=156CF4D0-EA6C-454C-9C7D-98A2DD3BFB70@acm.org \
--to=mattiase@acm.org \
--cc=44018@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.