From: Max Nikulin <manikulin@gmail.com>
To: 58774@debbugs.gnu.org, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: bug#58774: 29.0.50; [WISH]: Let us make EWW browse WWW Org files correctly
Date: Thu, 27 Oct 2022 22:35:57 +0700 [thread overview]
Message-ID: <d8bead8c-f97d-1de5-ae06-df81fefb7389@gmail.com> (raw)
In-Reply-To: <Y1oPNvuDiYhiHFck@protected.localdomain>
On 27/10/2022 11:55, Jean Louis wrote:
>
> Now is clear that main problem here is that Org advertises somewhere
> to be "text" in MIME context, while it is not, it is by default
> "application" and thus unsafe, see:
...
> Text Media Types
> https://datatracker.ietf.org/doc/html/rfc6838#section-4.2.1
I do not see any problem or any difference what MIME type you are going
to associate with Org mode. I agree with Arne that text/... type is more
appropriate for a format readable as text. I do not see any
contradictions with that RFC.
"Org Mode
Your life in plain text"
Chromium is able to display text/x-org internally just as text/plain and
I like it as a way to preview and review file contents. I have not
managed to configure Firefox to achieve the same behavior that allows to
avoid an external application (certainly not Emacs at first).
> We can't just speak of safety alone when we are in general
> computing environment, we must also speak of usefulness.
I do not mind to have org-view-mode that saves me from execution some
code unintentionally. Since most of the code was written without having
in mind such feature, I expect a lot of iterations before all
possibilities to run code will be plumbed. I suspect that it is possible
to ruin whole protection by a small piece of elisp code. I am unaware of
sandboxing in Emacs. I expect that making Org mode safe enough will
require a lot of efforts by developers.
Your are pushing Org to rather hostile environment: highly automated
attacks to distribute exploits, market of breached computers listening
for remote commands. A running cryptominer would be rather innocent
consequence, through the same backdoor you may receive an encryptor or
various stuff searching for credentials and access tokens in your files.
Emacs is protected mostly by its low popularity. A lot of efforts have
been invested in browser making attacks more expensive, but still
attractive due to possible benefits. I do not like to increase surface
for attacks. Someone may create a plugin targeting Emacs users just
because it would be easy enough.
Consider converting Org files to HTML as an unpleasant tax for the sake
of safety.
> All I want is to access my personal read-only Org files by using WWW
> and browse from one to the other by using links.
How are you going to distinguish your personal files and arbitrary files
from non-trusted sources? By signing your files and maintaining list of
trusted certificates?
For personal notes I would expect e.g. private instance of nextcloud
file share (that is internally HTTP server), not accessing files
directly through HTTP.
next prev parent reply other threads:[~2022-10-27 15:38 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 12:06 29.0.50; [WISH]: Let us make EWW browse WWW Org files correctly Jean Louis
2022-10-25 15:02 ` Dr. Arne Babenhauserheide
2022-10-25 19:56 ` Jean Louis
2022-10-25 21:54 ` Dr. Arne Babenhauserheide
2022-10-26 7:57 ` Jean Louis
2022-10-26 11:55 ` Dr. Arne Babenhauserheide
2022-10-26 12:20 ` Jean Louis
2022-10-26 12:45 ` Andreas Schwab
2022-10-26 13:19 ` bug#58774: " Jean Louis
2022-10-26 13:55 ` Andreas Schwab
2022-10-26 17:36 ` Jean Louis
2022-10-27 7:58 ` Andreas Schwab
2022-10-27 8:40 ` Jean Louis
2022-10-27 11:22 ` Andreas Schwab
2022-10-27 11:23 ` Dr. Arne Babenhauserheide
2022-10-26 7:59 ` Jean Louis
2022-10-25 23:03 ` Ihor Radchenko
2022-10-26 6:07 ` bug#58774: " Stefan Kangas
2022-10-26 6:52 ` Ihor Radchenko
2022-10-26 8:24 ` Jean Louis
2022-10-26 20:22 ` indieterminacy
2022-10-26 11:30 ` Dr. Arne Babenhauserheide
2022-10-26 21:41 ` Tim Cross
2022-10-27 10:43 ` Dr. Arne Babenhauserheide
2022-10-26 13:15 ` Stefan Kangas
2022-10-26 8:21 ` Jean Louis
2022-10-26 17:07 ` Max Nikulin
2022-10-26 18:37 ` Jean Louis
2022-10-26 21:16 ` Dr. Arne Babenhauserheide
2022-10-27 4:25 ` tomas
2022-10-27 11:10 ` Dr. Arne Babenhauserheide
2022-10-26 21:56 ` indieterminacy
2022-10-26 20:00 ` Tim Cross
2022-10-25 22:13 ` Ag Ibragimov
2022-10-26 8:28 ` Jean Louis
2022-10-26 13:00 ` Rudolf Adamkovič
2022-10-26 13:42 ` bug#58774: " Jean Louis
2022-10-27 4:55 ` Jean Louis
2022-10-27 11:13 ` Dr. Arne Babenhauserheide
2022-10-27 17:41 ` Jean Louis
2022-10-27 21:43 ` Dr. Arne Babenhauserheide
2022-10-27 15:35 ` Max Nikulin [this message]
2022-10-27 17:58 ` bug#58774: " Jean Louis
2022-10-27 21:49 ` Dr. Arne Babenhauserheide
2022-10-27 18:25 ` Jean Louis
2022-10-27 19:53 ` Quiliro Ordóñez
2022-10-27 19:58 ` Quiliro Ordóñez
2022-10-27 21:57 ` Dr. Arne Babenhauserheide
2022-10-27 22:18 ` Jean Louis
2022-10-27 23:14 ` Dr. Arne Babenhauserheide
2022-10-27 23:20 ` Ihor Radchenko
2022-10-28 8:28 ` Dr. Arne Babenhauserheide
2022-11-02 4:09 ` 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=d8bead8c-f97d-1de5-ae06-df81fefb7389@gmail.com \
--to=manikulin@gmail.com \
--cc=58774@debbugs.gnu.org \
--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).