all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: <tomas@tuxteam.de>
Cc: Robert Pluim <rpluim@gmail.com>,
	 emacs-devel@gnu.org,  Kyle Meyer <kyle@kyleam.com>
Subject: Re: master c86995d07e9: Enable code block evaluation when generating .org manuals
Date: Fri, 07 Jun 2024 13:13:56 +0800	[thread overview]
Message-ID: <s5434ppuygb.fsf@yahoo.com> (raw)
In-Reply-To: <ZmKL4ggL1OZCxc+c@tuxteam.de> (tomas@tuxteam.de's message of "Fri, 7 Jun 2024 06:26:10 +0200")

<tomas@tuxteam.de> writes:

> 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.

This can only be true if documentation changes are scrutinized so little
that code, and by extension malicious code simply passes unnoticed.
Otherwise, it would be best to credit the Org Mode developers with the
same due dilligence as ours, or the resulting attitude will appear
condescending at best.

> 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?
>
> 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).

You mean to imply that Org Mode is more susceptible to organized
sabotage than other players whose code we import, such as Gnulib, or,
heaven forbid, we ourselves?  That way lies madness.



  reply	other threads:[~2024-06-07  5:13 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 [this message]
2024-06-07  6:38           ` tomas
2024-06-07  6:42         ` Eli Zaretskii
2024-06-07  7:38           ` Robert Pluim
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=s5434ppuygb.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=rpluim@gmail.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.