unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Reproducers for recent Emacs security issues
Date: Wed, 17 Apr 2024 21:31:16 +0700	[thread overview]
Message-ID: <uvomfl$p0u$1@ciao.gmane.io> (raw)
In-Reply-To: <87msptqw41.fsf@ust.hk>

On 16/04/2024 20:23, Andrew Cohen wrote:
> 
>      EZ> Maybe I misunderstand something (I don't use Gnus), but isn't it
>      EZ> a security problem that the presence of such a line in an email
>      EZ> message causes Emacs to download a remote file?
> 
> It doesn't cause the file to be downloaded immediately---it displays a
> message identifying downloading the file as a possible security risk,
> and requires confirmation in order to proceed with the download. This
> seems OK from the security viewpoint.

The dialog was introduced in Org mode 9.6 while Emacs-28.2 (the version 
in Debian stable) has Org 9.5. Moreover, Emacs before 29.3 had a bug, 
and attempts to fetch remote file happened even when users declined 
requests. (I do not think, user experience would be great in the case of 
a message having a dozen of #+setupfile lines...)

> But this is what 'gnus-article-emulate-mime is supposed to do:
> it consults a list of regular expressions to match and invokes handlers
> to deal with them (whether the article is mime or not).

I did not figure out at first that it is not an attachment that 
activates Org mode for message body.

However almost certainly it is incorrect that in the case of

#+startup: latexpreview
\begin{equation}
x = 1
\end{equation}

`org-mode' is invoked just for
---- 8< ----
#+startup: latexpreview
\begin{equation}
---- >8 ----

I am in doubts if the intention is to highlight just the #+startup line 
or rest of the body.

If a message contains just #+startup without immediately following 
\begin{equation} then Org mode does not tries if latex command is 
available and it is even more confusing.




      reply	other threads:[~2024-04-17 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14  3:23 Reproducers for recent Emacs security issues Sean Whitton
2024-04-14  4:41 ` Max Nikulin
2024-04-15  9:27   ` Sean Whitton
2024-04-15  9:32     ` Ihor Radchenko
2024-04-15  9:46       ` Sean Whitton
2024-04-15 10:09         ` Ihor Radchenko
2024-04-15 11:20         ` Max Nikulin
2024-04-15 12:00           ` Ihor Radchenko
2024-04-15 13:42             ` Andrew Cohen
2024-04-15 18:33             ` Florian Weimer
2024-04-15 23:30               ` Andrew Cohen
2024-04-16  4:35                 ` Max Nikulin
2024-04-16 12:25                 ` Eli Zaretskii
2024-04-16 13:23                   ` Andrew Cohen
2024-04-17 14:31                     ` Max Nikulin [this message]

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='uvomfl$p0u$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-devel@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.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).