From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Org may fetch remote content without asking user consent
Date: Wed, 7 Feb 2024 17:54:07 +0700 [thread overview]
Message-ID: <upvngj$150v$1@ciao.gmane.io> (raw)
Consider the following .org file:
--- 8< ---
#+setupfile: /dav:localhost#8000:/msg-123456.org
--- >8 ---
When Emacs opens it, HTTP server (plain HTTP, not WebDAV is used for
test) logs contain
python3 -m http.server 8000
Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ...
127.0.0.1 - - [07/Feb/2024 17:34:52] code 501, message Unsupported
method ('OPTIONS')
127.0.0.1 - - [07/Feb/2024 17:34:52] "OPTIONS /msg-123456.org HTTP/1.1"
501 -
127.0.0.1 - - [07/Feb/2024 17:34:52] code 501, message Unsupported
method ('OPTIONS')
127.0.0.1 - - [07/Feb/2024 17:34:52] "OPTIONS /msg-123456.org HTTP/1.1"
501 -
Emacs *Messages* buffer:
Tramp: Opening connection for localhost using dav...failed
Unable to read file "/dav:localhost#8000:/msg-123456.org"
Tramp: Opening connection for localhost using dav...failed
Unable to read file "/dav:localhost#8000:/msg-123456.org"
No dialog whether the file should be downloaded is displayed.
My expectation is that Org should not connect to remote servers in
default configuration unless it is explicitly approved by the user.
I am unsure what user option may be changed to mitigate the issue.
- Debian 12 bookworm
- Org commit 18d98e
- gvfs-backends (dependency of gnome-core) package is installed
next reply other threads:[~2024-02-07 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:54 Max Nikulin [this message]
2024-02-07 16:12 ` [BUG] Org may fetch remote content without asking user consent Ihor Radchenko
2024-02-07 16:39 ` Max Nikulin
2024-02-07 17:10 ` Ihor Radchenko
2024-02-08 10:50 ` Max Nikulin
2024-02-08 15:07 ` Ihor Radchenko
2024-02-11 15:03 ` Max Nikulin
2024-02-13 13:31 ` 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='upvngj$150v$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).