From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 44018@debbugs.gnu.org
Subject: bug#44018: Don't consider play-sound-file to be a 'safe' function
Date: Fri, 16 Oct 2020 07:39:05 +0200 [thread overview]
Message-ID: <87mu0mrapy.fsf@gnus.org> (raw)
In-Reply-To: <83zh4nwgbs.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Oct 2020 20:26:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Are the risks the same on all the supported platforms, or just on
> some?
My understanding of unsafep.el isn't that it's trying to protect against
any particular exploits, but just give a list of things that are totally
and utterly OK to eval. So you have stuff like:
commit a8c41b4c0d3b0a3e87f17bbcdd8ac12dae296b3a
Author: Chong Yidong <cyd@stupidchicken.com>
AuthorDate: Mon Oct 18 13:28:20 2010 -0400
Don't allow functions that display messages in unsafep.
So even `message' isn't "safe" in this context. I think it's odd to
have `play-sound-file' marked as "safe" if `message' isn't.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-16 5:39 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 [this message]
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
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
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=87mu0mrapy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44018@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.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 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).