From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <tomas@tuxteam.de>,
luangruo@yahoo.com, emacs-devel@gnu.org, kyle@kyleam.com
Subject: Re: master c86995d07e9: Enable code block evaluation when generating .org manuals
Date: Fri, 07 Jun 2024 09:38:12 +0200 [thread overview]
Message-ID: <87cyoti4nv.fsf@gmail.com> (raw)
In-Reply-To: <86msnxfe45.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Jun 2024 09:42:18 +0300")
>>>>> On Fri, 07 Jun 2024 09:42:18 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> This is, strictly speaking, right, of course. Expectation-wise it does
>> lower the bar for an attacker somewhat, since now the malicious code just
>> has to be snuck into documentation.
>>
>> So I think Robert is right that it's worth a discussion (whatever the
>> outcome might be: perhaps treat the doc as code and give it as much
>> scrutiny?
Eli> That ship sailed when we decided to allow manuals to be written in
Eli> Org. So discussing this now is way too late, unless you want to
Eli> suggest to go back on that decision and force all the manuals to be
Eli> written in Texinfo.
Allowing Org just added another markup language. Subverting that
requires crafting documentation that causes the texinfo or org
handling code to misbehave. I doubt thatʼs impossible, given the
ingenuity of attackers, but enabling direct evaluation of emacs lisp
makes such subversion a whole lot easier.
>> Anyway, the libxz episode shows that it seems to be easier to sneak
>> malicious code "elsewhere" (in that case it was the test suite, but
>> you get te idea).
Eli> So you are saying that our co-maintainers are not to be trusted not to
Eli> sneak such code into release tarballs? That's quite an insult, I'd
Eli> say.
Itʼs not a question of trust, nor an attack on maintainersʼ ability:
hiding such code from well-intentioned, skilled maintainers can and
has been done.
Eli> Why is it that a crime perpetrated by some villain immediately causes
Eli> people to suspect everyone around them to be capable of similar
Eli> crimes?
Nobody is accusing maintainers of bad intentions. My point was merely
that we should think carefully about enabling such a feature.
If the end result is that documentation changes are inspected more
closely, thatʼs not necessarily a bad thing.
Robert
--
next prev parent reply other threads:[~2024-06-07 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171767737644.19678.784876979840850798@vcs2.savannah.gnu.org>
[not found] ` <20240606123616.DE7C9C1F9EF@vcs2.savannah.gnu.org>
2024-06-06 14:31 ` master c86995d07e9: Enable code block evaluation when generating .org manuals Robert Pluim
2024-06-07 2:39 ` Kyle Meyer
2024-06-07 8:50 ` Stefan Kangas
2024-06-09 17:55 ` Ihor Radchenko
2024-06-09 18:26 ` Stefan Kangas
2024-06-09 18:45 ` Ihor Radchenko
2024-06-09 19:19 ` Stefan Kangas
2024-06-15 14:38 ` Ihor Radchenko
2024-06-15 14:47 ` Stefan Kangas
2024-06-17 11:46 ` Ihor Radchenko
2024-06-18 19:37 ` Stefan Kangas
2024-06-07 3:54 ` Po Lu
2024-06-07 4:26 ` tomas
2024-06-07 5:13 ` Po Lu
2024-06-07 6:38 ` tomas
2024-06-07 6:42 ` Eli Zaretskii
2024-06-07 7:38 ` Robert Pluim [this message]
2024-06-07 11:01 ` Eli Zaretskii
2024-06-07 11:17 ` Po Lu
2024-06-07 8:12 ` tomas
2024-06-09 2:16 ` Richard Stallman
2024-06-09 18:12 ` Ihor Radchenko
2024-06-09 18:27 ` Eli Zaretskii
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=87cyoti4nv.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=luangruo@yahoo.com \
--cc=tomas@tuxteam.de \
/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.