From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG][Security] begin_src :var evaluated before the prompt to confirm execution
Date: Fri, 28 Oct 2022 11:11:18 +0700 [thread overview]
Message-ID: <tjfkp7$ggm$1@ciao.gmane.io> (raw)
In-Reply-To: <87fsf8my7h.fsf@localhost>
On 28/10/2022 10:19, Ihor Radchenko wrote:
> Jean Louis writes:
>
>> * Max Nikulin [2022-10-27 06:21]:
>>> Expected result:
>>> No code from the Org buffer and linked files is executed prior to
>>> confirmation from the user.
>>
>> Should that be or is it a general policy for Org mode?
>
> Yes, it is a general policy.
> Org should not execute arbitrary Elisp without confirmation, unless the
> user customizes the confirmation query to non-default.
There are significantly different contexts: trusted files created
locally and arbitrary files fetched through some link in the web.
Features really convenient in the former case may became a disaster in
the latter.
If a user is prompted to confirm evaluation of each table formula then
spreadsheet feature becomes unusable.
---- >8 ----
Enter value and press =TAB=
| | Value | Result |
|---+-------+--------|
| # | | |
#+tblfm: $3='(progn (message "%s" "pwnd") 0)
---- 8< ----
I suspect a bunch of similar problems with export feature. The ability
to save an .org file as a nicely formatted PDF is great but
simultaneously dangerous for files obtained from the net. I would like
to have safe export, but I am afraid that actually the code would be
fragile.
next prev parent reply other threads:[~2022-10-28 4:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 3:18 [BUG][Security] begin_src :var evaluated before the prompt to confirm execution Max Nikulin
2022-10-27 4:22 ` Jean Louis
2022-10-27 4:46 ` Max Nikulin
2022-10-28 4:33 ` Ihor Radchenko
2022-10-28 3:19 ` Ihor Radchenko
2022-10-28 4:11 ` Max Nikulin [this message]
2022-10-28 7:30 ` Jean Louis
2022-10-28 3:15 ` [PATCH] " Ihor Radchenko
2022-10-28 17:12 ` Max Nikulin
2022-10-29 3:19 ` Ihor Radchenko
2022-11-10 5:55 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='tjfkp7$ggm$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).